From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 30062] New: Huge amounts of "HDIO_GET_IDENTITY failed for /dev/sr0" messages during boot
Date: Mon, 28 Feb 2011 10:52:28 GMT [thread overview]
Message-ID: <bug-30062-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=30062
Summary: Huge amounts of "HDIO_GET_IDENTITY failed for
/dev/sr0" messages during boot
Product: IO/Storage
Version: 2.5
Kernel Version: 2.6.38-rc6
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: SCSI
AssignedTo: linux-scsi@vger.kernel.org
ReportedBy: monoped@sudrala.de
Regression: Yes
My system (Crux 2.7) contains an older SCSI disk, and a SCSI CD writer
(Plextor). When booting into 2.6.38, I get an endless sequence of errors like
ata_id[xyz]: HDIO_GET_IDENTITY failed for '/dev/sr0'
The errors start when the command
udevadm trigger --type=devices --action=add
is executed. There are also about 50 udevd processes in the process list. The
system gets extremely slow, and the only way to make it usable again is by
saying 'killall udevd'. Apparently udev has an issue with the CD writer (while
it handles the harddisk correctly).
The same system works well with kernel 2.6.37.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-28 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 10:52 bugzilla-daemon [this message]
2011-03-02 0:19 ` [Bug 30062] Huge amounts of "HDIO_GET_IDENTITY failed for /dev/sr0" messages during boot bugzilla-daemon
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=bug-30062-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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).