From: Christian Lamparter <chunkeey@web.de>
To: Bob Copeland <me@bobcopeland.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Johannes Berg <johannes@sipsolutions.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: WARN_ON at minstrel_get_rate (include/net/mac80211.h:2111) with p54usb
Date: Sun, 19 Jul 2009 00:32:57 +0200 [thread overview]
Message-ID: <200907190032.58156.chunkeey@web.de> (raw)
In-Reply-To: <b6c5339f0907181419h28b84166s72ba9386f2833c61@mail.gmail.com>
On Saturday 18 July 2009 23:19:36 Bob Copeland wrote:
> On Sat, Jul 18, 2009 at 11:03 AM, Larry Finger<Larry.Finger@lwfinger.net> wrote:
> > Christian Lamparter wrote:
> >> On Saturday 18 July 2009 03:05:04 Larry Finger wrote:
> >>> Johannes and Christian,
> >>>
> >>> I am getting a WARN_ON from mac80211 in the location stated in the
> >>> subject. I put in some test prints and got the following:
> >>>
> >>> sband->n_bitrates 8, Band 1, supp_rates 0x0
> >> hmm, so something decides to talk to a 5GHz network here?
> >> But the AP doesn't have any available rates in that band!?
> >
> > Ah, band 1 is 5GHz, not 2.4. There are no 802.11a AP's in my neighborhood.
> >
> >> If my memory serves my right some people have triggered the same WARN_ON
> >> with the ath5k driver as well...
> >> unfortunately, I didn't follow the thread and now I can't find it anymore.
> >>
> >> (btw: is your b43 11a capable as well?)
> >
> > Yes it is, but that section is software crippled.
> >
> > Thanks for the patch. I'll let you know what happens.
>
> In the ath5k case as well, I'm willing to bet it has something to do with dual
> band operation. IIRC at least some instances of this in the past were due to
> getting the rate after the band was changed, e.g. due to scanning, and the peer
> of course didn't support any rates on that band.
>
well, ieee80211_sta_monitor_work - which probes the AP every now and then -
didn't check if we're scanning.
The attached diff survives a non-stop scanning without throwing the WARN in
rate_lowest_index once.
However, I'm not so sure about the locking for hw_scanning and sw_scanning.
It looks like only scan.c manipulates them under the scan mutex.
But then, do we need locking for a single threaded workqueue? guess not.
---
Larry,
here's another _fix_ which might even fix the problem after all ;-)
Regards,
Chr
---
diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
index 18dad22..4833e7c 100644
--- a/net/mac80211/mlme.c
+++ b/net/mac80211/mlme.c
@@ -2210,6 +2210,9 @@ static void ieee80211_sta_monitor_work(struct work_struct *work)
container_of(work, struct ieee80211_sub_if_data,
u.mgd.monitor_work);
+ if (sdata->local->sw_scanning || sdata->local->hw_scanning)
+ return;
+
ieee80211_mgd_probe_ap(sdata, false);
}
next prev parent reply other threads:[~2009-07-18 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A611FC0.9040507@lwfinger.net>
[not found] ` <200907181433.47985.chunkeey@web.de>
2009-07-18 15:03 ` WARN_ON at minstrel_get_rate (include/net/mac80211.h:2111) with p54usb Larry Finger
2009-07-18 16:08 ` WARN_ON at minstrel_get_rate (include/net/mac80211.h:2111) Christian Lamparter
2009-07-18 17:48 ` Christian Lamparter
2009-07-20 16:17 ` Luis R. Rodriguez
2009-07-18 21:19 ` WARN_ON at minstrel_get_rate (include/net/mac80211.h:2111) with p54usb Bob Copeland
2009-07-18 22:32 ` Christian Lamparter [this message]
2009-07-19 14:37 ` Larry Finger
2009-07-19 20:09 ` [PATCH] mac80211: do not monitor the connection while scanning Christian Lamparter
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=200907190032.58156.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=Larry.Finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
/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.