From: Stefan Behrens <sb2004@freenet.de>
To: linux-hotplug@vger.kernel.org
Subject: FC3 system hangs after inserting USB stick
Date: Sun, 05 Dec 2004 17:39:13 +0000 [thread overview]
Message-ID: <41B347C1.2000306@freenet.de> (raw)
Hi there,
I have repeated problems with a hanging FC 3 system after inserting
a USB 2.0 memory stick. Sometimes I just cannot mount the FS, sometimes
the whole machine hangs when trying to mount. In such case, none of the
Ctrl-Alt keystrokes works. I had to press the reset button on my box.
I'm running FC 3 with stock kernel 2.6.9 and udev upgraded to
udev-039-10.FC3.1.i386.rpm.
However, this does not seem to be a 2.6 problem, I had similar effects
with the same stick on a notebook running 2.4.27 (upgraded FC1).
In one case even the power button didn't work and I had to remove the
battery ....
I tried formatting the stick using WinXP and also tried mkdosfs but with
no effect.
Here is a trace, inserting the stick (fails), removing it, inserting it
again (worked the 2nd time). Note I did not mount the device at all to
produce any of the errors and printouts.
----
Dec 5 18:10:49 localhost kernel: usb 1-6: new high speed USB device using address 2
Dec 5 18:10:49 localhost kernel: SCSI subsystem initialized
Dec 5 18:10:49 localhost kernel: Initializing USB Mass Storage driver...
Dec 5 18:10:49 localhost kernel: scsi0 : SCSI emulation for USB Mass Storage devices
Dec 5 18:10:49 localhost kernel: Vendor: Model: Rev: 2.00
Dec 5 18:10:49 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02
Dec 5 18:10:49 localhost kernel: usbcore: registered new driver usb-storage
Dec 5 18:10:50 localhost kernel: USB Mass Storage support registered.
Dec 5 18:10:50 localhost scsi.agent[3082]: disk at /devices/pci0000:00/0000:00:10.3/usb1/1-6/1-6:1.0
/host0/0:0:0:0
Dec 5 18:10:50 localhost kernel: sda: Unit Not Ready, sense:
Dec 5 18:10:50 localhost kernel: Current : sense key Unit Attention
Dec 5 18:10:50 localhost kernel: Additional sense: Not ready to ready change, medium may have change
d
Dec 5 18:10:50 localhost kernel: sda : READ CAPACITY failed.
Dec 5 18:10:50 localhost kernel: sda : status=1, message\0, host=0, driver\b
Dec 5 18:10:50 localhost kernel: Current sd: sense key Unit Attention
Dec 5 18:10:50 localhost kernel: Additional sense: Not ready to ready change, medium may have change
d
Dec 5 18:10:50 localhost kernel: sda: Write Protect is off
Dec 5 18:10:50 localhost kernel: sda: assuming drive cache: write through
Dec 5 18:12:04 localhost kernel: sda:<6>scsi: Device offlined - not ready after error recovery: hos
t 0 channel 0 id 0 lun 0
Dec 5 18:12:05 localhost kernel: SCSI error : <0 0 0 0> return code = 0x50000
Dec 5 18:12:05 localhost kernel: end_request: I/O error, dev sda, sector 2097144
Dec 5 18:12:05 localhost kernel: Buffer I/O error on device sda, logical block 262143
Dec 5 18:12:05 localhost kernel: scsi0 (0:0): rejecting I/O to offline device
Dec 5 18:12:05 localhost kernel: Buffer I/O error on device sda, logical block 262143
Dec 5 18:12:05 localhost kernel: sda1
Dec 5 18:12:05 localhost kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Dec 5 18:12:05 localhost kernel: usb 1-6: USB disconnect, address 2
Dec 5 18:12:10 localhost wait_for_sysfs[3139]: either wait_for_sysfs (udev 039) needs an update to handle the device '/block/sda/sda1' properly (no bus device link) or the
sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
Dec 5 18:12:11 localhost kernel: usb 1-6: new high speed USB device using address 3
Dec 5 18:12:11 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Dec 5 18:12:11 localhost kernel: Vendor: Model: Rev: 2.00
Dec 5 18:12:11 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02
Dec 5 18:12:11 localhost kernel: sda: Unit Not Ready, sense:
Dec 5 18:12:11 localhost kernel: Current : sense key Unit Attention
Dec 5 18:12:11 localhost kernel: Additional sense: Not ready to ready change, medium may have changed
Dec 5 18:12:11 localhost kernel: SCSI device sda: 128000 512-byte hdwr sectors (66 MB)
Dec 5 18:12:11 localhost kernel: sda: Write Protect is off
Dec 5 18:12:11 localhost kernel: sda: assuming drive cache: write through
Dec 5 18:12:12 localhost scsi.agent[3255]: disk at /devices/pci0000:00/0000:00:10.3/usb1/1-6/1-6:1.0/host1/1:0:0:0
Dec 5 18:12:11 localhost kernel: sda: sda1
Dec 5 18:12:12 localhost kernel: Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
----
Any idea? This really shouldn't happen.
Thanks&br
/Stefan.
--
PGP public key available:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x1D42A873
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-12-05 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 17:39 Stefan Behrens [this message]
2004-12-05 17:52 ` FC3 system hangs after inserting USB stick Kay Sievers
2004-12-06 7:50 ` Stefan Behrens
2004-12-06 9:40 ` Kay Sievers
2004-12-06 9:48 ` Stefan Behrens
2004-12-06 9:58 ` Kay Sievers
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=41B347C1.2000306@freenet.de \
--to=sb2004@freenet.de \
--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).