On Sat, 14 Jan 2017, c400 wrote: ... > ffffa262eb5516c0 321863050 S Bo:4:002:2 -115 31 = 55534243 6e000000 > 00100000 80000a28 00000008 10000008 00000000 000000 > ffffa262eb5516c0 321863062 C Bo:4:002:2 0 31 > > ffffa26333a3d3c0 321863073 S Bi:4:002:1 -115 4096 < > ffffa26333a3d3c0 321863103 C Bi:4:002:1 0 4096 = 00000000 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 > ffffa262eb5516c0 321863127 S Bi:4:002:1 -115 13 < > ffffa262eb5516c0 321863143 C Bi:4:002:1 0 13 = 55534253 6e000000 00000000 00 At this point everything was working. A 4096-byte read just completed normally. > ffffa262eb5516c0 321863190 S Bo:4:002:2 -115 31 = 55534243 6f000000 > 00700000 80000a28 00000008 40000038 00000000 000000 > ffffa262eb5516c0 321863202 C Bo:4:002:2 0 31 > > ffffa2633391ecc0 321863211 S Bi:4:002:1 -115 28672 < > ffffa2633391ecc0 353264495 C Bi:4:002:1 -104 1024 = 00000000 00000000 > 00000000 00000000 00000000 00000000 00000000 00000000 This shows a 28-KB read that failed after the first 4 KB had been transferred. No further data was received and the transfer was aborted after about 30 seconds. > ffffa2633391ecc0 353264543 S Ci:4:001:0 s a3 00 0000 0001 0004 4 < > ffffa2633391ecc0 353264550 C Ci:4:001:0 0 4 = 03020000 > ffffa2633312eb40 353264658 S Co:4:001:0 s 23 03 0004 0001 0000 0 > ffffa2633312eb40 353264665 C Co:4:001:0 0 0 > ffffa26336cf3600 353324060 S Ci:4:001:0 s a3 00 0000 0001 0004 4 < > ffffa26336cf3600 353324078 C Ci:4:001:0 0 4 = 03021000 > ffffa2633828d900 353324135 S Co:4:001:0 s 23 01 0014 0001 0000 0 > ffffa2633828d900 353324149 C Co:4:001:0 0 0 > ffffa263371bc540 353324271 S Co:4:001:0 s 23 01 001d 0001 0000 0 > ffffa263371bc540 353324278 C Co:4:001:0 0 0 > ffffa2633256c240 353324353 S Co:4:001:0 s 23 01 0019 0001 0000 0 > ffffa2633256c240 353324366 C Co:4:001:0 0 0 > ffffa262ee14a600 353324421 S Co:4:001:0 s 23 01 0010 0001 0000 0 > ffffa262ee14a600 353324427 C Co:4:001:0 0 0 > ffffa263325d80c0 353324527 S Ci:4:001:0 s a3 00 0000 0001 0004 4 < > ffffa263325d80c0 353324533 C Ci:4:001:0 0 4 = 03020000 > ffffa262ee1da0c0 355788061 S Ci:4:002:0 s 80 06 0100 0000 0008 8 < This shows the start of a reset. Apparently the reset did not finish normally. > Here it is! Launched USBMON and inserted USB3 flash into buggy > controler. Then stoped monitoring. Obviously there is some sort of communications problem. Either the device stopped transferring data or else the xHCI host controller stopped receiving it. From the usbmon trace, there's no way to tell which. However, if the device works okay with an EHCI host controller or on another computer, that would indicate the problem is in the xHCI controller. Maybe Mathias can offer some advice. Alan Stern > 2017-01-14 0:01 GMT+03:00 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>: > > On Fri, 13 Jan 2017, c400 wrote: > > > >> kernel 4.9.3 > >> still not working > >> latest log: > >> > >> [ 196.984424] sd 7:0:0:0: [sdc] 31293440 512-byte logical blocks: > >> (16.0 GB/14.9 GiB) > >> [ 196.984564] sd 7:0:0:0: [sdc] Write Protect is off > >> [ 196.984566] sd 7:0:0:0: [sdc] Mode Sense: 23 00 00 00 > >> [ 196.984689] sd 7:0:0:0: [sdc] No Caching mode page found > >> [ 196.984690] sd 7:0:0:0: [sdc] Assuming drive cache: write through > >> [ 196.984696] device: '8:32': device_add > >> [ 196.984714] PM: Adding info for No Bus:8:32 > >> [ 196.984727] device: 'sdc': device_add > >> [ 196.984747] PM: Adding info for No Bus:sdc > >> [ 197.085658] sdc: sdc1 > >> [ 197.085664] device: 'sdc1': device_add > >> [ 197.085680] PM: Adding info for No Bus:sdc1 > >> [ 197.086929] sd 7:0:0:0: [sdc] Attached SCSI removable disk > >> [ 230.955006] FAT-fs (sdc1): Volume was not properly unmounted. Some > >> data may be corrupt. Please run fsck. > >> [ 234.422942] DMAR: DRHD: handling fault status reg 2 > >> [ 234.422946] DMAR: [DMA Read] Request device [02:00.0] fault addr > >> fffbb000 [fault reason 06] PTE Read access is not set > >> [ 234.422950] xhci_hcd 0000:02:00.0: WARNING: Host System Error > >> [ 234.446078] xhci_hcd 0000:02:00.0: Host not halted after 16000 microseconds. > >> [ 270.447035] xhci_hcd 0000:02:00.0: xHCI host not responding to stop > >> endpoint command. > >> [ 270.447040] xhci_hcd 0000:02:00.0: Assuming host is dying, halting host. > >> [ 270.470143] xhci_hcd 0000:02:00.0: Host not halted after 16000 microseconds. > >> [ 270.470153] xhci_hcd 0000:02:00.0: Non-responsive xHCI host is not halting. > >> [ 270.470154] xhci_hcd 0000:02:00.0: Completing active URBs anyway. > >> [ 270.470161] xhci_hcd 0000:02:00.0: HC died; cleaning up -- 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
