From: Martin Lottermoser <Martin.Lottermoser@t-online.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: PATA DMA problem leading to kernel panic on reading movie DVDs
Date: Mon, 18 May 2009 21:12:07 +0200 [thread overview]
Message-ID: <20090518191207.GA7531@wanza.invalid> (raw)
In-Reply-To: <200905172135.10136.bzolnier@gmail.com>
Hi,
On Sun, May 17, 2009 at 09:35:09PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Martin, this is one of ATAPI drives which support UDMA66 but have broken
> cable detection. Since 2.6.26 we have a special quirk for it ide (commit
> 3ced5c49bd2d1f2c7f769e3a54385883de63a652) and subsequent one in libata
> (commit e9f3340673c1da32041f2a282b166c72cd78632e).
>
> In your system's case the cable detection doesn't seem to work properly
> which in turn results in all kind of later problems.
>
> It could be that the quirk itself needs to be revised (I wonder if it was
> originally tested with 40-wires cable) or maybe we need some other cable
> detection fix...
>
> Please:
>
> * send 'hdparm --Istdout /dev/hdc' output
>
> * try 2.6.30-rc6 (maybe 2.6.29.3 oops has been fixed already and we just
> need to backport it)
>
> also connecting the drive using 80-wires cable and getting another hdparm
> output (+ seeing if it helps the other problems) would be very useful.
I've done that now as well. Test runs with Debian's 2.6.26 and with 2.6.30-rc6
show no problems: no disabling of DMA, no kernel panic.
The hdparm output ("hdparm --Istdout") is the same for a 40-wire cable and an
80-wire cable (checked under 2.6.26).
This indicates that your hypothesis above that it's a cable detection problem
is correct.
Just out of curiosity: is this a bug on the drive's side or in the kernel?
Or in other words: if the output of "hdparm -I" shows the drive as attached
to be able to support UDMA4, is this a statement passed through unmodified
from the drive or is this a deduction made by the kernel? I ask because
under 2.6.22.9 and 2.6.23.14 I got a message that "host side 80-wire cable
detection failed".
Should anyone find a fix to correct/circumvent this problem in the kernel,
I'ld be willing to test it on my system; just send a patch file or tell me
where to pick it up.
Regards,
Martin Lottermoser
--
Martin Lottermoser Martin.Lottermoser at _REMOVE_t-online.de
Greifswaldstrasse 28
38124 Braunschweig http://home.vrweb.de/martin.lottermoser
Germany
next prev parent reply other threads:[~2009-05-18 19:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 9:12 PATA DMA problem leading to kernel panic on reading movie DVDs Martin Lottermoser
2009-05-17 10:42 ` Borislav Petkov
2009-05-17 11:15 ` Martin Lottermoser
2009-05-17 12:14 ` Martin Lottermoser
2009-05-17 19:34 ` Borislav Petkov
2009-05-17 19:45 ` Bartlomiej Zolnierkiewicz
2009-05-17 19:50 ` Borislav Petkov
2009-05-17 20:18 ` Bartlomiej Zolnierkiewicz
2009-05-17 20:30 ` Borislav Petkov
2009-05-17 22:48 ` Bartlomiej Zolnierkiewicz
2009-05-18 6:32 ` Borislav Petkov
2009-05-17 17:59 ` Robert Hancock
2009-05-17 19:35 ` Bartlomiej Zolnierkiewicz
2009-05-17 20:18 ` Martin Lottermoser
2009-05-18 16:40 ` Martin Lottermoser
2009-05-18 19:12 ` Martin Lottermoser [this message]
2009-05-19 15:19 ` Bartlomiej Zolnierkiewicz
2009-05-19 18:29 ` Martin Lottermoser
2009-05-19 19:30 ` Bartlomiej Zolnierkiewicz
2009-05-19 21:11 ` Bartlomiej Zolnierkiewicz
2009-05-19 21:12 ` Martin Lottermoser
2009-05-19 21:31 ` Bartlomiej Zolnierkiewicz
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=20090518191207.GA7531@wanza.invalid \
--to=martin.lottermoser@t-online.de \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).