libreport version: 2.0.10 cmdline: BOOT_IMAGE=/vmlinuz-3.6.7-4.fc16.i686 root=/dev/mapper/vg_universe-lv_root ro rd.md=0 rd.dm=0 rd.lvm.lv=vg_universe/lv_swap KEYTABLE=us quiet rd.lvm.lv=vg_universe/lv_root SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 backtrace: :WARNING: at drivers/net/wireless/iwlwifi/dvm/tx.c:1187 iwlagn_rx_reply_tx+0x96c/0x990 [iwldvm]() :Hardware name: Dell System Vostro 3450 :Modules linked in: tcp_lp fuse be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi cxgb3 mdio 8021q garp stp llc fcoe ib_iser rfcomm libfcoe libfc scsi_transport_fc scsi_tgt tpm_bios rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi bnep ip6t_REJECT nf_conntrack_ipv6 nf_conntrack_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 xt_state nf_conntrack ip6table_filter ip6_tables binfmt_misc uvcvideo videobuf2_core videodev media videobuf2_vmalloc videobuf2_memops iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi snd_hda_codec_realtek arc4 iwldvm mac80211 coretemp kvm_intel kvm dell_wmi sparse_keymap btusb bluetooth dell_laptop dcdbas microcode joydev lpc_ich i2c_i801 snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm r8169 mii snd_timer snd soundcore snd_page_alloc iwlwifi cfg80211 rfkill uinput crc32c_intel ums_realtek usb_storage wmi i915 drm_kms_helper drm i2c_algo_bit i2c_core video :Pid: 0, comm: swapper/0 Not tainted 3.6.7-4.fc16.i686 #1 :Call Trace: : [<c043c822>] warn_slowpath_common+0x72/0xa0 : [<f89ce5ec>] ? iwlagn_rx_reply_tx+0x96c/0x990 [iwldvm] : [<f89ce5ec>] ? iwlagn_rx_reply_tx+0x96c/0x990 [iwldvm] : [<c043c872>] warn_slowpath_null+0x22/0x30 : [<f89ce5ec>] iwlagn_rx_reply_tx+0x96c/0x990 [iwldvm] : [<c047477b>] ? load_balance+0x9b/0x670 : [<f89d7d0e>] iwl_rx_dispatch+0x6e/0xe0 [iwldvm] : [<c04705c4>] ? update_cfs_load+0x2c4/0x2d0 : [<f80249ed>] iwl_irq_tasklet+0x6bd/0xa10 [iwlwifi] : [<c0444da0>] ? local_bh_enable_ip+0x90/0x90 : [<c0445343>] tasklet_action+0x53/0xb0 : [<c0444e39>] __do_softirq+0x99/0x1d0 : [<c0444da0>] ? local_bh_enable_ip+0x90/0x90 : <IRQ> [<c04451ae>] ? irq_exit+0x7e/0xa0 : [<c046b01e>] ? scheduler_ipi+0x4e/0xe0 : [<c0423ce7>] ? smp_reschedule_interrupt+0x27/0x30 : [<c0952c99>] ? reschedule_interrupt+0x31/0x38 : [<c044007b>] ? kmsg_dump_get_line_nolock+0x8b/0x130 : [<c06badc4>] ? intel_idle+0xc4/0x120 : [<c0825045>] ? cpuidle_enter+0x15/0x20 : [<c082563d>] ? cpuidle_idle_call+0x9d/0x260 : [<c040ae9a>] ? cpu_idle+0xaa/0xe0 : [<c0932635>] ? rest_init+0x5d/0x68 : [<c0bfc9c0>] ? start_kernel+0x36d/0x373 : [<c0bfc48e>] ? repair_env_string+0x51/0x51 : [<c0bfc2c2>] ? i386_start_kernel+0x78/0x7d
This looks somewhat related to 882495
*** Bug 887418 has been marked as a duplicate of this bug. ***
I would like to see what happen before this warning. Please attach full dmesg (which include this warning). You can find it in .cache/abrt/spool/oops-{DATE}/ or in /var/spool/abrt/oops-{DATE}/ . Looks like this problem is reproducible somehow, are there any steps to reproduce ? Or rather it happen at random while normal wireless network usage?
Stanislaw, I experience this error several times a day. I notice it most often when resuming from suspend, when docking/undocking, and screen lid close/open (which requires a screen unlock). Oftentimes these events occur at the same time (dock suspended laptop, open lid, resume, unlock screen).
Once the problem happens please do "dmesg > dmesg.txt" and attach dmesg.txt here, or attach dmesg saved by ABRT as described in comment 3.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Jeremy, please attach dmesg, since you experience this error several times a day, it should not be problem to showing us full dmesg with the WARNING.
Created attachment 690052 [details] Dmesg output leading up to the error @ Jan 29 10:53:31
Note that I recently received a firmware update for intel wireless via yum. Since then, I do not receive the error as often, but it still does occur. Regardless of if the error message appears or not, I still have wireless connectivity issues when undocking and suspending (in which case I usually completely disable wireless, then enable and reconnect).
Regarding warning. This is firmware issue which could be ignored by driver. On 3.7 kernel available currently in Fedora 17 warning was removed by commit: commit 0f3bbc6a750c13a1aa862ec4268f530ab062b04a Author: Emmanuel Grumbach <emmanuel.grumbach> Date: Sun Dec 2 09:56:44 2012 +0200 iwlwifi: silently ignore fw flaws in Tx path commit 27edb1accf5695ff00a32c85c4a00ac7e1e7f298 upstream. Regarding connectivity issues. From logs from comment 8 looks like network setup correctly after resume from suspend, DHCP assign IP address for wired interface em1 (at Jan 29 09:05:45) and on wireless interface (at Jan 29 09:05:53). After about 30 minutes there are problems with renewal of IP address on wireless interface: Jan 29 09:30:24 dhcp-88-12 dhclient[24247]: DHCPREQUEST on wlan0 to 1.1.1.1 port 67 (xid=0xe928ee6) Jan 29 09:30:27 dhcp-88-12 dhclient[24247]: DHCPREQUEST on wlan0 to 1.1.1.1 port 67 (xid=0xe928ee6) what is issue with wireless device or AP. But after next 28 minutes we finally succeed: Jan 29 09:58:29 dhcp-88-12 dhclient[24247]: DHCPACK from 1.1.1.1 (xid=0xe928ee6) Jan 29 09:58:29 dhcp-88-12 dhclient[24247]: bound to 10.192.49.135 -- renewal in 3126 seconds. Then you remove laptop from dock, and we have those two messages: Jan 29 09:58:48 dhcp-88-12 NetworkManager[837]: <info> (em1): device state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] Jan 29 09:58:48 dhcp-88-12 NetworkManager[837]: <info> (em1): deactivating device (reason 'carrier-changed') [40] Jan 29 09:58:48 dhcp-88-12 NetworkManager[837]: <info> (em1): canceled DHCP transaction, DHCP client pid 24012 <snip> Jan 29 09:59:12 dhcp-88-12 NetworkManager[837]: <info> (wlan0): device state change: activated -> unavailable (reason 'none') [100 20 0] Jan 29 09:59:12 dhcp-88-12 NetworkManager[837]: <info> (wlan0): deactivating device (reason 'none') [0] Jan 29 09:59:12 dhcp-88-12 NetworkManager[837]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 24247 So NetworkManager disable wired interface with 'carried-changed' reason. That is fine assuming cable was connected to docking station. But deactivating wireless device is strange, perhaps this is a bug on NetworkManager. Jeremy, if you disconnect cable from docking station and use only wireless network while laptop is docked, does undocking also then deactivate wireless device ?
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.