Wireless Access

Hi,

One of our AP is rebooting again and again. In the logs I get following error:

Reboot Reason: Reboot caused by kernel page fault at virtual address 00000010, epc == 00000010, ra == c06b32a4

Our controller is 3400 and running OS 6.1.3.12. AP is 105.

What is causing it?

Regards,

Farzan

You need to open a case with TAC.  Only they can understand that error message and fix it.

On the boot try doing

clear os

purgeenv

saveenv

reset

And reconfigure the ap again.   And see if that happens

The tac will ask you to do that... So if it doesnt work  you can tell them i already did clear os and purgeenv.

If it keep telling you the same error they will likely change the AP if its faulty.

Cheers

Carlos

Yes it is happening still after performing the steps you have mentioned. I am opening a case with TAC.

Thanks

I had the same problema with IAP-103 using the virtual controller:

Reboot Time and Cause: Reboot caused by kernel page fault at virtual address 003a0000, epc == c0354158, ra == c0354160

I opened any tickets support on Aruba but at the moment no solution about this.

Aruba's engeniers change my hardoware but the problem wasn't resolved.

Hi All, 

It's likely similar with my case.  I have1 IAP 215 (Master) and 8 103 IAP Instant. Firmware version - Version 6.5.4.3

Reboot Time and Cause: Reboot caused by kernel page fault at vi

virtual address 27bd00a4, epc == 801c5ca0, ra == c03a5c44

It's rebooting every 6 hours sometimes 1 hour. 

Was this resolved? 

Same here.

Have several 115s which are constantly rebooting with random intervals - from 6 hours at night up to every 15 minutes

Reboot Time and Cause: Reboot caused by kernel page fault at virtual address 45f4c1ba, epc == 801c5ca0, ra == c040ec44
Reboot Time and Cause: Reboot caused by kernel page fault at virtual address 00f40005, epc == 801c5ca0, ra == c040ec44

Reboot Time and Cause: Reboot caused by kernel page fault at virtual address eaf6ead4, epc == 801c5ca0, ra == c040ec44

Reboot alerts:

you are both very likely hitting a s/w bug, raise a tac case, resist the urge (requests) to replace hardware for no justified reason. Same thing for purging the ap, that is not a solution for a s/w issue.