Package: kernel
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)

Comment
-----
Copied files from hard drive to sd-card and unmounted the sd-card afterwards.

drivers/mmc/host/sdhci.c:934 sdhci_send_command+0x37/0x88a:
        WARN_ON(host->cmd);

I guess this means it's still busy sending a command?

I just remembered that I did everything (mount, copy, umount) through KDE 4 when this happened and it was not the first oops of this kind when I did an umount of an sd-card in that built-in reader.

I rebooted later and did some more copying manually (mount, cp, umount in a shell) which worked fine.  Also the same procedure with a USB card-reader worked fine.

Cheers,
T.

I cannot tell if it was still busy because all but the power LED do not work on my laptop (Lenovo T520) due to problems with the graphics card driver(s) - it is this nvidia optimus/intel thing. :-(  Therefore there was no indication of further activity after KDE reported that it would be safe to remove the card.

Cheers,
T.

*** Bug 744467 has been marked as a duplicate of this bug. ***

*** Bug 747275 has been marked as a duplicate of this bug. ***

*** Bug 760315 has been marked as a duplicate of this bug. ***

I'm getting a very similar error on my macbook pro 8,1 running Fedora 16.  I put a sdcard in the reader, unmounted with disk manager, then ran photorec from gnome-terminal.  When it was almost done the error started happening repeatedly, about once per second until I removed the card.  I put the card back in to copy files to it, it auto-mounted, and I copied one file successfully.  After trying to copy another, the errors started again and the copy didn't happen.  

The card reader:
$ lspci -vvknn | grep SD
02:00.1 SD Host controller [0805]: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader [14e4:16bc] (rev 10) (prog-if 01)


Here's the back trace:

WARNING: at drivers/mmc/host/sdhci.c:777 sdhci_send_command+0x5e9/0x85b [sdhci]()
Hardware name: MacBookPro8,1
Modules linked in: mmc_block usb_storage cdc_acm uas b43 mac80211 cfg80211 bcma ssb tcp_lp ppdev parport_pc lp parport fuse lockd vboxpci vboxnetadp vboxnetflt vboxdrv rfcomm bnep coretemp nf_conntrack_ipv4 nf_conntrack_netbios_ns nf_defrag_ipv4 nf_conntrack_broadcast ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables vfat fat arc4 snd_hda_codec_hdmi snd_hda_codec_cirrus applesmc iTCO_wdt iTCO_vendor_support joydev uvcvideo btusb videodev media v4l2_compat_ioctl32 bcm5974 bluetooth rfkill tg3 snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc microcode i2c_i801 input_polldev apple_bl sunrpc uinput binfmt_misc firewire_ohci firewire_core crc_itu_t sdhci_pci sdhci mmc_core i915 drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded: ssb]
Pid: 8149, comm: mmcqd/0 Tainted: G        WC  3.1.2-1.fc16.x86_64 #1
Call Trace:
 [<ffffffff81057a1e>] warn_slowpath_common+0x83/0x9b
 [<ffffffff81057a50>] warn_slowpath_null+0x1a/0x1c
 [<ffffffffa00553b8>] sdhci_send_command+0x5e9/0x85b [sdhci]
 [<ffffffff81085d46>] ? arch_local_irq_restore+0x6/0xd
 [<ffffffff81085d6f>] ? arch_local_irq_save+0x15/0x1b
 [<ffffffff814b71ac>] ? _raw_spin_unlock_irqrestore+0x17/0x19
 [<ffffffffa00565ba>] sdhci_request+0x11b/0x131 [sdhci]
 [<ffffffffa00df8cf>] mmc_start_request+0x1ac/0x1b3 [mmc_core]
 [<ffffffffa00dffe2>] mmc_start_req+0xe3/0x11e [mmc_core]
 [<ffffffffa029ea80>] mmc_blk_issue_rw_rq+0x85/0x29f [mmc_block]
 [<ffffffff81014b35>] ? paravirt_read_tsc+0x9/0xd
 [<ffffffffa029ef04>] mmc_blk_issue_rq+0x26a/0x28d [mmc_block]
 [<ffffffff8120c76b>] ? blk_start_request+0x3a/0x3f
 [<ffffffffa029fc73>] mmc_queue_thread+0xb7/0x146 [mmc_block]
 [<ffffffffa029fbbc>] ? mmc_blk_probe+0x227/0x227 [mmc_block]
 [<ffffffff81072cdf>] kthread+0x84/0x8c
 [<ffffffff814bfa74>] kernel_thread_helper+0x4/0x10
 [<ffffffff81072c5b>] ? kthread_worker_fn+0x148/0x148
 [<ffffffff814bfa70>] ? gs_change+0x13/0x13

Is this still happening with 2.6.43/3.3?

Still happens with Fedora 17, latest kernel 3.4.x and 3.5.x. although not very often.

This is usually what I see as well.

   5.147695] mmcblk0: error -110 sending status command, retrying
[    5.147815] mmcblk0: error -110 sending status command, retrying
[    5.147896] mmcblk0: error -110 sending status command, aborting
[    5.147943] end_request: I/O error, dev mmcblk0, sector 60710784
[    5.147987] Buffer I/O error on device mmcblk0, logical block 7588848
[    5.149220] mmcblk0: error -110 sending status command, retrying
[    5.149296] mmcblk0: error -110 sending status command, retrying
[    5.149374] mmcblk0: error -110 sending status command, aborting
[    5.149426] end_request: I/O error, dev mmcblk0, sector 60710784
[

Of course, this only happens if you leave the SDCARD in the slot on boot.

If you take it out, and insert the SDCARD afterwards, then no problem.

-gc

If it's happening in 3.5.x kernels, can you please report it directly to the linux-mmc and/or linux-kernel mailing lists?

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Closing insufficient data as there has been no recent activity on this, please reopen if this is still an issue