Comment 609 for bug 88746

Revision history for this message
In , balihb (balihb-linux-kernel-bugs) wrote :

On Fri, Jul 25, 2008 at 12:49, Felipe Balbi <email address hidden> wrote:
> Hi,
>
> On Thu, 24 Jul 2008 23:15:56 -0700, Andrew Morton
> <email address hidden> wrote:
>>> After using any usb2.0 device I have on my machine (only on linux, as on
>> winxp
>>> there is no problem) for a few minutes I get this:
>>> usb 6-5: reset high speed USB device using ehci_hcd and address 8
>>> usb 6-5: device descriptor read/64, error -110
>>> usb 6-5: device descriptor read/64, error -110
>>> usb 6-5: reset high speed USB device using ehci_hcd and address 8
>>> usb 6-5: device descriptor read/64, error -110
>>> usb 6-5: device descriptor read/64, error -110
>>> usb 6-5: reset high speed USB device using ehci_hcd and address 8
>>> usb 6-5: device not accepting address 8, error -110
>>> usb 6-5: reset high speed USB device using ehci_hcd and address 8
>>> usb 6-5: device not accepting address 8, error -110
>>> usb 6-5: USB disconnect, address 8
>>> sd 4:0:0:0: Device offlined - not ready after error recovery
>>> sd 4:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
>>> end_request: I/O error, dev sdc, sector 530560
>>> sd 4:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
>>> end_request: I/O error, dev sdc, sector 530576
>>> Buffer I/O error on device sdc1, logical block 138851
>>> lost page write due to I/O error on sdc1
>>> sd 4:0:0:0: [sdc] READ CAPACITY failed
>>> sd 4:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
>>> sd 4:0:0:0: [sdc] Sense not available.
>>> sd 4:0:0:0: [sdc] Write Protect is off
>>> sd 4:0:0:0: [sdc] Mode Sense: 00 00 00 00
>>> sd 4:0:0:0: [sdc] Assuming drive cache: write through
>>> sd 4:0:0:0: [sdc] READ CAPACITY failed
>>> sd 4:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
>>> sd 4:0:0:0: [sdc] Sense not available.
>>> sd 4:0:0:0: [sdc] Write Protect is off
>>> sd 4:0:0:0: [sdc] Mode Sense: 00 00 00 00
>>> sd 4:0:0:0: [sdc] Assuming drive cache: write through
>>> sd 4:0:0:2: [sde] READ CAPACITY failed
>>> sd 4:0:0:2: [sde] Result: hostbyte=0x01 driverbyte=0x00
>>> sd 4:0:0:2: [sde] Sense not available.
>>> sd 4:0:0:2: [sde] Write Protect is off
>>> sd 4:0:0:2: [sde] Mode Sense: 00 00 00 00
>>> sd 4:0:0:2: [sde] Assuming drive cache: write through
>>> sd 4:0:0:1: [sdd] READ CAPACITY failed
>>> sd 4:0:0:1: [sdd] Result: hostbyte=0x01 driverbyte=0x00
>>> sd 4:0:0:1: [sdd] Sense not available.
>>> sd 4:0:0:1: [sdd] Write Protect is off
>>> sd 4:0:0:1: [sdd] Mode Sense: 00 00 00 00
>>> sd 4:0:0:1: [sdd] Assuming drive cache: write through
>>> Buffer I/O error on device sdc1, logical block 138851
>>> lost page write due to I/O error on sdc1
>>> sd 4:0:0:3: [sdf] READ CAPACITY failed
>>> sd 4:0:0:3: [sdf] Result: hostbyte=0x01 driverbyte=0x00
>>> sd 4:0:0:3: [sdf] Sense not available.
>>> sd 4:0:0:3: [sdf] Write Protect is off
>>> sd 4:0:0:3: [sdf] Mode Sense: 00 00 00 00
>>> sd 4:0:0:3: [sdf] Assuming drive cache: write through
>>> sd 4:0:0:1: [sdd] READ CAPACITY failed
>>> sd 4:0:0:1: [sdd] Result: hostbyte=0x01 driverbyte=0x00
>>> sd 4:0:0:1: [sdd] Sense not available.
>>> sd 4:0:0:2: [sde] READ CAPACITY failed
>>> sd 4:0:0:2: [sde] Result: hostbyte=0x01 driverbyte=0x00
>>> sd 4:0:0:2: [sde] Sense not available.
>
> What were you doing with the device before it resets ?

I was copying from it.

> If it was mounted and it somehow reset, it could be
> even a flaky cable.

It can't be. On Windows I have no problem.

>
> Check, also, that hald-addon-storage is probably polling
> an unexistent /dev/sdX.

how?

>
> --
> Best Regards,
>
> Felipe Balbi
> http://blog.felipebalbi.com
> <email address hidden>
>
>