Bug 43164 - FC card not detected/mounted via external multicard reader
Summary: FC card not detected/mounted via external multicard reader
Status: RESOLVED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-25 19:48 UTC by Damjan
Modified: 2015-02-19 17:51 UTC (History)
4 users (show)

See Also:
Kernel Version: 3.0.0-17-generic
Subsystem:
Regression: No
Bisected commit-id:


Attachments
CPU info (6.43 KB, text/plain)
2012-04-25 19:48 UTC, Damjan
Details
modules while attached directly to laptop (3.42 KB, text/plain)
2012-04-25 19:50 UTC, Damjan
Details
IO ports while attached directly (1.14 KB, text/plain)
2012-04-25 19:51 UTC, Damjan
Details
IO mem while attached directly (3.48 KB, text/plain)
2012-04-25 19:51 UTC, Damjan
Details
lspci (55.99 KB, application/octet-stream)
2012-04-25 19:52 UTC, Damjan
Details
scsi (976 bytes, application/octet-stream)
2012-04-25 19:53 UTC, Damjan
Details
usbmon output collected while reader is connected to the dock USB port (1.70 KB, application/octet-stream)
2012-09-18 16:35 UTC, Damjan
Details
usbmon data after reader is connected on a dock port (129.06 KB, application/octet-stream)
2012-09-21 23:18 UTC, Damjan
Details

Description Damjan 2012-04-25 19:48:09 UTC
Hi,
trying to mount compact flash card via external multicard reader gives different results on different ports, but it fails in all cases to detect and mount the card.

If reader is attached directly to the laptop (Thinkpad W510) to the ports on the left side of it, the reader is recognized, but not CF card insterted afterwards (...xhci_hcd 0000:0f:00.0: xHCI xhci_drop_endpoint called with disabled ep...)

In case reader is attached via ports on docking station, it fails to accept even the reader itself (kernel loops trying to accept it: ... READ CAPACITY failed ...)


Kernel version:
Linux version 3.0.0-17-generic (buildd@yellow) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #30-Ubuntu SMP Thu Mar 8 20:45:39 UTC 2012

No Oopses...

TIA,
Damjan

P.S.: it seems only one file can be attached at the bug report time. I expect the rest can be uploaded afterwards.
Comment 1 Damjan 2012-04-25 19:48:53 UTC
Created attachment 73085 [details]
CPU info
Comment 2 Damjan 2012-04-25 19:50:11 UTC
Created attachment 73086 [details]
modules while attached directly to laptop
Comment 3 Damjan 2012-04-25 19:51:04 UTC
Created attachment 73087 [details]
IO ports while attached directly
Comment 4 Damjan 2012-04-25 19:51:51 UTC
Created attachment 73088 [details]
IO mem while attached directly
Comment 5 Damjan 2012-04-25 19:52:51 UTC
Created attachment 73089 [details]
lspci
Comment 6 Damjan 2012-04-25 19:53:45 UTC
Created attachment 73090 [details]
scsi
Comment 7 Damjan 2012-04-25 20:05:12 UTC
For some reasons syslog cannot be attached. Here it is as a comment.

From syslog - entries when attached directly:
Apr 25 18:59:14 think kernel: [29252.633525] usb 3-1.4: new full speed USB device number 6 using xhci_hcd
Apr 25 18:59:14 think kernel: [29252.660509] usb 3-1.4: not running at top speed; connect to a high speed hub
Apr 25 18:59:15 think mtp-probe: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:1c.6/0000:0f:00.0/usb3/3-1/3-1.4"
Apr 25 18:59:15 think kernel: [29252.680751] scsi9 : usb-storage 3-1.4:1.0
Apr 25 18:59:15 think mtp-probe: bus: 3, device: 6 was not an MTP device
Apr 25 18:59:16 think kernel: [29253.683055] scsi 9:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
Apr 25 18:59:16 think kernel: [29253.683684] scsi 9:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
Apr 25 18:59:16 think kernel: [29253.684449] scsi 9:0:0:2: Direct-Access     Generic  USB xD/SM Reader 1.02 PQ: 0 ANSI: 0
Apr 25 18:59:16 think kernel: [29253.685141] scsi 9:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
Apr 25 18:59:16 think kernel: [29253.927310] sd 9:0:0:0: Attached scsi generic sg2 type 0
Apr 25 18:59:16 think kernel: [29253.927484] sd 9:0:0:1: Attached scsi generic sg3 type 0
Apr 25 18:59:16 think kernel: [29253.927642] sd 9:0:0:2: Attached scsi generic sg4 type 0
Apr 25 18:59:16 think kernel: [29253.927803] sd 9:0:0:3: Attached scsi generic sg5 type 0
Apr 25 18:59:16 think kernel: [29253.932498] sd 9:0:0:0: [sdb] Attached SCSI removable disk
Apr 25 18:59:16 think kernel: [29253.932997] sd 9:0:0:1: [sdc] Attached SCSI removable disk
Apr 25 18:59:16 think kernel: [29253.933442] sd 9:0:0:2: [sdd] Attached SCSI removable disk
Apr 25 18:59:16 think kernel: [29253.933947] sd 9:0:0:3: [sde] Attached SCSI removable disk
Apr 25 19:00:39 think kernel: [29337.196008] usb 3-1.4: reset full speed USB device number 6 using xhci_hcd
Apr 25 19:00:39 think kernel: [29337.222992] xhci_hcd 0000:0f:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880121af1c80
Apr 25 19:00:39 think kernel: [29337.222999] xhci_hcd 0000:0f:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880121af1cc0
Apr 25 19:00:40 think kernel: [29337.735732] usb 3-1.4: reset full speed USB device number 6 using xhci_hcd
Apr 25 19:00:40 think kernel: [29337.762773] xhci_hcd 0000:0f:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880121af1c80
Apr 25 19:00:40 think kernel: [29337.762780] xhci_hcd 0000:0f:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880121af1cc0
Apr 25 19:00:40 think kernel: [29337.959667] usb 3-1.4: reset full speed USB device number 6 using xhci_hcd




