Red Hat Bugzilla – Bug 444104
126.96.36.199-64.fc8 USB hang after attaching USB card reader/hub
Last modified: 2009-01-09 01:25:39 EST
Description of problem:
When connecting the 8-in-1 USB card reader and USB Hub contained in a Dell
2405FPW monitor to my system running 188.8.131.52-64.fc8 x86_64, I lose my USB mouse
and lsusb hangs in an uninterruptable sleep. If this card reader/hub is
connected when booting this kernel, the boot hangs after displaying the "loading
RedHat nash..." line.
This is a freshly installed new machine. The problem does not occur with the
original kernel on the Fedora 8 install CD. This machine is fully patched with
all updates. This machine is running a gigabyte MA-790X-DS4 motherboard with
the most current (F4) BIOS installed.
This USB device had been connected to a machine running 32bit Fedora 8 and had
Version-Release number of selected component (if applicable):
This happens every time the USB device is connected while running this kernel
Steps to Reproduce:
1. Boot system with 184.108.40.206-64.fc8 x86_64 kernel
2. Connect USB card reader/hub contained in Dell 2405FPW monitor
3. watch USB mouse disappear and not return even after removing card reader/HUB
and reconnecting mouse. Note that USB keyboard remains working.
4. Run /sbin/lsusb and watch it hang in an uninterruptable sleep.
- Essentially any connected USB devices, other than keyboard, disappear.
- lsusb hangs
- Have all usb devices working and card reader and hub available for use
- lsusb to not hang
Can you get a snapshot of the system state when lsusb freezes?
1. Boot with these additional kernel options:
2. attach the device and run lsusb
3. in another window, type:
echo 't' >/proc/sysrq-trigger
4. upload what that command dumps to the system log
Created attachment 303849 [details]
syslog messages as requested
Created attachment 303850 [details]
smolt output for this system
I've attached the smolt data for this system in case there are any details in
it which may be of use.
khubd D ffffffff81280d60 0 152 2
ffff81012f09dcc0 0000000000000046 0000000000000000 ffffffff8126829c
0000000000000000 ffff81012f0988b0 ffff81012fa69160 ffff81012f098b90
ffffffffffffffff ffffffff8800623b 0000000000000000 0000000000000000
Problem still present with 220.127.116.11-85.fc8 kernel (x86_64).
Noticed lock up when attempting to use scanner (Seiko Epson Corp. Perfection
2400 Photo). Also noticed lockup when plugging in a USB thumb drive.
All devices, mouse, scanner and thumb drive, where plugged in via Belkin 7 port
USB hub (f5u237). I have removed this hub from the system and connect mouse
directly to motherboard USB port. Connecting monitor (hub and card reader) now
works fine and running the scanner through the hub in the monitor works fine.
Plugging in a usb stick to either a motherboard usb port or the monitor usb hub
causes a lock up.
This hub had been working on a Fedora 8 (32bit) machine perfectly fine and was
simply moved to a new machine (64bit).
Put the Belkin hub back on the system and it works fine. The Dell hub/card
reader, though, still locks up things when it's connected.
Is anyone even looking into this? I'll provided whatever info/testing is needed
to try and resolve the problem.
18.104.22.168-92.fc8 still exhibits the problem.
I've done some more testing and narrowed things down a little bit more, at least
with respect to what devices cause the lock up.
I have two machines that have the problem. Both are the same as reported
previously in the bug (gigabyte MA-790X-DS4 motherboards). The lockups occur on
both machines in the same manner, all but eliminating failed hardware.
Anytime a USB hub or device containing a USB hub is plugged in and you attempt
to do move any significant amount of data over USB (anything other than keyboard
and mouse), the lock up occurs. I've had the lock up occur in the following cases:
- attach a usb memory stick through a usb hub. Note that the mouse is normally
connected to the hub and everything works fine when ONLY the mouse is using the hub.
- With a hub attached and attempting to use a scanner (Epson perfections 2400
photo). Occurs when scanner is attached to either a hub or to a port on the
- With an HP Deskjet D4260 (contains a hub) with or without another hub
attached to the machine. Occurs when attempting to send a print job.
My guesses at this point are that the problem is either:
- Something bad in the Gigabyte BIOS. If this where true, I'd expect many
reports of problems from Windows users. I've not found any.
- There is something about the Fedora 8 kernels that don't like this board or
BIOS. I've not tried a 32bit install to see if this is limited to 64bit installs.
It'd be nice if someone could at least identify the general direction of the
I changed this to urgent since (a) I haven't had any feedback on this issue
after the initial request for info, and (b) I have two machines that have
limited usability. (reliable usb is pretty critical for desktops/workstations
Wow, 3 months and no help at all on my bug. Not even someone to say "sorry,
your mother board/BIOS is the problem". Granted that posted this right about
the time that Fedora 9 came out, but after a couple of months, I'd hope that
someone would at least post some status on this.
Chris, it looked like you were well on track. If it really were a hang
during unlinks in ehci_hcd, I could look into it closer.
I would greatly appreciate that since I've had to stop considering Fedora a
viable workstation OS on my machines because of this bug. I have two machines
of identical hardware config that I can test with to try and get this bug fixed.
(In reply to comment #7)
> Anytime a USB hub or device containing a USB hub is plugged in and you attempt
> to do move any significant amount of data over USB (anything other than keyboard
> and mouse), the lock up occurs. I've had the lock up occur in the following
> - attach a usb memory stick through a usb hub. Note that the mouse is normally
> connected to the hub and everything works fine when ONLY the mouse is using
> - With a hub attached and attempting to use a scanner (Epson perfections 2400
> photo). Occurs when scanner is attached to either a hub or to a port on the
> - With an HP Deskjet D4260 (contains a hub) with or without another hub
> attached to the machine. Occurs when attempting to send a print job.
Works perfectly for me with a Dell USB hub built into a Dell display.
I can copy 25 gigabytes of data to a USB hard drive with no problem.
OTOH connecting the same drive to the front connectors on the same machine (Dell
490 workstation) causes all kinds of problems. Data transfers very slowly and
the whole system slows down until the data is copied.
I don't believe that the problem is the Dell monitor/HUB. I've used this
monitor/HUB on other machines. I believe the problem is associated with the
Gigabyte MA-790X-DS4 motherboard/chipsets and the kernel. Across two different
identical machines (with this mobo) and various different USB devices and hubs,
the same problem exists. If a hub of any sort (stand alone, in the Dell
monitor, in the HP Printer) is attached and you try to do anything over USB
(file xfer to USB drive/stick, printing, scanning, etc) USB locks up completely.
The only USB device accessable/working is the keyboard; lsusb hangs in
uninterruptable sleep; any other processes trying to touch anything USB end up
in uninterruptable sleep.
At this point (3 months after initial bug report), I just don't consider Fedora
a viable workstation and have stopped using it. I still have the machines with
Fedora on them and am happy to do whatever testing/troubleshooting I can to help
resolve this. At some point, though, I will re-image the machines (probably to
CentOS) and re-dploy them for other uses.
Great, may I close the bug then?
Close it if you want, though the problem still exists.
Just to summarize the problem:
- This motherboard (http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2695)
- plus Fedora 8 kernels
- plus USB Hubs
- results in USB lockups as described earlier in the thread and supported with the syslog messages and dumps as requested.
I have two different machines that exhibit the same exact problem. I've used all of the USB peripherals in other machines with Fedora 8 and had no problems.
Something about this specific board/BIOS and the newer kernels doesn't seem to get along.
I've been using Linux exclusively on my desktop (and most of my servers) for over 10 years now -- started with Redhat 4.2 and continued on. I've tried to push Linux on the desktop with friends, coworkers and as general advocacy. This bug and the lack of support for it has been my last straw with desktop Linux. I've bought a couple of Macs to replace my Linux desktops and am extremely happy with things just working. I love the ideals and values of Free Software, but when the software simply won't work and I can't get anyone help to fix it, the value of it quickly goes to zero. I'm not a big fan of paying for a closed source system, but I do have to say it's nice to have a system that "just works" and access to a lot of very nice desktop applications -- Aperture, iLife, Final Cut Express, etc.
I wish I could be of more help in getting this problem fixed, but I'm not a kernel developer, so it's a bit outside of my expertise. I had been more than happy to do whatever testing was needed or anything else possible to help solve the problem. Regretfully I must say "so long, and thanks for all the fish."
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.