Bug 165081 - cat /proc/bus/usb/devices hangs
cat /proc/bus/usb/devices hangs
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
4
athlon Linux
medium Severity low
: ---
: ---
Assigned To: Dave Jones
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-04 03:49 EDT by charlie redditt
Modified: 2015-01-04 17:21 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-04 21:24:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
contents of /proc/bus/usb/devices (card reader is usb storage device) (3.79 KB, text/plain)
2005-08-04 03:49 EDT, charlie redditt
no flags Details

  None (edit)
Description charlie redditt 2005-08-04 03:49:48 EDT
Description of problem:
cat /proc/bus/usb/devices hangs if biostar 6 in 1 card reader is plugged into
usb port.  Also, system-config-printer hangs when trying to add a new printer
(thought this was 144536, but seems to be unrelated) and system-config-network
will not start when the card reader is plugged in.

unplug the card reader and everything works again.

Version-Release number of selected component (if applicable):


How reproducible:
easily

Steps to Reproduce:
1. plug in biostar 6-in-1 card reader into any free usb port
2. cat /proc/bus/usb/devices (or try to add a printer via system-config-printer,
or try to start system-config-network)
3.
  
Actual results: cat /proc/bus/usb/devices hangs (system-config-network gets
stuck in uninterruptible state, system-config-printer hangs when trying to add
printer, etc.)

Expected results:
The above should not hang, get stuck in uninterruptible state, etc.

Additional info:
This seems peculiar to this card reader and Fedora. I have two other card
readers (one a lexar, one a combo floppy drive/6-in-1 card reader) and neither
have this problem.  Moreover I have used this card reader with Knoppix 3.6 and
Windoze without this problem.  I have two machines running FC4, one an ECS k7s5a
with a 950MHz Duron and 256MB, and one an KM400MLV with a Barton core Athlon
~1.5 MHZ) and 512MB.  Both have the same problem with the card reader.

This problem is easily avoided by using another card reader, but due to the
scope of effected stuff (multiple system-config scripts) I thought I should make
a public note of this.

If further info is needed, please note that I will unavailable until Aug 15.
Comment 1 charlie redditt 2005-08-04 03:49:48 EDT
Created attachment 117433 [details]
contents of /proc/bus/usb/devices (card reader is usb storage device)
Comment 2 Warren Togami 2005-08-04 05:14:14 EDT
You must provide the exact version of the kernel you are running.
Comment 3 charlie redditt 2005-08-04 10:50:26 EDT
Fedora kernels that I am running:
2.6.12-cor (custom compile)
2.6.12-1.1398_FC4
2.6.11-1.1369_FC4

I experience the problem with all three kernels.
Comment 4 Dave Jones 2005-08-04 13:31:35 EDT
can you attach the output of dmesg after inserting the device please ?
Comment 5 charlie redditt 2005-08-04 16:18:02 EDT
#after attaching the device for the first time in several hours
usb 5-1: new full speed USB device using uhci_hcd and address 4
Initializing USB Mass Storage driver...
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
  Vendor: USB2.0    Model: CardReader CF RW  Rev: 0.0>
  Type:   Direct-Access                      ANSI SCSI revision: 00
Attached scsi removable disk sdb at scsi5, channel 0, id 0, lun 0
  Vendor: USB2.0    Model: CardReader Combo  Rev: 0.0>
  Type:   Direct-Access                      ANSI SCSI revision: 00
Attached scsi removable disk sdc at scsi5, channel 0, id 0, lun 1
usb-storage: device scan complete

# and only AFTER I disconnected the device did the below appear ...
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb 5-1: USB disconnect, address 4

#plugging it back in
usb 5-1: new full speed USB device using uhci_hcd and address 5
#nothing more for a minute or two...

#then after disconnecting it again... 
scsi7 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
usb 5-1: USB disconnect, address 5
Comment 6 Dave Jones 2005-09-30 03:00:06 EDT
Mass update to all FC4 bugs:

An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.

Thanks.
Comment 7 charlie redditt 2005-10-05 12:42:54 EDT
I installed kernel i686 2.6.13-1.1526_FC4 and booted to it without issue.
Unfortunately, the problem remains.  I detected no change in behavior.
Comment 8 Pete Zaitcev 2005-10-05 18:42:49 EDT
I'd like to see an output of alt-sysrq-t.
Please kill all unrelated processes and do it while in text mode at
init level 3 (to get rid of X)
The objective here is to capture the cat which hangs, khubd, and
usb-storage threads.
Please do not drop the dmesg into the comments box, attach instead.
Comment 9 Dave Jones 2005-11-10 15:05:19 EST
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.
Comment 10 Dave Jones 2006-02-03 02:11:35 EST
This is a mass-update to all currently open kernel bugs.

A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

Thank you.
Comment 11 John Thacker 2006-05-04 21:24:43 EDT
Closing per previous comment.

Note You need to log in before you can comment on or make changes to this bug.