From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: ath5k: invalid hw_rix with 64 stations.
Date: Wed, 01 Dec 2010 16:49:28 -0800 [thread overview]
Message-ID: <4CF6ED18.5010704@candelatech.com> (raw)
We were testing with 64 virtual stations running WPA, with
a single instance of supplicant controlling all interfaces and
the scan-sharing enabled. It was running clean w/out encryption
(and w/out supplicant).
We see a large number of these types of warnings. We had a proprietary
module loaded, but it was not in active use. We're going to reproduce
without it, but in the meantime, here is a representative trace:
Dec 1 16:35:23 localhost kernel: ------------[ cut here ]------------
Dec 1 16:35:23 localhost kernel: WARNING: at /home/greearb/git/linux.wireless-testing-ct/drivers/net/wireless/ath/ath5k/base.c:620
ath5k_hw_to_driver_rix+0x5b/0x5f [ath5k]()
Dec 1 16:35:23 localhost kernel: Hardware name:
Dec 1 16:35:23 localhost kernel: invalid hw_rix: 1b
Dec 1 16:35:23 localhost kernel: Modules linked in: 8021q garp stp llc fuse michael_mic macvlan wanlink(P) pktgen w83627hf hwmon_vid hwmon nfs lockd fscache
nfs_acl auth_rpcgss sunrpc ipv6 dm_multipath uinput arc4 ecb ath5k ath mac80211 cfg80211 e1000e i2c_i801 e100 output iTCO_wdt iTCO_vendor_support mii i2c_core
serio_raw pcspkr ata_generic pata_acpi [last unloaded: ipt_addrtype]
Dec 1 16:35:23 localhost kernel: Pid: 2298, comm: clock-applet Tainted: P 2.6.37-rc4-wl+ #9
Dec 1 16:35:23 localhost kernel: Call Trace:
Dec 1 16:35:23 localhost kernel: [<8043144d>] warn_slowpath_common+0x77/0x8c
Dec 1 16:35:23 localhost kernel: [<f8663994>] ? ath5k_hw_to_driver_rix+0x5b/0x5f [ath5k]
Dec 1 16:35:23 localhost kernel: [<f8663994>] ? ath5k_hw_to_driver_rix+0x5b/0x5f [ath5k]
Dec 1 16:35:23 localhost kernel: [<804314de>] warn_slowpath_fmt+0x2e/0x30
Dec 1 16:35:23 localhost kernel: [<f8663994>] ath5k_hw_to_driver_rix+0x5b/0x5f [ath5k]
Dec 1 16:35:23 localhost kernel: [<f8663ba5>] ath5k_tasklet_tx+0x1ab/0x2f0 [ath5k]
Dec 1 16:35:23 localhost kernel: [<80435948>] tasklet_action+0x78/0xc1
Dec 1 16:35:23 localhost kernel: [<80436034>] __do_softirq+0x75/0x121
Dec 1 16:35:23 localhost kernel: [<80435fbf>] ? __do_softirq+0x0/0x121
Dec 1 16:35:23 localhost kernel: <IRQ> [<80435f0c>] ? irq_exit+0x29/0x5d
Dec 1 16:35:23 localhost kernel: [<804042c9>] ? do_IRQ+0x8e/0xa2
Dec 1 16:35:23 localhost kernel: [<80403729>] ? common_interrupt+0x29/0x30
Dec 1 16:35:23 localhost kernel: ---[ end trace 5cdceca81890f6e3 ]---
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2010-12-02 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 0:49 Ben Greear [this message]
2010-12-02 0:54 ` ath5k: invalid hw_rix with 64 stations Ben Greear
2010-12-02 4:19 ` Nick Kossifidis
2010-12-02 6:25 ` Ben Greear
2010-12-02 16:18 ` Nick Kossifidis
2010-12-02 18:16 ` Ben Greear
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=4CF6ED18.5010704@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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).