O2 Micro cardreader [1217:8621] could not read a specific mmc card

[Taihsiang Ho]

Dell Inspiron 3048 (CID 201401-14493) on Ubuntu 14.04.1

Steps to reproduce the bug:
1. boot the system, login and wait for the desktop ready to use
2. plugin mmc card

Expected result:
mmc directory will pop up and ready to use it.

Actual result:
no thing pop up on desktop

----------- dmesg ----------

[ 41.180392] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
[ 51.210537] mmc0: Timeout waiting for hardware interrupt.
[ 51.212627] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
[ 61.229658] mmc0: Timeout waiting for hardware interrupt.
[ 61.231738] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
[ 71.248714] mmc0: Timeout waiting for hardware interrupt.
[ 71.250815] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
[ 81.267947] mmc0: Timeout waiting for hardware interrupt.
[ 81.270026] mmc0: error -110 whilst initialising MMC card
[ 81.377041] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
[ 86.065388] mmc0: Card removed during transfer!
[ 86.065398] mmc0: Resetting controller.
[ 86.065544] mmc0: error -123 whilst initialising MMC card

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: boot/vmlinuz-3.13.0-32-generic]
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1447 F.... pulseaudio
 /dev/snd/controlC1: ubuntu 1447 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri Nov 28 05:20:43 2014
