From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath5k: invalid hw_rix with 64 stations.
Date: Wed, 01 Dec 2010 16:54:27 -0800 [thread overview]
Message-ID: <4CF6EE43.2020905@candelatech.com> (raw)
In-Reply-To: <4CF6ED18.5010704@candelatech.com>
On 12/01/2010 04:49 PM, Ben Greear wrote:
> 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:
Here's another one from a non-tainted kernel. Seems this is trivial
to reproduce.
------------[ cut here ]------------
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]()
Hardware name:
invalid hw_rix: 1b
Modules linked in: 8021q garp stp llc fuse michael_mic macvlan 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 i2c_core output serio_raw pcspkr mii iTCO_wdt iTCO_vendor_support ata_generic pata_acpi [last
unloaded: ipt_addrtype]
Pid: 1225, comm: rsyslogd Tainted: G W 2.6.37-rc4-wl+ #9
Call Trace:
[<8043144d>] warn_slowpath_common+0x77/0x8c
[<f8663994>] ? ath5k_hw_to_driver_rix+0x5b/0x5f [ath5k]
[<f8663994>] ? ath5k_hw_to_driver_rix+0x5b/0x5f [ath5k]
[<804314de>] warn_slowpath_fmt+0x2e/0x30
[<f8663994>] ath5k_hw_to_driver_rix+0x5b/0x5f [ath5k]
[<f8663ba5>] ath5k_tasklet_tx+0x1ab/0x2f0 [ath5k]
[<80435948>] tasklet_action+0x78/0xc1
[<80436034>] __do_softirq+0x75/0x121
[<80435fbf>] ? __do_softirq+0x0/0x121
<IRQ> [<80435f0c>] ? irq_exit+0x29/0x5d
[<804042c9>] ? do_IRQ+0x8e/0xa2
[<80403729>] ? common_interrupt+0x29/0x30
[<8044007b>] ? __queue_work+0x138/0x1af
[<804b8e53>] ? mntput+0x0/0x15
[<804b8fb1>] ? path_put+0x15/0x18
[<8046b551>] ? audit_free_names+0x40/0x59
[<8046b6fe>] ? audit_syscall_exit+0x91/0x10f
[<804031d0>] ? sysexit_audit+0x24/0x44
---[ end trace e87e98eb2549568d ]---
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-12-02 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 0:49 ath5k: invalid hw_rix with 64 stations Ben Greear
2010-12-02 0:54 ` Ben Greear [this message]
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=4CF6EE43.2020905@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 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.