Le Mardi 12 Juillet 2005 20:57, Alan Stern a écrit : > On the other hand, _something_ was generating an interrupt request that > got mapped to IRQ 21 by the hardware. And these requests do seem to be > associated with USB activity. Maybe the EHCI controller is responsible? > One of your postings showed both uhci_hcd:usb2 and ehci_hcd:usb4 mapped to > IRQ 11. That could indicate a shared signal line, which is currently > being mapped incorrectly. > > You can test this a couple of ways. The easiest is to rmmod ehci_hcd, or > prevent it from being loaded in the first place, by renaming > /lib/modules/.../drivers/usb/host/ehci_hcd.ko so that modprobe can't find > it. Also your BIOS may offer the option of disabling USB 2.0 support > entirely. Try doing this under the kernel that has the test patch > installed.
I've tested as you suggest : - Disabled USB 2.0 in BIOS - Renamed ehci_hcd.ko so that modprobe can't find it - Booted the test-patched kernel with same options as previously, MOUSE UNPLUGGED. - After boot "cat /proc/interrupts" shows "0" count for IRQ 21 - Nothing special isn't logged anymore in dmesg or /var/log/messages. - Plugging / unplugging the mouse or other devices doesn't cause anything visible to happen. Nothing gets logged, IRQ 21 counter stays at 0. I could as well not have done it ;-) > Without ehci_hcd loaded, the EHCI controller should not generate any > interrupt requests. If your problem then goes away, and plugging or > unplugging the mouse doesn't cause anything unusual to happen, that will > be a pretty clear indication. Well, so that's a pretty clear indication, but surely clearer to you than to me ;-) So, what's up, doc ? ;-)) -- Michel Bouissou <[EMAIL PROTECTED]> OpenPGP ID 0xDDE8AC6E - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
