linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 19 May 2009 20:29:28 +0200	[thread overview]
Message-ID: <20090519182928.GA8172@wanza.invalid> (raw)
In-Reply-To: <200905191719.35543.bzolnier@gmail.com>

Hello,

On Tue, May 19, 2009 at 05:19:35PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Subject: [PATCH] ide: fix 40-wire cable detection for TSST SH-S202* ATAPI devices

I'm sorry, but that also generated a panic, looking identical to the
behaviour as for the unpatched 2.6.30-rc6.

After booting the patched kernel, the syslog file showed:

  hdc: UDMA/66 mode selected

"hdparm -I" reported that the drive was set to "udma4". On accessing the DVD,
the kernel panicked. Here's the main output from netconsole:

  hdc: cdrom_decode_status: error=0x40 <3>{ LastFailedSense=0x04 }
  ide: failed opcode was: unknown
  hdc: DMA disabled
  ------------[ cut here ]------------
  kernel BUG at drivers/ide/ide-io.c:872!
  invalid opcode: 0000 [#1]
  last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/ide1/1.0/block/hdc/size

After booting the kernel and before doing the test I had checked with
"uname -a" that this really was the newly compiled kernel. After reboot I
checked that ide-iops.o existed and had a modification time later than the
moment I applied your patch. Also, the new vmlinuz is 64 bytes shorter than
the unpatched one. Therefore I don't think I made some silly mistake which
led to the patch being ignored.

The offer for testing patches remains open :-).

Regards,
Martin Lottermoser
--
Martin Lottermoser             Martin.Lottermoser at _REMOVE_t-online.de
Greifswaldstrasse 28
38124 Braunschweig             http://home.vrweb.de/martin.lottermoser
Germany

  reply	other threads:[~2009-05-19 18:30 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
2009-05-19 15:19       ` Bartlomiej Zolnierkiewicz
2009-05-19 18:29         ` Martin Lottermoser [this message]
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=20090519182928.GA8172@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).