From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.org>,
Ben Greear <greearb@candelatech.com>
Subject: Re: WARN_ON in ieee80211_scan_completed_finish triggered
Date: Mon, 07 Mar 2011 12:44:57 +0100 [thread overview]
Message-ID: <1299498297.3790.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1299498147.5665.3.camel@marge>
On Mon, 2011-03-07 at 12:42 +0100, Michael Buesch wrote:
> On Mon, 2011-03-07 at 10:51 +0100, Johannes Berg wrote:
> > On Sun, 2011-03-06 at 21:25 +0100, Michael Buesch wrote:
> > > I just noticed the following warning on my p54spi device
> > > with compat-wireless-2011-02-25 (OpenWrt):
> > >
> >
> > > [ 1182.826599] WARNING: at net/mac80211/scan.c:310 ieee80211_rx_bss_free+0x20c/0x4b8 [mac80211]()
> >
> > Unfortunately the backtrace gives no hint at all, is it possible that
> > there was an ifdown that canceled the scan?
>
> I don't think there was an ifdown.
Ok
> It seems that it happened right after a regulatory
> update. See printk timestamps in the full kernel log:
> [ 1182.269927] cfg80211: Calling CRDA for country: DE
> [ 1182.369659] cfg80211: Regulatory domain changed to country: DE
> [ 1182.376586] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> [ 1182.386138] cfg80211: (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
> [ 1182.395385] cfg80211: (5150000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> [ 1182.404449] cfg80211: (5250000 KHz - 5350000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> [ 1182.413146] cfg80211: (5470000 KHz - 5725000 KHz @ 40000 KHz), (N/A, 2698 mBm)
> [ 1182.821472] ------------[ cut here ]------------
> [ 1182.826599] WARNING: at /home/mb/develop/svn/openwrt_n810/trunk/build_dir/linux-omap24xx/compat-wireless-2011-02-25/net/mac80211/scan.c:310 ieee80211_rx_bss_free+0x20c/0x4b8 [mac80211]()
It's still almost half a second, and the regulatory update was because
you connected to an AP that had a country IE. It could be related, but I
doubt it.
johannes
next prev parent reply other threads:[~2011-03-07 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 20:25 WARN_ON in ieee80211_scan_completed_finish triggered Michael Buesch
2011-03-07 9:51 ` Johannes Berg
2011-03-07 11:42 ` Michael Buesch
2011-03-07 11:44 ` Johannes Berg [this message]
2011-03-07 12:03 ` Johannes Berg
2011-03-07 13:14 ` Johannes Berg
2011-03-07 13:59 ` Michael Buesch
2011-03-07 14:22 ` Stanislaw Gruszka
2011-03-07 14:30 ` Johannes Berg
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=1299498297.3790.3.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=nbd@openwrt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.