Re: usb 1-2: reset high-speed USB device number 3 using ehci-pci

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

 



On Wed, 25 May 2016, Mathieu Malaterre wrote:

> Hi,
> 
> I am trying to track down an issue that happen during Debian
> Installation from a USB key onto a Mac Mini G4 (PPC) [*].
> 
> Basically the USB key is working nicely (`badblocks` is fine), however
> under this specific circumstances, the USB key needs to be physically
> removed and then re-plugged so that it can be read.
> 
> dmesg log excerpt:
> 
> [    4.259597] scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer Mini
>   0.2  PQ: 0 ANSI: 2
> [    4.265282] sd 2:0:0:0: [sdb] 2001888 512-byte logical blocks:
> (1.02 GB/977 MiB)
> [    4.267027] sd 2:0:0:0: [sdb] Write Protect is off
> [    4.267040] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [    4.268149] sd 2:0:0:0: [sdb] No Caching mode page found
> [    4.268162] sd 2:0:0:0: [sdb] Assuming drive cache: write through
> [    4.393824] usb 1-2: reset high-speed USB device number 3 using ehci-pci
> [    4.653835] usb 1-2: reset high-speed USB device number 3 using ehci-pci
> [    4.913832] usb 1-2: reset high-speed USB device number 3 using ehci-pci
> [    5.177821] usb 1-2: reset high-speed USB device number 3 using ehci-pci
> [    5.437844] usb 1-2: reset high-speed USB device number 3 using ehci-pci
> [    5.697847] usb 1-2: reset high-speed USB device number 3 using ehci-pci
> [    5.831893] sd 2:0:0:0: [sdb] tag#0 FAILED Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [    5.831913] sd 2:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00
> 00 00 08 00
> [    5.831919] blk_update_request: I/O error, dev sdb, sector 0
> [    5.831926] Buffer I/O error on dev sdb, logical block 0, async page read
> 
> 
> I failed so far to reproduce it, since anytime I try to `mount` it it works.
> 
> Comments welcome on how to track this down ?

If you can't reproduce a failure, you can't track it down.

Also, an installation kernel is not well suited to tracking failures.  
It's a somewhat unstable environment without all the resources that 
would normally be available.

If you can acquire a usbmon trace showing what happens when the flash 
drive is plugged in and the reset occurs, that would help.

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