Hi Alan, > No output at all? Even when you use a VT console and you do "echo 8 > >proc/sys/kernel/printk"? When using "lsusb -v", I get the line that tells me which device is to be listed first, then nothing anymore. When disabling the ehci-pci module, I get nothing at all. I've taken a photo so you can see for yourself: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1485057/+attachment/4458832/+files/screenshot-freeze.JPG The series of actions was: 1. enable kernel debug output 2. detach external mouse, to verify that messages appear 3. hit enter to get a new prompt line 4. trigger the freeze with "lsusb -v" > 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. > > Your guess is correct. If the order of the probes is relevant, although > > it shouldn't be, maybe the order on shutdown/unbind also plays a role? > > Who knows? But bear in mind, probing inevitably involves communicating > with the device, whereas unbind need not. > > 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. > 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 :-) cheers, Roland -- 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
