From: Bob Copeland <me@bobcopeland.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Nick Kossifidis <mickflemm@gmail.com>
Subject: Re: ath5k warning on bitrate
Date: Wed, 12 Aug 2009 12:51:55 -0400 [thread overview]
Message-ID: <b6c5339f0908120951u76c9ac9amfb006ba4960a07c9@mail.gmail.com> (raw)
In-Reply-To: <43e72e890908120945l14f6590ev38f7083a1b1dae8@mail.gmail.com>
On Wed, Aug 12, 2009 at 12:45 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> I have some patches on top of this for ath5k but I doubt they were the
> culprit. The warning comes from the second check:
> rix = sc->rate_idx[sc->curband->band][hw_rix];
> if (WARN(rix < 0, "invalid hw_rix: %x\n", hw_rix))
> rix = 0;
Just another case of sc->curband being wrong when processing this.
> [ 402.717626] ath5k phy0: noise floor calibration timeout (2462MHz)
Because of a scan. Did we break the thing that flushed rx processing
on channel changes?
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2009-08-12 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 16:45 ath5k warning on bitrate Luis R. Rodriguez
2009-08-12 16:51 ` Bob Copeland [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=b6c5339f0908120951u76c9ac9amfb006ba4960a07c9@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.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