mmc0: Got command interrupt 0x00030000 even though no command operation was in progress.

Mainline 2.6.35-999-generic #201007091441 works without issues ...

Hi Jean-Louis,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please 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 604122

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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Seems to occur in latest kernel: 2.6.35-19-generic

It seems like its because of the change in the kernel config:

+CONFIG_MMC_RICOH_MMC=y

If we disable it again, so old module gets used, it runs perfect again!

Another note is that it always seem to work when an SD-card is plugged in @ boottime.

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fradi 1531 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xf4480000 irq 18'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10250127,00100003 HDA:11c11040,10250127,00100200'
   Controls : 22
   Simple ctrls : 13
DistroRelease: Ubuntu 10.10
HibernationDevice: RESUME=UUID=ec1771de-9b18-4f38-a077-1af373417341
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100918)
MachineType: Acer, inc. Aspire 4520
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=44fce413-7aab-434f-b143-74ebb6600484 ro quiet splash
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Regression: Yes
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: ubuntu-une maverick kernel-fs regression-release needs-upstream-testing
Uname: Linux 2.6.35-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/14/2008
dmi.bios.vendor: Acer
dmi.bios.version: v1.3632
dmi.board.name: Mono
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrv1.3632:bd05/14/2008:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 4520
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Same behavior here. Adding apport information.

Further observations:
 - my HP PSC 2355 printer could not read the SD card either (error message on the printer screen)
 - my computer has been able to mount and normally read / write on the card before.

I had borrowed the card from friends and i've given it back now so i won't be able to test it further.

@Jean-Louis: you might want to format the card with your camera and see if the problem persists. I suspect that the bug is triggered by a particular state of the file-system on the SD card.

Formatted the card in FAT32. Same issue.

I just installed the newest daily kernel, and I got the following error:
[ 120.070050] r852: detected xD writeable card in slot
[ 120.338535] ------------[ cut here ]------------
[ 120.338568] WARNING: at /home/kernel-ppa/COD/linux/drivers/mtd/nand/r852.c:776 r852_irq+0x1ee/0x250 [r852]()
[ 120.338574] Hardware name: MP061
[ 120.338578] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat mmc_block cryptd aes_x86_64 aes_generic ip6table_filter ip6_tables binfmt_misc rfcomm sco bnep l2cap ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp sit tunnel4 parport_pc ppdev snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_usb_audio snd_hwdep snd_usbmidi_lib snd_pcm snd_seq_midi nouveau snd_rawmidi snd_seq_midi_event snd_seq snd_timer arc4 snd_seq_device ttm drm_kms_helper drm snd i2c_algo_bit iwl3945 iwlcore mac80211 r852 soundcore video snd_page_alloc intel_agp btusb psmouse sm_common nand nand_ids nand_ecc mtd serio_raw output dell_laptop dcdbas cfg80211 shpchp lp dell_wmi bluetooth joydev parport usbhid hid b44 firewire_ohci sdhci_pci firewire_core sdhci crc_itu_t ssb mii led_class
[ 120.338708] Pid: 0, comm: swapper Not tainted 2.6.36-999-generic #201010180905
[ 120.338712] Call Trace:
[ 120.338717] <IRQ> [<ffffffffa026effe>] ? r852_irq+0x1ee/0x250 [r852]
[ 120.338739] [<ffffffff810626f0>] warn_slowpath_common+0x90/0xc0
[ 120.338747] [<ffffffff8106273a>] warn_slowpath_null+0x1a/0x20
[ 120.338757] [<ffffffffa026effe>] r852_irq+0x1ee/0x250 [r852]
[ 120.338766] [<ffffffff810cd297>] handle_IRQ_event+0x57/0x150
[ 120.338774] [<ffffffff810cfe43>] handle_fasteoi_irq+0x93/0x120
[ 120.338782] [<ffffffff8100d934>] handle_irq+0x24/0x40
[ 120.338790] [<ffffffff8159066f>] do_IRQ+0x6f/0xf0
[ 120.338798] [<ffffffff81588b13>] ret_from_intr+0x0/0x11
[ 120.338802] <EOI> [<ffffffff81339b87>] ? acpi_idle_enter_bm+0x1c2/0x1ff
[ 120.338818] [<ffffffff81339b80>] ? acpi_idle_enter_bm+0x1bb/0x1ff
[ 120.338827] [<ffffffff81470e7e>] cpuidle_idle_call+0x8e/0x130
[ 120.338836] [<ffffffff81009764>] cpu_idle+0xa4/0x120
[ 120.338844] [<ffffffff8156da82>] rest_init+0x72/0x80
[ 120.338854] [<ffffffff81ae8efa>] start_kernel+0x29a/0x380
[ 120.338861] [<ffffffff81ae8140>] ? early_idt_handler+0x0/0x71
[ 120.338869] [<ffffffff81ae8325>] x86_64_start_reservations+0x65/0xa0
[ 120.338876] [<ffffffff81ae843d>] x86_64_start_kernel+0xbd/0xe0
[ 120.338882] ---[ end trace 32b1a2e720cf1dd3 ]---
[ 120.380108] No NAND device found.

