Description of problem: Occured after resume from sleep. Additional info: reporter: libreport-2.2.2 WARNING: CPU: 1 PID: 0 at net/mac80211/util.c:662 ieee80211_can_queue_work.isra.13+0x32/0x40 [mac80211]() queueing ieee80211 work while going to suspend Modules linked in: fuse ccm fcoe libfcoe 8021q garp stp libfc mrp scsi_transport_fc llc scsi_tgt ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_conntrack nf_conntrack ip6_tables iTCO_wdt gpio_ich iTCO_vendor_support dm_crypt samsung_laptop uvcvideo videobuf2_vmalloc videobuf2_memops snd_hda_codec_realtek snd_hda_codec_generic videobuf2_core coretemp videodev snd_hda_intel media snd_hda_codec snd_hwdep microcode snd_seq snd_seq_device i2c_i801 serio_raw arc4 snd_pcm ath9k ath9k_common ath9k_hw lpc_ich ath mfd_core mac80211 cfg80211 snd_timer snd rfkill soundcore shpchp acpi_cpufreq binfmt_misc i915 i2c_algo_bit sky2 drm_kms_helper drm i2c_core video ecryptfs encrypted_keys trusted tpm CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.14.4-200.fc20.x86_64 #1 Hardware name: SAMSUNG ELECTRONICS CO., LTD. N250P /N250P , BIOS 01HG.M011.20101209.RHU 12/09/2010 0000000000000000 cb4e323d176caf14 ffff88003f303d88 ffffffff816ef1d2 ffff88003f303dd0 ffff88003f303dc0 ffffffff8108a1bd ffff88003b1e4620 ffff88003bf58e08 0000000000000100 ffffffffa02afce0 ffff88003bf58880 Call Trace: <IRQ> [<ffffffff816ef1d2>] dump_stack+0x45/0x56 [<ffffffff8108a1bd>] warn_slowpath_common+0x7d/0xa0 [<ffffffffa02afce0>] ? ieee80211_sta_bcn_mon_timer+0x40/0x40 [mac80211] [<ffffffff8108a23c>] warn_slowpath_fmt+0x5c/0x80 [<ffffffffa03515df>] ? ath9k_hw_stopdmarecv+0xdf/0x170 [ath9k_hw] [<ffffffffa0298212>] ieee80211_can_queue_work.isra.13+0x32/0x40 [mac80211] [<ffffffffa0298245>] ieee80211_queue_work+0x25/0x50 [mac80211] [<ffffffffa02afcfc>] ieee80211_sta_timer+0x1c/0x20 [mac80211] [<ffffffff81095d26>] call_timer_fn+0x36/0x100 [<ffffffffa02afce0>] ? ieee80211_sta_bcn_mon_timer+0x40/0x40 [mac80211] [<ffffffff810964fa>] run_timer_softirq+0x21a/0x2d0 [<ffffffff8108f8a5>] __do_softirq+0xf5/0x2a0 [<ffffffff8108fcbd>] irq_exit+0xbd/0xd0 [<ffffffff81701875>] smp_apic_timer_interrupt+0x45/0x60 [<ffffffff817001dd>] apic_timer_interrupt+0x6d/0x80 <EOI> [<ffffffff81054566>] ? native_safe_halt+0x6/0x10 [<ffffffff8101df5f>] default_idle+0x1f/0xc0 [<ffffffff8101e856>] arch_cpu_idle+0x26/0x30 [<ffffffff810e4c45>] cpu_startup_entry+0xf5/0x2a0 [<ffffffff81044f8b>] start_secondary+0x23b/0x300
Created attachment 900548 [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.17.2-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 have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 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.