HibernationDevice: RESUME=UUID=265f8dc9-0dff-4a1b-9a3b-08fb662a7daf
InstallationDate: Installed on 2014-11-26 (2 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 20 Model 3048
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=f35024ba-c412-4316-8474-bd2a586c6c1b ro rootdelay=60 quiet splash initcall_debug vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X19
dmi.board.name: 0HD5K4
dmi.board.vendor: Dell Inc.
dmi.board.version: X02
dmi.chassis.type: 13
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrX19:bd12/18/2013:svnDellInc.:pnInspiron20Model3048:pvr01:rvnDellInc.:rn0HD5K4:rvrX02:cvnDellInc.:ct13:cvr:
dmi.product.name: Inspiron 20 Model 3048
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Taihsiang Ho, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product-support/product/inspiron-20-3048-aio/drivers an update to your BIOS is available (A03). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc7-vivid/

[Adam Lee (adam8157)]

I would like to know the testing results of #3 and #4 too, @Taihsiang Ho, could you please? thanks.

[Taihsiang Ho (tai271828)]

This issue could reproduce by a transcend mmc but not by another unknown brand mmc.

[Taihsiang Ho (tai271828)]

I tried mainline 3.19 kernel and could reproduce as same as
"This issue could reproduce by a transcend mmc but not by another unknown brand mmc."
described in comment #6

-----------------------------

Besides, there are other interesting tests I have done:
a transcend mmc could reproduce this issue on:
system-A: 12.04.5 with cardreader[10ec:5229] of machine CID 201209-11634
system-B: 14.04.1(3.13.0-32) with cardreader[10ec:5229] of machine CID 201401-14493 (reported as this bug)
system-C: 14.04.1(mainline 3.19) with cardreader[10ec:5229] of machine CID 201401-14493

and could NOT reproduce this issue on:
system-D: 12.04.5 (3.13.0-40) with [0bda:0177] Realtek Semiconductor Corp. (this is a usb device and its info dumped by lsusb)
system-E: 14.04.1(3.13.0-46-generic) with [0bda:0158] Realtek Semiconductor Corp. USB 2.0 multicard reader

-----------------------------

the unknown brand mmc could NOT reproduce this issue:
system-A: not tested
system-B: could not reproduce.
system-C: could not reproduce.
system-D: could not reproduce.
system-E: could not reproduce.

There is no plan to update BIOS.

[Adam Lee (adam8157)]

O2Micro engineer confirmed it's a known issue, please test this kernel: http://kernel.ubuntu.com/~adamlee/lp1397285/

[Taihsiang Ho (tai271828)]

tested the comment #8, the issue could be reproduced.

attachment:
dmesg-for-comment-8-transcend-mmc.log - dmesg when reproducing this issue by the transcend mmc.
dmesg-for-comment-8-plug-a-workable-card - dmesg when NOT reproducing (mmc could be read) this issue by the other mmc card.

[Taihsiang Ho (tai271828)]

test steps:
1. plugin the transcend mmc which reproduces this bug.
2. plug-out mmc in step 1, plugin the other mmc which does not reproduce this bug.
3. plug-out mmc in step 2, re-plugin the transcend mmc in step 1.

result:
(tested with kernel 3.13.0-32)
the transcend mmc could now be read.

(tested with kernel in comment 8)
the transcend mmc is still not working.

[Adam Lee (adam8157)]

mail from vendor:

> I read the bug description and find below info:
>
> (1) The original error log is:
>
>
> [ 41.180392] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
> [ 51.210537] mmc0: Timeout waiting for hardware interrupt.
> [ 51.212627] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
> [ 61.229658] mmc0: Timeout waiting for hardware interrupt.
> [ 61.231738] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
> [ 71.248714] mmc0: Timeout waiting for hardware interrupt.
> [ 71.250815] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
> [ 81.267947] mmc0: Timeout waiting for hardware interrupt.
> [ 81.270026] mmc0: error -110 whilst initialising MMC card
> [ 81.377041] mmc0: Got data interrupt 0x02000000 even though no data operation was in progress.
> [ 86.065388] mmc0: Card removed during transfer!
> [ 86.065398] mmc0: Resetting controller.
> [ 86.065544] mmc0: error -123 whilst initialising MMC card
>
>
> (2) After add quirks2 , the error log is:
> mmcblk0: error -84 transferring data, sector 128, nr 8, cmd response 0x900, card status 0x0
> [ 3.871994] mmcblk0: retrying using single block read
> [ 3.874248] mmcblk0: error -84 transferring data, sector 128, nr 8, cmd response 0x900, card status 0x0
> [ 3.876503] mmcblk0: error -84 transferring data, sector 129, nr 7, cmd response 0x900, card status 0x0
> [ 3.878758] mmcblk0: error -84 transferring data, sector 130, nr 6, cmd response 0x900, card status 0x0
> [ 3.881013] mmcblk0: error -84 transferring data, sector 131, nr 5, cmd response 0x900, card status 0x0
> [ 3.883268] mmcblk0: error -84 transferring data, sector 132, nr 4, cmd response 0x900, card status 0x0
> [ 3.885523] mmcblk0: error -84 transferring data, sector 133, nr 3, cmd response 0x900, card status 0x0
> [ 3.887778] mmcblk0: error -84 transferring data, sector 134, nr 2, cmd response 0x900, card status 0x0
> [ 3.890032] mmcblk0: error -84 transferring data, sector 135, nr 1, cmd response 0x900, card status 0x0
> [ 3.894348] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x400900
>
> Analysis: (1) The First failed is our known issue, it is failed at init stage.
> (2) After the known issue is fixed, log 2 is another issue.
>
> In order to debug issue, could you show me the picture of the transcend mmc card you use?

[Taihsiang Ho (tai271828)]

picture for comment 13 - the transcend mmc card which could reproduce this bug.

[Adam Lee (adam8157)]

@Taihsiang

Please test with this debug kernel: http://kernel.ubuntu.com/~adamlee/lp1397285_debug It will fail, but dmesg will show lots of debugging informations we need. Thanks!

[Taihsiang Ho (tai271828)]

attachment comment15-150416-log.tar.gz was collected by:

1. dpkg -i the debs provided in the comment 15
2. reboot
3. insert a mmc which could NOT reproduce this issue. collect dmesg
4. insert a mmc which could reproduce this issue (the transcend one). collect dmesg

in attachment:
dpkg-l-* - message dumped by dpkg -l for you to confirm the packages status when I collected dmesg.
dmesg-* - dmesg info mentioned in step 3 and 4
uname-a.log: shown the kernel the system used when collecting dmesg.

[Taihsiang Ho (tai271828)]

I also tried the trans mmc which could reproduce this bug on CID 201401-14493,
on another 14.04.1 system.

This mmc could be read and written data normally.
dmesg-working-trans.log is the dmesg collected by that 14.04.1 system for your reference.

[Adam Lee (adam8157)]

only affects that single very specific mmc card, set to won't fix