On Mon, 7 Sep 2015, Roland Weber wrote: > > It would be nice to find out exactly where the unbind freezes. Here > > are some routines to check; try sprinkling printk or dev_info > > statements at various places within them: > > Thanks. I'll send some results later this week. The fact that you get no output when doing the unbind indicates that the freeze occurs relatively early. > > On the other hand, the fact that probing order matters is itself a bug. > > Unfortunately, a bug in the hardware or firmware that we can do nothing > about, if I am not mistaken. Well, maybe and maybe not. We should at least bring it to the attention of the xHCI maintainer, once the current bug has been located and fixed. > > Try blacklisting the ehci-pci module. Unfortunately, there is no way > > to tell the kernel not to allow a driver to probe a particular device. > > Thanks for the tip. I suppose I'll have to compile a kernel where > that is actually a module and not directly compiled in :-) Yes. Or a kernel where CONFIG_USB_EHCI_PCI is disabled. Hmmm, I just took a look at the code. Something I had forgotten about was added recently; a table of devices that ehci-pci should ignore. If you add your device to that list, ehci-pci won't bind to it. See bypass_pci_id_table in drivers/usb/host/ehci-pci.c. Of course, that also will involve rebuilding part of the kernel... Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
