Bug#555835: [usb-storage] linux-image-2.6.30-2-686: Unusual usb storage Samsung YP-CP3 not working
On Fri, 20 Nov 2009, Vitaly Kuznetsov wrote:
> Alan Stern <stern@rowland.harvard.edu> writes:
>
> >> So, the minimum is US_FL_MAX_SECTORS_64 | US_FL_BULK_IGNORE_TAG
> >
> > I would still like to see a usbmon trace showing what happens with
> > US_FL_BULK_IGNORE_TAG and _without_ US_FL_MAX_SECTORS_64.
> >
>
> usbmon attached, dmesg looks like:
>
> [90833.235667] usb-storage: device found at 10
> [90833.235672] usb-storage: waiting for device to settle before scanning
> [90838.232280] usb-storage: device scan complete
> [90838.232741] scsi 10:0:0:0: Direct-Access SAMSUNG YP-CP3 1.00 PQ: 0 ANSI: 0
> [90838.233107] scsi 10:0:0:1: Direct-Access SAMSUNG microSD Card 1.00 PQ: 0 ANSI: 0 CCS
> [90838.251803] sd 10:0:0:0: [sdb] 7649280 512-byte hardware sectors: (3.91 GB/3.64 GiB)
> [90838.252389] sd 10:0:0:0: [sdb] Write Protect is off
> [90838.252394] sd 10:0:0:0: [sdb] Mode Sense: 03 00 00 00
> [90838.252397] sd 10:0:0:0: [sdb] Assuming drive cache: write through
> [90838.254505] sd 10:0:0:0: [sdb] Assuming drive cache: write through
> [90838.254513] sdb:
> [90838.255649] sd 10:0:0:0: [sdb] Attached SCSI removable disk
> [90838.256630] sd 10:0:0:1: [sdc] Attached SCSI removable disk
> [90838.389146] sd 10:0:0:0: [sdb] Unhandled error code
> [90838.389150] sd 10:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [90838.389155] end_request: I/O error, dev sdb, sector 8
> [90838.389159] __ratelimit: 110 callbacks suppressed
> [90838.389162] Buffer I/O error on device sdb, logical block 1
> [90838.389168] Buffer I/O error on device sdb, logical block 2
> [90838.389171] Buffer I/O error on device sdb, logical block 3
> [90838.389174] Buffer I/O error on device sdb, logical block 4
> [90838.389177] Buffer I/O error on device sdb, logical block 5
> [90838.389180] Buffer I/O error on device sdb, logical block 6
> [90838.389183] Buffer I/O error on device sdb, logical block 7
> [90838.389186] Buffer I/O error on device sdb, logical block 8
> [90838.389189] Buffer I/O error on device sdb, logical block 9
> [90838.389192] Buffer I/O error on device sdb, logical block 10
> [90838.502971] sd 10:0:0:0: [sdb] Unhandled error code
> [90838.502975] sd 10:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [90838.502980] end_request: I/O error, dev sdb, sector 0
> [90838.674599] sd 10:0:0:0: [sdb] Unhandled error code
> [90838.674602] sd 10:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [90838.674607] end_request: I/O error, dev sdb, sector 0
> [90840.751890] sd 10:0:0:0: [sdb] Unhandled error code
> [90840.751898] sd 10:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [90840.751907] end_request: I/O error, dev sdb, sector 0
Okay, thanks. It looks like the IGNORE_RESIDUE flag might also work.
But if MAX_SECTORS_64 is good enough, it's probably a better choice.
Have you tested this device with a microSD card inserted?
Alan Stern
Reply to: