Bug 919176

Summary: WARNING: at net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x359/0x360 [mac80211]()
Product: [Fedora] Fedora Reporter: ian.odette
Component: kernelAssignee: Stanislaw Gruszka <sgruszka>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bstedwell, emmanuel.grumbach, gansalmon, ilw, itamar, jonathan, jwboyer, kernel-maint, madhu.chinakonda, sgruszka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e2ede7130506df6e9ea30d233b8adcedd7fa6959
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-19 04:58:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg file for the incident none

Description ian.odette 2013-03-07 19:10:03 UTC
Description of problem:
I returned to my workspace and plugged my computer into the peripherals that it was connected to before I left. These include a displaylink usb to dvi adapter, a vga cable, ethernet, power and a usb hub connected to my keyboard and mouse.

Additional info:
WARNING: at net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x359/0x360 [mac80211]()
Hardware name: Latitude E6430
wlan0:  Failed check-sdata-in-driver check, flags: 0x4
Modules linked in: tcp_lp fuse ebtable_nat ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast bnep bluetooth be2iscsi iscsi_boot_sysfs ip6table_mangle bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ip6t_REJECT ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi nf_conntrack_ipv6 nf_defrag_ipv6 scsi_transport_iscsi 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 arc4 iwldvm mac80211 iTCO_wdt iTCO_vendor_support dell_wmi ppdev sparse_keymap dell_laptop dcdbas coretemp microcode joydev snd_hda_codec_idt i2c_i801 snd_hda_intel snd_hda_codec lpc_ich mfd_core snd_hwdep snd_seq snd_seq_device iwlwifi snd_pcm cfg80211 snd_page_alloc snd_timer rfkill snd soundcore mei vhost_net tun macvtap macvlan kvm_intel kvm uinput parport_pc parport dm_crypt crc32c_intel ghash_clmulni_intel sdhci_pci nouveau sdhci mmc_core i915 udl e1000e mxm_wmi drm_usb i2c_algo_bit ttm drm_kms_helper drm i2c_core wmi video sunrpc
Pid: 870, comm: NetworkManager Not tainted 3.8.1-201.fc18.x86_64 #1
Call Trace:
 [<ffffffff8105e61f>] warn_slowpath_common+0x7f/0xc0
 [<ffffffff8105e716>] warn_slowpath_fmt+0x46/0x50
 [<ffffffffa0541b49>] ieee80211_bss_info_change_notify+0x359/0x360 [mac80211]
 [<ffffffffa0541c33>] ieee80211_ifa_changed+0xe3/0x100 [mac80211]
 [<ffffffff8165365d>] notifier_call_chain+0x4d/0x70
 [<ffffffff81088578>] __blocking_notifier_call_chain+0x58/0x80
 [<ffffffff810885b6>] blocking_notifier_call_chain+0x16/0x20
 [<ffffffff815af16c>] __inet_del_ifa+0x14c/0x290
 [<ffffffff815af3da>] inet_rtm_deladdr+0x10a/0x160
 [<ffffffff81555a03>] rtnetlink_rcv_msg+0x113/0x2f0
 [<ffffffff815558f0>] ? __rtnl_unlock+0x20/0x20
 [<ffffffff8156f4c1>] netlink_rcv_skb+0xb1/0xc0
 [<ffffffff815525f5>] rtnetlink_rcv+0x25/0x40
 [<ffffffff8156ede1>] netlink_unicast+0x1a1/0x220
 [<ffffffff8156f161>] netlink_sendmsg+0x301/0x3c0
 [<ffffffff8152bab0>] sock_sendmsg+0xb0/0xe0
 [<ffffffff8152d551>] ? sock_recvmsg+0xc1/0xf0
 [<ffffffff81196408>] ? mem_cgroup_charge_common+0xa8/0x120
 [<ffffffff8152d47c>] __sys_sendmsg+0x3ac/0x3c0
 [<ffffffff8165336c>] ? __do_page_fault+0x23c/0x4d0
 [<ffffffff811bb389>] ? mntput_no_expire+0x49/0x130
 [<ffffffff811bb496>] ? mntput+0x26/0x40
 [<ffffffff8119ed0e>] ? __fput+0x16e/0x240
 [<ffffffff8152f449>] sys_sendmsg+0x49/0x90
 [<ffffffff81657c19>] system_call_fastpath+0x16/0x1b

Potential duplicate: bug 861875

Comment 1 Stanislaw Gruszka 2013-03-11 12:59:44 UTC
Did you suspend/resume machine when it happen ?

Comment 2 ian.odette 2013-03-12 15:37:32 UTC
Nope, the computer was on and active the entire time.

