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

Bug#507728: linux-image-2.6.26-1-686: USB mass storage devices unreliable when connected through USB hubs



On Wed, Dec 03, 2008 at 11:05:54PM +0000, Sam Morris wrote:
> Package: linux-image-2.6.26-1-686
> Version: 2.6.26-10
> Severity: important
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> USB mass storage devices always seem to fail after a few moments of reading or
> writing when they are connected via a USB hub. This is accompanied by messages
> such as the following:
> 
> Dec  3 22:56:32 xerces kernel: [ 3975.148272] sd 6:0:0:0: [sda] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
> Dec  3 22:56:32 xerces kernel: [ 3975.148286] end_request: I/O error, dev sda, sector 8065
> Dec  3 22:56:32 xerces kernel: [ 3975.148303] Buffer I/O error on device sda1, logical block 1
> Dec  3 22:56:32 xerces kernel: [ 3975.148307] lost page write due to I/O error on sda1
> Dec  3 22:56:32 xerces kernel: [ 3975.148625] usb 4-3.1: USB disconnect, address 10
> Dec  3 22:56:32 xerces kernel: [ 3975.151790] Buffer I/O error on device sda1, logical block 8192
> Dec  3 22:56:32 xerces kernel: [ 3975.151800] lost page write due to I/O error on sda1
> Dec  3 22:56:32 xerces hald[3015]: forcibly attempting to lazy unmount /dev/sda1 as enclosing drive was disconnected
> Dec  3 22:56:32 xerces hald: unmounted /dev/sda1 from '/media/UDISK 2.0' on behalf of uid 0
> 
> This happens with two computers (a Samsung Q45 and a PC with an Asus A7V8X-X
> motherboard); two mass storage devices (an Xclef HD-500 40 GB MP3 player, and a
> play.com 16 GB flash device) and two hubs (a Belin F5U234 and a Trust
> HU-5870V).
> 
> In all cases, connecting the device directly to the computer without going
> through a hub eliminates the problem.
> 
> If the device disconnects while I am copying files to it then this causes DATA
> LOSS as the original files are removed (this is probably a separate bug that I
> should file against nautilus though).

Hi,
The next release of Debian (6.0, code name Squeeze) will be based
on 2.6.32. Please test the current 2.6.32 from unstable and tell
us whether the problem persists. If so, we should report it upstream
to the kernel.org developers.

The 2.6.32 kernel is available from packages.debian.org and can
be installed in both Debian stable, testing and unstable
installations.

Thanks,
        Moritz



Reply to: