Thanks for the reply. This started happening in 2.6.21 suddenly, which is why I tried upgrading to 2.6.22. It seemed to have started happening when my bluetooth light mysteriously went on one day. I went into bios and disabled some IO devices earlier today; "Wireless USB", my firewire port, and the bluetooth adapter. The bluetooth light went off, and this has not happened since. I think it's safe to say it's not going to happen again, since I was getting the IRQ messages every few minutes and it's not happening at all now. I don't have any hardware to test of those IO ports were working or not anyway...
Some of the hardware in this laptop behaves strangely, like using the madwifi drivers with the Atheros wireless will throw the device into a state where it will not be recognized by ndiswrapper or anything until I power down and pull the battery or boot Vista and then boot linux. That's a known issue with the madwifi drivers and my chipset, I'm wondering if something similar happened with the bluetooth chipset/drivers. If anyone needs more info or wants me to try to reproduce the problem let me know, but it's working for the moment again. It looks like others have had the same issue. http://www.thinkwiki.org/wiki/Installing_Debian_Lenny_on_a_ThinkPad_T61#Problems Thanks, Dylan On 7/12/07, Alan Stern <[EMAIL PROTECTED]> wrote: > On Thu, 12 Jul 2007, Dylan Taft wrote: > > > Hi all. I'm using a vanilla linux-2.6.22 kernel. I just noticed I > > get these messages while my laptop is sitting around doing nothing, 2 > > of my USB ports get disabled. I'm not sure what's causing them, to > > reproduce I just let the laptop sit idle for maybe 5 minutes. rmmod > > uhci_hcd > > Sure you don't mean ehci_hcd? Acoording to your /proc/interrupts > listing, it is the driver using IRQ 23. > > > and modprobeing it brings it back for a few more minutes but > > the message pops back up. I'm using a Lenovo T61. Does anyone have > > any possible suggestions or kernel patches I can try? Thanks! > > These errors occur because some device is using IRQ 23 but the kernel > doesn't know it. Maybe the kernel thinks it is using some other IRQ or > maybe the kernel doesn't know of the device's existence at all. > > You could compare /proc/interrupts with earlier kernel versions to see > if anything has changed. > > Sometimes problems in the ACPI drivers can cause this behavior. You > can try booting with acpi=noirq. > > Alan Stern > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
