On Mon, 19 Dec 2011, Tim Coote wrote: > No. But it does describe how the host drivers can confuse devices. > And my experience of such devices is that, for instance, they can be > swamped with error conditions that causes a stack overflow. Any I'm > hypothesising that's what's happened here. No need to hypothesize. Look at the actual data from usbmon or wireshark and see what's really happening. > > echo X >/sys/bus/pci/drivers/uhci_hcd/unbind > > > > Replace X with the correct name of the UHCI device for the bus your > > device is plugged into -- this will be one of the file names in the > > /sys/bus/pci/drivers/uhci_hcd directory, such as 0000:00:1d.1. > > > > To rebind the controller, use the same command but replace "unbind" > > with "bind". > Thanks. This does seem to work. However, this did not solve the problem the first time (I unbound what I thought was the correct device, but I can see that it could simply be the wrong one, so I'm going to disable them all tonight. > > Are there any instructions on how these types of commands work. I've found something on lwn, but it misses the context of what the different connections can be. These's lots of documentation about these things in the Linux kernel source's Documentation directory. In particular, the unbind and bind files are explained in Documentation/ABI/testing/sysfs-bus-pci (although they apply to all buses now, not just PCI). 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
