SDHC card fails to initialize with error -110

[David Ames]

I am running an up to date oneiric install on a Lenovo X220i.

When I put my Lexar 4GB SDHC card in the reader dmesg shows:

[45040.698830] mmc0: error -110 whilst initialising SD card

After a few seconds then hundreds of the folloing I/O errors:

[45050.981675] end_request: I/O error, dev mmcblk0, sector 131
[45050.981759] mmcblk0: error -110 sending status command
[45050.981762] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[45050.981765] end_request: I/O error, dev mmcblk0, sector 132
[45050.981849] mmcblk0: error -110 sending status command
[45050.981852] mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[45050.981855] end_request: I/O error, dev mmcblk0, sector 133

The SD card works fine in another system running Natty. This has lasted through several oneiric kernel updates.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu2
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thedac 2003 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xd2520000 irq 44'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:14f1506e,17aa21da,00100000 HDA:80862805,80860101,00100000'
   Controls : 20
   Simple ctrls : 8
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown'
   Mixer name : 'ThinkPad EC (unknown)'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=/dev/sda5
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
MachineType: LENOVO 4286CTO
Package: linux (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae root=UUID=0b6a7836-c45f-47ab-a3aa-8501544d39db ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic-pae N/A
 linux-backports-modules-3.0.0-12-generic-pae N/A
 linux-firmware 1.60
StagingDrivers: mei
Tags: oneiric running-unity staging
Uname: Linux 3.0.0-12-generic-pae i686
UpgradeStatus: Upgraded to oneiric on 2011-09-12 (16 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET42WW (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4286CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET42WW(1.12):bd04/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4286CTO
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 861668

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[David Ames (thedac)]

apport information

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest release candidate kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Thanks in advance.

[DataGovernor (adler1)]

I have the experienced the same bug in my Thinkpad x220i 4290CP2 and tested it with the kernel that shipped with Ubuntu 11.10 and just now again with kernel 3.1 and neither fixes this problem. I have also tried to access my SDHC cards in my Canon 60D camera via USB and ubuntu also does not recognize the card in the camera.

[ 86.452528] mmc0: error -110 whilst initialising SD card
[ 96.453669] mmc0: Timeout waiting for hardware interrupt.
[ 96.453677] sdhci: =========== REGISTER DUMP (mmc0)===========
[ 96.453685] sdhci: Sys addr: 0x00000000 | Version: 0x00000502
[ 96.453692] sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
[ 96.453699] sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[ 96.453706] sdhci: Present: 0x01f70001 | Host ctl: 0x00000005
[ 96.453713] sdhci: Power: 0x00000000 | Blk gap: 0x00000000
[ 96.453720] sdhci: Wake-up: 0x00000000 | Clock: 0x00000000
[ 96.453726] sdhci: Timeout: 0x00000009 | Int stat: 0x00000000
[ 96.453734] sdhci: Int enab: 0x00ff0083 | Sig enab: 0x00ff0083
[ 96.453741] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 96.453749] sdhci: Caps: 0x21e8c8b2 | Caps_1: 0x00008073
[ 96.453756] sdhci: Cmd: 0x00000102 | Max curr: 0x00000040
[ 96.453761] sdhci: Host ctl2: 0x00000000
[ 96.453763] sdhci: ===========================================

This bug is not fixed.

[DataGovernor (adler1)]

kernel-bug-exists-upstream

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[DataGovernor (adler1)]

I notice that this bug was reported before in other distributions in upstream kernels:

https://bbs.archlinux.org/viewtopic.php?id=125813

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/787606

I have tried to file an upstream bug report on bugzilla.kernel.org but that site does not work.

[Joseph Salisbury (jsalisbury)]

Yes, it appears that bugzilla.kernel.org is still unavailable. I added the tag: kernel-needs-upstream-bug-report which will allow us to see what bugs still need to be reported upstream when bugzilla.kernel.org is back.

[DataGovernor (adler1)]

I found a fix for this that I tested and it works. See here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/773524

[DataGovernor (adler1)]

I want to add that this fix is only temporary. See #13 in my link earlier. This fix only works when you invoke a series of commands:

sudo setpci -v -d 1180:e823 f9.B=fc
sudo setpci -v -d 1180:e823 150.B=10
sudo setpci -v -d 1180:e823 f9.B=00
sudo setpci -v -d 1180:e823 fc.B=01
sudo setpci -v -d 1180:e823 e1.B=32
sudo setpci -v -d 1180:e823 fc.B=00

sudo rmmod sdhci_pci
sudo rmmod sdhci
sudo modprobe sdhci
sudo modprobe sdhci_pci

However, this fix is in none of the kernels so it is not permanent. But it would be great if this could be added to one of the upstream kernels.

[timobaumann (timobaumann)]

this fix mentioned in the previous comment is still necessary on every reboot to make the SD card reader work in my Thinkpad T420s, even though bug 773524 has been marked fixed ages ago.

It would be nice if us Lenovo users were not left behind Toshiba Tecra users...

[penalvch (penalvch)]

David Ames, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

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

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[David Ames (thedac)]

I reported this bug on oneric. It has been solved for me since precise. I am currently running saucy with the same hardware and it works just fine.

Sounds like others may still have a problem though.

[penalvch (penalvch)]

David Ames, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/861668/comments/33 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Regarding others who may have bugs, they would need to file separate reports. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.