[ath9k-devel] ath9k/ath5k + 80211s crash

[ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k at yahoo.com]

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 at OpenWrt:/# iw dev wlan0 interface add mesh type mp mesh_id mesh
root at OpenWrt:/# ifconfig -a | grep mesh
mesh      Link encap:Ethernet  HWaddr 00:0B:6B:57:09:37  
root at 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

[ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k at yahoo.com]

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 at yahoo.com <austinxxh-ath9k@yahoo.com> wrote:

> From: austinxxh-ath9k at yahoo.com <austinxxh-ath9k@yahoo.com>
> Subject: ath9k/ath5k + 80211s crash
> To: linux-wireless at vger.kernel.org, ath9k-devel at lists.ath9k.org, devel at 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 at OpenWrt:/# iw dev wlan0 interface add mesh type mp
> mesh_id mesh
> root at OpenWrt:/# ifconfig -a | grep mesh
> mesh? ? ? Link encap:Ethernet? HWaddr
> 00:0B:6B:57:09:37? 
> root at 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 at lists.open80211s.org
> http://open80211s.com/mailman/listinfo/devel
> 

Re: ath9k/ath5k + 80211s crash

[austinxxh-ath9k]

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
> 

[ath9k-devel] ath9k/ath5k + 80211s crash

[Bob Copeland]

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

Re: ath9k/ath5k + 80211s crash

[Bob Copeland]

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

[ath9k-devel] ath9k/ath5k + 80211s crash

[Andrey Yurovsky]

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 at yahoo.com <austinxxh-ath9k@yahoo.com> wrote:
>
>> From: austinxxh-ath9k at yahoo.com <austinxxh-ath9k@yahoo.com>
>> Subject: ath9k/ath5k + 80211s crash
>> To: linux-wireless at vger.kernel.org, ath9k-devel at lists.ath9k.org, devel at 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 at OpenWrt:/# iw dev wlan0 interface add mesh type mp
>> mesh_id mesh
>> root at OpenWrt:/# ifconfig -a | grep mesh
>> mesh? ? ? Link encap:Ethernet? HWaddr
>> 00:0B:6B:57:09:37
>> root at 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 at lists.open80211s.org
>> http://open80211s.com/mailman/listinfo/devel
>>
> _______________________________________________
> Devel mailing list
> Devel at lists.open80211s.org
> http://open80211s.com/mailman/listinfo/devel
>

Re: ath9k/ath5k + 80211s crash

[Andrey Yurovsky]

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
>

[ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k at yahoo.com]

I was using compat-wireless-0521. the reboot of ath9k/80211s could be a soft-watchdog reset caused by the lockup you mentioned. thanks. going to try a new wireless release.

ath5k does not look good to me, going back to madwifi for a typical b/g AP setting instead.

80211s looks neat to me, though it's still not well tested in the field. tried olsrd with ath9k it seems working fine.

xxiao

--- On Tue, 6/2/09, Andrey Yurovsky <andrey@cozybit.com> wrote:

> From: Andrey Yurovsky <andrey@cozybit.com>
> Subject: Re: ath9k/ath5k + 80211s crash
> To: austinxxh-ath9k at yahoo.com, devel at lists.open80211s.org
> Cc: linux-wireless at vger.kernel.org, ath9k-devel at lists.ath9k.org
> Date: Tuesday, June 2, 2009, 11:58 AM
> 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 at yahoo.com
> <austinxxh-ath9k@yahoo.com>
> wrote:
> >
> >> From: austinxxh-ath9k at yahoo.com
> <austinxxh-ath9k@yahoo.com>
> >> Subject: ath9k/ath5k + 80211s crash
> >> To: linux-wireless at vger.kernel.org,
> ath9k-devel at lists.ath9k.org,
> devel at 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 at OpenWrt:/# iw dev wlan0 interface add mesh
> type mp
> >> mesh_id mesh
> >> root at OpenWrt:/# ifconfig -a | grep mesh
> >> mesh? ? ? Link encap:Ethernet? HWaddr
> >> 00:0B:6B:57:09:37
> >> root at 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 at lists.open80211s.org
> >> http://open80211s.com/mailman/listinfo/devel
> >>
> > _______________________________________________
> > Devel mailing list
> > Devel at lists.open80211s.org
> > http://open80211s.com/mailman/listinfo/devel
> >
> 

[ath9k-devel] ath9k/ath5k + 80211s crash

[Luis R. Rodriguez]

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

Re: [ath9k-devel] ath9k/ath5k + 80211s crash

[Luis R. Rodriguez]

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] ath9k/ath5k + 80211s crash

[austinxxh-ath9k at yahoo.com]

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 at yahoo.com" <austinxxh-ath9k@yahoo.com>, "devel at lists.open80211s.org" <devel@lists.open80211s.org>, "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>, "linux-wireless at 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
> 

Re: [ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k]

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] ath9k/ath5k + 80211s crash

[곽reom]

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 at yahoo.com
> To: andrey at cozybit.com; lrodriguez at atheros.com
> CC: devel at lists.open80211s.org; ath9k-devel at lists.ath9k.org; linux-wireless at 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 at yahoo.com" <austinxxh-ath9k@yahoo.com>, "devel at lists.open80211s.org" <devel@lists.open80211s.org>, "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>, "linux-wireless at 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 at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090603/5066fb16/attachment.htm 

[ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k at yahoo.com]

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 at lists.open80211s.org, ath9k-devel at lists.ath9k.org, linux-wireless at 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 at yahoo.com
> > To: andrey at cozybit.com; lrodriguez at atheros.com
> > CC: devel at lists.open80211s.org;
> ath9k-devel at lists.ath9k.org; linux-wireless at 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 at yahoo.com"
> <austinxxh-ath9k@yahoo.com>,
> "devel at lists.open80211s.org"
> <devel@lists.open80211s.org>,
> "ath9k-devel at lists.ath9k.org"
> <ath9k-devel@lists.ath9k.org>,
> "linux-wireless at 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 at lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>  
> 
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> 

Re: [ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k]

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
> 

[ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k at yahoo.com]

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 at lists.open80211s.org, ath9k-devel at lists.ath9k.org, linux-wireless at 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 at yahoo.com
> > To: andrey at cozybit.com; lrodriguez at atheros.com
> > CC: devel at lists.open80211s.org;
> ath9k-devel at lists.ath9k.org; linux-wireless at 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 at yahoo.com"
> <austinxxh-ath9k@yahoo.com>,
> "devel at lists.open80211s.org"
> <devel@lists.open80211s.org>,
> "ath9k-devel at lists.ath9k.org"
> <ath9k-devel@lists.ath9k.org>,
> "linux-wireless at 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 at lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>  
> 
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> 

Re: [ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k]

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
> 

[ath9k-devel] ath9k/ath5k + 80211s crash

[곽reom]

I have wireless monitoring device and checked beacons with it.

in other way, you can check beacons by adding debugging message at ath5k_beacon_send function.

ath5k_beacon_send function has to be called.


i used next command for mesh configuration.

----------

iw phy phy0 interface add mesh0 type mesh mesh_id test

iwconfig mesh0 channel 157

ifconfig mesh0 192.168.0.1 up

 

if mesh0 sends beacons, other device(192.168.0.2 in my case) shows mesh0(192.168.0.1) with command "iw dev mesh0 station dump"

 

 

> Date: Tue, 2 Jun 2009 20:28:18 -0700
> From: austinxxh-ath9k at yahoo.com
> Subject: Re: [ath9k-devel] ath9k/ath5k + 80211s crash
> To: devel at lists.open80211s.org; ath9k-devel at lists.ath9k.org; linux-wireless at vger.kernel.org; acidreom at hotmail.com
> 
> 
> 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 at lists.open80211s.org, ath9k-devel at lists.ath9k.org, linux-wireless at 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 at yahoo.com
> > > To: andrey at cozybit.com; lrodriguez at atheros.com
> > > CC: devel at lists.open80211s.org;
> > ath9k-devel at lists.ath9k.org; linux-wireless at 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 at yahoo.com"
> > <austinxxh-ath9k@yahoo.com>,
> > "devel at lists.open80211s.org"
> > <devel@lists.open80211s.org>,
> > "ath9k-devel at lists.ath9k.org"
> > <ath9k-devel@lists.ath9k.org>,
> > "linux-wireless at 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 at lists.ath9k.org
> > > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> > 
> > 
> > -----Inline Attachment Follows-----
> > 
> > _______________________________________________
> > ath9k-devel mailing list
> > ath9k-devel at lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
> > 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090603/35ca06a9/attachment-0001.htm 

[ath9k-devel] ath9k/ath5k + 80211s crash

[Nick Kossifidis]

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

Re: ath9k/ath5k + 80211s crash

[Nick Kossifidis]

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

[ath9k-devel] ath9k/ath5k + 80211s crash

[Andrey Yurovsky]

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.

Re: ath9k/ath5k + 80211s crash

[Andrey Yurovsky]

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.

[ath9k-devel] ath9k/ath5k + 80211s crash

[Nick Kossifidis]

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

Re: ath9k/ath5k + 80211s crash

[Nick Kossifidis]

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

[ath9k-devel] ath9k/ath5k + 80211s crash

[sjreom]

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


In my case, that is not a solution.

The problem is ath5k_hw_set_opmode() is called before mesh configuration.

Operation mode was set in a function ath5k_add_interface(),

but ath5k_hw_set_opmode() called before it.

So there's no chance to configure h/w in mesh mode.

 

If I add ath5k_reset() command at the end of ath5k_add_interface(), then beacon starts instantly.

 

I found what problem is, but I don't know what is neat solution.

So I hope someone who knows well about the atheros driver make a patch.

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090604/26750970/attachment.htm 

[ath9k-devel] ath9k/ath5k + 80211s crash

[Andrey Yurovsky]

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
>

Re: ath9k/ath5k + 80211s crash

[Andrey Yurovsky]

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
>

[ath9k-devel] ath9k/ath5k + 80211s crash

[Nick Kossifidis]

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

Re: ath9k/ath5k + 80211s crash

[Nick Kossifidis]

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

[ath9k-devel] ath9k/ath5k + 80211s crash

[austinxxh-ath9k at yahoo.com]

ath9k + 80211s has no crash anymore. however after assigned IP to the mesh node, I could not ping at all, it's not working.

ath5k crashes on ar71xx boards, just learned it might have something to do with silicon bug from atheros instead of ath5k driver bug.

xxiao

--- On Thu, 6/4/09, Nick Kossifidis <mickflemm@gmail.com> wrote:

> From: Nick Kossifidis <mickflemm@gmail.com>
> Subject: Re: ath9k/ath5k + 80211s crash
> To: "Andrey Yurovsky" <andrey@cozybit.com>
> Cc: austinxxh-ath9k at yahoo.com, devel at lists.open80211s.org, linux-wireless at vger.kernel.org, ath9k-devel at lists.ath9k.org
> Date: Thursday, June 4, 2009, 10:39 PM
> 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
>