Messages in this thread | | | Subject | Re: [git pull] Input update for 2.6.17 | From | Marcel Holtmann <> | Date | Tue, 27 Jun 2006 21:33:38 +0200 |
| |
Hi Linus,
> > Yes, if you have the UHCI driver loaded first, then when EHCI is loaded, > > it disconnects everything on the bus and re-enumerates it. > > > > But EHCI is built into the kernel first, before UHCI, so unless you are > > using modules, nothing should be getting disconnected at boot time. > > Yeah, that's not it. > > It _seems_ to be triggered by this: > > Bluetooth: HCI device and connection manager initialized > Bluetooth: HCI socket layer initialized > usb 5-1: USB disconnect, address 2 > usb 5-1: new full speed USB device using uhci_hcd and address 4 > usb 5-1: configuration #1 chosen from 1 choice > Bluetooth: HCI USB driver ver 2.9 > usbcore: registered new driver hci_usb
I actually doubt that it is any of Bluetooth modules, but to be sure you might boot the next time without the hci_usb driver around.
Regards
Marcel
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |