https://bugzilla.kernel.org/show_bug.cgi?id=212955 --- Comment #23 from Lucas Endres (jaffa225man@xxxxxxxxx) --- (In reply to Alan Stern from comment #22) > Using two different drivers would definitely explain the different patterns > of communication with the device in your two usbmon traces. > > But it doesn't explain why, with one of the drivers, the device seems to > stop responding when used with EHCI (and works okay with xHCI!). Maybe this > is caused by a bug in the device's firmware. It that's true, changing the > communication pattern might work around the problem. Sorry, but here's another pertinent factor that I should have mentioned earlier if I haven't: It could very well be a bug in the UA-101's firmware, since if I connect an audible input and watch it on the UA-101's builtin levels meter (with it already on), I think it does freeze. The levels remain when the input is unplugged, after plugging in USB while running a nonworking commit. Thanks for the insight! I suppose I should start comparing the code to each module, since I think that's what you're suggesting. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
