Additional info: reporter: libreport-2.2.2 WARNING: CPU: 1 PID: 0 at drivers/net/wireless/iwlegacy/4965-mac.c:2727 il4965_hdl_tx+0xcb1/0xda0 [iwl4965]() Modules linked in: nls_utf8 isofs fuse ccm ip6t_rpfilter ip6t_REJECT xt_conntrack bnep 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 coretemp kvm arc4 snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_seq iwl4965 iwlegacy mac80211 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media iTCO_wdt iTCO_vendor_support snd_seq_device lpc_ich snd_pcm tifm_7xx1 tifm_core mfd_core i2c_i801 microcode cfg80211 serio_raw btusb bluetooth snd_page_alloc snd_timer snd soundcore sony_laptop shpchp rfkill acpi_cpufreq usb_storage nouveau mxm_wmi wmi i2c_algo_bit drm_kms_helper ata_generic firewire_ohci pata_acpi ttm firewire_core yenta_socket crc_itu_t sky2 drm i2c_core video CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.13.9-200.fc20.x86_64 #1 Hardware name: Sony Corporation VGN-FZ31S/VAIO, BIOS R2110J7 12/21/2007 0000000000000009 ffff88007fd03d28 ffffffff81687dac 0000000000000000 ffff88007fd03d60 ffffffff8106d4dd ffff8800799f17c0 000000000000000a 0000000000000052 000000000000005d 00000000000002ab ffff88007fd03d70 Call Trace: <IRQ> [<ffffffff81687dac>] dump_stack+0x45/0x56 [<ffffffff8106d4dd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8106d5ba>] warn_slowpath_null+0x1a/0x20 [<ffffffffa04e53e1>] il4965_hdl_tx+0xcb1/0xda0 [iwl4965] [<ffffffffa04e2805>] il4965_rx_handle+0x225/0x590 [iwl4965] [<ffffffff81091d55>] ? enqueue_hrtimer+0x25/0x80 [<ffffffffa04e3006>] il4965_irq_tasklet+0x496/0x6d0 [iwl4965] [<ffffffff810721d6>] tasklet_action+0xf6/0x100 [<ffffffff810725dc>] __do_softirq+0xec/0x280 [<ffffffff81072a7d>] irq_exit+0xbd/0xd0 [<ffffffff81698f96>] do_IRQ+0x56/0xc0 [<ffffffff8168ec6d>] common_interrupt+0x6d/0x6d <EOI> [<ffffffff8153212f>] ? cpuidle_enter_state+0x4f/0xc0 [<ffffffff81532259>] cpuidle_idle_call+0xb9/0x1f0 [<ffffffff8101c8fe>] arch_cpu_idle+0xe/0x30 [<ffffffff810c0685>] cpu_startup_entry+0xc5/0x290 [<ffffffff81040e5b>] start_secondary+0x22b/0x2e0 Potential duplicate: bug 1003298
Created attachment 893176 [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.14.4-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 experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 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.
I just experienced this with kernel 3.14.8-200.fc20.x86_64 on my ThinkPad x61t. ABRT took me here but told me that the bz is closed. Please re-open.
*********** 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.