Bug 781977 - Sandisk Cruzer , a USB SD Card reader, won't open with Fedora 16
Summary: Sandisk Cruzer , a USB SD Card reader, won't open with Fedora 16
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-16 08:48 UTC by Silvio Schneider
Modified: 2013-01-16 10:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-16 10:53:51 UTC
Type: ---


Attachments (Terms of Use)

Description Silvio Schneider 2012-01-16 08:48:32 UTC
Description of problem:
Apprently Jule Verne didn't have a digital camera.
When plugin in the SD Card reader nothing happens.
The /var/log/messages is showing this
Jan 14 16:57:56 tower kernel: [    2.130017] usb 7-1: new full speed USB 
device number 2 using uhci_hcd
Jan 14 16:57:56 tower kernel: [    2.243028] usb 7-1: device descriptor 
read/64, error -71
Jan 14 16:57:56 tower kernel: [    2.279347] pata_jmicron 0000:03:00.1: 
enabling device (0000 -> 0001)
Jan 14 16:57:56 tower kernel: [    2.279357] pata_jmicron 0000:03:00.1: 
PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jan 14 16:57:56 tower kernel: [    2.280649] scsi6 : pata_jmicron
Jan 14 16:57:56 tower kernel: [    2.281688] scsi7 : pata_jmicron
Jan 14 16:57:56 tower kernel: [    2.282189] ata7: PATA max UDMA/100 cmd 
0xdc00 ctl 0xd880 bmdma 0xd400 irq 17
Jan 14 16:57:56 tower kernel: [    2.282192] ata8: PATA max UDMA/100 cmd 
0xd800 ctl 0xd480 bmdma 0xd408 irq 17
Jan 14 16:57:56 tower kernel: [    2.457021] usb 7-1: device descriptor 
read/64, error -71
Jan 14 16:57:56 tower kernel: [    2.597190] firewire_ohci 0000:05:03.0: 
PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan 14 16:57:56 tower kernel: [    2.650056] firewire_ohci: Added 
fw-ohci device 0000:05:03.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x11
Jan 14 16:57:56 tower kernel: [    2.660017] usb 7-1: new full speed USB 
device number 3 using uhci_hcd
Jan 14 16:57:56 tower kernel: [    2.773038] usb 7-1: device descriptor 
read/64, error -71
Jan 14 16:57:56 tower kernel: [    2.987031] usb 7-1: device descriptor 
read/64, error -71
Jan 14 16:57:56 tower kernel: [    3.151138] firewire_core: created 
device fw0: GUID 001e8c00010aec51, S400
Jan 14 16:57:56 tower kernel: [    3.190028] usb 7-1: new full speed USB 
device number 4 using uhci_hcd
Jan 14 16:57:56 tower kernel: [    3.598071] usb 7-1: device not 
accepting address 4, error -71
Jan 14 16:57:56 tower kernel: [    3.700030] usb 7-1: new full speed USB 
device number 5 using uhci_hcd
Jan 14 16:57:56 tower kernel: [    4.108062] usb 7-1: device not 
accepting address 5, error -71
Jan 14 16:57:56 tower kernel: [    4.108074] hub 7-0:1.0: unable to 
enumerate USB device on port 1


Version-Release number of selected component (if applicable):
-

How reproducible:
Plugin in the Sandisk USB SD Card reader

  
Actual results:
The Cardreader LED blinks up, nothing else happens.

Expected results:
Gnome dialog with new drive should show up


Additional info:
The Sandisk Cruzer SD Card reade looks like this

http://bilder.preisvergleich.org/products/DE/800/000/012/984/E_000012984529_DE_800.jpg

This used to work in older of Fedora. I couldn't find a working workaround so far.

Comment 1 Dave Jones 2012-03-22 16:54:57 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 2 Dave Jones 2012-03-22 16:58:33 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 3 Dave Jones 2012-03-22 17:10:00 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 4 Silvio Schneider 2012-03-30 06:56:02 UTC
issue still exists with 
Linux tower 3.3.0-4.fc16.x86_64 #1 SMP Tue Mar 20 18:05:40 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

