All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: trog@wincom.net
Cc: alan@redhat.com, linux-kernel@vger.kernel.org, mlord@pobox.com
Subject: IDE documentation bitrot, (Was: ATAPI DMA timeouts showing up in logs)
Date: Mon, 2 Dec 2002 17:37:44 +0000 (GMT)	[thread overview]
Message-ID: <200212021737.gB2HbiGN000686@darkstar.example.net> (raw)
In-Reply-To: <3deb797f.41fc.0@wincom.net> from "Dennis Grant" at Dec 02, 2002 10:18:11 AM

>>> 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.

>>> 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. :)

There have been quite a few posts to linux-kernel about IDE diagnostic
messages that people are interpreting as fatal errors when they
aren't, and I've noticed that Documentation/ide.txt hasn't been
updated much for a long time - maybe it would be worth bringing it up
to date?

Is the current maintainer Mark Lord or Marcin Dalecki?  In the 2.5.x
tree, it's had obsolete info removed, but it hasn't been brought up to
date.

John.

  reply	other threads:[~2002-12-02 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 15:18 ATAPI DMA timeouts showing up in logs Dennis Grant
2002-12-02 17:37 ` John Bradford [this message]
2002-12-02 17:36   ` IDE documentation bitrot, (Was: ATAPI DMA timeouts showing up in logs) 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=200212021737.gB2HbiGN000686@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlord@pobox.com \
    --cc=trog@wincom.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.