Re: usb-storage, error reading the last 8 sectors, regression in2.6.25-rc7

From: Alan Stern
Date: Sun Mar 30 2008 - 15:00:07 EST


On Sun, 30 Mar 2008, Sergey Dolgov wrote:

> Hi!
>
> If I boot Asus Eee PC with 8 Gb Transcend SDHC card inserted into the
> internal card reader, 2.6.25-rc7 prints the following:
>
> [ 9.914968] scsi 2:0:0:0: Direct-Access USB2.0 CardReader SD0 0100 PQ: 0 ANSI: 0
> [ 10.248951] sd 2:0:0:0: [sdb] 15660032 512-byte hardware sectors (8018 MB)
> [ 10.249695] sd 2:0:0:0: [sdb] Write Protect is off
> [ 10.249928] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [ 10.249935] sd 2:0:0:0: [sdb] Assuming drive cache: write through
> [ 10.256632] sd 2:0:0:0: [sdb] 15660032 512-byte hardware sectors (8018 MB)
> [ 10.257440] sd 2:0:0:0: [sdb] Write Protect is off
> [ 10.257546] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [ 10.257552] sd 2:0:0:0: [sdb] Assuming drive cache: write through
> [ 10.257657] sdb: sdb1 sdb2 sdb3
> [ 10.259560] sd 2:0:0:0: [sdb] Attached SCSI removable disk
> [ 10.260489] usb-storage: device scan complete
> [ 10.380590] sd 2:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
> [ 10.380590] sd 2:0:0:0: [sdb] Sense Key : 0x4 [current]
> [ 10.380590] sd 2:0:0:0: [sdb] ASC=0x11 ASCQ=0x0
> [ 10.380590] end_request: I/O error, dev sdb, sector 15660024
>
> As a result, no sdb device is created by udev.
>
> If the card is inserted after the boot, it sometimes works fine (I've
> tested with "dd if=/dev/sdb of=/dev/null bs=512 skip=15660000"), and
> sometimes fails in the same way (the same I/O error message, dd
> hangs).
>
> 2.6.24.4 is fine (no problems at boot, always can dd read the whole
> card, all 15660032 sectors of it).
>
> The other SD card I've got, 2 Gb, also works ok even with 2.6.25-rc7.

Can you build both 2.6.24.4 and 2.6.25-rc7 with
CONFIG_USB_STORAGE_DEBUG enabled, and post the dmesg logs from both
kernels showing what happens when the SDHC card is probed during boot?
Comparing the two logs should indicate where the crucial difference
lies.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/