Date: Wed, 12 May 2004 16:45:18 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-current@freebsd.org Subject: Re: ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=21267353 Message-ID: <40A2387E.1050208@DeepCore.dk> In-Reply-To: <Pine.BSF.4.53.0405121431040.66978@e0-0.zab2.int.zabbadoz.net> References: <20040512145212.62e7db1e@it.buh.cameradicommercio.ro> <40A21BF1.4080502@DeepCore.dk> <Pine.BSF.4.53.0405121431040.66978@e0-0.zab2.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bjoern A. Zeeb wrote:
>>>Could someone tell me what this means (-CURRENT)?
>>
>>The WRITE operation was signalled done by the disk by issueing an
>>interrupt and the finished request was put on a taskqueue to have it
>>return status to the system. However the timeout code fired because the
>>taskqueue hadn't been executed yet (it will wait one ome timeout period
>>before the result is forced through)..
>>
>>So there is no harm done, but the taskqueue was slow to respond...
>
>
> as postend to freebsd-amd64 I am getting far too many of those and
> they won't stop.
>
> From time to time there is also
> ad10: WARNING - WRITE_DMA interrupt was seen but taskqueue stalled LBA=...
> between all the ${subject} lines.
Hmm, something is keeping the taskqueue busy, and its not ATA...
--
-Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40A2387E.1050208>