From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: IDE CD problems in 2.6.13rc6
Date: Sun, 14 Aug 2005 14:46:41 +0100 [thread overview]
Message-ID: <1124027202.14138.46.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e05081404354fe6a097@mail.gmail.com>
On Sul, 2005-08-14 at 13:35 +0200, Bartlomiej Zolnierkiewicz wrote:
> > The symptoms vary. On some of my machines just inserting
> > an audio CD makes the box instantly lock up.
You've got all the gnome cruft running. Start by turning that off. Then
try inserting/removing audio discs, playing them with "cdplay". I'd
expect that to be ok
Next try ripping an audio cd without all the gnome crud loaded. If that
works (it may or may not) then its practical to try and pin down the bug
and see if its error handling (the locking patterns all changed in the
base kernel recently hence all those new PIIX error reports) or
something else.
> I checked 2.6.13-rc6 patch and I see no IDE / CD changes which
> could be responsible for this regression. You can try reverting ide-cd
> changes and see if this helps. IRQ routing changes?
Then you'd expect to see "drive confused" methods. It could be IRQ
related - missing IRQ might do it although I'd expect that to cause
crashes during probe if we got extra IRQs (because the code to handle it
was removed from the base kernel even though it is required).
Another thing that will do this is if you bomb the drive with commands
from somewhere (say GNOME) or crash the firmware, which is why you need
to isolate all the gnome gunge for testing, and if that makes the
difference see if its a kernel or higher level change and if so what its
doing that causes problems.
Alan
next prev parent reply other threads:[~2005-08-14 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 23:29 IDE CD problems in 2.6.13rc6 Dave Jones
2005-08-14 0:26 ` Con Kolivas
2005-08-14 0:30 ` Con Kolivas
2005-08-14 13:53 ` Alan Cox
2005-08-14 11:35 ` Bartlomiej Zolnierkiewicz
2005-08-14 13:46 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-14 17:43 Voluspa
2005-08-14 19:30 Voluspa
2005-08-14 19:55 Nick Warne
2005-08-14 20:10 Nick Warne
2005-08-14 22:51 Voluspa
2005-08-15 0:37 ` Alan Cox
2005-08-15 0:53 ` Voluspa
2005-08-15 18:30 Nick Warne
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=1124027202.14138.46.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=davej@redhat.com \
--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