Hi all,

As a further debugging step I exchanged the Wistron CM9 with a Wistron DNMA-82 and the adhoc mode
with the latest Openwrt on my RS pro runs just fine.
When I use an Alix board with the same Openwrt + CM9 + ath5k + adhoc mode all runs fine.

It looks like for me that there is a kind of an ENDIAN bug in the adhoc code of the CM9 card.
Because the RS pro is BIG ENDIAN and the Alix board is little ENDIAN.

Maybe that could be helpful in terms of nailing down the part of code causing the problem.


Bye Bluse



h2o-post
7. Juni 2011 02:20

Hi all,

I tested the lastest Openwrt backfire commit
b5a33bb5d58805d5b1d84a4cf47feeca52984705

RS-pro + CM9 + sta/ap = working
RS-pro + CM9 + adhoc = kernel oops
PCI error 1 at PCI addr 0x10008020
Data bus error, epc == 870c6b24, ra == 870c6b20
Oops[#1]:

and I tested OpenWrt from 19.April commit f3a65e72dbe5884ceb0f421429ce0d1f29fcb8fa
same result.

further troubleshooting attempts without success:

1.) - vanilla OpenWrt madwifi works fine in adhoc mode

2.) - change DMASIZE via this patch:

Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath5k/dma.c
===================================================================
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath5k/dma.c
2011-06-06 17:37:37.000000000 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath5k/dma.c
2011-06-07 00:09:23.000000000 +0200
@@ -789,13 +789,13 @@
if (ah->ah_version != AR5K_AR5210) {
#ifndef CONFIG_ATHEROS_AR71XX
AR5K_REG_WRITE_BITS(ah, AR5K_TXCFG,
- AR5K_TXCFG_SDMAMR, AR5K_DMASIZE_128B);
+ AR5K_TXCFG_SDMAMR, AR5K_DMASIZE_4B);
AR5K_REG_WRITE_BITS(ah, AR5K_RXCFG,
- AR5K_RXCFG_SDMAMW, AR5K_DMASIZE_128B);
+ AR5K_RXCFG_SDMAMW, AR5K_DMASIZE_4B);
#else
/* WAR for AR71xx PCI bug */
AR5K_REG_WRITE_BITS(ah, AR5K_TXCFG,

Index: compat-wireless-2011-05-27/drivers/net/wireless/ath/ath5k/initvals.c
===================================================================
--- compat-wireless-2011-05-27.orig/drivers/net/wireless/ath/ath5k/initvals.c
2011-06-06 17:37:37.000000000 +0200
+++ compat-wireless-2011-05-27/drivers/net/wireless/ath/ath5k/initvals.c
2011-06-07 00:09:54.000000000 +0200
@@ -59,11 +59,11 @@
{ AR5K_IER, AR5K_IER_DISABLE },
{ AR5K_BSR, 0, AR5K_INI_READ },
#ifndef CONFIG_ATHEROS_AR71XX
- { AR5K_TXCFG, AR5K_DMASIZE_128B },
- { AR5K_RXCFG, AR5K_DMASIZE_128B },
+ { AR5K_TXCFG, AR5K_DMASIZE_4B },
+ { AR5K_RXCFG, AR5K_DMASIZE_4B },
#else
/* WAR for AR71xx PCI bug */

Bye Bluse


> --------------------------------------------------------------------------------
>
> Sedat Dilek <mailto:[email protected]>
> 31. Mai 2011 20:16
>
>
> On Tue, May 31, 2011 at 7:30 PM, Russell Senior
>
> Just FYI:
> Nick sent the patch from [1] to linux-wireless ML a few weeks ago.
>
> - Sedat -
>
> [1]
> http://www.kernel.org/pub/linux/kernel/people/mickflemm/01-fast-chan-switch-modparm
> _______________________________________________
> ath5k-devel mailing list
> [email protected]
> https://lists.ath5k.org/mailman/listinfo/ath5k-devel
> --------------------------------------------------------------------------------
>
> Russell Senior <mailto:[email protected]>
> 31. Mai 2011 19:30
>
>
>
> Russell> I just confirmed Peizhao Hu's observation. The CM9's with
> Russell> chips marked AR5213A-001 panic on MIPS. CM9's with chips
> Russell> marked AR5213A-00 do not. It looks like (from my small
> Russell> sample immediately at hand) the stock radios on Netgear
> Russell> WGT634U also are marked AR5213A-00, and don't seem to panic.
>
> Seems to be fixed in OpenWrt r27024. Thanks Felix!
>
> https://dev.openwrt.org/changeset/27024/
>
>
> --------------------------------------------------------------------------------
>
> Russell Senior <mailto:[email protected]>
> 7. Mai 2011 03:30
>
>
>>>>>> "Felix" == Felix Fietkau<[email protected]> writes:
>
> Felix> On 2011-05-04 4:39 PM, Russell Senior wrote:
>>>>>>>> "Russell" == Russell Senior<[email protected]> writes:
> Russell> Recently trying to abandon madwifi for good on some embedded
> Russell> devices with OpenWrt, encountered kernel panics. Same radio
> Russell> on an x86 platform (Soekris net4826), no kernel panic.
> Russell> Different atheros radio, no kernel panic. Tried two
> Russell> different MIPS boards (Netgear WGT634U and Ubiquiti
> Russell> RouterStation), both panic'd.
> Russell> Netgear WGT634U:http://pastebin.ca/2051127 Ubiquiti
> Russell> RouterStation:http://pastebin.ca/2052610
>>> Here is another panic, this time not resulting from hostapd, but
>>> from an adhoc vif:
>>>
>>> http://pastebin.ca/2053827
>>>
>>> The initial panic appears to occur in a different function from the
>>> hostapd initiated panics:
> Felix> Again a beacon related register, this time AR5K_BEACON
>
> I just confirmed Peizhao Hu's observation. The CM9's with chips
> marked AR5213A-001 panic on MIPS. CM9's with chips marked AR5213A-00
> do not. It looks like (from my small sample immediately at hand) the
> stock radios on Netgear WGT634U also are marked AR5213A-00, and don't
> seem to panic.
>
> Maybe our Atheros friends can tell us what the differences between
> these two chips are?
>
>
> --------------------------------------------------------------------------------
>
> Felix Fietkau <mailto:[email protected]>
> 4. Mai 2011 16:47
>
>
> Again a beacon related register, this time AR5K_BEACON
>
> - Felix
> _______________________________________________
> ath5k-devel mailing list
> [email protected]
> https://lists.ath5k.org/mailman/listinfo/ath5k-devel
> --------------------------------------------------------------------------------
>
> Russell Senior <mailto:[email protected]>
> 4. Mai 2011 16:39
>
>
>
> Russell> Recently trying to abandon madwifi for good on some embedded
> Russell> devices with OpenWrt, encountered kernel panics. Same radio
> Russell> on an x86 platform (Soekris net4826), no kernel panic.
> Russell> Different atheros radio, no kernel panic. Tried two
> Russell> different MIPS boards (Netgear WGT634U and Ubiquiti
> Russell> RouterStation), both panic'd.
>
> Russell> Netgear WGT634U: http://pastebin.ca/2051127 Ubiquiti
> Russell> RouterStation: http://pastebin.ca/2052610
>
> Here is another panic, this time not resulting from hostapd, but from
> an adhoc vif:
>
> http://pastebin.ca/2053827
>
> The initial panic appears to occur in a different function from the
> hostapd initiated panics:
>
> PCI error 1 at PCI addr 0x10008020
> Data bus error, epc == 83006b24, ra == 83006b20
> Oops[#1]:
> Cpu 0
> $ 0 : 00000000 802f0000 deadc0de 00000002
> $ 4 : b0008020 00000002 018003e8 00000000
> $ 8 : 830a8228 00000015 83ad8df0 0000006c
> $12 : 00000001 0000000c 00000005 00000008
> $16 : 8387a000 01000000 00008020 00008024
> $20 : 0000802c 00008030 018003e8 000003e9
> $24 : 00000008 0000021c
> $28 : 83832000 83833b70 0000003b 83006b20
> Hi : 00000000
> Lo : 00000020
> epc : 83006b24 ath5k_hw_reset_tsf+0x48/0x98 [ath5k]
> Not tainted
> ra : 83006b20 ath5k_hw_reset_tsf+0x44/0x98 [ath5k]
> Status: 1000f403 KERNEL EXL IE
> Cause : 1080001c
> PrId : 00019374 (MIPS 24Kc)
> Modules linked in: batman_adv ath5k ath mac80211 cfg80211 compat arc4
> aes_generic crypto_algapi ipv6 leds_gpio gpio_keys_polled input_polldev input_core
> Process kworker/u:0 (pid: 5, threadinfo=83832000, task=83819100, tls=00000000)
> Stack : 00000000 00000001 00000000 00000000 000000d0 8387a000 00008034 00001f30
> 00001ef0 83006d28 00000008 000200d0 0000ed54 800ade3c 83ad8da0 83ad8da0
> 018003e8 00000000 00000000 000003e8 00000000 0000ed54 00000000 830113cc
> 00000002 802c74fc 00000000 80099364 00000000 00000000 00000000 000252d0
> 000000d0 00000001 802c74f8 003fffff 8387a000 00000000 0000021c 83845300
> ...
> Call Trace:
> [<83006b24>] ath5k_hw_reset_tsf+0x48/0x98 [ath5k]
> [<83006d28>] ath5k_hw_init_beacon+0x1b4/0x250 [ath5k]
> [<830113cc>] ath5k_beacon_update_timers+0x248/0xc8c [ath5k]
> [<83bc81f8>] ieee80211_process_addba_request+0x520/0xa44 [mac80211]
>
>
> Code: 0c058bb8 00442021 8e0500e4 <00518825> 02601021 0245100b 00402821
> 8e0200d4 02202021
> [...]
>
>
_______________________________________________
ath5k-devel mailing list
[email protected]
https://lists.ath5k.org/mailman/listinfo/ath5k-devel


Sedat Dilek
31. Mai 2011 20:16

On Tue, May 31, 2011 at 7:30 PM, Russell Senior

Just FYI:
Nick sent the patch from [1] to linux-wireless ML a few weeks ago.

- Sedat -

[1] http://www.kernel.org/pub/linux/kernel/people/mickflemm/01-fast-chan-switch-modparm
_______________________________________________
ath5k-devel mailing list
[email protected]
https://lists.ath5k.org/mailman/listinfo/ath5k-devel


Russell Senior
31. Mai 2011 19:30


Russell> I just confirmed Peizhao Hu's observation. The CM9's with
Russell> chips marked AR5213A-001 panic on MIPS. CM9's with chips
Russell> marked AR5213A-00 do not. It looks like (from my small
Russell> sample immediately at hand) the stock radios on Netgear
Russell> WGT634U also are marked AR5213A-00, and don't seem to panic.

Seems to be fixed in OpenWrt r27024. Thanks Felix!

https://dev.openwrt.org/changeset/27024/




Russell Senior
7. Mai 2011 03:30

"Felix" == Felix Fietkau <[email protected]> writes:
Felix> On 2011-05-04 4:39 PM, Russell Senior wrote:
"Russell" == Russell Senior<[email protected]> writes:
Russell> Recently trying to abandon madwifi for good on some embedded
Russell> devices with OpenWrt, encountered kernel panics.  Same radio
Russell> on an x86 platform (Soekris net4826), no kernel panic.
Russell> Different atheros radio, no kernel panic.  Tried two
Russell> different MIPS boards (Netgear WGT634U and Ubiquiti
Russell> RouterStation), both panic'd.
Russell> Netgear WGT634U: http://pastebin.ca/2051127 Ubiquiti
Russell> RouterStation: http://pastebin.ca/2052610
 Here is another panic, this time not resulting from hostapd, but
from an adhoc vif:

http://pastebin.ca/2053827

The initial panic appears to occur in a different function from the
hostapd initiated panics:
Felix> Again a beacon related register, this time AR5K_BEACON

I just confirmed Peizhao Hu's observation.  The CM9's with chips
marked AR5213A-001 panic on MIPS.  CM9's with chips marked AR5213A-00
do not.  It looks like (from my small sample immediately at hand) the
stock radios on Netgear WGT634U also are marked AR5213A-00, and don't
seem to panic.

Maybe our Atheros friends can tell us what the differences between
these two chips are?




Felix Fietkau
4. Mai 2011 16:47

Again a beacon related register, this time AR5K_BEACON

- Felix
_______________________________________________
ath5k-devel mailing list
[email protected]
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
_______________________________________________
ath5k-devel mailing list
[email protected]
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

Reply via email to