On Sat, 5 Aug 2006, Jesper Juhl wrote: > > Just as before. > > > > I can't tell you what's causing this to happen, except that it appears to > > be some sort of hardware problem. > > Hmm, the odd thing is that there are no USB devices connected at all.
My guess is that this has nothing to do with the USB controller, other than the fact that IRQ 217 is enabled because the controller uses it. Probably the real problem, the unhandled interrupt requests, comes from some other device entirely. > > Since it doesn't seem to cause any harm > > you could just live with it. > > > > Or, if you're not using any full-speed or low-speed USB devices, you could > > simply prevent uhci-hcd from loading at all. Then IRQ 217 wouldn't get > > enabled in the first place. > > > True, that just seems like a hack... It is. Without knowing the underlying cause of the problem, it's the best I can suggest. If you compare /proc/interrupts with earlier versions of the kernel (where the problem doesn't occur), does it look the same? Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
