Description of problem: After I resume from suspend, my /home2 file system mounted on an SDHC card disappears. Version-Release number of selected component (if applicable): Fedora 17, latest updates, installed yesterday. How reproducible: Every time I suspend and then resume. Steps to Reproduce: 1. Suspend system via XFCE logout dialog box 2. Resume by pushing power button 3. Attempt to access file system that used to be available under /home2 Actual results: No file system contents available under /home2, or get an "Input/output error" when trying to access directories on file system, presumably because the directory information has been cached. Expected results: File system on SDHC card available after resume. Additional info: ABRT picked this up, and attached it to bug 824107. Reading through those bug notes, none of them seem to match or are even similar to my problem or symptoms. The kernel has produced a backtrace: [ 826.346548] ------------[ cut here ]------------ [ 826.346561] WARNING: at kernel/irq/manage.c:1198 __free_irq+0x93/0x1d0() [ 826.346563] Hardware name: Inspiron 910 [ 826.346566] Trying to free already-free IRQ 16 [ 826.346567] Modules linked in: tcp_diag inet_diag fuse lockd sunrpc rfcomm ip6t_REJECT bnep nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter nf_conntrack_ipv4 nf_defrag_ipv4 ip6_tables xt_state nf_conntrack arc4 btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core dell_laptop compal_laptop dcdbas videodev media coretemp microcode iwl4965 iwlegacy i2c_i801 snd_hda_codec_realtek mac80211 snd_hda_intel lpc_ich mfd_core snd_hda_codec snd_hwdep cfg80211 snd_pcm r8169 mii rfkill snd_page_alloc jmb38x_ms snd_timer memstick snd soundcore uinput xts gf128mul mmc_block dm_crypt sdhci_pci sdhci mmc_core i915 video i2c_algo_bit drm_kms_helper drm i2c_core [last unloaded: scsi_wait_scan] [ 826.346668] Pid: 23, comm: kworker/0:1 Not tainted 3.5.2-3.fc17.i686.PAE #1 [ 826.346670] Call Trace: [ 826.346675] [<c0447932>] warn_slowpath_common+0x72/0xa0 [ 826.346685] [<c04c6273>] ? __free_irq+0x93/0x1d0 [ 826.346691] [<c04c6273>] ? __free_irq+0x93/0x1d0 [ 826.346697] [<c0447a03>] warn_slowpath_fmt+0x33/0x40 [ 826.346703] [<c04c6273>] __free_irq+0x93/0x1d0 [ 826.346710] [<c04c63f3>] free_irq+0x43/0xa0 [ 826.346723] [<f7e6e19b>] sdhci_remove_host+0x4b/0x140 [sdhci] [ 826.346740] [<f7e7cb62>] sdhci_pci_remove_slot+0x36/0x74 [sdhci_pci] [ 826.346753] [<f7e7cbdd>] sdhci_pci_remove+0x3d/0x60 [sdhci_pci] [ 826.346766] [<c06944df>] pci_device_remove+0x2f/0xe0 [ 826.346777] [<c074660b>] __device_release_driver+0x5b/0xb0 [ 826.346786] [<c0746684>] device_release_driver+0x24/0x40 [ 826.346792] [<c0745e76>] bus_remove_device+0xb6/0x110 [ 826.346798] [<c07430ba>] ? device_remove_attrs+0x2a/0x60 [ 826.346806] [<c0743905>] device_del+0xe5/0x160 [ 826.346812] [<c07439a1>] device_unregister+0x21/0x60 [ 826.346818] [<c068e566>] pci_stop_bus_device+0x76/0x80 [ 826.346824] [<c06a4840>] acpiphp_disable_slot+0xa0/0x160 [ 826.346832] [<c06a492c>] acpiphp_check_bridge.isra.15+0x2c/0xe0 [ 826.346838] [<c06e0e42>] ? acpi_get_name+0x3e/0xa9 [ 826.346846] [<c06a4f38>] _handle_hotplug_event_bridge+0x2f8/0x470 [ 826.346852] [<c06a3510>] ? acpiphp_unregister_hotplug_slot+0x60/0x60 [ 826.346859] [<c053c8c2>] ? kmem_cache_free+0xf2/0x100 [ 826.346867] [<c046232c>] ? cwq_activate_first_delayed+0x3c/0x80 [ 826.346875] [<c0462508>] process_one_work+0x108/0x370 [ 826.346882] [<c06a4c40>] ? _handle_hotplug_event_func+0x1b0/0x1b0 [ 826.346888] [<c0462a49>] worker_thread+0xf9/0x280 [ 826.346894] [<c047266e>] ? complete+0x4e/0x60 [ 826.346902] [<c0462950>] ? rescuer_thread+0x1b0/0x1b0 [ 826.346908] [<c04670c2>] kthread+0x72/0x80 [ 826.346915] [<c0467050>] ? flush_kthread_worker+0x70/0x70 [ 826.346921] [<c09689fe>] kernel_thread_helper+0x6/0x10 [ 826.346931] ---[ end trace 42e7decef2eceec5 ]---
Any progress on this? Do I need to provide any further information? It means I can't suspend or hibernate my laptop, which is quite inconvenient. Thanks.
Created attachment 659645 [details] Full dmesg including kernel oops Full dmesg in case it is useful
Are you still seeing this with 3.7.9 or 3.8.2 in updates-testing?
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Hi, sorry not to get back to you sooner. Yes, it is still occurring with kernel package 3.8.3-103. Has the kernel oops been submitted to the kernel devs/driver developer and they've said it has been fixed? Bug 863557 is also the same problem, on the same type of machine (Dell Inspiron 910/mini 9). Bug 600156 also seems to be the same problem, although the machine type isn't mentioned in the bug report.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.