full log
Mar 30 08:53:00 tower dbus-daemon[899]: ** Message: No devices in use, exit
Mar 30 08:53:33 tower kernel: [  497.561031] usb 7-2: new full-speed USB device number 2 using uhci_hcd
Mar 30 08:53:33 tower kernel: [  497.775041] usb 7-2: New USB device found, idVendor=0781, idProduct=8888
Mar 30 08:53:33 tower kernel: [  497.775046] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 30 08:53:33 tower kernel: [  497.775050] usb 7-2: Product: Cruzer        
Mar 30 08:53:33 tower kernel: [  497.775052] usb 7-2: Manufacturer: SanDisk
Mar 30 08:53:33 tower kernel: [  497.775055] usb 7-2: SerialNumber: 0E2703000304
Mar 30 08:53:33 tower mtp-probe: checking bus 7, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-2"
Mar 30 08:53:33 tower mtp-probe: bus: 7, device: 2 was not an MTP device
Mar 30 08:53:33 tower kernel: [  498.062100] Initializing USB Mass Storage driver...
Mar 30 08:53:33 tower kernel: [  498.062314] scsi8 : usb-storage 7-2:1.0
Mar 30 08:53:33 tower kernel: [  498.062419] usbcore: registered new interface driver usb-storage
Mar 30 08:53:33 tower kernel: [  498.062422] USB Mass Storage support registered.
Mar 30 08:53:34 tower kernel: [  499.069074] scsi 8:0:0:0: Direct-Access     SanDisk  Cruzer           2.00 PQ: 0 ANSI: 0 CCS
Mar 30 08:53:34 tower kernel: [  499.070098] sd 8:0:0:0: Attached scsi generic sg2 type 0
Mar 30 08:53:39 tower kernel: [  503.641063] sd 8:0:0:0: [sdb] 1 512-byte logical blocks: (512 B/512 B)
Mar 30 08:53:39 tower kernel: [  503.644061] sd 8:0:0:0: [sdb] Write Protect is on
Mar 30 08:53:39 tower kernel: [  503.647056] sd 8:0:0:0: [sdb] No Caching mode page present
Mar 30 08:53:39 tower kernel: [  503.647060] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Mar 30 08:53:39 tower kernel: [  503.665056] sd 8:0:0:0: [sdb] No Caching mode page present
Mar 30 08:53:39 tower kernel: [  503.665062] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Mar 30 08:54:09 tower kernel: [  533.882032] usb 7-2: reset full-speed USB device number 2 using uhci_hcd
Mar 30 08:54:09 tower kernel: [  533.996028] usb 7-2: device descriptor read/64, error -71
Mar 30 08:54:10 tower kernel: [  534.261023] usb 7-2: device descriptor read/64, error -71
Mar 30 08:54:10 tower kernel: [  534.515021] usb 7-2: reset full-speed USB device number 2 using uhci_hcd
Mar 30 08:54:10 tower kernel: [  534.679026] usb 7-2: device descriptor read/64, error -71
Mar 30 08:54:10 tower kernel: [  534.945026] usb 7-2: device descriptor read/64, error -71
Mar 30 08:54:11 tower kernel: [  535.148027] usb 7-2: reset full-speed USB device number 2 using uhci_hcd
Mar 30 08:54:11 tower kernel: [  535.558053] usb 7-2: device not accepting address 2, error -71
Mar 30 08:54:11 tower kernel: [  535.660028] usb 7-2: reset full-speed USB device number 2 using uhci_hcd
Mar 30 08:54:11 tower kernel: [  536.069021] usb 7-2: device not accepting address 2, error -71
Mar 30 08:54:11 tower kernel: [  536.069049] usb 7-2: USB disconnect, device number 2
Mar 30 08:54:11 tower kernel: [  536.069083] sd 8:0:0:0: Device offlined - not ready after error recovery
Mar 30 08:54:11 tower kernel: [  536.069093] sd 8:0:0:0: [sdb] Unhandled error code
Mar 30 08:54:11 tower kernel: [  536.069096] sd 8:0:0:0: [sdb]  Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Mar 30 08:54:11 tower kernel: [  536.069101] sd 8:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
Mar 30 08:54:11 tower kernel: [  536.069112] end_request: I/O error, dev sdb, sector 0
Mar 30 08:54:11 tower kernel: [  536.069118] Buffer I/O error on device sdb, logical block 0
Mar 30 08:54:11 tower kernel: [  536.069228] Dev sdb: unable to read RDB block 0
Mar 30 08:54:11 tower kernel: [  536.069249]  sdb: unable to read partition table
Mar 30 08:54:11 tower kernel: [  536.069496] sd 8:0:0:0: [sdb] READ CAPACITY failed
Mar 30 08:54:11 tower kernel: [  536.069499] sd 8:0:0:0: [sdb]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Mar 30 08:54:11 tower kernel: [  536.069504] sd 8:0:0:0: [sdb] Sense not available.
Mar 30 08:54:11 tower kernel: [  536.069534] sd 8:0:0:0: [sdb] Write Protect is off
Mar 30 08:54:11 tower kernel: [  536.069554] sd 8:0:0:0: [sdb] Asking for cache data failed
Mar 30 08:54:11 tower kernel: [  536.069557] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Mar 30 08:54:11 tower kernel: [  536.069561] sd 8:0:0:0: [sdb] Attached SCSI removable disk
Mar 30 08:54:12 tower kernel: [  536.223024] usb 7-2: new full-speed USB device number 3 using uhci_hcd
Mar 30 08:54:12 tower kernel: [  536.387014] usb 7-2: device descriptor read/64, error -71
Mar 30 08:54:12 tower kernel: [  536.601022] usb 7-2: device descriptor read/64, error -71
Mar 30 08:54:12 tower kernel: [  536.804029] usb 7-2: new full-speed USB device number 4 using uhci_hcd
Mar 30 08:54:12 tower kernel: [  536.969028] usb 7-2: device descriptor read/64, error -71
Mar 30 08:54:13 tower kernel: [  537.234021] usb 7-2: device descriptor read/64, error -71
Mar 30 08:54:13 tower kernel: [  537.488028] usb 7-2: new full-speed USB device number 5 using uhci_hcd
Mar 30 08:54:13 tower kernel: [  537.897065] usb 7-2: device not accepting address 5, error -71
Mar 30 08:54:13 tower kernel: [  538.050025] usb 7-2: new full-speed USB device number 6 using uhci_hcd
Mar 30 08:54:14 tower kernel: [  538.458062] usb 7-2: device not accepting address 6, error -71
Mar 30 08:54:14 tower kernel: [  538.458074] hub 7-0:1.0: unable to enumerate USB device on port 2

