SD card reader does not work

Bug #186115 reported by Francois Thirioux on 2008-01-26
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
Nominated for Intrepid by Sean McNamara

Bug Description

Hi,

My TI SD card reader still does not work (Hardy, Toshiba U200) : lsusb gives nothing. I know that there are some other bugs like that, but it's quite annoying that this card reader WAS working on Edgy, and a lot of us are disappointed of this regression since Feisty.

Thanks a lot for any solution.

Possible patch from Mandriva :

http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/updates/2008.0/kernel-2.6/current/PATCHES/patches/DB35_mmc_power_up_delay.patch?view=markup&pathrev=114631

lspci relevant outputs :

03:0b.2 Mass storage controller [0180]: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) [104c:803b]
 Subsystem: Toshiba America Info Systems Unknown device [1179:0001]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 64 (1750ns min, 1000ns max), Cache Line Size: 32 bytes
 Interrupt: pin D routed to IRQ 19
 Region 0: Memory at ffa05000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: <access denied>

03:0b.3 SD Host controller [0805]: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller [104c:803c] (prog-if 01)
 Subsystem: Toshiba America Info Systems Unknown device [1179:0001]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 64 (1750ns min, 1000ns max), Cache Line Size: 32 bytes
 Interrupt: pin D routed to IRQ 19
 Region 0: Memory at ffa06800 (32-bit, non-prefetchable) [size=256]
 Capabilities: <access denied>

Saivann Carignan (oxmosys) wrote :

Thanks for your bug report. To help identifying your device, can you attach the following files created by these commands on a terminal?

If your card reader is external (USB) : lsusb > lsusb.log
If your card reader is a part of your laptop : lspci -nnvv > lspci.log
dmesg > dmesg.log

Francois Thirioux (fthx) wrote :

here they are !

Thanks !

Francois Thirioux (fthx) wrote :

oups...

description: updated
Saivann Carignan (oxmosys) wrote :

Thanks for your fast answer! Can you remove your old dmesg.log file, reboot your computer and once your computer is successfully booted, insert a SD card in the SD card reader, wait 5 seconds, remove your SD card and then do again "dmesg > dmesg.log". If you attach that dmesg.log file, we will maybe have some helpful debugging informations.

Francois Thirioux (fthx) wrote :

I could do that, but I did that during my searches to solve this issue.
The dmesg shows absolutely nothing : nobody in my Ubuntu knows that my Toshiba owns a SD reader...

I was told that there was a patch at Mandriva :
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/updates/2008.0/kernel-2.6/current/PATCHES/patches/DB35_mmc_power_up_delay.patch?view=markup&pathrev=114631

Thanks again.

Saivann Carignan (oxmosys) wrote :

Can you do it anyway just to make sure? I saw :

[ 27.554372] mmc0: SDHCI at 0xffa06800 irq 19 DM

In your actual dmesg. Even if the device does not work properly, there's still some chances that we have some useful outputs. Thank your for all the information you provided so far.

Francois Thirioux (fthx) wrote :

here !

Saivann Carignan (oxmosys) wrote :

Thank your very much, you were right. In order to complete that bug report, can you attach the following files?

uname -a > uname.log
cat /proc/version_signature > version.log

description: updated
Francois Thirioux (fthx) wrote :

Linux ~ 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
Ubuntu 2.6.24-12.22-generic

Thanks

Saivann Carignan (oxmosys) wrote :
Saivann Carignan (oxmosys) wrote :
Changed in linux:
assignee: nobody → ubuntu-kernel-team
status: New → Confirmed
Saivann Carignan (oxmosys) wrote :

I assigned the bug to the linux kernel team, thanks for all the information that you provided. They have now all information to need to work on this bug. I hope that it will get fixed soon for you :)

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Sean McNamara (smcnam) wrote :

On behalf of a user on #ubuntu IRC:

1. The user is running Ubuntu 8.10 with the latest 2.6.27-generic packages.
2. The user has the tifm_* kernel modules loaded.
3. They are getting the same information in dmesg about the card detection when one is inserted (MMC, SD, xD tested).
4. No automounting; no /dev/mmcblk* device descriptors are created.
5. The user has the same top-level hardware as the original reporter, confirmed by PCI ID [104c:803b]. However, it appears that the "subsystem" of this user's device is different; the subsystem's PCI ID is [17ff:0590].

The IRC user did not indicate whether they have tested this device with another release of Ubuntu, but I was unable to help them resolve this problem. Can we please investigate whether the kernel actually tries to support these devices, and if so, what is the nature of the bug that is holding everything back? Unfortunately, I do not own one of these card readers, so I can't investigate in detail myself. They are shipped internally in select laptop models, so acquiring one for testing is not cheap.

Thanks,

Sean

Francois Thirioux, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: hardy
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers