[SOLVED] Mouse / input0 goes dead at unspecified intervals in X

rylan76 · 06-14-2012, 09:50 AM

Hi Guys

I've got a situation where, if I leave my system alone for a few minutes, when I come back to it the mouse isn't working. Keyboard input is fine, as if all other USB connected devices, sound, etc. The system is still totally stable and the kernel doesn't panic or anything - the mouse just doesn't work anymore.

E. g. the pointer is frozen onscreen, and the only way to get it "unfrozen" is to quit X-Windows and restart it.

I see the following in dmesg:

Code:

hub 5-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
usb 5-2: USB disconnect, address 8
usb 5-2: new low speed USB device using uhci_hcd and address 9
usb 5-2: New USB device found, idVendor=192f, idProduct=0616
usb 5-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 5-2: Product: USB Optical Mouse
usb 5-2: configuration #1 chosen from 1 choice
input: USB Optical Mouse as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0/input/input16
generic-usb 0003:192F:0616.0008: input,hidraw0: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1d.3-2/input0

The above repeats 5 or 6 times.

The message refers to EMI - electro-magnetic interference?

If so, anybody got any idea how I can "restart" input0 without quitting the entire X-server and restarting the entire setup?

I'm looking for a command to spawn a process or thread (guessing here) that runs input0 (my mouse) in the X-server...

Strange thing is if I use the system constantly, the mouse doesn't get frozen up. This is not hardware as far as I can tell, in Windows (dual-booted on the same machine) the mouse stays fine for days.

Thanks!

Soadyheid · 06-15-2012, 07:51 AM

Quote:

This is not hardware as far as I can tell, in Windows (dual-booted on the same machine) the mouse stays fine for days.

This implies that it DOES eventually freeze?

To eliminate the mouse hardware completely, have you tried replacing the mouse which seems one of the easiest things to check?

Play Bonny!

rylan76 · 11-05-2012, 01:04 AM

Ok got this fixed.

It was apparently RF interference - move to a different location in a different town and the problem is gone.

I suspect several radio alarm systems that were near my previous physical location where this problem was experienced.