From: Harvey Harrison <harvey.harrison@gmail.com>
To: Christian Lamparter <chunkeey@web.de>
Cc: Michael Buesch <mb@bu3sch.de>,
John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Lots of minstrel WARN_ONS with current -git
Date: Thu, 15 Jan 2009 09:20:13 -0800 [thread overview]
Message-ID: <1232040014.5595.1.camel@brick> (raw)
In-Reply-To: <200901151813.57146.chunkeey@web.de>
On Thu, 2009-01-15 at 18:13 +0100, Christian Lamparter wrote:
> On Thursday 15 January 2009 17:50:51 Harvey Harrison wrote:
> > On Thu, 2009-01-15 at 17:31 +0100, Christian Lamparter wrote:
> > > On Thursday 15 January 2009 16:33:11 Michael Buesch wrote:
> > > > On Wednesday 14 January 2009 23:51:20 Harvey Harrison wrote:
> > > > > Seeing lots of these WARN_ONS with current -git. Known issue?
> > > > >
> > > > > b43 hardware.
> > > > >
> > > > > [41850.615621] WARNING: at net/mac80211/rc80211_minstrel.c:69 minstrel_rate_init+0x92/0x3c0()
> > > >
> > > > I think that happens, if you have a b-only AP.
> > >
> > > erm, see : "minstrel: fix warning if lowest supported rate index is not 0"
> > > ( http://www.spinics.net/lists/linux-wireless/msg25799.html )
> > >
> > > The fix is in wireless-testing & wireless-next since a few days now...
> > > Or is this a new bug?
> >
> > I'll try that out shortly, report was against linus mainline.
> >
> Oh? with 2.6.28 or the current 2.6.29-rcX line?
> If you get this WARNING with 2.6.29-rcX, you don't have to worry...
> http://patchwork.kernel.org/patch/2184/
>
Yeah, somewhere a little past 2.6.29-rc1, thanks again.
Harvey
prev parent reply other threads:[~2009-01-15 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 22:51 Lots of minstrel WARN_ONS with current -git Harvey Harrison
2009-01-15 15:33 ` Michael Buesch
2009-01-15 16:31 ` Christian Lamparter
2009-01-15 16:50 ` Harvey Harrison
2009-01-15 17:13 ` Christian Lamparter
2009-01-15 17:20 ` Harvey Harrison [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=1232040014.5595.1.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=chunkeey@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).