From syslog - when attached via docking station:
Apr 25 19:05:15 think kernel: [29613.270278] usb 1-1.5.3: new high speed USB device number 13 using ehci_hcd
Apr 25 19:05:15 think kernel: [29613.365414] scsi20 : usb-storage 1-1.5.3:1.0
Apr 25 19:05:15 think mtp-probe: checking bus 1, device 13: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3"
Apr 25 19:05:15 think mtp-probe: bus: 1, device: 13 was not an MTP device
Apr 25 19:05:16 think kernel: [29614.363383] scsi 20:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
Apr 25 19:05:16 think kernel: [29614.364124] scsi 20:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
Apr 25 19:05:16 think kernel: [29614.364813] scsi 20:0:0:2: Direct-Access     Generic  USB xD/SM Reader 1.02 PQ: 0 ANSI: 0
Apr 25 19:05:16 think kernel: [29614.365566] scsi 20:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
Apr 25 19:05:16 think kernel: [29614.466797] sd 20:0:0:0: Attached scsi generic sg2 type 0
Apr 25 19:05:16 think kernel: [29614.466952] sd 20:0:0:1: Attached scsi generic sg3 type 0
Apr 25 19:05:16 think kernel: [29614.467115] sd 20:0:0:2: Attached scsi generic sg4 type 0
Apr 25 19:05:16 think kernel: [29614.467270] sd 20:0:0:3: Attached scsi generic sg5 type 0
Apr 25 19:05:17 think kernel: [29614.590409] usb 1-1.5.3: USB disconnect, device number 13
Apr 25 19:05:17 think kernel: [29614.590795] sd 20:0:0:0: [sdb] Attached SCSI removable disk
Apr 25 19:05:17 think kernel: [29614.590824] sd 20:0:0:3: [sde] READ CAPACITY failed
Apr 25 19:05:17 think kernel: [29614.590829] sd 20:0:0:3: [sde]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Apr 25 19:05:17 think kernel: [29614.590834] sd 20:0:0:3: [sde] Sense not available.
Apr 25 19:05:17 think kernel: [29614.590871] sd 20:0:0:1: [sdc] READ CAPACITY failed
Apr 25 19:05:17 think kernel: [29614.590876] sd 20:0:0:3: [sde] Write Protect is off
Apr 25 19:05:17 think kernel: [29614.590881] sd 20:0:0:3: [sde] Mode Sense: 00 00 00 00
Apr 25 19:05:17 think kernel: [29614.590886] sd 20:0:0:1: [sdc]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Apr 25 19:05:17 think kernel: [29614.590891] sd 20:0:0:1: [sdc] Sense not available.
Apr 25 19:05:17 think kernel: [29614.590917] sd 20:0:0:2: [sdd] READ CAPACITY failed
Apr 25 19:05:17 think kernel: [29614.590922] sd 20:0:0:3: [sde] Asking for cache data failed
Apr 25 19:05:17 think kernel: [29614.590926] sd 20:0:0:3: [sde] Assuming drive cache: write through
Apr 25 19:05:17 think kernel: [29614.590931] sd 20:0:0:2: [sdd]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Apr 25 19:05:17 think kernel: [29614.590935] sd 20:0:0:2: [sdd] Sense not available.
Apr 25 19:05:17 think kernel: [29614.590958] sd 20:0:0:1: [sdc] Write Protect is off
Apr 25 19:05:17 think kernel: [29614.590962] sd 20:0:0:1: [sdc] Mode Sense: 00 00 00 00
Apr 25 19:05:17 think kernel: [29614.590974] sd 20:0:0:2: [sdd] Write Protect is off
Apr 25 19:05:17 think kernel: [29614.590977] sd 20:0:0:2: [sdd] Mode Sense: 00 00 00 00
Apr 25 19:05:17 think kernel: [29614.590996] sd 20:0:0:2: [sdd] Asking for cache data failed
Apr 25 19:05:17 think kernel: [29614.591000] sd 20:0:0:2: [sdd] Assuming drive cache: write through
Apr 25 19:05:17 think kernel: [29614.591176] sd 20:0:0:3: [sde] Attached SCSI removable disk
Apr 25 19:05:17 think kernel: [29614.591219] sd 20:0:0:1: [sdc] Asking for cache data failed
Apr 25 19:05:17 think kernel: [29614.591222] sd 20:0:0:1: [sdc] Assuming drive cache: write through
Apr 25 19:05:17 think kernel: [29614.591454] sd 20:0:0:2: [sdd] Attached SCSI removable disk
Apr 25 19:05:17 think kernel: [29614.591461] sd 20:0:0:1: [sdc] Attached SCSI removable disk
Apr 25 19:05:17 think kernel: [29615.125628] usb 1-1.5.3: new high speed USB device number 14 using ehci_hcd
Apr 25 19:05:17 think kernel: [29615.220958] scsi21 : usb-storage 1-1.5.3:1.0
Apr 25 19:05:17 think mtp-probe: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5.3"
Apr 25 19:05:17 think mtp-probe: bus: 1, device: 14 was not an MTP device
Comment 8 Alan 2012-09-06 11:13:38 UTC
There are two things going on here by the look of it

