From: ljb <ljb1813@pobox.com>
To: linux-hotplug@vger.kernel.org
Subject: cdrom_id from udev-135 hangs
Date: Tue, 24 Feb 2009 02:02:57 +0000 [thread overview]
Message-ID: <gnvkgg$m04$1@ger.gmane.org> (raw)
I am trying to upgrade an old PC from Slackware 12.1 (udev-118,
Linux-2.6.24.5) to Slackware 12.2 (udev-135, Linux-2.6.27.7). The system
hangs up during boot running cdrom_id. If I disable 60-cdrom_id.rules, or
replace cdrom_id with the one from udev-118, it works.
Running cdrom_id from udev-135 (138 too) logs lots of messages like those
shown below, and never completes. The drive is an IDE Sony CD-RW CRX175E2,
connected to an Intel SE440BX2 motherboard, and the drive works fine other
than this issue. How do I troubleshoot this?
kernel: hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
kernel: hdc: status error: error=0x20 { LastFailedSense=0x02 }
kernel: ide: failed opcode was: unknown
kernel: hdc: drive not ready for command
...
next reply other threads:[~2009-02-24 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 2:02 ljb [this message]
2009-02-24 2:14 ` cdrom_id from udev-135 hangs Kay Sievers
2009-02-25 3:24 ` ljb
2009-02-25 4:11 ` Bryan Kadzban
2009-02-26 2:57 ` ljb
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='gnvkgg$m04$1@ger.gmane.org' \
--to=ljb1813@pobox.com \
--cc=linux-hotplug@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).