From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IDE todo list
Date: 22 Mar 2003 19:07:21 +0000 [thread overview]
Message-ID: <1048360040.9221.23.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030322172453.GB9889@vana.vc.cvut.cz>
On Sat, 2003-03-22 at 17:24, Petr Vandrovec wrote:
> any hope that promise 20265 driver could detect non-udma66 cable
> and run at udma2 only? BIOS properly detect this, but Linux driver
> wants to use udma100, and usually dies hard with CRC errors during
> reading of PTBL extended chain (it also should not lockup when
> CRC error happens 5 times in a row, but ...).
The five CRC in a row is what causes the DMA->PIO changedown. That
implies there is a real bug in the error handling locking, or in
the driver handling of that.
Can you throw some printks into the ide code and see what kind of
a death you get when it tries to change back to PIO.
As to the cable stuff, I'll take a look at it in time, but both
need fixing
next prev parent reply other threads:[~2003-03-22 17:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 17:01 Alan Cox
2003-03-22 17:24 ` Petr Vandrovec
2003-03-22 19:07 ` Alan Cox [this message]
2003-03-22 18:03 ` Nicholas Wourms
2003-03-22 20:36 ` Alan Cox
2003-03-22 20:33 ` Nicholas Wourms
2003-03-22 23:32 ` Alan Cox
2003-03-23 3:49 ` Petr Vandrovec
2003-03-23 15:41 ` Alan Cox
2003-03-23 9:27 ` Matthias Andree
2003-03-23 11:19 ` Jens Axboe
2003-03-23 11:20 ` Jens Axboe
2003-03-23 12:33 ` Matthias Andree
2003-03-23 10:49 ` Jens Axboe
2003-03-23 15:23 ` Alan Cox
2003-03-23 14:13 ` Jens Axboe
2003-03-23 21:07 ` Andre Hedrick
[not found] <20030322160012$0f05@gated-at.bofh.it>
[not found] ` <20030322173016$24a8@gated-at.bofh.it>
[not found] ` <20030322180018$5114@gated-at.bofh.it>
2003-03-23 12:14 ` Allan Duncan
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=1048360040.9221.23.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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®