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: Bryan Phillippe <Bryan.Phillippe@watchguard.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: bss_info_change_notify warning (hacked 3.3.0-rc5+)
Date: Wed, 28 Mar 2012 12:10:05 -0700	[thread overview]
Message-ID: <4F73620D.507@candelatech.com> (raw)
In-Reply-To: <1332961193.3479.40.camel@jlt3.sipsolutions.net>

On 03/28/2012 11:59 AM, Johannes Berg wrote:
> On Wed, 2012-03-28 at 11:56 -0700, Ben Greear wrote:
>> On 03/07/2012 11:45 AM, Bryan Phillippe wrote:
>>>
>>> Yes, it's a known problem.  It's very reproducible for me on a non-hacked 3.3-rc1 as well: changing from AP to client mode, or setting up multiple APs, or changing from 2.4Ghz to 5Ghz all seem to trigger this warning with various stack traces.
>>
>> I'm still seeing this and related warnings on 3.3.0.  At least some
>> of them comes from calls the 'hostapd' process makes (I printed
>> current->comm in the warning).
>>
>> I am not having luck writing a simple script that reproduce this,
>> but my application that creates a VAP and bunch of virtual station
>> hits it every time on startup.
>>
>> Bryan:  Do you have a simple script that reproduces this problem?
>>
>> Johannes:  Any ideas on likely causes of this problem?  Might help
>> me zero in on the problem quicker...
>
> Hm. Maybe this is the problem?
>
> http://p.sipsolutions.net/d432de678ae3ff17.txt

I don't see any code that matches that in 3.3.0 (nothing with nl80211_start_ap, for instance)

Thanks,
Ben

>
> johannes


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


  reply	other threads:[~2012-03-28 19:10 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 [this message]
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=4F73620D.507@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=Bryan.Phillippe@watchguard.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).