Comment 5 Dave Jones 2012-10-23 15:40:02 UTC
# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 6 Silvio Schneider 2012-10-25 09:35:22 UTC
I am no on fedora 17
Kernel:
[root@tower ~]# uname -a
Linux tower 3.6.2-4.fc17.x86_64 #1 SMP Wed Oct 17 02:43:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

dmesg are looking better, but it's not getting automountanted. any advice?

[ 1910.812462] usb 2-1.4: new full-speed USB device number 5 using ehci_hcd
[ 1910.903550] usb 2-1.4: New USB device found, idVendor=0781, idProduct=8888
[ 1910.903554] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1910.903557] usb 2-1.4: Product: Cruzer        
[ 1910.903559] usb 2-1.4: Manufacturer: SanDisk
[ 1910.903562] usb 2-1.4: SerialNumber: 0E2703000304
[ 1910.904222] scsi7 : usb-storage 2-1.4:1.0
[ 1911.908059] scsi 7:0:0:0: Direct-Access     SanDisk  Cruzer           2.00 PQ: 0 ANSI: 0 CCS
[ 1911.911041] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 1911.914238] sd 7:0:0:0: [sdb] Attached SCSI removable disk
[ 1918.537578] sd 7:0:0:0: [sdb] 1 512-byte logical blocks: (512 B/512 B)
[ 1918.538438] sd 7:0:0:0: [sdb] Write Protect is on
[ 1918.538442] sd 7:0:0:0: [sdb] Mode Sense: 43 00 80 00
[ 1918.539278] sd 7:0:0:0: [sdb] No Caching mode page present
[ 1918.539281] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 1918.542903] sd 7:0:0:0: [sdb] No Caching mode page present
[ 1918.542906] sd 7:0:0:0: [sdb] Assuming drive cache: write through

