From: Richard Zidlicky <rz@linux-m68k.org>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Pavel Roskin <proski@gnu.org>, linux-wireless@vger.kernel.org
Subject: Re: rc80211_minstrel.c:70 WARNING with 2.6.34-rc4
Date: Mon, 19 Apr 2010 19:55:08 +0200 [thread overview]
Message-ID: <20100419175508.GB5312@linux-m68k.org> (raw)
In-Reply-To: <4BCC95CC.7030109@openwrt.org>
On Mon, Apr 19, 2010 at 07:41:32PM +0200, Felix Fietkau wrote:
> This warning typically shows up, whenever the driver reports a rate to
> minstrel in the tx status that is not part of the supported/negotiated
> rate set - that's the reason the index lookup above fails.
can that happen when both ends are configured to a fixed rate of 11M?
Richard
next prev parent reply other threads:[~2010-04-19 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 8:56 rc80211_minstrel.c:70 WARNING with 2.6.34-rc4 Richard Zidlicky
2010-04-19 16:34 ` Pavel Roskin
2010-04-19 17:41 ` Richard Zidlicky
2010-04-19 17:41 ` Felix Fietkau
2010-04-19 17:55 ` Richard Zidlicky [this message]
2010-04-19 18:00 ` Felix Fietkau
2010-04-22 21:38 ` Pavel Roskin
2010-04-22 22:15 ` Richard Zidlicky
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=20100419175508.GB5312@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=proski@gnu.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).