Description of problem: My wireless connection kept not responding. I was connected but no traffic passed. Other people arround me were fine. I first reconnected, that did not work; same result. Then I disabled my wireless adaptor (through network manager's 1 button click), waited 20 seconds and re-enabled it. After the reconnect I got this crash. A bit of traffic went through but now it's stuck again. Additional info: reporter: libreport-2.2.3 WARNING: CPU: 4 PID: 21725 at net/mac80211/main.c:256 ieee80211_restart_work+0x6d/0x70 [mac80211]() ieee80211_restart_work called with hardware scan in progress Modules linked in: fuse uas usb_storage ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_CHECKSUM iptable_mangle tun bridge stp llc ip6table_filter ip6_tables ebtable_nat ebtables ccm x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel arc4 iwldvm mac80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm iTCO_wdt iwlwifi r8169 dell_laptop uvcvideo iTCO_vendor_support videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media dcdbas dell_wmi mii sparse_keymap snd_timer snd soundcore cfg80211 rfkill shpchp mei_me mei dell_smo8800 microcode serio_raw i2c_i801 lpc_ich mfd_core nfsd auth_rpcgss nfs_acl lockd sunrpc binfmt_misc i915 i2c_algo_bit drm_kms_helper drm i2c_core wmi video CPU: 4 PID: 21725 Comm: kworker/4:0 Not tainted 3.16.2-200.fc20.x86_64 #1 Hardware name: Dell Inc. Dell System XPS L502X/0NJT03, BIOS A07 10/20/2011 Workqueue: events ieee80211_restart_work [mac80211] 0000000000000000 00000000f8aa9d59 ffff8801e9363d48 ffffffff81706ce1 ffff8801e9363d90 ffff8801e9363d80 ffffffff8108d0ad ffff88022f7a1738 ffff88022f7a0680 ffff88023e513dc0 ffff88023e518000 0000000000000100 Call Trace: [<ffffffff81706ce1>] dump_stack+0x45/0x56 [<ffffffff8108d0ad>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108d12c>] warn_slowpath_fmt+0x5c/0x80 [<ffffffffa050f1dd>] ieee80211_restart_work+0x6d/0x70 [mac80211] [<ffffffff810a90c6>] process_one_work+0x176/0x430 [<ffffffff810a979d>] worker_thread+0x11d/0x530 [<ffffffff810a9680>] ? rescuer_thread+0x300/0x300 [<ffffffff810b0268>] kthread+0xd8/0xf0 [<ffffffff810b0190>] ? insert_kthread_work+0x40/0x40 [<ffffffff8170e27c>] ret_from_fork+0x7c/0xb0 [<ffffffff810b0190>] ? insert_kthread_work+0x40/0x40
Created attachment 942240 [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.