cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
arobi
New Contributor

BSAP 2030 Kernel Panic

I have a brand new BSAP 2030 that is not running stable, it drops connections and randomly reboots. I connected a console cable and see that I'm dealing with a kernel panic. Is there any tips for how to move forward? Can I try to update the firmware again or use a different boot partition?

 

Boot Bank: B Count: 1
A: 3.2.1-653348 B: 3.5.0-662378

 

AP login: Oops: Kernel access of bad area, sig: 11 [#1]
P1010 RDB
last sysfs file:
Modules linked in: iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables ip_gre nf_conntrack_tftp nf_conntrack dynRF(P) ath_pktlog(P) umac ath_dfs(P) ath_dev(P) ath_rate_atheros(P) ath_hal(P) asf(P) adf(P) etherip vbrg(P) vnl(P) gc(P) shimlayer
**bleep**: c0093c88 LR: c00273ec CTR: c00970ec
REGS: cd9dbdd0 TRAP: 0300 Tainted: P (2.6.35)
MSR: 02021000 <VEC,ME,CE> CR: 24004a88 XER: 20000000
DEAR: ffffffff, ESR: 00000000
TASK = cd9eaa30[1489] 'ledD' THREAD: cd9da000
GPR00: 00000000 cd9dbe80 cd9eaa30 cf801480 000000d0 cd9c1600 00000000 cf800160
GPR08: 00000000 c0500000 00000001 cf414628 24004a72 1002720c 00000000 00000000
GPR16: 00000000 000000e5 00000030 00000004 00000024 0ffb46d4 0ffe654a ffffffff
GPR24: 00000001 00000000 cd9c1600 cd9d8000 ffffffff 000000d0 02029000 cf801480
**bleep** [c0093c88] kmem_cache_alloc+0x3c/0x9c
LR [c00273ec] mm_alloc+0x20/0x60
Call Trace:
[cd9dbe80] [20000000] 0x20000000 (unreliable)
[cd9dbea0] [c00273ec] mm_alloc+0x20/0x60
[cd9dbeb0] [c009e850] bprm_mm_init+0x1c/0x158
[cd9dbee0] [c009ec7c] do_execve+0x108/0x270
[cd9dbf20] [c0007b80] sys_execve+0x54/0x88
[cd9dbf40] [c000fc34] ret_from_syscall+0x0/0x3c
--- Exception: c01 at 0xff274c8
LR = 0xfeb8fec
Instruction dump:
bf810010 7c7f1b78 90010024 83a93ff0 7c9de838 7fc000a6 7c000146 80e30000
83870000 2f9c0000 419e0034 80030010 <7c1c002e> 90070000 7fc00106 73a08000
Kernel panic - not syncing: Fatal exception
Call Trace:
[cd9dbd10] [c0007cb0] show_stack+0x44/0x154 (unreliable)
[cd9dbd50] [c0380184] panic+0xa8/0x118
[cd9dbd90] [c000d004] die+0xec/0x19c
[cd9dbdb0] [c0014ae4] bad_page_fault+0x90/0xc8
[cd9dbdc0] [c00100e4] handle_page_fault+0x7c/0x80
--- Exception: 300 at kmem_cache_alloc+0x3c/0x9c
LR = mm_alloc+0x20/0x60
[cd9dbe80] [20000000] 0x20000000 (unreliable)
[cd9dbea0] [c00273ec] mm_alloc+0x20/0x60
[cd9dbeb0] [c009e850] bprm_mm_init+0x1c/0x158
[cd9dbee0] [c009ec7c] do_execve+0x108/0x270
[cd9dbf20] [c0007b80] sys_execve+0x54/0x88
[cd9dbf40] [c000fc34] ret_from_syscall+0x0/0x3c
--- Exception: c01 at 0xff274c8
LR = 0xfeb8fec
mtdoops: ready 1, 2 (no erase)
Rebooting in 5 seconds..

0 Kudos
1 Reply

Re: BSAP 2030 Kernel Panic

usually if left alone for a while it will flip its boot partition to the other, you attempt a factory reset to defaults as well