From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] kernel panic with ath9k
Date: Wed, 8 Feb 2012 17:54:00 -0500 [thread overview]
Message-ID: <20120208175400.40c00ca8@mj> (raw)
In-Reply-To: <4F32CCB8.8060600@openwrt.org>
On Wed, 08 Feb 2012 20:27:52 +0100
Felix Fietkau <nbd@openwrt.org> wrote:
> On 2012-02-08 8:10 PM, Adrian Chadd wrote:
> > Has anyone figured out why -1 is appearing?
> Maybe it's fixed by the mac80211 patch I submitted today. mac80211 was
> calling .tx_status on the rate control module before .rate_init.
> Just a wild guess...
I can reproduce the problem reliably with just one router (some stock
Linksys router with standard firmware) and one laptop (Asus Eee PC
1005PE with AR9285). 802.11n is not used. I just leave the laptop
turned on overnight, and it catches the warning at some point.
The bug might be "stimulated" by closing the lid and opening it again
while transmitting data (e.g. watching a video). But it doesn't happen
most of the time. And if it does happen, it takes about a couple of
minutes after the connection is reestablished.
This night, I caught two events less than a millisecond apart:
[18311.688446] wlan0: moving STA 00:21:29:a0:c7:b2 to state 1
[18311.688453] wlan0: moving STA 00:21:29:a0:c7:b2 to state 2
[18311.711759] wlan0: moving STA 00:21:29:a0:c7:b2 to state 3
[19634.009730] ath_rc_get_rateindex: rate->idx = -1
[19634.009762] ath_rc_get_rateindex: rate->idx = -1
[23124.212050] wlan0: moving STA 00:21:29:a0:c7:b2 to state 2
[23124.212061] wlan0: moving STA 00:21:29:a0:c7:b2 to state 1
[23124.212068] wlan0: moving STA 00:21:29:a0:c7:b2 to state 0
That's all with compat-wireless-3.3-rc1-2, which is used by Fedora.
Indeed, the memory corruption happens in ath_tx_status(),
the .tx_status function for ath9k rate control, so it's plausible.
I tried applying your patch to compat-wireless-3.3-rc1-2, but it
depends on the patch that introduced WLAN_STA_RATE_CONTROL. And that
patch doesn't apply cleanly because WLAN_STA_INSERTED is not in
compat-wireless-3.3-rc1-2.
The current bleeding edge compat-wireless is for 2012/02/06 and it
needs both the patch that introduces WLAN_STA_RATE_CONTROL and the one
that uses it. At least they can be applied and everything compiles.
I'm going to leave the patched bleeding edge compat-wireless overnight
(with the sanity check I added to the code). I'll report the results.
I believe the patch needs to be backported to Linux 3.3 and older
versions. The Fedora bug 768639 has 74 comments, mostly messages about
duplicate bugs.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2012-02-08 22:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 8:26 [ath9k-devel] kernel panic with ath9k Olivier Keshavjee
2012-02-04 15:48 ` Pavel Roskin
2012-02-07 22:00 ` Pavel Roskin
2012-02-08 19:10 ` Adrian Chadd
2012-02-08 19:27 ` Felix Fietkau
2012-02-08 22:54 ` Pavel Roskin [this message]
2012-02-10 6:05 ` Mohammed Shafi
2012-02-11 4:06 ` Pavel Roskin
2012-02-13 7:36 ` Mohammed Shafi
2012-02-15 14:23 ` Pavel Roskin
2012-02-15 15:48 ` Mohammed Shafi
2012-02-15 18:06 ` Pavel Roskin
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=20120208175400.40c00ca8@mj \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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).