Firstly the device doesn't like the USB3 port. That may be a hardware problem, certainly we see lots of stuff with compatibility problems that behaves this way. The second one with it looping may be a problem with how it behaves that is confusing the USB storage driver.

Cc's added
Comment 9 Alan Stern 2012-09-06 15:20:19 UTC
Damjan, can you attach a usbmon trace showing what happens when the reader is attached through the docking station?
Comment 10 Damjan 2012-09-18 16:35:10 UTC
Created attachment 80491 [details]
usbmon output collected while reader is connected to the dock USB port

output is attached - hope this is what you expect (http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt)
Comment 11 Alan Stern 2012-09-19 16:54:39 UTC
No, your dock.out file doesn't show anything.  Maybe you were monitoring the wrong bus; according to your logs above it should have been bus 1, not bus 3.
Comment 12 Damjan 2012-09-21 23:17:35 UTC
Ok, sorry for the inconvenience. I've tried again.

This is the device detected (from /sys fs):
T:  Bus=01 Lev=03 Prnt=03 Port=02 Cnt=01 Dev#= 21 Spd=12   MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=058f ProdID=6362 Rev= 1.00
S:  Manufacturer=Generic
S:  Product=Mass Storage Device
S:  SerialNumber=058F63626376
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms

Therefore following is used to collect data:
cat /sys/kernel/debug/usb/usbmon/1u > /tmp/dock_2.out

1u for Bus=01, right?

Output is attached.
Comment 13 Damjan 2012-09-21 23:18:26 UTC
Created attachment 80681 [details]
usbmon data after reader is connected on a dock port
Comment 14 Alan Stern 2012-09-22 02:04:44 UTC
The usbmon data shows pretty clearly that something is broken, either the reader or the CF card (if the card was inserted when you collected the usbmon trace -- was it?).

The reader exposes 4 logical units, LUN 0 - LUN 3.  LUNs 0, 2, 3 consistently give "Medium Not Present" status codes.  However all accesses to LUN 1, which presumably is the LUN used for CF cards, cause the reader to crash.  The computer resets it, and then exactly the same thing happens again -- over and over, about 30 times in the trace.

Has this reader ever worked attached to any computer?
Comment 15 Damjan 2012-09-23 05:34:28 UTC
The card was inserted in the reader all the time.

The card is readable on another embedded Linux machine.

The reader worked with the card on Windows XP. It didn't work on Windows 7.
Comment 16 Alan Stern 2012-09-23 15:28:55 UTC
I suggest you exchange the reader for a device that works better.

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