Alan, Thanks for the information provided and the quick answer. > What are these blktrace files? I don't recognize them. They are block device traces output (they are binnay, generated by blkparse command). These can be used to parse them with blkparse. I uploaded the parsed files (they are not usb related, but i took them at the same time to check at the block device layer later). http://dl.dropbox.com/u/72741231/blkparse-JMicron-152d_2338-teac_dv_w28ss_rz3-TEST-20120411.2-f16.out.gz http://dl.dropbox.com/u/72741231/blkparse-sunplus-1bcf_0c31-teac_dv_w28ss_rz3-TEST-20120411.1-f16.out.gz http://dl.dropbox.com/u/72741231/blkparse-sunplus-04fc_0c25-teac_dv_w28ss_rz3-TEST-20120411.1-f16.out.gz >> http://dl.dropbox.com/u/72741231/usbmon-sunplus-1bcf_0c31-teac_dv_w28ss_rz3-TEST-20120411.1-f16.out.gz > > This shows the bridge stopped transferring data in the middle of a > write and then disconnected itself when it was reset. No apparent > reason. > >> http://dl.dropbox.com/u/72741231/blktrace-sunplus-1bcf_0c31-teac_dv_w28ss_rz3-TEST-20120411.1-f16.out.gz >> >> http://dl.dropbox.com/u/72741231/usbmon-sunplus-04fc_0c25-teac_dv_w28ss_rz3-TEST-20120411.1-f16.out.gz > > This doesn't show much of anything -- something like a keyboard or > trackpad got woken up and then put back to sleep. > >> http://dl.dropbox.com/u/72741231/blktrace-sunplus-04fc_0c25-teac_dv_w28ss_rz3-TEST-20120411.1-f16.out.gz >> >> http://dl.dropbox.com/u/72741231/usbmon-JMicron-152d_2338-teac_dv_w28ss_rz3-TEST-20120411.1-f16.out.gz > > This shows the bridge either died or got unplugged a couple of times. > >> http://dl.dropbox.com/u/72741231/usbmon-JMicron-152d_2338-teac_dv_w28ss_rz3-TEST-20120411.2-f16.out.gz > > This shows pretty much the same thing as the first sunplus file. > >> http://dl.dropbox.com/u/72741231/blktrace-JMicron-152d_2338-teac_dv_w28ss_rz3-TEST-20120411.2-f16.out.gz > > You know, it's possible that the problem lies not in the bridges but in > your computer's USB hardware. That might explain why other devices > (like the trackpad) got messed up at the same time. > > Alan Stern > This is the controller where the keyboard and touchpad were affected, but that happened only once. (but the disconnection of the bridges is reproducible by trying enough). # lspci -nn | grep -i USB 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05) 00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05) I will continue trying with other usb controllers. (i know that the sunplus 1bcf:0c31 did disconnect in CentOS 5.3 with an nvidia usb controller on another motherboard with the same test). Said writer needs a patch to write twice, so maybe it needs something more and that causes an abnormal condition that usb cannot handle or identify. (and disconnect and reset the device to restore normal operation, wich is ok to do). Cheers. -- 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
