Hi folks,

Nothing exciting I'm afraid, I'm just replying to my own post of a few months back in order to provide a complete record.

The reported problem months ago was about USB failure of SL systems; it was usually first noticed by the failure of a USB mouse. (More details below). I had lots of useful suggestions from the list and didn't get anywhere with any of them. I just could not find time to look at it; there was always another system falling over that was of greater importance. So as you would expect from this, I finally got to looking at the machine in question when it got to the stage of failing to boot or just booting very, very slowly, and thus it leapt up the priority list. The "/var/log/messages" file was still being flooded with messages of the type "kernel: hub 1-0:1.0: connect-debounce failed, port 5 disabled". It turned out that these were caused by a hardware problem. An engineer from the supplying company came to site, he said he'd seen this sort of thing before with systems built on an Intel D945GTP motherboard. He simply altered the socket that the front USB ports connected to. (This motherboard offers two sockets for the front USB ports. He just swapped the connection from the more forward to the more backward of these two sockets.) As the engineer predicted from past experience, the machine booted without problems following this change. The messages that previously flooded the linux logs were gone.

So for this system, it was a hardware and not a software problem.

Regards,
Jon

Jon Clark wrote:
Thanks to all those who have provided help with the below problem. I will let you know what I find out when I have time to investigate further.

Cheers,
Jon

PS. The X environment in use is Gnome.

Art Wildman wrote:
Jon Clark wrote:
Hello,

I have been working with about twenty Scientific Linux machines for around five months, and in that time I have seen a complete USB failure on two different systems. Some of our systems have USB mouses attached which generally work fine. "Mouse not working" (the mouse 'freezes') is the fault reported by the users, but I think the problem is with all of the system USB capabilities. Some of the details of the latest failure are:

In "/var/log/messages":
Feb 28 11:38:56 sysname kernel: drivers/usb/input/hid-core.c: not resubmitting, input0 Feb 28 11:38:57 sysname kernel: hub 1-0:1.0: connect-debounce failed, port 5 disabled Feb 28 11:38:59 sysname kernel: hub 1-0:1.0: connect-debounce failed, port 6 disabled Feb 28 11:38:59 sysname kernel: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
Feb 28 11:38:59 sysname kernel: usb 2-2: USB disconnect, address 2
Feb 28 11:39:01 sysname kernel: hub 1-0:1.0: connect-debounce failed, port 5 disabled Feb 28 11:39:02 sysname kernel: hub 1-0:1.0: connect-debounce failed, port 6 disabled

(with the last two messages being repeated continuously.)

The last two messages also fill the system "dmesg" file.

See some of the testing tips in the Linux-USB.org FAQ - http://www.linux-usb.org/ Some mice are USB 2 & some aren't. BIOS, USB controller, driver and mouse polling speed can vary widely.
# lspci -v|grep -i hci
# lsmod | grep -i hci



The two systems that have experienced the failure have been running SL 4.1 and SL 4.4 and have different hardware (a two year old Dell and a 5 month old Viglen) so I think the chances of hardware incompatibility are minimal. (Besides, there are plenty of similar systems here using USB without problems, and the two systems that have experienced failure are usually OK.)


Check for BIOS updates & USB Hotplug configs in BIOS.

I have used "system-config-mouse" to check that the system has recognised the mouse correctly. It recognises a USB scroll mouse which is exactly what is in use.

A reboot fixes the problem, but without a mouse to close applications cleanly, data is lost. Reboot to fix is not an ideal solution either!

I was wondering if anyone else had experienced similar, and more importantly if they found a cause and solution. (I have seen in the list archive a similar problem reported, but the solution was to swap to a PS/2 mouse. I do not have enough PS/2 mice to replace all of our USB mice, and this does not help a user wanting to use a USB stick drive etc.)

Any solution, or advice on where to look for more information that might point to a cause would be appreciated.

Thanks,
Jon