Comment 3 Stanislaw Gruszka 2013-03-12 17:08:32 UTC
(In reply to comment #0)
> Description of problem:
> I returned to my workspace and plugged my computer into the peripherals that
> it was connected to before I left. These include a displaylink usb to dvi
> adapter, a vga cable, ethernet, power and a usb hub connected to my keyboard
> and mouse.

I'm not sure what does it mean, did you move with laptop somewhere (i.e. associate to different AP what should matter here) and then come back and plug laptop into docking station ?

Also please attach full dmesg file (with this warning included), which you can find in .cache/abrt/spool/oops-{DATE}/ or in /var/spool/abrt/oops-{DATE}/ ; or if ABRT entry was created for this warning, corresponding part from /var/log/messages (from kernel boot to the warning).

Comment 4 ian.odette 2013-03-12 17:27:38 UTC
Created attachment 709083 [details]
dmesg file for the incident

Comment 5 ian.odette 2013-03-12 17:39:17 UTC
I don't have a docking station at my desk but I am connected to several peripherals, you can find a list of them in my initial comment. This error occurred after I returned to my desk from a meeting and connected it to the peripherals.

The computer was not in a sleep state, it was powered on and logged in the entire time it was away from my desk. It almost certainly associated with a different AP during my time away from my desk.

It may be worth noting that my bios is set to disable the wifi card when an Ethernet connection is present.

Comment 6 Stanislaw Gruszka 2013-03-13 09:11:41 UTC
This is iwlwifi firmware problem, which print error just after RFKILL enable radio.

[14734.145413] iwlwifi 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000.

Comment 7 Emmanuel Grumbach 2013-03-13 09:29:06 UTC
I can see 2 sysasserts.
The first should be fixed by Johannes's patch on the passive channel bug.

Comment 8 Stanislaw Gruszka 2013-03-13 10:51:39 UTC
Emmanuel, I'm not sure which patch you reference, can you provide a link or commit id ?

Comment 9 Emmanuel Grumbach 2013-03-13 11:15:07 UTC
diff --git a/net/wireless/reg.c b/net/wireless/reg.c
index 3c1bb57..37b2c79 100644
--- a/net/wireless/reg.c
+++ b/net/wireless/reg.c
@@ -857,7 +857,7 @@ static void handle_channel(struct wiphy *wiphy,
                        return;

                REG_DBG_PRINT("Disabling freq %d MHz\n", chan->center_freq);
-               chan->flags = IEEE80211_CHAN_DISABLED;
+               chan->flags |= IEEE80211_CHAN_DISABLED;
                return;
        }

Comment 10 Stanislaw Gruszka 2013-03-14 10:38:45 UTC
*** Bug 920276 has been marked as a duplicate of this bug. ***

Comment 11 Stanislaw Gruszka 2013-03-14 13:16:18 UTC
I started kernel build with patch here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=5121021

Ian, please install it and try to reproduce the issue, let see if make the Microcode errors gone (at least one error should be fixed).

Comment 12 ian.odette 2013-03-14 13:34:19 UTC
I installed the patch and attempted to reproduce the issue. I couldn't get any errors to come up so I think it fixed something. Are there any logs you need me to provide?

Comment 13 Stanislaw Gruszka 2013-03-14 13:40:19 UTC
No, as long there are no Microcode errors in dmesg, it's no need for showing it.

Comment 14 Stanislaw Gruszka 2013-04-16 12:15:12 UTC
Intel, do we have now proper fix for this issue posted upstream ?

Comment 15 Stanislaw Gruszka 2013-04-16 14:18:38 UTC
Ok, patch posted here:
http://marc.info/?l=linux-wireless&m=136611635905949&w=2

Josh, please apply it as fix for this bug.

Comment 16 Josh Boyer 2013-04-16 14:44:08 UTC
Fixed on all branches.  Thanks!

Comment 17 Fedora Update System 2013-04-18 01:06:16 UTC
kernel-3.8.8-202.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/kernel-3.8.8-202.fc18

Comment 18 Fedora Update System 2013-04-18 22:20:06 UTC
kernel-3.9.0-0.rc7.git3.1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/kernel-3.9.0-0.rc7.git3.1.fc19

Comment 19 Fedora Update System 2013-04-19 04:58:46 UTC
kernel-3.8.8-202.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 20 Fedora Update System 2013-04-24 22:28:58 UTC
kernel-3.9.0-0.rc8.git0.2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/kernel-3.9.0-0.rc8.git0.2.fc19

Comment 21 Fedora Update System 2013-04-30 04:41:41 UTC
kernel-3.9.0-0.rc8.git0.2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.