Red Hat Bugzilla – Bug 147663
lsusb hangs when using an Intelligent Stick
Last modified: 2015-01-04 17:16:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020
Description of problem:
lsusb and many usb/mass storage related utilities choke and hangs when
trying to use an Intelligent Stick (I-Stick) USB Drive.
For example, I connnect the drive, nothing happends, go to console to
see if is at least detected, run lsusb, list only one of my usb
attached devices, and then hang forever.
There is no way to kill or terminate the process, unless I reboot.
I already loaded all relevant usb, such as usb-storage and uhci and
others, also sd_mod, sg, all already inserted and retried the
operation with lsusb with each one being loaded to test if it makes a
difference, but still same results.
Is probably a problem on the usb subsystem on the kernel, as even proc
output hangs (cat /proc/bus/usb/devices or cat /proc/scsi/scsi),
altough cat /proc/scsi/usb-storage/0 gives the following output:
Host scsi0: usb-storage
Product: Flash Disk
Serial Number: 106C1141D0AC7409
Protocol: Transparent SCSI
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Insert Intellient Stick to usb
Actual Results: lsusb hanged forever
Expected Results: lsusb whould list the memory stick device, or at
least not hang.
This is a kernel usb problem.
Assinging to kernel.
is this still occuring with the 766 kernel update ?
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.