Description of problem: Maybe problem raised during waking up system after suspending (opened notebook lid). Additional info: reporter: libreport-2.1.11 WARNING: CPU: 3 PID: 4069 at drivers/pci/pci.c:1430 pci_disable_device+0x84/0x90() Device xhci_hcd disabling already-disabled device Modules linked in: rfcomm fuse xt_CHECKSUM tun nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep binfmt_misc arc4 ath9k ath9k_common ath9k_hw uvcvideo snd_hda_codec_hdmi snd_hda_codec_realtek x86_pkg_temp_thermal ath videobuf2_vmalloc videobuf2_memops videobuf2_core snd_hda_intel coretemp snd_hda_codec videodev mac80211 kvm_intel kvm media crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel snd_hwdep snd_seq cfg80211 atl1c iTCO_wdt snd_seq_device ath3k asus_nb_wmi asus_wmi iTCO_vendor_support btusb snd_pcm sparse_keymap snd_page_alloc snd_timer snd soundcore shpchp mei_me mei lpc_ich mfd_core bluetooth rfkill microcode serio_raw i2c_i801 nfsd auth_rpcgss nfs_acl lockd sunrpc i915 mxm_wmi i2c_algo_bit drm_kms_helper drm i2c_core wmi video CPU: 3 PID: 4069 Comm: kworker/u32:1 Not tainted 3.12.5-302.fc20.x86_64 #1 Hardware name: ASUSTeK Computer Inc. U36SG/U36SG, BIOS U36SG.204 08/13/2012 Workqueue: events_unbound async_run_entry_fn 0000000000000009 ffff88024155fa60 ffffffff81662d11 ffff88024155faa8 ffff88024155fa98 ffffffff810691dd ffff880243564000 ffff880243564000 ffff880243564098 ffff88024355c098 0000000000000400 ffff88024155faf8 Call Trace: [<ffffffff81662d11>] dump_stack+0x45/0x56 [<ffffffff810691dd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8106924c>] warn_slowpath_fmt+0x4c/0x50 [<ffffffff8106f27b>] ? free_resource+0x5b/0x90 [<ffffffff813395c4>] pci_disable_device+0x84/0x90 [<ffffffff81487aac>] usb_hcd_pci_remove+0xcc/0x150 [<ffffffff814b7331>] xhci_pci_remove+0x41/0x70 [<ffffffff8133bfdb>] pci_device_remove+0x3b/0xb0 [<ffffffff813ff89f>] __device_release_driver+0x7f/0xf0 [<ffffffff813ff933>] device_release_driver+0x23/0x30 [<ffffffff813ff0c8>] bus_remove_device+0x108/0x180 [<ffffffff813fb995>] device_del+0x135/0x1d0 [<ffffffff81335b64>] pci_stop_bus_device+0x94/0xa0 [<ffffffff81335c52>] pci_stop_and_remove_bus_device+0x12/0x20 [<ffffffff8134e518>] pciehp_unconfigure_device+0xa8/0x1b0 [<ffffffff8134de78>] pciehp_disable_slot+0x68/0x200 [<ffffffff8134f310>] ? pciehp_get_adapter_status+0x30/0x90 [<ffffffff813473b0>] ? suspend_iter+0x40/0x40 [<ffffffff8134cb88>] pciehp_resume+0x38/0x60 [<ffffffff813473e7>] resume_iter+0x37/0x40 [<ffffffff813fb363>] device_for_each_child+0x43/0x70 [<ffffffff81347977>] pcie_port_device_resume+0x17/0x20 [<ffffffff8133bc24>] pci_pm_resume+0x64/0xb0 [<ffffffff8133bbc0>] ? pci_pm_thaw+0xa0/0xa0 [<ffffffff81407c59>] dpm_run_callback+0x49/0xa0 [<ffffffff81407db6>] device_resume+0xc6/0x1f0 [<ffffffff81407efd>] async_resume+0x1d/0x50 [<ffffffff810920d9>] async_run_entry_fn+0x39/0x120 [<ffffffff810835f6>] process_one_work+0x176/0x430 [<ffffffff8108422b>] worker_thread+0x11b/0x3a0 [<ffffffff81084110>] ? rescuer_thread+0x350/0x350 [<ffffffff8108b0d0>] kthread+0xc0/0xd0 [<ffffffff8108b010>] ? insert_kthread_work+0x40/0x40 [<ffffffff81671cbc>] ret_from_fork+0x7c/0xb0 [<ffffffff8108b010>] ? insert_kthread_work+0x40/0x40
Created attachment 852098 [details] File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Error still exists in kernel 3.13.4-200.fc20.x86_64. Problem arise after waking up system (by pressing spacebar) from suspend mode (closed laptop lid).
Description of problem: Problem occurs after waking up notebook from suspend mode. Version-Release number of selected component: kernel Additional info: reporter: libreport-2.2.0 cmdline: BOOT_IMAGE=/vmlinuz-3.13.6-200.fc20.x86_64 root=/dev/mapper/vg_asus64-lv_root ro rd.lvm.lv=vg_asus64/lv_swap rd.md=0 rd.dm=0 SYSFONT=True KEYTABLE=pl2 rd.luks=0 rd.lvm.lv=vg_asus64/lv_root LANG=pl_PL.utf8 rhgb quiet kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 3 PID: 2516 at drivers/pci/pci.c:1441 pci_disable_device+0x9c/0xb0() xhci_hcd 0000:04:00.0: disabling already-disabled device Modules linked in: fuse ipt_MASQUERADE xt_CHECKSUM tun ccm nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep binfmt_misc arc4 ath9k ath9k_common ath9k_hw ath mac80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec x86_pkg_temp_thermal snd_hwdep iTCO_wdt coretemp iTCO_vendor_support kvm_intel kvm uvcvideo asus_nb_wmi asus_wmi snd_seq snd_seq_device snd_pcm cfg80211 nouveau crct10dif_pclmul crc32_pclmul crc32c_intel snd_page_alloc snd_timer atl1c sparse_keymap ghash_clmulni_intel snd videobuf2_vmalloc videobuf2_memops ttm videobuf2_core soundcore videodev serio_raw mei_me media i2c_i801 lpc_ich microcode btusb mei mfd_core shpchp bluetooth rfkill nfsd auth_rpcgss nfs_acl lockd sunrpc i915 mxm_wmi i2c_algo_bit drm_kms_helper drm i2c_core wmi video CPU: 3 PID: 2516 Comm: kworker/u32:9 Not tainted 3.13.6-200.fc20.x86_64 #1 Hardware name: ASUSTeK Computer Inc. U36SG/U36SG, BIOS U36SG.204 08/13/2012 Workqueue: events_unbound async_run_entry_fn 0000000000000009 ffff880098bc9ab0 ffffffff8168730c ffff880098bc9af8 ffff880098bc9ae8 ffffffff8106d47d ffff8802435c4000 ffff8802435a6210 ffff8802435c4098 ffff8802411cef00 0000000000000400 ffff880098bc9b48 Call Trace: [<ffffffff8168730c>] dump_stack+0x45/0x56 [<ffffffff8106d47d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8106d4ec>] warn_slowpath_fmt+0x4c/0x50 [<ffffffff8107325b>] ? free_resource+0x5b/0x90 [<ffffffff8135023c>] pci_disable_device+0x9c/0xb0 [<ffffffff814a17fc>] usb_hcd_pci_remove+0xcc/0x150 [<ffffffff814d2231>] xhci_pci_remove+0x41/0x70 [<ffffffff81352bdb>] pci_device_remove+0x3b/0xb0 [<ffffffff814176bf>] __device_release_driver+0x7f/0xf0 [<ffffffff81417753>] device_release_driver+0x23/0x30 [<ffffffff8134c684>] pci_stop_bus_device+0x94/0xa0 [<ffffffff8134c772>] pci_stop_and_remove_bus_device+0x12/0x20 [<ffffffff81365178>] pciehp_unconfigure_device+0xa8/0x1b0 [<ffffffff81364ad8>] pciehp_disable_slot+0x68/0x200 [<ffffffff81365f80>] ? pciehp_get_adapter_status+0x30/0x90 [<ffffffff8135dfc0>] ? suspend_iter+0x40/0x40 [<ffffffff813637e8>] pciehp_resume+0x38/0x60 [<ffffffff8135dff7>] resume_iter+0x37/0x40 [<ffffffff814134a3>] device_for_each_child+0x43/0x70 [<ffffffff8135e587>] pcie_port_device_resume+0x17/0x20 [<ffffffff81352824>] pci_pm_resume+0x64/0xb0 [<ffffffff813527c0>] ? pci_pm_thaw+0xa0/0xa0 [<ffffffff8141f9e9>] dpm_run_callback+0x49/0xa0 [<ffffffff8141fb46>] device_resume+0xc6/0x1f0 [<ffffffff8141fc8d>] async_resume+0x1d/0x50 [<ffffffff81095189>] async_run_entry_fn+0x39/0x120 [<ffffffff81087b76>] process_one_work+0x176/0x430 [<ffffffff810887ab>] worker_thread+0x11b/0x3a0 [<ffffffff81088690>] ? rescuer_thread+0x350/0x350 [<ffffffff8108f272>] kthread+0xd2/0xf0 [<ffffffff8108f1a0>] ? insert_kthread_work+0x40/0x40 [<ffffffff8169623c>] ret_from_fork+0x7c/0xb0 [<ffffffff8108f1a0>] ? insert_kthread_work+0x40/0x40
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 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.