Kernel Panic on 1840 AP

[milesgordon]

This morning one of our 1840 APs went down. Upon investigation the AP is in a kernel panic loop. We have factory reset the AP and then reconfigured it back to its proper settings pointing to the vwlan appliance. The firmware seems to get updated to latest version but then this happens.

Network Cfg -> pOops[#1]:

Cpu 0

$ 0   : 00000000 00000001 00000008 000c0000

$ 4   : 00000000 82711600 82d16620 00000000

$ 8   : 00000019 82dab050 82d16620 82dab05e

$12   : ffffffe0 00000005 00001000 30323a35

$16   : 82d28680 82dab056 82dab050 00000001

$20   : 82d16620 82d71100 825a6260 81248400

$24   : 00000000 c013f8cc

$28   : 83144000 83145c00 82d28680 c013fddc

Hi    : 01de5980

Lo    : 01a28e50

epc   : c013cbd4 vbr_setup_skb_nfmark+0xc/0x20 [vbrg]     Tainted: PF

ra    : c013fddc vbr_prtd_eth_port_recv_frame+0x510/0xf78 [vbrg]

Status: 1000d403    KERNEL EXL IE

Cause : 00800008

BadVA : 0000007c

PrId  : 00019374

Modules linked in: wlan_acl ath_pci ath_dev wlan_xauth wlan_ccmp wlan_tkip wlan_                                                                                                                               wep wlan_scan_ap ath_rate_atheros ath_dfs ath_hal wlan vbrg gc vnl ag7100_mod 18                                                                                                                               80_wdt

Process killall (pid: 1803, threadinfo=83144000, task=8288c0d8)

Stack : c00cbb6c 00030002 8372c260 83145cc0 826bc000 c00c9838 00000001 00000000

        83145ca8 00000007 00000080 832600a4 80068bbc 00000000 832600a0 8372c260

        82711600 00000080 82d16620 00000000 00000010 00000001 00000040 82d71100

        810ac028 81248400 82d28680 8037db38 00000000 00000001 81248400 82d71100

        810ac028 81248400 00000040 80223f84 0000007c 00000000 00000000 0000007c

        ...

Call Trace:

[<c00cbb6c>] ieee80211_free_node+0x0/0xec [wlan]

[<c00c9838>] ieee80211_input_all+0x10c/0x284 [wlan]

[<80068bbc>] do_gettimeofday+0x78/0x160

[<80223f84>] netif_receive_skb+0x1c0/0x3f4

[<c00b2e4c>] ag7100_poll+0x1fc/0x7d8 [ag7100_mod]

[<80224450>] net_rx_action+0xc0/0x1ec

[<8008b0e4>] __do_softirq+0x84/0x130

[<8008b1f8>] do_softirq+0x68/0x80

[<800648f4>] do_IRQ+0x24/0x34

[<800615e8>] ar7100_interrupt_receive+0xe8/0x100

[<800615e8>] ar7100_interrupt_receive+0xe8/0x100

[<800df274>] may_open+0x58/0x224

[<800cbc54>] nameidata_to_filp+0x30/0x64

[<800cb99c>] __dentry_open+0x14/0x29c

[<800df5b0>] open_namei+0x170/0x7a8

[<800cbcd8>] filp_open+0x50/0x68

[<800cbf6c>] get_unused_fd+0x118/0x1cc

[<800cc134>] do_sys_open+0x7c/0xec

[<800cc200>] filp_close+0x48/0xa8

[<8006c840>] stack_done+0x20/0x3c

[<80063e88>] handle_ri_int+0x20/0x38

Code: 8ca4009c  38e70001  24020008 <8c83007c> 0007100b  00431804  03e00008  acc3                                                                                                                               0074  27bdffc0

Kernel panic - not syncing: Aiee, killing interrupt handler!

+WDT last is SET

Thanks for any help

[Anonymous]

Hi Miles,

Since the firmware levels can be different depending on the controller, would you be so kind as to list the controller platform (BSC/vWLAN) and version as well as the AP firmware?

[Anonymous · Accepted solution]

This issue was resolved by upgrading the AP firmware to 6.6.0.30

[Anonymous]

I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post to unmark it and select another in its place with the applicable buttons.  If you have any additional information on this that others may benefit from, please come back to this post to provide an update.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.