Created attachment 904075 [details] dmesg I am experiencing freequent (roughly two hourly) system lockups which appear to be caused by my wireless card/driver. The symptoms are: 1. Mouse/keyboard start freezing and jumping 2. All input locks up and display freezes (music etc still plays) 3. Hard reset required If I remove my usb wireless adapter as soon as 1 happens sometimes the lockup will not occur. This has been happening for over two months now across the 3.13 and 3.14 kernels. System: * Kernel: 3.14.5-200.fc20.x86_64 * Intel 2600k on an Asus z68 pro-v gen3 * TL-WN721N usb wireless adapter I'm happy to provide more hardware/configuration info if required. --BACKTRACE-- WARNING: CPU: 0 PID: 0 at drivers/net/wireless/ath/ath9k/htc_drv_txrx.c:502 ath9k_htc_tx_process+0x3ba/0x3d0 [ath9k_htc]() Modules linked in: isofs rfcomm 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 w83627ehf hwmon_vid ath9k_htc ath9k_common ath9k_hw ath snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_ca0132 snd_hda_codec_hdmi iTCO_wdt iTCO_vendor_support eeepc_wmi asus_wmi sparse_keymap mxm_wmi vfat fat x86_pkg_temp_thermal coretemp btusb kvm_intel kvm bluetooth crct10dif_pclmul 6lowpan_iphc crc32_pclmul crc32c_intel arc4 fuse rt2800pci rt2800mmio ghash_clmulni_intel rt2800lib rt2x00pci rt2x00mmio rt2x00lib eeprom_93cx6 mac80211 microcode snd_hda_intel serio_raw snd_hda_codec i2c_i801 snd_hwdep snd_seq cfg80211 snd_seq_device snd_pcm lpc_ich mfd_core e1000e crc_ccitt snd_timer rfkill snd ptp soundcore mei_me mei pps_core shpchp wmi binfmt_misc nfsd auth_rpcgss nfs_acl lockd sunrpc radeon i915 ttm i2c_algo_bit firewire_ohci drm_kms_helper firewire_core drm crc_itu_t i2c_core video CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.14.5-200.fc20.x86_64 #1 Hardware name: System manufacturer System Product Name/P8Z68-V PRO GEN3, BIOS 3402 05/07/2012 0000000000000000 4f05ffe003b85a01 ffff88042f203db8 ffffffff816efa42 0000000000000000 ffff88042f203df0 ffffffff8108a1cd ffff8803fd28b200 ffff8803fd1c57e0 ffff8803fd1c5da8 0000000000000000 ffff8804168cd8d4 Call Trace: <IRQ> [<ffffffff816efa42>] dump_stack+0x45/0x56 [<ffffffff8108a1cd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108a2fa>] warn_slowpath_null+0x1a/0x20 [<ffffffffa07887aa>] ath9k_htc_tx_process+0x3ba/0x3d0 [ath9k_htc] [<ffffffffa078838a>] ? ath9k_htc_tx_get_packet+0x13a/0x1a0 [ath9k_htc] [<ffffffffa078915e>] ath9k_htc_txstatus+0x3e/0x130 [ath9k_htc] [<ffffffffa0787cc5>] ath9k_wmi_event_tasklet+0x135/0x160 [ath9k_htc] [<ffffffff8108f4a6>] tasklet_action+0xf6/0x100 [<ffffffff8108f8b5>] __do_softirq+0xf5/0x2a0 [<ffffffff8108fccd>] irq_exit+0xbd/0xd0 [<ffffffff81702058>] do_IRQ+0x58/0xf0 [<ffffffff816f6f6d>] common_interrupt+0x6d/0x6d <EOI> [<ffffffff8158cd5f>] ? cpuidle_enter_state+0x4f/0xc0 [<ffffffff8158ce89>] cpuidle_idle_call+0xb9/0x1f0 [<ffffffff8101e83e>] arch_cpu_idle+0xe/0x30 [<ffffffff810e4c65>] cpu_startup_entry+0xf5/0x2a0 [<ffffffff816e0bc7>] rest_init+0x77/0x80 [<ffffffff81d25fd7>] start_kernel+0x45e/0x47f [<ffffffff81d25982>] ? repair_env_string+0x5c/0x5c [<ffffffff81d25120>] ? early_idt_handlers+0x120/0x120 [<ffffffff81d255ee>] x86_64_start_reservations+0x2a/0x2c [<ffffffff81d2573d>] x86_64_start_kernel+0x14d/0x170
*********** 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.