Bug 919524 - iwlwifi: WARNING: at iwlagn_mac_flush on suspend/resume
Summary: iwlwifi: WARNING: at iwlagn_mac_flush on suspend/resume
Keywords:
Status: CLOSED DUPLICATE of bug 896695
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9bd39f06e9a1d8487b102fe76c6...
: 906102 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-08 17:48 UTC by Ifrit
Modified: 2013-10-09 14:04 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 14:04:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Complete abrt oops data (31.29 KB, application/octet-stream)
2013-05-12 02:47 UTC, Brad Hubbard
no flags Details
dmesg.txt (117.77 KB, text/plain)
2013-05-13 12:24 UTC, Stanislaw Gruszka
no flags Details

Description Ifrit 2013-03-08 17:48:21 UTC
Description of problem:
I wake up from suspend mode

Additional info:
WARNING: at drivers/net/wireless/iwlwifi/dvm/../iwl-trans.h:633 iwlagn_mac_flush+0x1a3/0x1b0 [iwldvm]()
Hardware name: LIFEBOOK UH552
iwl_trans_wait_tx_queue_empty bad state = 0
Modules linked in: vfat fat ebtable_nat xt_CHECKSUM bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi rfcomm bnep arc4 iwldvm mac80211 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device iwlwifi snd_pcm btusb uvcvideo snd_page_alloc iTCO_wdt iTCO_vendor_support bluetooth snd_timer snd videobuf2_vmalloc lpc_ich videobuf2_memops videobuf2_core videodev qcserial usb_wwan qmi_wwan cdc_wdm usbnet cfg80211 rfkill i2c_i801 fujitsu_laptop mei media mfd_core mii coretemp soundcore microcode joydev vhost_net tun macvtap macvlan kvm_intel kvm uinput ums_realtek usb_storage i915 crc32c_intel i2c_algo_bit drm_kms_helper ghash_clmulni_intel drm i2c_core video sunrpc
Pid: 2593, comm: kworker/u:3 Not tainted 3.8.1-201.fc18.x86_64 #1
Call Trace:
 [<ffffffff8105e61f>] warn_slowpath_common+0x7f/0xc0
 [<ffffffff8105e716>] warn_slowpath_fmt+0x46/0x50
 [<ffffffffa0560703>] iwlagn_mac_flush+0x1a3/0x1b0 [iwldvm]
 [<ffffffffa04b8b96>] __ieee80211_recalc_idle+0x236/0x300 [mac80211]
 [<ffffffffa04b91b3>] ieee80211_recalc_idle+0x33/0x60 [mac80211]
 [<ffffffffa04eaa40>] ieee80211_sta_connection_lost.isra.27+0x80/0xc0 [mac80211]
 [<ffffffffa04eba18>] ieee80211_sta_work+0x168/0xe40 [mac80211]
 [<ffffffff8164d266>] ? __mutex_unlock_slowpath+0x36/0x50
 [<ffffffffa04b8609>] ieee80211_iface_work+0x2c9/0x360 [mac80211]
 [<ffffffff8107a5f7>] process_one_work+0x147/0x490
 [<ffffffffa04b8340>] ? ieee80211_recalc_smps_work+0x20/0x20 [mac80211]
 [<ffffffff8107ce8e>] worker_thread+0x15e/0x450
 [<ffffffff8107cd30>] ? busy_worker_rebind_fn+0x110/0x110
 [<ffffffff81081f50>] kthread+0xc0/0xd0
 [<ffffffff81081e90>] ? kthread_create_on_node+0x120/0x120
 [<ffffffff81657b6c>] ret_from_fork+0x7c/0xb0
 [<ffffffff81081e90>] ? kthread_create_on_node+0x120/0x120

Comment 1 Stanislaw Gruszka 2013-03-11 12:53:58 UTC
Please attach full dmesg for this bug report (with the warning). You can find it in .cache/abrt/spool/oops-{DATE}/ or in /var/spool/abrt/oops-{DATE}/ 

BTW, it should be attached by ABRT by default, what version of ABRT are you using?

Comment 2 Stanislaw Gruszka 2013-03-11 13:37:29 UTC
*** Bug 906102 has been marked as a duplicate of this bug. ***

Comment 3 Brad Hubbard 2013-05-12 02:47:56 UTC
Created attachment 746739 [details]
Complete abrt oops data

Reopening this as I am providing a complete set of data.

Comment 4 Brad Hubbard 2013-05-12 02:50:35 UTC
I saw this after disabling wireless networking via the KDE nm-applet and then reenabling. This was done after experiencing connectivity problems to the AP due to heavy usage by one of the other connected nodes.

Comment 5 Stanislaw Gruszka 2013-05-13 12:24:44 UTC
Created attachment 747211 [details]
dmesg.txt

dmesg from above tarball

Comment 6 Stanislaw Gruszka 2013-05-13 12:25:35 UTC
iwlwifi hardware error (?) followed by a warning.

Comment 7 Stanislaw Gruszka 2013-10-09 14:04:37 UTC

*** This bug has been marked as a duplicate of bug 896695 ***


Note You need to log in before you can comment on or make changes to this bug.