linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: bss_info_change_notify warning (hacked 3.3.0-rc5+)
Date: Mon, 12 Mar 2012 09:27:29 -0700	[thread overview]
Message-ID: <4F5E23F1.1010501@candelatech.com> (raw)
In-Reply-To: <1331536233.3496.6.camel@jlt3.sipsolutions.net>

On 03/12/2012 12:10 AM, Johannes Berg wrote:
> On Fri, 2012-03-09 at 10:31 -0800, Ben Greear wrote:
>> On 03/07/2012 10:55 PM, Johannes Berg wrote:
>>> On Wed, 2012-03-07 at 11:32 -0800, Ben Greear wrote:
>>>> 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)
>>>
>>> The warning means you're modifying an interface the driver doesn't (yet)
>>> know about.
>>>
>>> It's odd that you should be running into this on config_beacon() though
>>> since that can only execute when the interface is up ... can you print
>>> out the interface name in the warning?
>>
>> This is still reproducible in 3.3.0-rc6+ from yesterday.
>>
>>
>> I create the VAP with this command:
>>
>> ./local/sbin/iw phy wiphy0 interface add vap0 type __ap
>>
>>
>> vap0:  Failed check-sdata-in-driver check, flags: 0x0
>
> That's it? That doesn't create a warning here, and somehow you're
> running into nl80211_set_wiphy() which isn't called if you execute just
> that iw command.

Well, there's a lot of other stuff going on too.  Power is set, for one
thing, hostapd is started, etc.

I will see if I can come up with a easy way to reproduce this, but
it might be a few days as I'm stacked up with work at the moment.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2012-03-12 16:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 19:32 bss_info_change_notify warning (hacked 3.3.0-rc5+) Ben Greear
2012-03-07 19:45 ` 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 [this message]

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=4F5E23F1.1010501@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --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).