Additional info: reporter: libreport-2.1.10 WARNING: CPU: 2 PID: 32267 at drivers/net/wireless/iwlwifi/pcie/tx.c:1501 iwl_trans_pcie_send_hcmd+0x575/0x5d0 [iwlwifi]() Modules linked in: vfat fat usb_storage rfcomm fuse 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 snd_hda_codec_hdmi arc4 iwldvm mac80211 snd_hda_codec_realtek snd_hda_intel snd_hda_codec iwlwifi x86_pkg_temp_thermal snd_hwdep snd_seq snd_seq_device uvcvideo cfg80211 coretemp snd_pcm iTCO_wdt videobuf2_vmalloc iTCO_vendor_support snd_page_alloc btusb videobuf2_memops videobuf2_core bluetooth kvm_intel snd_timer snd i2c_i801 videodev media lpc_ich mfd_core samsung_laptop rfkill kvm soundcore shpchp serio_raw mei_me mei microcode binfmt_misc crct10dif_pclmul crc32_pclmul crc32c_intel i915 i2c_algo_bit drm_kms_helper ghash_clmulni_intel drm r8169 i2c_core mii video CPU: 2 PID: 32267 Comm: kworker/u16:2 Not tainted 3.12.5-302.fc20.x86_64 #1 Hardware name: SAMSUNG ELECTRONICS CO., LTD. 300V3A/300V4A/300V5A/300V3A/300V4A/300V5A, BIOS 02FI 06/16/2011 Workqueue: iwlwifi iwl_bg_bt_runtime_config [iwldvm] 0000000000000009 ffff8801f6937bd0 ffffffff81662d11 0000000000000000 ffff8801f6937c08 ffffffff810691dd ffff88023d484000 00000000ffffff91 ffff8801f6937ca0 00000000ffff0000 00000000ffff0000 ffff8801f6937c18 Call Trace: [<ffffffff81662d11>] dump_stack+0x45/0x56 [<ffffffff810691dd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff810692ba>] warn_slowpath_null+0x1a/0x20 [<ffffffffa03f43c5>] iwl_trans_pcie_send_hcmd+0x575/0x5d0 [iwlwifi] [<ffffffffa0525556>] iwl_dvm_send_cmd+0x46/0x110 [iwldvm] [<ffffffffa0525951>] iwl_dvm_send_cmd_pdu+0x41/0x50 [iwldvm] [<ffffffffa0525d2d>] iwlagn_send_advance_bt_config+0x32d/0x3f0 [iwldvm] [<ffffffff810115ce>] ? __switch_to+0x13e/0x4b0 [<ffffffffa05181d6>] iwl_bg_bt_runtime_config+0x46/0x50 [iwldvm] [<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 Potential duplicate: bug 989159
Created attachment 841636 [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.
In my system this bug had disappeared.
Closing per above.
I just got an identical trace on 3.13.5
Created attachment 872676 [details] dmesg
Created attachment 872691 [details] fix I am still not sure about this patch. I just wonder why lockdep hasn't complained louder. Is it enabled in these system? I do see the bug in the code though... Can this patch be tested?
(In reply to Emmanuel Grumbach from comment #7) > I just wonder why lockdep hasn't complained louder. > Is it enabled in these system? Lockdep is enabled only on fedora kernel-debug variant, which is not installed by default due to bad performance. > I do see the bug in the code though... > Can this patch be tested? I launched kernel build with the patch here: http://koji.fedoraproject.org/koji/taskinfo?taskID=6617851 William, Paulo, and others, please test it (note it has to finish to compile first).
> I launched kernel build with the patch here: > http://koji.fedoraproject.org/koji/taskinfo?taskID=6617851 > > William, Paulo, and others, please test it (note it has to finish to compile > first). I will certainly do so when I get home, but this has happened about twice in as many months so I doubt I'll see any immediate effect -- but will post again if I encounter any problems.
This problem happens when RFKILL switch is used, hence using it more frequently will help to stress the patch :-)
I am pretty sure that this patch should fix the bug - I am just wondering if it doesn't cause a deadlock or something like that. So a few hours of operation should be enough. I'd want this patch to make it to 3.14.
(In reply to Emmanuel Grumbach from comment #11) > I am pretty sure that this patch should fix the bug - I am just wondering if > it doesn't cause a deadlock or something like that. > So a few hours of operation should be enough. > I'd want this patch to make it to 3.14. So far so good: after two-three hours of operation with the patched kernel -- which included me spamming the hell out of the rfkill switch -- everything looks fine.
(In reply to William from comment #12) > (In reply to Emmanuel Grumbach from comment #11) > > I am pretty sure that this patch should fix the bug - I am just wondering if > > it doesn't cause a deadlock or something like that. > > So a few hours of operation should be enough. > > I'd want this patch to make it to 3.14. > > So far so good: after two-three hours of operation with the patched kernel > -- which included me spamming the hell out of the rfkill switch -- > everything looks fine. great thanks. Patch is on its way upstream.
Yep, patch was posted here: http://marc.info/?l=linux-wireless&m=139453882510796&w=2 Josh, please apply it as fix for this bug.
Fixed in git. Thanks to all!
kernel-3.13.7-200.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.13.7-200.fc20
kernel-3.13.7-100.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/kernel-3.13.7-100.fc19
Package kernel-3.13.7-200.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.13.7-200.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-4317/kernel-3.13.7-200.fc20 then log in and leave karma (feedback).
kernel-3.13.7-200.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.13.7-100.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.