Sarah, > Actually, I wonder if 2.6.32 stable needs commit bcef3fd from 2.6.33. > If the xHCI driver wasn't cleaning up the endpoint rings properly after > a transfer error, I suppose the hardware could get wedged. I see. where would I get this commit from? I have to stick with 2.6.32, as I'm using the binary ATI video driver, which doesn't work with 2.6.33... > If the hardware wasn't responding properly to commands, then URBs > wouldn't have been able to be killed, the USB core would have sat around > waiting on those URBs, and rmmod could never exit. I need a more > detailed log to figure out exactly why the hardware is wedged though. > Let me make the less-verbose debugging patch so you don't get log > corruption, and then we'll see what's going on. let me know how I can use this.. Akos -- 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
