Date: Sat, 13 Nov 2004 10:53:19 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout Message-ID: <25539.1100339599@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 13 Nov 2004 10:50:59 %2B0100." <4195D903.2090801@DeepCore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <4195D903.2090801@DeepCore.dk>, =?ISO-8859-1?Q?S=F8ren_Schmidt?= wri tes: >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 >> >> Can anyone help? I would gladely install test patches to track this >> 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 >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 >drive has finished the request it was asked, its the layers above ATA >that doesn't respond to the request beeing returned as finished. It is not really the task of the ata driver to fail requests at that time. How long is the timeout anyway ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25539.1100339599>