mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dennis Grant" <trog@wincom.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	trog@wincom.net,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ATAPI DMA timeouts showing up in logs
Date: Mon, 02 Dec 2002 10:18:11 -0500	[thread overview]
Message-ID: <3deb797f.41fc.0@wincom.net> (raw)

>On Thu, 1970-01-01 at 05:59, Dennis Grant wrote:

>> Now that I've got the proper IDE driver in place (2.4.20rc4)
>> and the master drive on the primary interface is running at
>> a full ATA133, these have started showing up in the logs - 
>> 2 or 3 a day:

> My guess is its the IDE command/DMA sequence bug that Khalid
> fixed in -ac. Some drives also take a very long time on 
> retrying blocks and that might cause a timeout/reset too.

OK.

Interestingly enough, the drive wasn't being used at all during the timeframe
when the messages show up - at least, not explictly. Perhaps some random process
was polling the drive....

Alan, I tried 2.4.20rc4-ac1 but while the patch took, it wouldn't compile. I'll
try again later and fwd where the error was. (I don't have access to that machine
at the moment)

>> This last one is the only indication that something might be >> amiss - the
two instances of "invalid argument" Other than
>> that, the drive appears to work just fine.

>Those are ones CD-ROM's dont support

Ah, OK. Perhaps hdparm shouldn't try them then. :)

Thanks.

DG

             reply	other threads:[~2002-12-02 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 15:18 Dennis Grant [this message]
2002-12-02 17:37 ` IDE documentation bitrot, (Was: ATAPI DMA timeouts showing up in logs) John Bradford
2002-12-02 17:36   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-12-02 13:36 ATAPI DMA timeouts showing up in logs Dennis Grant
2002-12-02 15:42 ` 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=3deb797f.41fc.0@wincom.net \
    --to=trog@wincom.net \
    --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

Powered by JetHome