Date: Sat, 13 Nov 2004 10:50:59 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: Zoltan Frombach <tssajo@hotmail.com> Cc: Garance A Drosihn <drosih@rpi.edu> Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout Message-ID: <4195D903.2090801@DeepCore.dk> In-Reply-To: <BAY2-DAV4h0Lc5T9Cfm00015c59@hotmail.com> References: <BAY2-DAV8jQHtMFauky0000f07f@hotmail.com> <p06020404bdb94f75aa0b@[128.113.24.47]> <BAY2-DAV4h0Lc5T9Cfm00015c59@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Zoltan Frombach wrote: > This is still an issue for me. Please read this post of mine: > http://lists.freebsd.org/pipermail/freebsd-stable/2004-November/009420.= html >=20 > Can anyone help? I would gladely install test patches to track this=20 > problem down. My system is 5.3-R. And the WRITE_DMA warning happens at = > least twice a day, it is so predictable. With thanks, Hmmm, that warning is issued from ATA when requests has been returned to = the systems bio_taskqueue but the system hasn't finished them within the = timeout. Now this is an indication of the system being unresponsive=20 already at that point, or at least that was the idea. It has nothing to do with a bad drive, since the interrupt was seen the=20 drive has finished the request it was asked, its the layers above ATA=20 that doesn't respond to the request beeing returned as finished. -S=F8ren >=20 > Zoltan >=20 > Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what=20 > does it mean? >=20 >=20 >> At 7:58 PM -0800 11/9/04, Zoltan Frombach wrote: >> >>> Well, since I posted my original message, I investigated >>> this a bit further. And according to this post=20 >>> http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027235.ht= ml >>> this is not necessarily an indication of a failing hard >>> drive... (Quote: "there is no harm done, but the taskqueue >>> was slow to respond...") And I can also tell you that this >>> very same hard drive *never* produced this error message in >>> the past 6 months while running FreeBSD 5.2-CURRENT (from >>> May 9, 2004). >> >> >> Fwiw, I am also seeing this warning/error message on a brand new >> machine with a brand new SATA hard disk in it. I have seen the >> message on multiple installs into different partitions on the same >> hard drive. I turned off some sysctl (hw.ata.ata_dma, *I think*) >> to see if that would avoid the problem, but it did not seem to. >> >> I usually do not notice any problem at the same time as the message, >> but I have seen a few buildworlds which just happened to abort at >> the same second this warning message appeared in /var/log/message. >> So, I am not sure the message is benign in all circumstances. >> >> I'm a bit busy with a variety of other issues right now, but I >> should have some time this coming weekend to run any tests or >> patches that might help to pin this down. >> >> --=20 >> Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu >> Senior Systems Programmer or gad@freebsd.org >> Rensselaer Polytechnic Institute or drosih@rpi.edu=20 >=20 >=20 > .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4195D903.2090801>