From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: bss_info_change_notify warning (hacked 3.3.0-rc5+)
Date: Wed, 07 Mar 2012 11:32:54 -0800 [thread overview]
Message-ID: <4F57B7E6.1050103@candelatech.com> (raw)
This is with a somewhat hacked 3.3.0-rc5+. Just
curious if this is a known problem.
Seems very reproducible on my system.
WARNING: at /home/greearb/git/linux-3.3.dev.y/net/mac80211/driver-ops.h:10 ieee80211_bss_info_change_noti)
Hardware name: To be filled by O.E.M.
Modules linked in: 8021q garp stp llc macvlan wanlink(PO) pktgen lockd arc4 joydev ppdev microcode serio_]
Pid: 1855, comm: hostapd Tainted: P C O 3.3.0-rc5+ #7
Call Trace:
[<ffffffff81036eda>] warn_slowpath_common+0x80/0x98
[<ffffffff81036f07>] warn_slowpath_null+0x15/0x17
[<ffffffffa02c0010>] ieee80211_bss_info_change_notify+0x15f/0x18c [mac80211]
[<ffffffffa02d472d>] ieee80211_config_beacon+0x58/0x208 [mac80211]
[<ffffffff8144773b>] ? __mutex_unlock_slowpath+0x10d/0x11f
[<ffffffffa02d4936>] ieee80211_add_beacon+0x35/0xa4 [mac80211]
[<ffffffffa01fd715>] nl80211_addset_beacon+0x317/0x34a [cfg80211]
[<ffffffff813b5a08>] genl_rcv_msg+0x1f4/0x239
[<ffffffff813b5814>] ? genl_rcv+0x28/0x28
[<ffffffff813b4836>] netlink_rcv_skb+0x3e/0x8f
[<ffffffff813b580d>] genl_rcv+0x21/0x28
[<ffffffff813b4611>] netlink_unicast+0xe9/0x152
[<ffffffff813b4d6a>] netlink_sendmsg+0x1f8/0x216
[<ffffffff81384122>] __sock_sendmsg_nosec+0x5f/0x6a
[<ffffffff8138416a>] __sock_sendmsg+0x3d/0x48
[<ffffffff81384a0a>] sock_sendmsg+0xa3/0xbc
[<ffffffff811d12c2>] ? blk_finish_plug+0x13/0x34
[<ffffffff810a8b87>] ? generic_file_aio_write+0xa6/0xb6
[<ffffffff81383b68>] ? copy_from_user+0x9/0xb
[<ffffffff813846b2>] ? move_addr_to_kernel+0x2b/0x65
[<ffffffff8138e909>] ? copy_from_user+0x9/0xb
[<ffffffff8138ec56>] ? verify_iovec+0x4f/0xa3
[<ffffffff8138516c>] __sys_sendmsg+0x20f/0x29c
[<ffffffff8144c242>] ? sub_preempt_count+0x92/0xa6
[<ffffffff81052ecf>] ? __srcu_read_unlock+0x3b/0x59
[<ffffffff8111d9c0>] ? fsnotify+0x255/0x285
[<ffffffff81385356>] sys_sendmsg+0x3d/0x5b
[<ffffffff8144dfb9>] system_call_fastpath+0x16/0x1b
---[ end trace 7abcbdd8b95b5194 ]---
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2012-03-07 19:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 19:32 Ben Greear [this message]
2012-03-07 19:45 ` bss_info_change_notify warning (hacked 3.3.0-rc5+) Bryan Phillippe
2012-03-28 18:56 ` Ben Greear
2012-03-28 18:59 ` Johannes Berg
2012-03-28 19:10 ` Ben Greear
2012-03-28 19:13 ` Johannes Berg
2012-03-28 19:45 ` Ben Greear
2012-03-29 6:38 ` Johannes Berg
2012-03-29 16:09 ` Ben Greear
2012-03-29 16:17 ` Johannes Berg
2012-04-02 21:58 ` Bryan Phillippe
2012-03-08 6:55 ` Johannes Berg
2012-03-09 18:31 ` Ben Greear
2012-03-12 7:10 ` Johannes Berg
2012-03-12 16:27 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F57B7E6.1050103@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).