Re: VL805 USB 3.0 does not see connected devices (only on x86_64) (x86 is ok)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
> [  270.470265] sd 7:0:0:0: [sdc] tag#0 FAILED Result:
> hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK
> [  270.470268] sd 7:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 06 51 22
> 00 00 0e 00
> [  270.470269] blk_update_request: I/O error, dev sdc, sector 413986
> [  270.538994] sd 7:0:0:0: [sdc] tag#0 FAILED Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [  270.538997] sd 7:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 06 51 23
> 00 00 0d 00
> [  270.538998] blk_update_request: I/O error, dev sdc, sector 413987
> [  270.986995] sd 7:0:0:0: [sdc] tag#0 FAILED Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [  270.986997] sd 7:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 06 51 22
> 00 00 01 00
> [  270.986999] blk_update_request: I/O error, dev sdc, sector 413986
> [  270.987063] FAT-fs (sdc1): Directory bread(block 411938) failed
> [  271.307002] sd 7:0:0:0: [sdc] tag#0 FAILED Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [  271.307004] sd 7:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 06 51 23
> 00 00 01 00
> [  271.307005] blk_update_request: I/O error, dev sdc, sector 413987
> [  271.307062] FAT-fs (sdc1): Directory bread(block 411939) failed
> [  271.307079] FAT-fs (sdc1): Directory bread(block 411940) failed

Please post a usbmon trace starting from just before you plug in the 
USB drive and continuing until the error occurs.  (Instructions for 
usbmon are in the kernel source file Documentation/usb/usbmon.txt.)

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



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux