From: Soeren Sonnenburg <kernel@nn7.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21pre6 (__ide_dma_test_irq) called while not waiting
Date: 11 Apr 2003 22:23:47 +0200 [thread overview]
Message-ID: <1050092626.2333.109.camel@fortknox> (raw)
In-Reply-To: <1049885242.9897.7.camel@dhcp22.swansea.linux.org.uk>
On Wed, 2003-04-09 at 12:47, Alan Cox wrote:
> On Mer, 2003-04-09 at 10:18, Soeren Sonnenburg wrote:
> > hdi: 4 bytes in FIFO
> > hdi: timeout waiting for DMA
> > hdi: (__ide_dma_test_irq) called while not waiting
> > hdi: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
> >
> > hdk: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
>
> This looks like a shared IRQ occurred while a command was being
> sent. The IDE layer apparently tested for the IRQ before it
> was ready to do so as part of finding out what is going on. The
> -ac tree (and pre7) may possibly have fixed it with the command
> delay stuff that Ross Biro figured out
Ok, I copied 2*25GB over the network trying all sorts of things to make
the compu crash. I was not successful :-)
However a hdparm -S0 -d1 -Xudma5 -c 1 -u 1 -m 16 /dev/hde was enough to
get that message again which I could not simple reproduce by just
copying things over the network. So it seems the actual bug was fixed in
pre7 but hdparm tweaking seems to need another fix to be safe...
Thanks,
Soeren.
next prev parent reply other threads:[~2003-04-11 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 9:18 Soeren Sonnenburg
2003-04-09 9:29 ` Andre Hedrick
2003-04-09 10:44 ` Alan Cox
2003-04-09 10:47 ` Alan Cox
2003-04-09 12:11 ` Soeren Sonnenburg
2003-04-11 20:23 ` Soeren Sonnenburg [this message]
2003-04-09 12:13 Chuck Ebbert
2003-04-09 12:15 ` Alan Cox
2003-04-09 14:35 Chuck Ebbert
2003-04-09 14:05 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1050092626.2333.109.camel@fortknox \
--to=kernel@nn7.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®