linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rc80211_minstrel.c:70 WARNING with 2.6.34-rc4
Date: Mon, 19 Apr 2010 12:34:15 -0400	[thread overview]
Message-ID: <1271694855.9026.51.camel@mj> (raw)
In-Reply-To: <20100418085653.GA7345@linux-m68k.org>

On Sun, 2010-04-18 at 10:56 +0200, Richard Zidlicky wrote:
> Hi,
> 
> I am getting tons of these http://www.kerneloops.org/submitresult.php?number=3048061,
> appears every packet triggers that.

The warning comes from the function rix_to_ndx() in rc80211_minstrel.c:

/* convert mac80211 rate index to local array index */
static inline int
rix_to_ndx(struct minstrel_sta_info *mi, int rix)
{
        int i = rix;
        for (i = rix; i >= 0; i--)
                if (mi->r[i].rix == rix)
                        break;
        WARN_ON(i < 0);
        return i;
}

> Can provide lots of debugging info.

My impression is that WARN_ON is not warranted in that function, but it
would be interesting to know how you got to that point.

What driver are you using?  What is the mode for the interface? What is
your hardware?  Is there anything unusual you do that triggers the
warning?  Are you using 5 GHz band by any chance?  Are you using
2.6.34-rc4 or it's compat-wireless compiled for another kernel?

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2010-04-19 16:34 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 [this message]
2010-04-19 17:41   ` Richard Zidlicky
2010-04-19 17:41     ` Felix Fietkau
2010-04-19 17:55       ` Richard Zidlicky
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=1271694855.9026.51.camel@mj \
    --to=proski@gnu.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rz@linux-m68k.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).