Red Hat Bugzilla – Bug 133897
Hotplu doesn't get run when usb devices are added on computers with ASUS P8P mainboard
Last modified: 2015-01-04 17:10:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
I noticed on some computers that adding a usb device doesn't activate
hotplug, so the device doesn't become available (nothing in logs, no
entries in /proc/bus/usb or /sys/bus/usb).
Since it works on other machines with the same setup (installed using
the same kickstart file), I think it is an issue with the hardware,
probably the mainboard, which is an ASUS P8P (or P8P800SE) in all the
cases where I encountered this bug.
Version-Release number of selected component (if applicable):
hotplug-2004_04_01-1 kudzu-188.8.131.52-1 kernel-2.6.7-1.494.2.2 or
Steps to Reproduce:
1. boot machine in kernel 2.6.7-1.492.2.2 or 2.6.8-1.521
2. plug in a usb device (tried with disk, camera, mouse)
Actual Results: nothing happens (no device available, nothing in
logs, no entries in /proc/bus/usb or /sys/bus/usb)
Expected Results: device should have been detected by hotplug and
made available to the system.
One of these machines still had kernel 2.6.6-1.435 installed, and
there it works.
Bug is the same with SMP kernels of those same releases.
There is one way to make such devices work: if it is plugged in when
the system is booted. So the usb mouse will usuallly work, only when
the mouse gets unplugged by accident, this requires a reboot.
No such workaround for flash keys, usb disks, cameras and probably
other usb devices.
If it's not getting any messages at all, that's a kernel/driver bug.
Additional info: when I disable USB 2 in the BIOS on one of those
machines, the kernel does see new devices when they are plugged in. So
for USB 1 devices, this is a workaround, and maybe it gives the kernel
develloppers a clue about the location of this bug.
FC3 works fine on these machines, with USB 2 enabled in the BIOS.
I'll try the 2.6.9 kernel from updates-testing on FC2 tomorrow to see
if it solved the problem there also.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.