From: Bob Copeland <me@bobcopeland.com>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: kernel crashes, 2.6.30, rt2x00, ath5k, ieee80211_get_*_rate, automatic rate control
Date: Tue, 23 Jun 2009 16:25:41 -0400 [thread overview]
Message-ID: <20090623202541.GA3635@hash.localnet> (raw)
In-Reply-To: <20090623174616.GA3914@linux-m68k.org>
On Tue, Jun 23, 2009 at 07:46:16PM +0200, Richard Zidlicky wrote:
> Got the confirmation that the patch for minstrel indeed does something good
> to me, both on the ath5k and rt73usb side. The code path seems to be trigered
> only in special circumstances in my configuration but the printk did fire on
> both ends after a while.
Good news, thanks for testing. Yeah it generally only occurs if you
have a nearby peer with a single (or none) available rates which is
why some people hit it a lot and others not so much.
The patch should already be on the way to stable, but I'll check on it.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-06-23 20:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 13:49 kernel crashes, 2.6.30, rt2x00, ath5k, ieee80211_get_*_rate, automatic rate control Richard Zidlicky
2009-06-21 18:04 ` Bob Copeland
2009-06-21 20:38 ` Richard Zidlicky
2009-06-22 20:15 ` Richard Zidlicky
2009-06-23 17:46 ` Richard Zidlicky
2009-06-23 20:25 ` Bob Copeland [this message]
2009-06-25 8:36 ` Richard Zidlicky
2009-07-05 12:31 ` Bob Copeland
2009-09-28 22:23 ` ath5k, wifi enable hotkeys Richard Zidlicky
2009-10-09 14:39 ` 2.6.31.[12] ath5k regression Richard Zidlicky
2009-10-10 12:58 ` Bob Copeland
2009-10-10 13:31 ` Bob Copeland
2009-10-11 12:26 ` Richard Zidlicky
2009-10-11 13:30 ` Bob Copeland
2009-10-11 22:00 ` Richard Zidlicky
2009-10-11 22:23 ` Bob Copeland
2009-10-12 20:23 ` Richard Zidlicky
2009-10-12 23:54 ` Bob Copeland
2009-10-13 19:37 ` Richard Zidlicky
2009-12-06 9:49 ` 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=20090623202541.GA3635@hash.localnet \
--to=me@bobcopeland.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.