Red Hat Bugzilla – Bug 142082
Will not boot with ANY usb plugged in, System hangs if you plug in usb after system is booted.
Last modified: 2015-01-04 17:13:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
Have FC3 2.6.9-1.681_FC3 installed and working without any usb devices.
If I plug in ANY usb device the computer hangs. both the mouse and
keyboard stop responding.
If I reboot and leave the usb device plugged in the system hangs when
it tries to initialize the hardware.
If I remove the usb device before I reboot all works as expected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.plug memory stick in usb
Actual Results: lose mouse and keyboard.
They nolonger respond.
Expected Results: should recognise the device
are you sure this has s.th. to do with udev?
I have read all the other simular problems on the web, and every thing
seems to point to udev. udev nows controls hotswaping usb devices.
I would be glad to work through the problems and debug it. All of the
things that I normally do to chase a problem have not worked. It just
hangs. It seems to me that this could be something like a bad rule in
udev. I have never wored with udev before, don't really know were to
udev does not control the usb devices, it only makes device nodes in
/dev. The problem you have sounds like a kernel problem.
I suspect this is the same as bug 139187, as I saw the same behavior. Problem
is kernel hang on removal of usb-storage module. Appears to be fixed in
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.