Wouldn't it make sense to release an update with

+CONFIG_MMC_RICOH_MMC=y

switched off as a workaround until the bug has been correctly fixed if this resolves the problem with our card readers?

Ok had a quick look at this option. Seems it got enabled as part of rebasing forward for Maverick. It seems that for v2.6.36 that this version of the diable was deprecated in favour of a better mechanism, and in that commit they note that it did not work so well either:

  commit ccc92c23240cdf952ef7cc39ba563910dcbc9cbe
  Author: Maxim Levitsky <email address hidden>
  Date: Tue Aug 10 18:01:42 2010 -0700

    mmc: make sdhci work with ricoh mmc controller

    The current way of disabling it is not well tested by vendor and has all
    kinds of bugs that show up on resume from ram/disk. A very good example
    is a dead SDHCI controller.

    Old way of disabling is still supported by continuing to use
    CONFIG_MMC_RICOH_MMC.

    Based on 'http://list.drzeus.cx/pipermail/sdhci-devel/2007-December/002085.html'
    Therefore most of the credit for this goes to Andrew de Quincey

From this write up it seems appropriate for kernels on v2.6.36 and later to turn this off expecting the device to work correctly without, it may also be appropriate to disable this work around in Maverick but that is less clear. I will put together a Natty test kernel with this change for testing. If that works ok we can try older releases.

Ok I have spun a patch to disable this option in Natty, could those of you who have this H/W test the kernels at the URL below and indicate here if they work for you. These kernels should work on Maverick too, thanks:

    http://people.canonical.com/~apw/lp604122-natty/

@Andy: i've tried this kernel with Maverick, no luck. It hangs on boot on my acer 4520.

@Andy: i've installed natty (went fine) and tried your patched kernel: it hangs on boot on my Acer 4520, as it does with Maverick.
So the patch does produce regression, at least on my hardware.

My wrong: natty's kernel randomly hangs on boot on my hardware, whether patched or not.
But: the patched kernel does solve this bug for me. Still getting the dmesg error, though the interrupt is 0x00080000 instead of 0x00030000. Should I file another bug report ?

the patched kernel does solve this bug for me

Should read:

the patched kernel does NOT solve this bug for me

I have Dell Inspiron 6400 with Natty with all updates.
lspci:
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
03:01.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
03:01.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)

SD slot used to work fine till yesterday - I was able to read and write SD cards I have.
Yesterday I copied some data into card, removed card, inserted in into another device, then brought it back and got error mentioned in the bugreport. Since then all cards I try produce this error. I tried to reboot, format card, etc - no result.
The important part is that it used to work, I removed card from slot, inserted it back (without rebooting/sleeping) and now it doesn't work at all.

Just tried Oneiric beta1 - same problem there.

On the other hand I just booted into Natty with card in slot and had same error, then I removed card and reinserted it - it was detected as mmc and mounted. But this happened only once.

if you issue (after inserting the card):

sudo modprobe -r r852 ; sudo modprobe -r sdhci_pci ; sudo modprobe r852 ; sudo modprobe sdhci_pci

then the card is recognized without error.

M.

#39
I just encountered the same error message and Muhali's method worked

Muhali's method worked for me as well.

Thankfully Muhali's method worked for me as well. I look forward to a more permanent fix.

Still occurs in Precise with kernel 3.2.0-24. Muhali's workaround (#39) confirmed to work here, too.

Hi had the same issue with Kernel 3.2.0-29-generic-pae and Muhali's workaround works.
When booting with the card inserted, it is sometimes recognised, sometimes you need to insert the SD card several times.

I am all new to ubuntu/linux as a laptop OS and if you have links on how to help to troubleshoot this kind of issues (enable debug logs etc...) I would be more than happy to contribute.

Jean-Louis Dupond, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this 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 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 following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

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.

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

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

Still a problem to me on Ubuntu 12.04 LTS precise pangolin (kernel 3.2.0-33-generic-pae)

Muhali's workaround (#39) confirmed to work here, too.
Can we have a real correction here ?

hardware : DELL XPS M1710

Tanguy Herrmann, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

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