* Re: ath9k/ath5k + 80211s crash
@ 2009-06-02 3:52 austinxxh-ath9k
2009-06-02 3:58 ` Bob Copeland
2009-06-02 16:58 ` Andrey Yurovsky
0 siblings, 2 replies; 12+ messages in thread
From: austinxxh-ath9k @ 2009-06-02 3:52 UTC (permalink / raw)
To: linux-wireless, ath9k-devel, devel
Sorry, it should be "ath9k reboots, ath5k crashes, the dump log is for ath5k, while ath9k displayed nothing".
--- On Mon, 6/1/09, austinxxh-ath9k@yahoo.com <austinxxh-ath9k@yahoo.com> wrote:
> From: austinxxh-ath9k@yahoo.com <austinxxh-ath9k@yahoo.com>
> Subject: ath9k/ath5k + 80211s crash
> To: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org, devel@lists.open80211s.org
> Date: Monday, June 1, 2009, 10:43 PM
>
> Below is what I saw today(compat-wireless 2009-05-21), I
> have both an ath9k and an ath5k card. ath9k crashes (see
> below), ath5k will just reboot the board after "ifconfig
> mesh up", any idea?
> thanks,
> X Xiao
>
>
> BusyBox v1.13.4 (2009-06-01 21:18:32 CDT) built-in shell
> (ash)
> Enter 'help' for a list of built-in commands.
>
> _______
> ________
> __
> |
> |.-----.-----.-----.| |
> | |.----.| |_
> | - || _
> | -__| || |
> | || _|| _|
>
> |_______|| __|_____|__|__||________||__|
> |____|
> |__| W I R E L E S
> S F R E E D O M
> KAMIKAZE (bleeding edge, r16290) -------------------
> * 10 oz Vodka Shake
> well with ice and strain
> * 10 oz Triple sec mixture into 10 shot
> glasses.
> * 10 oz lime juice Salute!
> ---------------------------------------------------
> root@OpenWrt:/# iw dev wlan0 interface add mesh type mp
> mesh_id mesh
> root@OpenWrt:/# ifconfig -a | grep mesh
> mesh Link encap:Ethernet HWaddr
> 00:0B:6B:57:09:37
> root@OpenWrt:/# ifconfig mesh up
> PCI error 1 at PCI addr 0x100109dc
> Data bus error, epc == c024f12c, ra == c024f128
> Oops[#1]:
> Cpu 0
> $ 0 : 00000000 00000000 deadc0de 000ffc00
> $ 4 : b00109dc b0010000 b0010000 0000000a
> $ 8 : 80170000 83aeaed0 00080000 00000000
> $12 : 00000000 839f04a8 802a0818 00000000
> $16 : 000009dc 8016b710 83aea000 000003ff
> $20 : 83aeaea8 8016b6bc 0000001c 00000007
> $24 : 00000000 80070000
>
> $28 : 82c5c000 82c5dc90 7fb0d068 c024f128
> Hi : 000000d8
> Lo : 00000144
> epc : c024f12c 0xc024f12c
> Not tainted
> ra : c024f128 0xc024f128
> Status: 1000f403 KERNEL EXL IE
> Cause : 1080001c
> PrId : 00019374 (MIPS 24Kc)
> Modules linked in: nf_nat_tftp nf_conntrack_tftp nf_nat_irc
> nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp i
> Process ifconfig (pid: 896, threadinfo=82c5c000,
> task=839f0000, tls=00000000)
> Stack : 83aea000 83a9d680 00000000 00000018 83aea000
> 83b109a0 83aea000 83aea000
> 00000300 83b101e0 82cddeb8
> 83b109a8 c025977c c0259700 ffffffff 00000000
> 00000002 00000000 00000003
> 00000000 00080000 00000000 00000000 00000000
> 00000000 00000000 00000000
> 00000000 00000001 83b109a0 82cddec0 c02599e0
> 00000000 c025a164 00000001
> 8009525c 82cddb80 00000300 83b101e0 82cdd800
> ...
> Call Trace:[<c025977c>] 0xc025977c
> [<c0259700>] 0xc0259700
> [<c02599e0>] 0xc02599e0
> [<c025a164>] 0xc025a164
> [<8009525c>] 0x8009525c
> [<c01dcb64>] 0xc01dcb64
> [<c01ff3b8>] 0xc01ff3b8
> [<800dc19c>] 0x800dc19c
> [<c01eb4b0>] 0xc01eb4b0
> [<800b4040>] 0x800b4040
> [<801b85e8>] 0x801b85e8
> [<801b4454>] 0x801b4454
> [<800bdc94>] 0x800bdc94
> [<800bdc94>] 0x800bdc94
> [<801b632c>] 0x801b632c
> [<801b6b80>] 0x801b6b80
> [<801ffbf8>] 0x801ffbf8
> [<801ff9c8>] 0x801ff9c8
> [<801b75f8>] 0x801b75f8
> [<801b75ec>] 0x801b75ec
> [<801a75b8>] 0x801a75b8
> [<800e0890>] 0x800e0890
> [<800e0db0>] 0x800e0db0
> [<801a7e30>] 0x801a7e30
> [<800d5344>] 0x800d5344
> [<800d51c0>] 0x800d51c0
> [<801a7ebc>] 0x801a7ebc
> [<800e0e64>] 0x800e0e64
> [<80062504>] 0x80062504
> [<80062504>] 0x80062504
>
>
> Code: 02a0f809 02042021 8e450008
> <34440800> 0220f809 02052821
> 8e440008 26c21100 3053fffc
> Segmentation fault
>
> _______________________________________________
> Devel mailing list
> Devel@lists.open80211s.org
> http://open80211s.com/mailman/listinfo/devel
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ath9k/ath5k + 80211s crash
2009-06-02 3:52 ath9k/ath5k + 80211s crash austinxxh-ath9k
@ 2009-06-02 3:58 ` Bob Copeland
2009-06-02 16:58 ` Andrey Yurovsky
1 sibling, 0 replies; 12+ messages in thread
From: Bob Copeland @ 2009-06-02 3:58 UTC (permalink / raw)
To: austinxxh-ath9k; +Cc: linux-wireless, ath9k-devel, devel
On Mon, Jun 1, 2009 at 11:52 PM, <austinxxh-ath9k@yahoo.com> wrote:
>
> Sorry, it should be "ath9k reboots, ath5k crashes, the dump log is for ath5k, while ath9k displayed nothing".
Can you fit a debug kernel on your platform? The oops is pretty
unintelligible as-is.
--
Bob Copeland %% www.bobcopeland.com
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ath9k/ath5k + 80211s crash
2009-06-02 3:52 ath9k/ath5k + 80211s crash austinxxh-ath9k
2009-06-02 3:58 ` Bob Copeland
@ 2009-06-02 16:58 ` Andrey Yurovsky
2009-06-02 22:30 ` [ath9k-devel] " Luis R. Rodriguez
2009-06-03 18:21 ` Nick Kossifidis
1 sibling, 2 replies; 12+ messages in thread
From: Andrey Yurovsky @ 2009-06-02 16:58 UTC (permalink / raw)
To: austinxxh-ath9k, devel; +Cc: linux-wireless, ath9k-devel
With wireless-testing from a couple of days ago, an X86 system, and this patch:
http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
ath9k can bring up a mesh point interface and doesn't crash for me,
but there are no mesh beacons, so mesh isn't working. On ath5k, there
are also no beacons and mesh doesn't work, but there's no crash.
On Mon, Jun 1, 2009 at 8:52 PM, <austinxxh-ath9k@yahoo.com> wrote:
>
> Sorry, it should be "ath9k reboots, ath5k crashes, the dump log is for ath5k, while ath9k displayed nothing".
>
> --- On Mon, 6/1/09, austinxxh-ath9k@yahoo.com <austinxxh-ath9k@yahoo.com> wrote:
>
>> From: austinxxh-ath9k@yahoo.com <austinxxh-ath9k@yahoo.com>
>> Subject: ath9k/ath5k + 80211s crash
>> To: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org, devel@lists.open80211s.org
>> Date: Monday, June 1, 2009, 10:43 PM
>>
>> Below is what I saw today(compat-wireless 2009-05-21), I
>> have both an ath9k and an ath5k card. ath9k crashes (see
>> below), ath5k will just reboot the board after "ifconfig
>> mesh up", any idea?
>> thanks,
>> X Xiao
>>
>>
>> BusyBox v1.13.4 (2009-06-01 21:18:32 CDT) built-in shell
>> (ash)
>> Enter 'help' for a list of built-in commands.
>>
>> _______
>> ________
>> __
>> |
>> |.-----.-----.-----.| |
>> | |.----.| |_
>> | - || _
>> | -__| || |
>> | || _|| _|
>>
>> |_______|| __|_____|__|__||________||__|
>> |____|
>> |__| W I R E L E S
>> S F R E E D O M
>> KAMIKAZE (bleeding edge, r16290) -------------------
>> * 10 oz Vodka Shake
>> well with ice and strain
>> * 10 oz Triple sec mixture into 10 shot
>> glasses.
>> * 10 oz lime juice Salute!
>> ---------------------------------------------------
>> root@OpenWrt:/# iw dev wlan0 interface add mesh type mp
>> mesh_id mesh
>> root@OpenWrt:/# ifconfig -a | grep mesh
>> mesh Link encap:Ethernet HWaddr
>> 00:0B:6B:57:09:37
>> root@OpenWrt:/# ifconfig mesh up
>> PCI error 1 at PCI addr 0x100109dc
>> Data bus error, epc == c024f12c, ra == c024f128
>> Oops[#1]:
>> Cpu 0
>> $ 0 : 00000000 00000000 deadc0de 000ffc00
>> $ 4 : b00109dc b0010000 b0010000 0000000a
>> $ 8 : 80170000 83aeaed0 00080000 00000000
>> $12 : 00000000 839f04a8 802a0818 00000000
>> $16 : 000009dc 8016b710 83aea000 000003ff
>> $20 : 83aeaea8 8016b6bc 0000001c 00000007
>> $24 : 00000000 80070000
>>
>> $28 : 82c5c000 82c5dc90 7fb0d068 c024f128
>> Hi : 000000d8
>> Lo : 00000144
>> epc : c024f12c 0xc024f12c
>> Not tainted
>> ra : c024f128 0xc024f128
>> Status: 1000f403 KERNEL EXL IE
>> Cause : 1080001c
>> PrId : 00019374 (MIPS 24Kc)
>> Modules linked in: nf_nat_tftp nf_conntrack_tftp nf_nat_irc
>> nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp i
>> Process ifconfig (pid: 896, threadinfo=82c5c000,
>> task=839f0000, tls=00000000)
>> Stack : 83aea000 83a9d680 00000000 00000018 83aea000
>> 83b109a0 83aea000 83aea000
>> 00000300 83b101e0 82cddeb8
>> 83b109a8 c025977c c0259700 ffffffff 00000000
>> 00000002 00000000 00000003
>> 00000000 00080000 00000000 00000000 00000000
>> 00000000 00000000 00000000
>> 00000000 00000001 83b109a0 82cddec0 c02599e0
>> 00000000 c025a164 00000001
>> 8009525c 82cddb80 00000300 83b101e0 82cdd800
>> ...
>> Call Trace:[<c025977c>] 0xc025977c
>> [<c0259700>] 0xc0259700
>> [<c02599e0>] 0xc02599e0
>> [<c025a164>] 0xc025a164
>> [<8009525c>] 0x8009525c
>> [<c01dcb64>] 0xc01dcb64
>> [<c01ff3b8>] 0xc01ff3b8
>> [<800dc19c>] 0x800dc19c
>> [<c01eb4b0>] 0xc01eb4b0
>> [<800b4040>] 0x800b4040
>> [<801b85e8>] 0x801b85e8
>> [<801b4454>] 0x801b4454
>> [<800bdc94>] 0x800bdc94
>> [<800bdc94>] 0x800bdc94
>> [<801b632c>] 0x801b632c
>> [<801b6b80>] 0x801b6b80
>> [<801ffbf8>] 0x801ffbf8
>> [<801ff9c8>] 0x801ff9c8
>> [<801b75f8>] 0x801b75f8
>> [<801b75ec>] 0x801b75ec
>> [<801a75b8>] 0x801a75b8
>> [<800e0890>] 0x800e0890
>> [<800e0db0>] 0x800e0db0
>> [<801a7e30>] 0x801a7e30
>> [<800d5344>] 0x800d5344
>> [<800d51c0>] 0x800d51c0
>> [<801a7ebc>] 0x801a7ebc
>> [<800e0e64>] 0x800e0e64
>> [<80062504>] 0x80062504
>> [<80062504>] 0x80062504
>>
>>
>> Code: 02a0f809 02042021 8e450008
>> <34440800> 0220f809 02052821
>> 8e440008 26c21100 3053fffc
>> Segmentation fault
>>
>> _______________________________________________
>> Devel mailing list
>> Devel@lists.open80211s.org
>> http://open80211s.com/mailman/listinfo/devel
>>
> _______________________________________________
> Devel mailing list
> Devel@lists.open80211s.org
> http://open80211s.com/mailman/listinfo/devel
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ath9k-devel] ath9k/ath5k + 80211s crash
2009-06-02 16:58 ` Andrey Yurovsky
@ 2009-06-02 22:30 ` Luis R. Rodriguez
2009-06-03 18:21 ` Nick Kossifidis
1 sibling, 0 replies; 12+ messages in thread
From: Luis R. Rodriguez @ 2009-06-02 22:30 UTC (permalink / raw)
To: Andrey Yurovsky
Cc: austinxxh-ath9k@yahoo.com, devel@lists.open80211s.org,
ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
On Tue, Jun 02, 2009 at 09:58:59AM -0700, Andrey Yurovsky wrote:
> With wireless-testing from a couple of days ago, an X86 system, and this patch:
> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
> ath9k can bring up a mesh point interface and doesn't crash for me,
> but there are no mesh beacons, so mesh isn't working. On ath5k, there
> are also no beacons and mesh doesn't work, but there's no crash.
If no one is really interested in fixing we should just disable mesh
for both ath5k and ath9k.
Luis
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ath9k/ath5k + 80211s crash
2009-06-02 16:58 ` Andrey Yurovsky
2009-06-02 22:30 ` [ath9k-devel] " Luis R. Rodriguez
@ 2009-06-03 18:21 ` Nick Kossifidis
2009-06-03 19:52 ` Andrey Yurovsky
1 sibling, 1 reply; 12+ messages in thread
From: Nick Kossifidis @ 2009-06-03 18:21 UTC (permalink / raw)
To: Andrey Yurovsky; +Cc: austinxxh-ath9k, devel, linux-wireless, ath9k-devel
2009/6/2 Andrey Yurovsky <andrey@cozybit.com>:
> With wireless-testing from a couple of days ago, an X86 system, and this patch:
> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
> ath9k can bring up a mesh point interface and doesn't crash for me,
> but there are no mesh beacons, so mesh isn't working. On ath5k, there
> are also no beacons and mesh doesn't work, but there's no crash.
>
Hmm, try adding NL80211_IFTYPE_MESH_POINT here ->
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/pcu.c;h=ec35503f6a40e6b6a1cc4323287b31e7cdd3a428;hb=HEAD#l733
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ath9k/ath5k + 80211s crash
2009-06-03 18:21 ` Nick Kossifidis
@ 2009-06-03 19:52 ` Andrey Yurovsky
2009-06-03 19:59 ` Nick Kossifidis
0 siblings, 1 reply; 12+ messages in thread
From: Andrey Yurovsky @ 2009-06-03 19:52 UTC (permalink / raw)
To: Nick Kossifidis; +Cc: austinxxh-ath9k, devel, linux-wireless, ath9k-devel
On Wed, Jun 3, 2009 at 11:21 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
> 2009/6/2 Andrey Yurovsky <andrey@cozybit.com>:
>> With wireless-testing from a couple of days ago, an X86 system, and this patch:
>> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
>> ath9k can bring up a mesh point interface and doesn't crash for me,
>> but there are no mesh beacons, so mesh isn't working. On ath5k, there
>> are also no beacons and mesh doesn't work, but there's no crash.
>>
>
>
> Hmm, try adding NL80211_IFTYPE_MESH_POINT here ->
>
> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/pcu.c;h=ec35503f6a40e6b6a1cc4323287b31e7cdd3a428;hb=HEAD#l733
It's already there, in ath5k_hw_set_opmode. We'll need to trace
what's going on and see why we don't get beacons. Last night I had an
ath5k MP suddenly start beaconing but I haven't been able to reproduce
that yet.
Xiao -- to test beaconing, I set up a second network interface in
monitor mode and capture frames with wireshark, in my case that's on a
separate PC.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ath9k/ath5k + 80211s crash
2009-06-03 19:52 ` Andrey Yurovsky
@ 2009-06-03 19:59 ` Nick Kossifidis
2009-06-04 17:42 ` Andrey Yurovsky
0 siblings, 1 reply; 12+ messages in thread
From: Nick Kossifidis @ 2009-06-03 19:59 UTC (permalink / raw)
To: Andrey Yurovsky; +Cc: austinxxh-ath9k, devel, linux-wireless, ath9k-devel
2009/6/3 Andrey Yurovsky <andrey@cozybit.com>:
> On Wed, Jun 3, 2009 at 11:21 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>> 2009/6/2 Andrey Yurovsky <andrey@cozybit.com>:
>>> With wireless-testing from a couple of days ago, an X86 system, and this patch:
>>> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
>>> ath9k can bring up a mesh point interface and doesn't crash for me,
>>> but there are no mesh beacons, so mesh isn't working. On ath5k, there
>>> are also no beacons and mesh doesn't work, but there's no crash.
>>>
>>
>>
>> Hmm, try adding NL80211_IFTYPE_MESH_POINT here ->
>>
>> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/pcu.c;h=ec35503f6a40e6b6a1cc4323287b31e7cdd3a428;hb=HEAD#l733
>
> It's already there, in ath5k_hw_set_opmode. We'll need to trace
> what's going on and see why we don't get beacons. Last night I had an
> ath5k MP suddenly start beaconing but I haven't been able to reproduce
> that yet.
736 /* When in AP mode zero timer0 to start TSF */
737 if (ah->ah_op_mode == NL80211_IFTYPE_AP)
738 ath5k_hw_reg_write(ah, 0, AR5K_TIMER0);
We need to do this for NL80211_IFTYPE_MESH_POINT or DBA won't fire up
and beacon queue wont start...
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ath9k/ath5k + 80211s crash
2009-06-03 19:59 ` Nick Kossifidis
@ 2009-06-04 17:42 ` Andrey Yurovsky
2009-06-05 3:39 ` Nick Kossifidis
0 siblings, 1 reply; 12+ messages in thread
From: Andrey Yurovsky @ 2009-06-04 17:42 UTC (permalink / raw)
To: Nick Kossifidis; +Cc: austinxxh-ath9k, devel, linux-wireless, ath9k-devel
On Wed, Jun 3, 2009 at 12:59 PM, Nick Kossifidis <mickflemm@gmail.com> wrote:
> 2009/6/3 Andrey Yurovsky <andrey@cozybit.com>:
>> On Wed, Jun 3, 2009 at 11:21 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>>> 2009/6/2 Andrey Yurovsky <andrey@cozybit.com>:
>>>> With wireless-testing from a couple of days ago, an X86 system, and this patch:
>>>> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
>>>> ath9k can bring up a mesh point interface and doesn't crash for me,
>>>> but there are no mesh beacons, so mesh isn't working. On ath5k, there
>>>> are also no beacons and mesh doesn't work, but there's no crash.
>>>>
>>>
>>>
>>> Hmm, try adding NL80211_IFTYPE_MESH_POINT here ->
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/pcu.c;h=ec35503f6a40e6b6a1cc4323287b31e7cdd3a428;hb=HEAD#l733
>>
>> It's already there, in ath5k_hw_set_opmode. We'll need to trace
>> what's going on and see why we don't get beacons. Last night I had an
>> ath5k MP suddenly start beaconing but I haven't been able to reproduce
>> that yet.
>
> 736 /* When in AP mode zero timer0 to start TSF */
> 737 if (ah->ah_op_mode == NL80211_IFTYPE_AP)
> 738 ath5k_hw_reg_write(ah, 0, AR5K_TIMER0);
>
> We need to do this for NL80211_IFTYPE_MESH_POINT or DBA won't fire up
> and beacon queue wont start...
Thanks Nik, that gets beaconing going but only after a issuing a scan
(we have the same problem on rt2x00).
> --
> GPG ID: 0xD21DB2DB
> As you read this post global entropy rises. Have Fun ;-)
> Nick
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: ath9k/ath5k + 80211s crash
2009-06-04 17:42 ` Andrey Yurovsky
@ 2009-06-05 3:39 ` Nick Kossifidis
0 siblings, 0 replies; 12+ messages in thread
From: Nick Kossifidis @ 2009-06-05 3:39 UTC (permalink / raw)
To: Andrey Yurovsky; +Cc: austinxxh-ath9k, devel, linux-wireless, ath9k-devel
2009/6/4 Andrey Yurovsky <andrey@cozybit.com>:
> On Wed, Jun 3, 2009 at 12:59 PM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>> 2009/6/3 Andrey Yurovsky <andrey@cozybit.com>:
>>> On Wed, Jun 3, 2009 at 11:21 AM, Nick Kossifidis <mickflemm@gmail.com> wrote:
>>>> 2009/6/2 Andrey Yurovsky <andrey@cozybit.com>:
>>>>> With wireless-testing from a couple of days ago, an X86 system, and this patch:
>>>>> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
>>>>> ath9k can bring up a mesh point interface and doesn't crash for me,
>>>>> but there are no mesh beacons, so mesh isn't working. On ath5k, there
>>>>> are also no beacons and mesh doesn't work, but there's no crash.
>>>>>
>>>>
>>>>
>>>> Hmm, try adding NL80211_IFTYPE_MESH_POINT here ->
>>>>
>>>> http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=blob;f=drivers/net/wireless/ath/ath5k/pcu.c;h=ec35503f6a40e6b6a1cc4323287b31e7cdd3a428;hb=HEAD#l733
>>>
>>> It's already there, in ath5k_hw_set_opmode. We'll need to trace
>>> what's going on and see why we don't get beacons. Last night I had an
>>> ath5k MP suddenly start beaconing but I haven't been able to reproduce
>>> that yet.
>>
>> 736 /* When in AP mode zero timer0 to start TSF */
>> 737 if (ah->ah_op_mode == NL80211_IFTYPE_AP)
>> 738 ath5k_hw_reg_write(ah, 0, AR5K_TIMER0);
>>
>> We need to do this for NL80211_IFTYPE_MESH_POINT or DBA won't fire up
>> and beacon queue wont start...
>
> Thanks Nik, that gets beaconing going but only after a issuing a scan
> (we have the same problem on rt2x00).
>
Cool, i'll send a patch for this asap ;-)
Thanks for testing !
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ath9k-devel] ath9k/ath5k + 80211s crash
@ 2009-06-03 0:55 austinxxh-ath9k
0 siblings, 0 replies; 12+ messages in thread
From: austinxxh-ath9k @ 2009-06-03 0:55 UTC (permalink / raw)
To: Andrey Yurovsky, Luis R. Rodriguez
Cc: devel@lists.open80211s.org, ath9k-devel@lists.ath9k.org,
linux-wireless@vger.kernel.org
Not good, I definitely like to use 80211s with ath9k, though I'm not familiar enough to fix anything related to them yet. Say, I don't know what's the relationship between 80211s and ath9k/ath5k at this point. Trying 0602 release now and see if it improves anything.
I was told b43 runs well with 80211s, hope ath5k/ath9k will do the same someday.
X Xiao
--- On Tue, 6/2/09, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
> From: Luis R. Rodriguez <lrodriguez@atheros.com>
> Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s crash
> To: "Andrey Yurovsky" <andrey@cozybit.com>
> Cc: "austinxxh-ath9k@yahoo.com" <austinxxh-ath9k@yahoo.com>, "devel@lists.open80211s.org" <devel@lists.open80211s.org>, "ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
> Date: Tuesday, June 2, 2009, 5:30 PM
> On Tue, Jun 02, 2009 at 09:58:59AM
> -0700, Andrey Yurovsky wrote:
> > With wireless-testing from a couple of days ago, an
> X86 system, and this patch:
> > http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
> > ath9k can bring up a mesh point interface and doesn't
> crash for me,
> > but there are no mesh beacons, so mesh isn't
> working. On ath5k, there
> > are also no beacons and mesh doesn't work, but there's
> no crash.
>
> If no one is really interested in fixing we should just
> disable mesh
> for both ath5k and ath9k.
>
> Luis
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ath9k-devel] ath9k/ath5k + 80211s crash
@ 2009-06-03 1:47 austinxxh-ath9k
0 siblings, 0 replies; 12+ messages in thread
From: austinxxh-ath9k @ 2009-06-03 1:47 UTC (permalink / raw)
To: devel, ath9k-devel, linux-wireless, 곽reom
Yes I just tried 0602 release of wireless and the reboot problem is gone. I'm fighting with other problems(ifconfig segfault) which are unrelated to ath9k/11s before I can fully test them.
Thanks!
Xxiao
--- On Tue, 6/2/09, 곽reom <acidreom@hotmail.com> wrote:
> From: 곽reom <acidreom@hotmail.com>
> Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s crash
> To: devel@lists.open80211s.org, ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
> Date: Tuesday, June 2, 2009, 8:26 PM
>
>
>
> #yiv1864732320 .hmmessage P
> {
> margin:0px;padding:0px;}
> #yiv1864732320 {
> font-size:9pt;font-family:굴림;}
>
>
>
> 802.11s works fine on my system with latest
> wireless-testing ath5k.
>
> There's only one problem.
>
> mesh0 doesn't send beacon automatically when i up mesh0
> first time.
>
> Only after doing down and up again mesh0, beacon was send
> and mesh works.
>
> I don't think crashing and rebooting with mesh setting
> is a related problem with ath5k or ath9k.
>
> > Date: Tue, 2 Jun 2009 17:55:20 -0700
> > From: austinxxh-ath9k@yahoo.com
> > To: andrey@cozybit.com; lrodriguez@atheros.com
> > CC: devel@lists.open80211s.org;
> ath9k-devel@lists.ath9k.org; linux-wireless@vger.kernel.org
> > Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s crash
> >
> >
> > Not good, I definitely like to use 80211s with ath9k,
> though I'm not familiar enough to fix anything related
> to them yet. Say, I don't know what's the
> relationship between 80211s and ath9k/ath5k at this point.
> Trying 0602 release now and see if it improves anything.
> >
> > I was told b43 runs well with 80211s, hope ath5k/ath9k
> will do the same someday.
> >
> > X Xiao
> >
> > --- On Tue, 6/2/09, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> >
> > > From: Luis R. Rodriguez
> <lrodriguez@atheros.com>
> > > Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s
> crash
> > > To: "Andrey Yurovsky"
> <andrey@cozybit.com>
> > > Cc: "austinxxh-ath9k@yahoo.com"
> <austinxxh-ath9k@yahoo.com>,
> "devel@lists.open80211s.org"
> <devel@lists.open80211s.org>,
> "ath9k-devel@lists.ath9k.org"
> <ath9k-devel@lists.ath9k.org>,
> "linux-wireless@vger.kernel.org"
> <linux-wireless@vger.kernel.org>
> > > Date: Tuesday, June 2, 2009, 5:30 PM
> > > On Tue, Jun 02, 2009 at 09:58:59AM
> > > -0700, Andrey Yurovsky wrote:
> > > > With wireless-testing from a couple of days
> ago, an
> > > X86 system, and this patch:
> > > >
> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
> > > > ath9k can bring up a mesh point interface
> and doesn't
> > > crash for me,
> > > > but there are no mesh beacons, so mesh
> isn't
> > > working. On ath5k, there
> > > > are also no beacons and mesh doesn't
> work, but there's
> > > no crash.
> > >
> > > If no one is really interested in fixing we
> should just
> > > disable mesh
> > > for both ath5k and ath9k.
> > >
> > > Luis
> > >
> > _______________________________________________
> > ath9k-devel mailing list
> > ath9k-devel@lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel@lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [ath9k-devel] ath9k/ath5k + 80211s crash
@ 2009-06-03 3:28 austinxxh-ath9k
0 siblings, 0 replies; 12+ messages in thread
From: austinxxh-ath9k @ 2009-06-03 3:28 UTC (permalink / raw)
To: devel, ath9k-devel, linux-wireless, 곽reom
the new wireless-testing(6/2/09) did not cause reset anymore. however "iw dev mesh station dump" showed nothing, even after I did "ifconfig mesh up" and "ifconfig mesh down" a few times. How did you know if it's sending beacons or not? are you using the monitor interface or something?
this is what i did:
-------------------
iw dev wlan0 interface add mesh type mp mesh_id mesh
ifconfig mesh up
ifconfig mesh 192.168.3.80
iw dev mesh station dump
--------------------
do the same on a second node, with a different mesh IP address.
nothing showed up, with olsr I can see two nodes are "merged"
wish i know more to debug this, learning...
xxiao
--- On Tue, 6/2/09, 곽reom <acidreom@hotmail.com> wrote:
> From: 곽reom <acidreom@hotmail.com>
> Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s crash
> To: devel@lists.open80211s.org, ath9k-devel@lists.ath9k.org, linux-wireless@vger.kernel.org
> Date: Tuesday, June 2, 2009, 8:26 PM
>
>
>
> #yiv1908813577 .hmmessage P
> {
> margin:0px;padding:0px;}
> #yiv1908813577 {
> font-size:9pt;font-family:굴림;}
>
>
>
> 802.11s works fine on my system with latest
> wireless-testing ath5k.
>
> There's only one problem.
>
> mesh0 doesn't send beacon automatically when i up mesh0
> first time.
>
> Only after doing down and up again mesh0, beacon was send
> and mesh works.
>
> I don't think crashing and rebooting with mesh setting
> is a related problem with ath5k or ath9k.
>
> > Date: Tue, 2 Jun 2009 17:55:20 -0700
> > From: austinxxh-ath9k@yahoo.com
> > To: andrey@cozybit.com; lrodriguez@atheros.com
> > CC: devel@lists.open80211s.org;
> ath9k-devel@lists.ath9k.org; linux-wireless@vger.kernel.org
> > Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s crash
> >
> >
> > Not good, I definitely like to use 80211s with ath9k,
> though I'm not familiar enough to fix anything related
> to them yet. Say, I don't know what's the
> relationship between 80211s and ath9k/ath5k at this point.
> Trying 0602 release now and see if it improves anything.
> >
> > I was told b43 runs well with 80211s, hope ath5k/ath9k
> will do the same someday.
> >
> > X Xiao
> >
> > --- On Tue, 6/2/09, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> >
> > > From: Luis R. Rodriguez
> <lrodriguez@atheros.com>
> > > Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s
> crash
> > > To: "Andrey Yurovsky"
> <andrey@cozybit.com>
> > > Cc: "austinxxh-ath9k@yahoo.com"
> <austinxxh-ath9k@yahoo.com>,
> "devel@lists.open80211s.org"
> <devel@lists.open80211s.org>,
> "ath9k-devel@lists.ath9k.org"
> <ath9k-devel@lists.ath9k.org>,
> "linux-wireless@vger.kernel.org"
> <linux-wireless@vger.kernel.org>
> > > Date: Tuesday, June 2, 2009, 5:30 PM
> > > On Tue, Jun 02, 2009 at 09:58:59AM
> > > -0700, Andrey Yurovsky wrote:
> > > > With wireless-testing from a couple of days
> ago, an
> > > X86 system, and this patch:
> > > >
> http://osdir.com/ml/linux-wireless/2009-05/msg01241.html
> > > > ath9k can bring up a mesh point interface
> and doesn't
> > > crash for me,
> > > > but there are no mesh beacons, so mesh
> isn't
> > > working. On ath5k, there
> > > > are also no beacons and mesh doesn't
> work, but there's
> > > no crash.
> > >
> > > If no one is really interested in fixing we
> should just
> > > disable mesh
> > > for both ath5k and ath9k.
> > >
> > > Luis
> > >
> > _______________________________________________
> > ath9k-devel mailing list
> > ath9k-devel@lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel@lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2009-06-05 3:39 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-02 3:52 ath9k/ath5k + 80211s crash austinxxh-ath9k
2009-06-02 3:58 ` Bob Copeland
2009-06-02 16:58 ` Andrey Yurovsky
2009-06-02 22:30 ` [ath9k-devel] " Luis R. Rodriguez
2009-06-03 18:21 ` Nick Kossifidis
2009-06-03 19:52 ` Andrey Yurovsky
2009-06-03 19:59 ` Nick Kossifidis
2009-06-04 17:42 ` Andrey Yurovsky
2009-06-05 3:39 ` Nick Kossifidis
-- strict thread matches above, loose matches on Subject: below --
2009-06-03 0:55 [ath9k-devel] " austinxxh-ath9k
2009-06-03 1:47 austinxxh-ath9k
2009-06-03 3:28 austinxxh-ath9k
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).