Kernel 3.4 with USB peripherals

[Gareth Jones]

I've filed a bug about this (https://bugzilla.redhat.com/show_bug.cgi?id=829976), but I'm wondering if anyone else is having similar problems, or if my system is just a freak!

Basically, I've got my mouse and keyboard both connected to my computer via a USB2 hub built into my monitor. With linux-3.4.0-1.fc17, every few seconds they are disconnected and immediately reconnected, causing the mouse to freeze until it is clicked, and the keyboard to stop working for a few seconds whilst the input drivers initialize. All previous kernels have worked fine.

Any suggestions, me-toos, or eh?s welcome.

[nonamedotc]

I have a wireless mouse through an USB hub and a wired USB mouse at work. Both work fine.

uname -r
3.4.0-1.fc17.x86_64

P.S. I used to have one of my HDD having the problem similar to what you described. But it was a different story altogether (USB cord problems)

I have no issues with 3.4.2

$ lsusb
Bus 001 Device 003: ID 0ac8:3450 Z-Star Microelectronics Corp. 
Bus 003 Device 002: ID 050d:0912 Belkin Components 
Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 004 Device 003: ID 046d:c31a Logitech, Inc. Comfort Wave 450
Bus 005 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

$ uname -r
3.4.2-1.fc16.x86_64

[george_toolan]

What kind of monitor is this?

Have you tried to connect your keyboard and mouse directly to your motherboard without the hub?

[weitjong]

I have the same kernel version but I have not encountered any problem. I have a 2-Port USB KVM where my keyboard is directly connected to it, however, the KVM mouse port is connected to the monitor's USB hub where my mouse and other USB devices are connected to. That is, when the KVM switches between PC and Mac, all the USB devices are switched over cleanly and on the fly while both PC and Mac are turned on. This setup has worked for me since F15 to F16 to F17 even with this kernel 3.4.0-1. I hope it stays that way!

The only system where I experience something similar to what you described for the mouse is when I boot my PC to Windows 7 for a gaming fix. The only way I can prevent my mouse from constantly connecting/disconnecting is by temporarily plugging in the mouse receiver directly to a USB port provided by the PC's front panel.

For what it's worth, have you tried to connect your monitor's USB hub to another USB port in the PC or change another USB cable to try? Recently I bought a Belkin 7-port USB hub that comes with a faulty USB cable. It took me awhile to bang my head until I found out the cable was the culprit. BTW, the Belkin hub works nicely also so far, it chains up with the monitor's hub. I don't see any regression issue with the new kernel.

[droidhacker]

I suggest plugging directly into the mainboard, at least for TESTING. Could be the hub has some power savings mode that doesn't play well with either Linux or your peripherals.

[Gareth Jones]

Well this just gets weirder. I've really not a clue what's going on.

I moved my desk and PC around, plugged in the mouse and keyboard directly into the computer, and booted 3.4.0-1. Everything worked fine, which wasn't particularly unexpected. So I moved them back to the monitor's ports (possibly not the same way around as they were originally, but there are only 2 ports on the back and 2 on the side). They carried on working. I rebooted. Still working. I've given the power a full cycle and it's still fine. I didn't even touch the USB cable between the monitor and computer, although moving things around might have nudged it a bit I suppose.

Given that this problem has been bothering me for several days, but only with 3.4.0-1, and with other kernels the side-ports were frequently used for hard-disks and SSDs, I'm stumped! Is 3.4.0-1 just more sensitive to dodgy USB connections or something? That seems unlikely...

I don't think I'll close the bug until tomorrow, when I'm satisfied that it all still works after a few hours sleep with flat capacitors.

For what it's worth, the monitor is a Dell SP2309W driven by an nVidia GeForce 9800 GT (Nouveau), and an ASUS P6T Deluxe motherboard. The mouse and keyboard are pretty bog-standard.

[weitjong]

Originally Posted by Gareth Jones

I moved my desk and PC around, ....

I see that changing the feng-shui of your work place has brought you good luck .