Description of problem: I accessed an SD card. It read the files, but when I accessed one, it crashed. Additional info: WARNING: at drivers/mmc/host/sdhci.c:977 sdhci_send_command+0xc36/0xd70 [sdhci]() Hardware name: 276552G Modules linked in: vfat fat mmc_block fuse 8021q garp stp llc fcoe libfcoe libfc scsi_transport_fc scsi_tgt be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm bnep ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iTCO_wdt iTCO_vendor_support coretemp kvm_intel uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core kvm microcode videodev media cdc_ether usbnet mii snd_hda_codec_conexant cdc_wdm cdc_acm i2c_i801 snd_hda_intel snd_hda_codec snd_hwdep lpc_ich snd_seq mfd_core snd_seq_device r592 memstick btusb arc4 bluetooth iwldvm mac80211 snd_pcm iwlwifi cfg80211 snd_page_alloc snd_timer e1000e mei thinkpad_acpi snd soundcore rfkill uinput btrfs libcrc32c zlib_deflate sdhci_pci firewire_ohci sdhci mmc_core firewire_core crc_itu_t yenta_socket w mi i915 video i2c_algo_bit drm_kms_helper drm i2c_core Pid: 0, comm: swapper/0 Not tainted 3.7.9-104.fc17.x86_64 #1 Call Trace: <IRQ> [<ffffffff8105e6ff>] warn_slowpath_common+0x7f/0xc0 [<ffffffff8105e75a>] warn_slowpath_null+0x1a/0x20 [<ffffffffa014f5b6>] sdhci_send_command+0xc36/0xd70 [sdhci] [<ffffffff81301438>] ? is_swiotlb_buffer+0x18/0x40 [<ffffffff812f100a>] ? delay_tsc+0x4a/0x80 [<ffffffffa014fa80>] ? sdhci_finish_data+0x390/0x390 [sdhci] [<ffffffff812f0f58>] ? __const_udelay+0x28/0x30 [<ffffffffa014c50c>] ? sdhci_reset+0x9c/0x180 [sdhci] [<ffffffffa014fa80>] ? sdhci_finish_data+0x390/0x390 [sdhci] [<ffffffffa014f838>] sdhci_finish_data+0x148/0x390 [sdhci] [<ffffffff816291bb>] ? printk+0x61/0x63 [<ffffffff810b5f04>] ? tick_program_event+0x24/0x30 [<ffffffffa014fa80>] ? sdhci_finish_data+0x390/0x390 [sdhci] [<ffffffffa014fb0f>] sdhci_timeout_timer+0x8f/0xd0 [sdhci] [<ffffffff810b4936>] ? clockevents_program_event+0x76/0x120 [<ffffffff8106d40a>] call_timer_fn+0x3a/0x120 [<ffffffff810b533c>] ? tick_broadcast_set_event+0x4c/0x60 [<ffffffffa014fa80>] ? sdhci_finish_data+0x390/0x390 [sdhci] [<ffffffff8106f19e>] run_timer_softirq+0x1fe/0x2b0 [<ffffffff810ec1b7>] ? handle_irq_event_percpu+0xa7/0x1f0 [<ffffffff81067080>] __do_softirq+0xd0/0x210 [<ffffffff8163ca9c>] call_softirq+0x1c/0x30 [<ffffffff81016315>] do_softirq+0x75/0xb0 [<ffffffff81067355>] irq_exit+0xb5/0xc0 [<ffffffff8163d343>] do_IRQ+0x63/0xe0 [<ffffffff816335ad>] common_interrupt+0x6d/0x6d <EOI> [<ffffffff8101b8d3>] ? native_sched_clock+0x13/0x80 [<ffffffff8136cc37>] ? arch_local_irq_enable+0x8/0xd [<ffffffff8109652e>] ? sched_clock_idle_wakeup_event+0x1e/0x20 [<ffffffff8136d4fc>] acpi_idle_enter_simple+0xcc/0x106 [<ffffffff814dc519>] cpuidle_enter+0x19/0x20 [<ffffffff814dcba9>] cpuidle_idle_call+0xa9/0x260 [<ffffffff8101d47f>] cpu_idle+0xaf/0x120 [<ffffffff8160f8c2>] rest_init+0x72/0x80 [<ffffffff81cfac44>] start_kernel+0x3d1/0x3de [<ffffffff81cfa672>] ? repair_env_string+0x5e/0x5e [<ffffffff81cfa356>] x86_64_start_reservations+0x131/0x135 [<ffffffff81cfa45a>] x86_64_start_kernel+0x100/0x10f
*** This bug has been marked as a duplicate of bug 924652 ***
Created attachment 730308 [details] dmesg output when this happened Please note, that after the inital occurence of the bug it didn't happen again. However, the card obviously lost and regained connection several times (the message in the notification bar appeared several times).
Sorry - accidently commented in this bug. Information is also in the other one.