On Mon, 26 Sep 2005, Chuck Ebbert wrote: > On Sat, 24 Sep 2005 at 10:59:14 -0400, Alan Stern wrote: > > > Have you tried building these things as modules instead of compiling them > > into the kernel? Then you could test what happens when you simply rmmod > > ohci_hcd. > > I don't like modules because of the extra boot time and lower performance.
Extra boot time I can understand. Lower performance I can't, though. In fact, performance should be _improved_ with modules because unused modules won't be loaded into the kernel, taking up memory space. Anyway, even if you don't like modules for everyday use, you can certainly try them for testing purposes. > I plugged the mouse into a different machine and saw the messages you > expected, > but not a single message comes from ehci_hcd when I plug the mouse or hub into > the notebook. This confirms my suspicion that you've got a hardware problem with your controllers. > > The settings of the OHCI controller are somehow > > interfering with the proper operation of the EHCI controller. > > All three hcd's are using IRQ 217, which may be using MSI (how do I tell?) I didn't mean that the IRQs interfere, I meant that the OHCI controller is preventing the EHCI controller from connecting to the USB bus correctly. > And I just tried an i386 kernel; it has the same problem so it's not > specific to x86_64. Like I said, a hardware issue. Alan Stern ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel