[2.6.10-rc2-mm3] Broken usb2 mass-storage?

[2.6.10-rc2-mm3] Broken usb2 mass-storage?

[Christian Axelsson]

Hi!

Im trying to attach a usb2 200gb drive to my laptop that is runnig 
2.6.10-rc2-mm3. Upon connect I get this in dmesg:

   usb 1-2: new high speed USB device using ehci_hcd and address 4
   scsi0 : SCSI emulation for USB Mass Storage devices
   usb-storage: device found at 4
   usb-storage: waiting for device to settle before scanning
     Vendor: Maxtor 6  Model: Y200P0            Rev: YAR4
     Type:   Direct-Access                      ANSI SCSI revision: 04
   SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
   sda: assuming drive cache: write through
    sda: sda1
   Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
   Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0

Then I try to access the disk (via fdisk or mount anything) and I get 
the following in dmesg:

   usb 1-2: reset high speed USB device using ehci_hcd and address 4
   usb 1-2: scsi_eh_0 timed out on ep0in
   usb 1-2: device descriptor read/64, error -110
   usb 1-2: scsi_eh_0 timed out on ep0in
   usb 1-2: device descriptor read/64, error -110
   usb 1-2: reset high speed USB device using ehci_hcd and address 4
   usb 1-2: scsi_eh_0 timed out on ep0in
   usb 1-2: device descriptor read/64, error -110

Then it stalls a while and this shows up:

   scsi: Device offlined - not ready after error recovery: host 0 
channel 0 id 0 lun 0
   usb 1-2: USB disconnect, address 4
   scsi0 (0:0): rejecting I/O to offline device
   scsi0 (0:0): rejecting I/O to offline device
   usb-storage: device scan complete
   usb 1-2: new high speed USB device using ehci_hcd and address 5
   usb 1-2: khubd timed out on ep0in
   usb 1-2: device descriptor read/64, error -110

And repeats this.. I think you get the point ;)
The process trying to access the disk hangs.
Note: the drive works flawless under windows and has worked fine under 
linux during various stages of the 2.5 and early 2.6 kernels :)

-- 
Regards,
Christian

Re: [2.6.10-rc2-mm3] Broken usb2 mass-storage?

[Greg KH]

On Mon, Nov 29, 2004 at 11:36:03PM +0100, Christian Axelsson wrote:
> Hi!
> 
> Im trying to attach a usb2 200gb drive to my laptop that is runnig 
> 2.6.10-rc2-mm3. Upon connect I get this in dmesg:

Hm, so 2.6.10-rc2 works for you?

>   usb 1-2: new high speed USB device using ehci_hcd and address 4
>   scsi0 : SCSI emulation for USB Mass Storage devices
>   usb-storage: device found at 4
>   usb-storage: waiting for device to settle before scanning
>     Vendor: Maxtor 6  Model: Y200P0            Rev: YAR4
>     Type:   Direct-Access                      ANSI SCSI revision: 04
>   SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
>   sda: assuming drive cache: write through
>    sda: sda1
>   Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>   Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0

That looks good.

> Then I try to access the disk (via fdisk or mount anything) and I get 
> the following in dmesg:
> 
>   usb 1-2: reset high speed USB device using ehci_hcd and address 4
>   usb 1-2: scsi_eh_0 timed out on ep0in

Ick, not good.

I'll leave the rest of the logs below, for the linux-usb-devel people to
potentually help out.

Oh, have you tried the ub driver instead?  Does that work for this
device?

>   usb 1-2: device descriptor read/64, error -110
>   usb 1-2: scsi_eh_0 timed out on ep0in
>   usb 1-2: device descriptor read/64, error -110
>   usb 1-2: reset high speed USB device using ehci_hcd and address 4
>   usb 1-2: scsi_eh_0 timed out on ep0in
>   usb 1-2: device descriptor read/64, error -110
> 
> Then it stalls a while and this shows up:
> 
>   scsi: Device offlined - not ready after error recovery: host 0 
> channel 0 id 0 lun 0
>   usb 1-2: USB disconnect, address 4
>   scsi0 (0:0): rejecting I/O to offline device
>   scsi0 (0:0): rejecting I/O to offline device
>   usb-storage: device scan complete
>   usb 1-2: new high speed USB device using ehci_hcd and address 5
>   usb 1-2: khubd timed out on ep0in
>   usb 1-2: device descriptor read/64, error -110
> 
> And repeats this.. I think you get the point ;)
> The process trying to access the disk hangs.
> Note: the drive works flawless under windows and has worked fine under 
> linux during various stages of the 2.5 and early 2.6 kernels :)
> 

thanks,

greg k-h

Re: [linux-usb-devel] Re: [2.6.10-rc2-mm3] Broken usb2 mass-storage?

[David Brownell]

On Monday 29 November 2004 3:20 pm, Greg KH wrote:

> > Then I try to access the disk (via fdisk or mount anything) and I get 
> > the following in dmesg:
> > 
> >   usb 1-2: reset high speed USB device using ehci_hcd and address 4
> >   usb 1-2: scsi_eh_0 timed out on ep0in
> 
> Ick, not good.

Has this device always needed a reset?  The interesting
bits of the log are probably the ones immediatelly preceding
the decision to reset it.  Two possibilities come to mind:
something broke the reset logic (the device is clearly not
working right after the reset) ... or something changed to
make the device go bonkers _before_ the reset, which seems
a bit more likely with my current lack-of-facts.  (Especially
if rc2 works and mm3 doesn't.)

- Dave


> ...
> 
> >   usb 1-2: device descriptor read/64, error -110
> >   usb 1-2: scsi_eh_0 timed out on ep0in
> >   usb 1-2: device descriptor read/64, error -110
> >   usb 1-2: reset high speed USB device using ehci_hcd and address 4
> >   usb 1-2: scsi_eh_0 timed out on ep0in
> >   usb 1-2: device descriptor read/64, error -110
> > 
> > Then it stalls a while and this shows up:
> > 
> >   scsi: Device offlined - not ready after error recovery: host 0 
> > channel 0 id 0 lun 0
> >   usb 1-2: USB disconnect, address 4
> >   scsi0 (0:0): rejecting I/O to offline device
> >   scsi0 (0:0): rejecting I/O to offline device
> >   usb-storage: device scan complete
> >   usb 1-2: new high speed USB device using ehci_hcd and address 5
> >   usb 1-2: khubd timed out on ep0in
> >   usb 1-2: device descriptor read/64, error -110
> > 
> > And repeats this.. I think you get the point ;)
> > The process trying to access the disk hangs.
> > Note: the drive works flawless under windows and has worked fine under 
> > linux during various stages of the 2.5 and early 2.6 kernels :)
> >