From: Will Keaney <keaneyw@gmail.com>
To: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: [Fwd: Re: Trouble Associating with ath5k on AR5212]
Date: Wed, 08 Apr 2009 09:38:43 -0400 [thread overview]
Message-ID: <49DCA8E3.3060603@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]
Looks like thunderbird chose to send as HTML again...
-------- Original Message --------
Bob Copeland wrote:
> On Mon, Apr 06, 2009 at 10:02:45PM -0400, Will Keaney wrote:
>
>> As before, I didn't see any additional dmesg output from athk, even with
>> 'dmesg -n7'.
>>
>
> Hmm, you should be seeing association requests in any case. How are
> you starting the wireless network? Can you try setting the -dd option
> to wpa_supplicant?
>
I'm starting it by modprobing ath5k or ath_pci, depending on what needs
to be tested. udev calls Gentoo's init script for the interface that's
created, which starts wpa_supplicant. I can add debugging flags as well.
When testing with the guest wireless at work today, I got the attached
error in dmesg. I only got it once, and haven't been able to reproduce
it, but thought it might be of interest.
Will
[-- Attachment #1.2: error.txt --]
[-- Type: text/plain, Size: 2376 bytes --]
[ 6260.056196] ------------[ cut here ]------------
[ 6260.056206] WARNING: at drivers/net/wireless/ath5k/base.c:1099 ath5k_tasklet_
rx+0x380/0x516 [ath5k]()
[ 6260.056213] Hardware name: 6459CTO
[ 6260.056218] invalid hw_rix: 1a
[ 6260.056222] Modules linked in: ath5k bnep rfcomm l2cap bluetooth bridge stp l
lc nvidia(P) cpufreq_ondemand oss_usb oss_hdaudio osscore fuse cpufreq_conservat
ive acpi_cpufreq freq_table i2c_i801 i2c_core video output rtc thermal e1000e pc
spkr processor button battery ac evdev [last unloaded: wlan]
[ 6260.056297] Pid: 0, comm: swapper Tainted: P 2.6.29-wl-dirty #10
[ 6260.056303] Call Trace:
[ 6260.056308] <IRQ> [<ffffffff8023aaa3>] warn_slowpath+0xd3/0x10f
[ 6260.056334] [<ffffffff804191d7>] ? synaptics_process_byte+0x6e3/0x700
[ 6260.056344] [<ffffffff804feb4f>] ? _spin_lock_irqsave+0x18/0x34
[ 6260.056352] [<ffffffff804fed34>] ? _spin_unlock_irqrestore+0x12/0x2b
[ 6260.056362] [<ffffffff8033d0e3>] ? map_single+0x186/0x207
[ 6260.056371] [<ffffffff8033ca25>] ? swiotlb_virt_to_bus+0x1f/0x23
[ 6260.056382] [<ffffffff802228ea>] ? swiotlb_map_single_phys+0x0/0x18
[ 6260.056390] [<ffffffff804feb4f>] ? _spin_lock_irqsave+0x18/0x34
[ 6260.056398] [<ffffffff804fed34>] ? _spin_unlock_irqrestore+0x12/0x2b
[ 6260.056406] [<ffffffff8033ce09>] ? unmap_single+0xd8/0xe1
[ 6260.056415] [<ffffffff8033cf46>] ? swiotlb_unmap_single_attrs+0x56/0x5f
[ 6260.056434] [<ffffffffa096e49a>] ath5k_tasklet_rx+0x380/0x516 [ath5k]
[ 6260.056444] [<ffffffff8023f4b9>] tasklet_action+0xbc/0x126
[ 6260.056452] [<ffffffff8023fe11>] __do_softirq+0x60/0x10b
[ 6260.056461] [<ffffffff8020d1ec>] call_softirq+0x1c/0x28
[ 6260.056469] [<ffffffff8020e77c>] do_softirq+0x34/0x76
[ 6260.056477] [<ffffffff8023fb44>] irq_exit+0x36/0x7e
[ 6260.056484] [<ffffffff8020e9fb>] do_IRQ+0xda/0x10b
[ 6260.056492] [<ffffffff8020ca93>] ret_from_intr+0x0/0xa
[ 6260.056497] <EOI> [<ffffffffa00215f3>] ? acpi_idle_enter_bm+0x2ec/0x372 [pr
ocessor]
[ 6260.056531] [<ffffffffa00215e9>] ? acpi_idle_enter_bm+0x2e2/0x372 [processor
]
[ 6260.056541] [<ffffffff80257759>] ? tick_nohz_get_sleep_length+0x1a/0x31
[ 6260.056551] [<ffffffff8041f9d0>] ? cpuidle_idle_call+0x99/0xd1
[ 6260.056559] [<ffffffff8020b214>] ? cpu_idle+0x4f/0xa7
[ 6260.056568] [<ffffffff804ede71>] ? rest_init+0x75/0x77
[ 6260.056575] ---[ end trace e77764ee08516feb ]---
[-- Attachment #1.3: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next reply other threads:[~2009-04-08 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 13:38 Will Keaney [this message]
2009-04-08 14:58 ` [Fwd: Re: Trouble Associating with ath5k on AR5212] Bob Copeland
2009-04-08 15:44 ` Will Keaney
2009-04-08 16:20 ` Bob Copeland
2009-04-08 16:27 ` Will Keaney
2009-04-08 17:43 ` Will Keaney
2009-04-17 20:02 ` Will Keaney
-- strict thread matches above, loose matches on Subject: below --
2009-04-03 11:47 Will Keaney
2009-04-03 11:46 Will Keaney
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=49DCA8E3.3060603@gmail.com \
--to=keaneyw@gmail.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).