From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath5k: fix print on warning on ath5k_hw_to_driver_rix()
Date: Tue, 25 Aug 2009 11:58:42 -0700 [thread overview]
Message-ID: <20090825185842.GA7357@mosca> (raw)
In-Reply-To: <b6c5339f0908251145h3a075b86hab00d2223f9acc58@mail.gmail.com>
On Tue, Aug 25, 2009 at 11:45:12AM -0700, Bob Copeland wrote:
> On Tue, Aug 25, 2009 at 2:25 PM, Luis R.
> Rodriguez<lrodriguez@atheros.com> wrote:
> > This was printing the wrong value on the warning. While at it
> > lets expand this warning to provide a little more useful
> > information for debugging such as the band and hardware rate
> > index when possible and clarify what the warning is actually
> > printing.
>
> > rix = sc->rate_idx[sc->curband->band][hw_rix];
> > - if (WARN(rix < 0, "invalid hw_rix: %x\n", hw_rix))
> > + if (WARN(rix < 0, "invalid driver rate index: %x "
> > + "(hw_rix: %x band: %s)\n", rix, hw_rix,
> > + sc->curband->band ? "5 GHz" : "2.4 GHz"))
>
> rix will always be -1 here so no real need to print it.
OK how about the band info, think that's useful?
> I'm pretty sure band is going to be "the wrong one," because all
> instances of this warning I've seen have been valid rate indexes,
> like 1 mbit rates when scanning 5 ghz,
I got this on 0x1b which is ATH5K_RATE_CODE_1M, I was suspecting
the same.
> which could indicate some
> race condition with flushing the rx queue on channel changes.
I'll see if I can reproduce somehow.
> I haven't yet seen a hw rate we didn't know about.
So you've seen this lately as well?
Luis
next prev parent reply other threads:[~2009-08-25 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 18:25 [PATCH] ath5k: fix print on warning on ath5k_hw_to_driver_rix() Luis R. Rodriguez
2009-08-25 18:45 ` Bob Copeland
2009-08-25 18:58 ` Luis R. Rodriguez [this message]
2009-08-25 19:22 ` Bob Copeland
2009-08-25 23:38 ` Luis R. Rodriguez
2009-08-25 23:52 ` Luis R. Rodriguez
2009-08-26 14:08 ` Bob Copeland
2009-08-26 16:29 ` Luis R. Rodriguez
2009-08-26 17:03 ` Bob Copeland
2009-08-26 20:20 ` Luis R. Rodriguez
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=20090825185842.GA7357@mosca \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).