5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what does it mean?

[Zoltan Frombach]

So I should not apply that patch then? Right? Then what should I do to try 
to help the developers tracking down this problem? Any ideas, anyone? I get 
this warning without any heavy load or traffic yesterday twice. I'm sure it 
will happen again. Fortunately, in my case, it doesn't cause any program to 
malfunction or anything bad. In my case it really seems to be just a warning 
message. Not like for Frode Nordahl. I'd like to help testing, if anyone 
wants to send me a new patch, send it and I'll test it.

Zoltan

----- Original Message ----- 
From: "Søren Schmidt" <sos at DeepCore.dk>
To: "Robert Watson" <rwatson at freebsd.org>
Cc: "Zoltan Frombach" <tssajo at hotmail.com>; <freebsd-current at freebsd.org>
Sent: Wednesday, November 10, 2004 5:51 AM
Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what does 
it mean?


Robert Watson wrote:
> On Wed, 10 Nov 2004, Søren Schmidt wrote:
>
>
>>>I'm still a bit skeptical that the task queue is at fault -- I run my
>>>notebook with continuous measurement of the latency to schedule tasks,
>>>generating a warning for any latency > .5 seconds, and the only time I
>>>ever see that sort of latency is during the boot process when ACPI has
>>>scheduled a task to run, but the task queue thread has not yet been
>>>allowed to run:
>>
>>Right, the timeout is 5 secs. I havn't looked into how the taskqueues
>>are handled recently, but in case of ATA read/writes it is the
>>bio_taskqueue handled by geom thats in use not the catchall ones, does
>>your timing cover that as well?
>
>
> Nope -- I had assumed that the suggested task problems in question was the
> use of taskqueue_enqueue() in ata-queue for the timeout, rather than the
> bio_taskqueue() ata_completed() call.

OK, then there is no idea in trying the patch, it wont tell us anything.

-- 

-Søren