Comment 7 Silvio Schneider 2012-10-25 09:36:54 UTC
there are some more messages comming, actually still doesn't work

[ 1949.404650] usb 2-1.4: device descriptor read/64, error -32
[ 1949.578398] usb 2-1.4: device descriptor read/64, error -32
[ 1949.752318] usb 2-1.4: reset full-speed USB device number 5 using ehci_hcd
[ 1950.154057] usb 2-1.4: device not accepting address 5, error -32
[ 1950.227217] usb 2-1.4: reset full-speed USB device number 5 using ehci_hcd
[ 1950.628810] usb 2-1.4: device not accepting address 5, error -32
[ 1950.629139] sd 7:0:0:0: Device offlined - not ready after error recovery
[ 1950.629150] sd 7:0:0:0: [sdb] Unhandled error code
[ 1950.629153] sd 7:0:0:0: [sdb]  
[ 1950.629155] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
[ 1950.629157] sd 7:0:0:0: [sdb] CDB: 
[ 1950.629158] Read(10): 28 00 00 00 00 00 00 00 01 00
[ 1950.629168] end_request: I/O error, dev sdb, sector 0
[ 1950.629172] Buffer I/O error on device sdb, logical block 0
[ 1950.629205] sd 7:0:0:0: rejecting I/O to offline device
[ 1950.629223] sd 7:0:0:0: rejecting I/O to offline device
[ 1950.629246] usb 2-1.4: USB disconnect, device number 5
[ 1950.629334] Dev sdb: unable to read RDB block 0
[ 1950.629349]  sdb: unable to read partition table
[ 1950.629598] sdb: detected capacity change from 512 to 0
[ 1950.702974] usb 2-1.4: new full-speed USB device number 6 using ehci_hcd
[ 1950.776781] usb 2-1.4: device descriptor read/64, error -32
[ 1950.950703] usb 2-1.4: device descriptor read/64, error -32
[ 1951.124602] usb 2-1.4: new full-speed USB device number 7 using ehci_hcd
[ 1951.197538] usb 2-1.4: device descriptor read/64, error -32
[ 1951.371590] usb 2-1.4: device descriptor read/64, error -32
[ 1951.545383] usb 2-1.4: new full-speed USB device number 8 using ehci_hcd
[ 1951.947068] usb 2-1.4: device not accepting address 8, error -32
[ 1952.020125] usb 2-1.4: new full-speed USB device number 9 using ehci_hcd
[ 1952.421892] usb 2-1.4: device not accepting address 9, error -32
[ 1952.422064] hub 2-1:1.0: unable to enumerate USB device on port 4

Comment 8 Silvio Schneider 2013-01-16 10:53:51 UTC
I have tried the sd card reader on a windows xp machine. It can regonize it, but is unable to show any data from the sd card. 

One thing that could be that is that my SD Card is to big.
The card is 4GB. The reader is probably unable to read such big cards. Time to through it away, or better recycle it.


Note You need to log in before you can comment on or make changes to this bug.