On Tue, 14 Apr 2015, Alistair Grant wrote:
> Hi Mathias and Alan,
>
> As Mathias requested, I've included the usbmon output with the patch
> applied.
>
> It didn't make any difference to the end result, the mouse still fails
> to initialise correctly (no real surprise, I think), but is getting the
> same string that Alan reported earlier ("Laser 0"). I've also included
> the relevant lines from syslog below. (I also have a pcap file
> captured with tshark if anyone is interested).
>
> As always, thanks for your help,
> Alistair
>
> usbmon output:
...
> ffff880024c51b40 591168422 S Ci:1:006:0 s 80 06 0302 0409 00ff 255 <
> ffff880024c51b40 591169070 C Ci:1:006:0 -32 15 = 18034c00 61007300 65007200 200030
> ffff880024c51b40 591169098 S Ci:1:006:0 s 80 06 0302 0409 00ff 255 <
> ffff880024c51b40 591169854 C Ci:1:006:0 -32 15 = 18034c00 61007300 65007200 200030
> ffff880024c51b40 591169884 S Ci:1:006:0 s 80 06 0302 0409 00ff 255 <
> ffff880024c51b40 591170684 C Ci:1:006:0 -32 15 = 18034c00 61007300 65007200 200030
> ffff880024c51b40 591170702 S Ci:1:006:0 s 80 06 0302 0409 0002 2 <
> ffff880024c51b40 591171025 C Ci:1:006:0 0 2 = 1803
> ffff880024c51b40 591171037 S Ci:1:006:0 s 80 06 0302 0409 0018 24 <
> ffff880024c51b40 591171668 C Ci:1:006:0 -32 15 = 18034c00 61007300 65007200 200030
> ffff880024c51b40 591171679 S Ci:1:006:0 s 80 06 0302 0409 0018 24 <
> ffff880024c51b40 591172455 C Ci:1:006:0 -32 15 = 18034c00 61007300 65007200 200030
> ffff880024c51b40 591172466 S Ci:1:006:0 s 80 06 0302 0409 0018 24 <
> ffff880024c51b40 596169148 C Ci:1:006:0 -2 0
This is practically identical to the EHCI trace from before, right up
to the point where the mouse's firmware crashes. I can't explain the
difference in behavior; it must be some very subtle timing-related
issue.
There doesn't seem to be anything more to try. :-(
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
