On Tue, 24 Sep 2013, folkert wrote: > > Then the problem is most likely in the device or the firmware. If you > > get a usbmon trace, it might provide more information. > > > You asked what the firmware is doing wrong, but you already know the > > answer: It disconnects the device every 6-7 seconds. Perhaps it does > > this because it doesn't like the commands it receives from the > > computer. > > In this logging I plugged-in the device and waited for it to disconnect > and reconnect again. > I googled but did not find something that translates this logging into > human readable format. Are there any that you know of? No. But I can interpret it for you. > ffff88044d799980 4062710749 S Ci:3:001:0 s a3 00 0000 0001 0004 4 < > ffff88044d799980 4062710758 C Ci:3:001:0 0 4 = 00010000 > ffff88044d799980 4062710768 S Ci:3:001:0 s a3 00 0000 0002 0004 4 < > ffff88044d799980 4062710770 C Ci:3:001:0 0 4 = 00010000 > ffff88044d799980 4062710770 S Ci:3:001:0 s a3 00 0000 0003 0004 4 < > ffff88044d799980 4062710780 C Ci:3:001:0 0 4 = 00010000 > ffff88044d799980 4062710781 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < > ffff88044d799980 4062710782 C Ci:3:001:0 0 4 = 01030100 > ffff88044d799980 4062710783 S Co:3:001:0 s 23 01 0010 0004 0000 0 > ffff88044d799980 4062710786 C Co:3:001:0 0 0 > ffff880449ee9600 4062814544 S Ii:3:001:1 -115:2048 4 < > ffff8803b4a1d300 4062814640 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < > ffff8803b4a1d300 4062814645 C Ci:3:001:0 0 4 = 01030000 > ffff8803b4a1d300 4062814686 S Co:3:001:0 s 23 03 0004 0004 0000 0 > ffff8803b4a1d300 4062814690 C Co:3:001:0 0 0 > ffff8803b4a1d300 4062870540 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < > ffff8803b4a1d300 4062870551 C Ci:3:001:0 0 4 = 03031000 > ffff8803b4a1d300 4062926555 S Co:3:001:0 s 23 01 0014 0004 0000 0 > ffff8803b4a1d300 4062926583 C Co:3:001:0 0 0 The part above is normal device detection and reset. > ffff8803b4a1d300 4062942522 S Ci:3:123:0 s 80 06 0100 0000 0008 8 < > ffff8803b4a1d300 4062942946 C Ci:3:123:0 0 8 = 12010002 00000008 > ffff8803b4a1d300 4062943053 S Ci:3:123:0 s 80 06 0100 0000 0012 18 < > ffff8803b4a1d300 4062943699 C Ci:3:123:0 0 18 = 12010002 00000008 500d1000 07000102 0301 > ffff8803b4a1d300 4062943846 S Ci:3:123:0 s 80 06 0200 0000 0009 9 < > ffff8803b4a1d300 4062944426 C Ci:3:123:0 0 9 = 09022900 01010080 32 > ffff8803b4a1d300 4062944543 S Ci:3:123:0 s 80 06 0200 0000 0029 41 < > ffff8803b4a1d300 4062945716 C Ci:3:123:0 0 41 = 09022900 01010080 32090400 00020300 00000921 11010001 22300007 05810308 > ffff8803b4a1d300 4062945841 S Ci:3:123:0 s 80 06 0300 0000 00ff 255 < > ffff8803b4a1d300 4062946185 C Ci:3:123:0 0 4 = 04030704 > ffff8803b4a1d300 4062946297 S Ci:3:123:0 s 80 06 0302 0407 00ff 255 < > ffff8803b4a1d300 4062946920 C Ci:3:123:0 0 18 = 12035500 53004200 2d005400 65006d00 7000 > ffff8803b4a1d300 4062947054 S Ci:3:123:0 s 80 06 0301 0407 00ff 255 < > ffff8803b4a1d300 4062947836 C Ci:3:123:0 0 26 = 1a034300 6c006500 77006100 72006500 20004700 6d006200 4800 > ffff8803b4a1d300 4062947884 S Ci:3:123:0 s 80 06 0303 0407 00ff 255 < > ffff8803b4a1d300 4062948549 C Ci:3:123:0 0 12 = 0c033600 33003800 31003300 This is normal enumeration (reading the device's descriptors). > ffff8803b4a1d900 4062948944 S Co:3:123:0 s 00 09 0001 0000 0000 0 > ffff8803b4a1d900 4062949285 C Co:3:123:0 0 0 > ffff8803b4a1d180 4062949459 S Ci:3:123:0 s 80 06 0303 0407 00ff 255 < > ffff8803b4a1d180 4062949988 C Ci:3:123:0 0 12 = 0c033600 33003800 31003300 This installs the HID configuration and re-reads a string descriptor. > ffff8803b4a1d180 4062950110 S Co:3:123:0 s 21 0a 0000 0000 0000 0 > ffff8803b4a1d180 4062950425 C Co:3:123:0 0 0 > ffff8803b4a1d180 4062950455 S Ci:3:123:0 s 81 06 2200 0000 0030 48 < > ffff8803b4a1d180 4062951755 C Ci:3:123:0 0 48 = 06a0ff09 01a10109 02a10006 a1ff0903 1580257f 350045ff 75089506 81020904 > ffff88044bad9c80 4062951977 S Ci:3:123:0 s a1 01 0100 0000 0006 8 < > ffff88044bad9c80 4062952411 C Ci:3:123:0 0 6 = 00000000 0000 This is normal HID initialization: setting the Idle delay to 0, reading the report descriptor, and issuing a Get-Report request. > ffff880449ee9600 4069614870 C Ii:3:001:1 0:2048 1 = 10 > ffff880449ee9600 4069614889 S Ii:3:001:1 -115:2048 4 < > ffff88029ca33980 4069614999 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < > ffff88029ca33980 4069615003 C Ci:3:001:0 0 4 = 00010100 > ffff88029ca33980 4069615007 S Co:3:001:0 s 23 01 0010 0004 0000 0 > ffff88029ca33980 4069615010 C Co:3:001:0 0 0 > ffff8803b4a1d300 4069615639 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < > ffff8803b4a1d300 4069615651 C Ci:3:001:0 0 4 = 00010000 > ffff8803b4a1d300 4069646488 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < > ffff8803b4a1d300 4069646493 C Ci:3:001:0 0 4 = 00010000 > ffff8803b4a1d300 4069678554 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < > ffff8803b4a1d300 4069678564 C Ci:3:001:0 0 4 = 00010000 > ffff8803b4a1d300 4069710551 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < > ffff8803b4a1d300 4069710562 C Ci:3:001:0 0 4 = 00010000 Almost 7 seconds later, this shows the device disconnecting itself from the bus. There's no obvious reason. The rest of the trace is just the same thing repeated. 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