"system-config-mouse" is pretty buggy... it writes a best-guess mouse config to /etc/sysconfig/mouse. You can edit this by hand & try some other device and protocol options (cat /proc/bus/input/devices, reconnect usb mouse & test again). Take a look at your /etc/X11/xorg.conf & tell us what Driver and Protocol your using... then, try the 'evdev' driver below in my xorg.conf Input Section snippet. I use a MX500 mouse on a USB-PS/2 adapter for a KVM with this config so comment out what doesn't work for you. -HTH Art

Logitech MX-310 Mouse and Fedora Core
http://bradthemad.org/tech/notes/logitech_mx310_fedora.php
In your grub.conf at end of kernel line try...
kernel=psmouse.proto=exps

For XOrg 6.9 or greater, you'll want to use the new 'evdev' driver for USB mice...
http://gentoo-wiki.com/HOWTO_Advanced_Mouse
http://gentoo-wiki.com/HOWTO_static_USB_mouse
http://gentoo-wiki.com/HOWTO_Advanced_Mouse/Individual_Configurations

HOWTO Customize Mouse Polling Rate
http://gentoo-wiki.com/TIP_Change_mouse_hz
linuX-gamers.net - Howtos - Increase USB Mouse Polling Interval
http://www.linux-gamers.net/modules/wiwimod/index.php?page=HOWTO%20USBPolling
How to make your Logitech mouse work more precisely
http://www.linux-gamers.net/modules/wiwimod/index.php?page=HOWTO+lomoco
Logitech MX518 Mouse
http://www.linux-gamers.net/modules/wiwimod/index.php?page=HOWTO%20LOGITECH

#----------------Orig Mouse Generic PS2--------------------------------
#Section "InputDevice"
#    Identifier  "Mouse0"
#    Driver      "mouse"
#    Option        "Protocol" "IMPS/2"
#    Option        "Device" "/dev/input/mice"
#    Option        "ZAxisMapping" "4 5"
#    Option        "Emulate3Buttons" "yes"
#EndSection
#-----------------Logitech MX-310 ---------------------------------------
# Logitech MX-310 Mouse and Fedora Core
#http://bradthemad.org/tech/notes/logitech_mx310_fedora.php
# linuX-gamers.net - Get all mouse buttons working - evdev - MX-700
#http://www.linux-gamers.net/modules/wiwimod/index.php?page=HOWTO+Mouse+Buttons #echo -e "pointer = 1 3 2 4 5 8 9 6 7 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32\n" > ~/.Xmodmap
#======================================================================
Section "InputDevice"
       Identifier  "Mouse0"
       Driver      "mouse"
       Option      "Device" "/dev/input/mice"
       Option     "Protocol" "ExplorerPS/2"
       Option     "ZAxisMapping" "6 7"
       Option     "Emulate3Buttons" "false"
       Option     "Buttons" "7"
       Option     "SendCoreEvents" "true"
EndSection

#---------------- USB Mouse ----------------------------------------
# http://gentoo-wiki.com/HOWTO_Advanced_Mouse
# linuX-gamers.net - Get all mouse buttons working - evdev
#http://www.linux-gamers.net/modules/wiwimod/index.php?page=HOWTO+Mouse+Buttons
# linuX-gamers.net - Howtos - Increase USB Mouse Polling Interval
#http://www.linux-gamers.net/modules/wiwimod/index.php?page=HOWTO%20USBPolling
#Section "InputDevice"
#        Identifier  "Mouse[0]"
#        Driver      "evdev"
# Option "Device" "/dev/input/event0" # (cat /proc/bus/input/devices)
#        Option      "Name" "Logitech MX510"
#EndSection
#----------------------------------------------------------------------





--
----------------------------
Jon Clark
Scientific Officer
Dept. of Applied Mathematics
University of Sheffield
Sheffield, S3 7RH, UK
----------------------------

Reply via email to