<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks Rob. That’s an interesting thread. I’ll look
into that param and google around for similar.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
tclug-list-bounces@mn-linux.org [mailto:tclug-list-bounces@mn-linux.org] <b>On
Behalf Of </b>Robert Nesius<br>
<b>Sent:</b> Friday, May 28, 2010 9:39 AM<br>
<b>To:</b> TCLUG Mailing List<br>
<b>Subject:</b> Re: [tclug-list] ata "failed command: WRITE DMA",
"ATA bus error" messages<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>I don't have a silver-bullet
solution/root-cause for you, but to me this looks like an issue with your newer
kernel and drivers running against your older chipset and drives. It
seems the kernel is not wanting to use Direct Memory Access when talking to ATA
(IDE) drives. <br>
<br>
Here is a link to a thread that has a suggestion for configuring the kernel to
use a legacy mode when interacting with them, if I read it right. And
user Kane indicated specifying an irqpoll parameter also did the trick for
him. <br>
<br>
<a href="http://bbs.archlinux.org/viewtopic.php?pid=332907">http://bbs.archlinux.org/viewtopic.php?pid=332907</a><br>
<br>
-Rob<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Fri, May 28, 2010 at 8:19 AM, Jeff Jensen <<a
href="mailto:jjensen@apache.org">jjensen@apache.org</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>Searching through the last boot log (trying to determine
what is ata2), I<br>
see:<br>
<br>
For the old 40G:<br>
ata2.00: ATAPI: CRD-8400B, 1.04, max UDMA/33<o:p></o:p></p>
<div>
<p class=MsoNormal>ata2.00: configured for PIO4<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>ata2.00: device is on DMA blacklist, disabling DMA<o:p></o:p></p>
</div>
<p class=MsoNormal>ata2.01: 78165360 sectors, multi 16: LBA<br>
ata2.01: ATA-5: WDC WD400BB-00CLB0, 05.04E05, max UDMA/100<o:p></o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>ata2.01: configured for UDMA/33<o:p></o:p></p>
</div>
<p class=MsoNormal>For the new 1TB:<br>
ata6.00: ATA-8: WDC WD1001FALS-00J7B1, 05.00K05, max UDMA/133<br>
ata6.00: configured for UDMA/133<br>
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)<br>
ata6: SATA max UDMA/133 mmio m1048576@0xf4100000 port 0xf4128000 irq 5<br>
<br>
<br>
It looks like ata1 & ata2 are the IDEs and ata3-ata6 are the new SATA card<br>
(?). So perhaps these messages are potential drive failure ones?<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal><br>
<br>
-----Original Message-----<br>
From: Jeff Jensen [mailto:<a href="mailto:jjensen@apache.org">jjensen@apache.org</a>]<br>
Sent: Friday, May 28, 2010 8:02 AM<br>
To: '<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a>'<br>
Subject: ata "failed command: WRITE DMA", "ATA bus error"
messages<br>
<br>
To my old backup server (running BackupPC), I recently added a PCI SATA card<br>
and 1TB drive, and installed Fedora 13 (and removed 2 IDE smaller drives;<br>
the boot drive is still an older IDE 40G; was running Fedora 11).
Messages<br>
log regularly has this set of messages, much more frequent when the backup<br>
is running:<br>
<br>
May 28 06:49:38 nacho kernel: ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0<br>
action 0x6<br>
May 28 06:49:38 nacho kernel: ata2.01: BMDMA stat 0x44<br>
May 28 06:49:38 nacho kernel: ata2.01: failed command: WRITE DMA<br>
May 28 06:49:38 nacho kernel: ata2.01: cmd<br>
ca/00:c0:4f:8c:1a/00:00:00:00:00/f0 tag 0 dma 98304 out<br>
May 28 06:49:38 nacho kernel: res<br>
51/84:00:0e:8d:1a/00:00:00:00:00/f0 Emask 0x10 (ATA bus error)<br>
May 28 06:49:38 nacho kernel: ata2.01: status: { DRDY ERR }<br>
May 28 06:49:38 nacho kernel: ata2.01: error: { ICRC ABRT }<br>
May 28 06:49:38 nacho kernel: ata2: soft resetting link<br>
May 28 06:49:38 nacho kernel: ata2.00: device is on DMA blacklist, disabling<br>
DMA<br>
May 28 06:49:38 nacho kernel: ata2.00: configured for PIO4<br>
May 28 06:49:38 nacho kernel: ata2.01: configured for UDMA/33<br>
May 28 06:49:38 nacho kernel: ata2: EH complete<br>
<br>
I've googled various words from the messages, but what I find are CD drive<br>
related messages and "now it takes longer to boot, so change
modprobe" type<br>
things. I think mine is related to the new drive (just a hint from the
"ATA<br>
bus error" and 'ata' all over the messages ;-), possibly harmless messages<br>
or maybe a SATA card config or compatibility problem(?). I'm surprised
they<br>
keep repeating - if it was just a config error, I would think it would<br>
adjust once (maybe at boot) and then be done.<br>
<br>
Can anyone point me to an RTFM or hints how to research/what is the cause<br>
pretty-please?!<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list"
target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>