linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [Fwd: Re: Trouble Associating with ath5k on AR5212]
@ 2009-04-08 13:38 Will Keaney
  2009-04-08 14:58 ` Bob Copeland
  0 siblings, 1 reply; 9+ messages in thread
From: Will Keaney @ 2009-04-08 13:38 UTC (permalink / raw)
  To: Linux Wireless


[-- 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 --]

^ permalink raw reply	[flat|nested] 9+ messages in thread
* [Fwd: Re: Trouble Associating with ath5k on AR5212]
@ 2009-04-03 11:47 Will Keaney
  0 siblings, 0 replies; 9+ messages in thread
From: Will Keaney @ 2009-04-03 11:47 UTC (permalink / raw)
  To: Linux Wireless

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

Forwarding back to the list, as I was silly and sent as HTML originally...

-------- Original Message --------
Bob Copeland wrote:
> On Thu, Apr 02, 2009 at 09:20:05PM -0400, Will Keaney wrote:
>   
>> For what it's worth, I have also tried using iwconfig to associate to
>> the neighbor's network under ath5k without success.  So I don't think
>> it's related to wpa_supplicant's scanning algorithm.
>>     
>
> Well it's a long shot but I thought I'd mention it because I had
> very similar results due to long scans, where wpa_supplicant would
> time out and fail associations.  
>
> Try 'dmesg -n 7', then capture the output of dmesg while trying to
> associate, that should show the reason (CONFIG_PRINTK_TIME=y is helpful
> too). 
>   
dmesg shows this:
[38645.639170] ath5k 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> 
IRQ 17
[38645.639199] ath5k 0000:03:00.0: setting latency timer to 64
[38645.639342] ath5k 0000:03:00.0: registered as 'phy5'
[38645.872038] phy5: Selected rate control algorithm 'minstrel'
[38645.882037] Registered led device: ath5k-phy5::rx
[38645.882090] Registered led device: ath5k-phy5::tx
[38645.882097] ath5k phy5: Atheros AR5414 chip found (MAC: 0xa3, PHY: 0x61)
[38646.133614] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[38667.211026] ath5k phy5: noise floor calibration timeout (5785MHz)

I think the key there is the last line.  There is no further output in 
dmesg, regardless of what I do in wpa_supplicant.

Thanks,

Will Keaney

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 271 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread
* [Fwd: Re: Trouble Associating with ath5k on AR5212]
@ 2009-04-03 11:46 Will Keaney
  0 siblings, 0 replies; 9+ messages in thread
From: Will Keaney @ 2009-04-03 11:46 UTC (permalink / raw)
  To: Linux Wireless

[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]

Forwarding back to the list, as I was silly and sent as HTML originally...

-------- Original Message --------
Bob Copeland wrote:
> On Thu, Apr 2, 2009 at 10:12 AM, Will Keaney <keaneyw@gmail.com> wrote:
>   
>> Hello,
>> I have been following the wireless-testing branch for a few months,
>> hoping with each revision that my Atheros card would finally work
>> properly with ath5k. �So far, I've been able to scan for and see nearby
>> networks, but I haven't been able to associate to them.
>>     
>
> Does limiting wpa_supplicant to only scan the 2 GHz channels help?
>
> e.g. setting "scan_freq=2412 2437 2462" in your wpa_supplicant.conf
> scans 1 6 and 11.
>   
Thanks for the suggestion.  It appears that my installed version of 
wpa_supplicant does not support the scan_freq parameter.  A google 
search found precisely one example of it being used, in a sample 
wpa_supplicant.conf in the epitest git repo.
For what it's worth, I have also tried using iwconfig to associate to 
the neighbor's network under ath5k without success.  So I don't think 
it's related to wpa_supplicant's scanning algorithm.

Will Keaney

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 271 bytes --]

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2009-04-17 20:02 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-08 13:38 [Fwd: Re: Trouble Associating with ath5k on AR5212] Will Keaney
2009-04-08 14:58 ` 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

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).