> Attached is another set of usbmon captures, as well as the dmesg output
> for each session.
I get the impression that this is a hardware bug, but there's not enough
data to be sure. Attached is a revised version of the diagnostic patch;
it will provide a lot more detail about what's going on. Once again, I'll
need to see both the dmesg logs and the usbmon traces.
Before starting each run, do "dmesg -C" to clear the kernel's log buffer.
(The boot-up messages aren't particularly relevant.) It's not necessary
to have more than one recording attempt per run.
Alan Stern
P.S.: Let me know if the attached patch doesn't survive the transition
from email.
On Wed, 6 Feb 2013, Stephen Thirlwall wrote:
> Attached is another set of usbmon captures, as well as the dmesg output
> for each session.
I get the impression that this is a hardware bug, but there's not enough
data to be sure. Attached is a revised version of the diagnostic patch;
it will provide a lot more detail about what's going on. Once again, I'll
need to see both the dmesg logs and the usbmon traces.
Before starting each run, do "dmesg -C" to clear the kernel's log buffer.
(The boot-up messages aren't particularly relevant.) It's not necessary
to have more than one recording attempt per run.
Alan Stern
P.S.: Let me know if the attached patch doesn't survive the transition
from email.