Description of problem: had power_save on Additional info: WARNING: at drivers/net/wireless/iwlwifi/dvm/../iwl-trans.h:541 iwl_dvm_send_cmd+0x130/0x140 [iwldvm]() Hardware name: UX32VD iwl_trans_send_cmd bad state = 0 Modules linked in: cpufreq_stats fuse ebtable_nat nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables bnep vfat fat iTCO_wdt iTCO_vendor_support asus_nb_wmi asus_wmi sparse_keymap coretemp snd_hda_codec_hdmi microcode snd_hda_codec_realtek arc4 uvcvideo videobuf2_vmalloc videobuf2_memops serio_raw videobuf2_core videodev snd_hda_intel iwldvm media snd_hda_codec mac80211 snd_hwdep snd_seq snd_seq_device btusb bluetooth i2c_i801 lpc_ich mfd_core snd_pcm iwlwifi cfg80211 snd_page_alloc snd_timer rfkill snd soundcore vhost_net mei tun macvtap macvlan kvm_intel kvm uinput btrfs libcrc32c zlib_deflate crc32c_intel nouveau i915 ghash_clmulni_intel i2c_algo_bit drm_kms_helper ttm mxm_wmi drm i2c_core wmi video Pid: 1885, comm: kworker/u:2 Not tainted 3.7.2-201.fc18.x86_64 #1 Call Trace: [<ffffffff8105e67f>] warn_slowpath_common+0x7f/0xc0 [<ffffffff8105e776>] warn_slowpath_fmt+0x46/0x50 [<ffffffffa05b2980>] iwl_dvm_send_cmd+0x130/0x140 [iwldvm] [<ffffffffa05b6bc6>] iwl_send_add_sta+0xd6/0x120 [iwldvm] [<ffffffffa05273e2>] ? ieee80211_bss_info_update+0x2c2/0x390 [mac80211] [<ffffffffa05b931b>] iwl_sta_rx_agg_stop+0x12b/0x190 [iwldvm] [<ffffffffa05ac8cf>] iwlagn_mac_ampdu_action+0x2af/0x310 [iwldvm] [<ffffffffa052b4ee>] ___ieee80211_stop_rx_ba_session+0xbe/0x250 [mac80211] [<ffffffffa052b6d9>] __ieee80211_stop_rx_ba_session+0x59/0x80 [mac80211] [<ffffffff81517e01>] ? skb_release_data+0xf1/0x110 [<ffffffffa0529a12>] ieee80211_process_delba+0x42/0x50 [mac80211] [<ffffffffa052edd8>] ieee80211_iface_work+0x2f8/0x360 [mac80211] [<ffffffff8107a487>] process_one_work+0x147/0x490 [<ffffffffa052eae0>] ? ieee80211_netdev_select_queue+0x20/0x20 [mac80211] [<ffffffff8107cd1e>] worker_thread+0x15e/0x450 [<ffffffff8107cbc0>] ? busy_worker_rebind_fn+0x110/0x110 [<ffffffff81081c80>] kthread+0xc0/0xd0 [<ffffffff81010000>] ? ftrace_raw_event_xen_mmu_flush_tlb_others+0x50/0xe0 [<ffffffff81081bc0>] ? kthread_create_on_node+0x120/0x120 [<ffffffff8163da2c>] ret_from_fork+0x7c/0xb0 [<ffffffff81081bc0>] ? kthread_create_on_node+0x120/0x120 Potential duplicate: bug 861599
Please attach full dmesg (which include this warning), which you can find it in .cache/abrt/spool/oops-{DATE}/ or in /var/spool/abrt/oops-{DATE}/ .
Created attachment 687793 [details] dmesg as requested This looks like the right one. I haven't seen this reoccur yet, even though I'm still on 3.7.2-201.fc18.x86_64.
Problem is caused by firmware error.
Watching a you-tube video. Package: kernel OS Release: Fedora release 18 (Spherical Cow)
(In reply to comment #4) > Watching a you-tube video. > Please share your log. The NMI W. Andrew got seems very hard to reproduce. I would be surprised that you got the exact same error. Although the WARN_ON may be the same, it still doesn't mean that the fw error that happens before the WARN_ON is the same.
*** Bug 910628 has been marked as a duplicate of this bug. ***
*** Bug 919524 has been marked as a duplicate of this bug. ***
*** Bug 969610 has been marked as a duplicate of this bug. ***
*** Bug 989551 has been marked as a duplicate of this bug. ***
*** Bug 996502 has been marked as a duplicate of this bug. ***
*** Bug 999053 has been marked as a duplicate of this bug. ***
*** Bug 1000191 has been marked as a duplicate of this bug. ***
Created attachment 809980 [details] 0001-iwlwifi-don-t-WARN-on-host-commands-sent-when-firmwa.patch
Created attachment 809981 [details] 0002-iwlwifi-don-t-WARN-on-bad-firmware-state.patch
Josh, please apply two above patches as fix for this bug. Though those patches only remove WARN_ON which trigger ABRT and print normal dmesg error instead. Root of the problem is crashing firmware due to bugs it has or because driver does not talk nicely with firmware. We can not solve that easily. But in most cases we restart firmware and things works, we don't need to trigger warning on firmware restarting and patches remove possibility of that. Users who have problem with driver functionality apart of warning should open different bug report.
Added to all Fedora branches. Yay, no more extraneous backtraces!
kernel-3.11.4-201.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/kernel-3.11.4-201.fc19
kernel-3.11.4-101.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kernel-3.11.4-101.fc18
kernel-3.11.4-301.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.11.4-301.fc20
Package kernel-3.11.4-201.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.11.4-201.fc19' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18820/kernel-3.11.4-201.fc19 then log in and leave karma (feedback).
kernel-3.11.4-301.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.11.4-201.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
kernel-3.11.4-101.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.