[lkml]   [2006]   [Jun]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [git pull] Input update for 2.6.17
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.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-27 21:36    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean