Page 1 of 1

RB/800 - System rebooted because of kernel failure

Posted: Tue Nov 29, 2011 6:55 pm
by wildbill442
I'm having problems with a RB800 rebooted every ~24hrs.

The RB800 is running RouterOS v5.7, and has 4 x R52Hn-m cards.

The error message is written in the log file after reboot. Contents of the autosupout.rif file include the following:
routerboard: yes
model: 800
serial-number: 24D301AFE4E1
current-firmware:
upgrade-firmware: 2.30


BIOS
bad command name bios (line 3 column 18)


SETTINGS
baud-rate: 115200
boot-delay: 5s
enter-setup-on: any-key
boot-device: nand-if-fail-then-ethernet
cpu-frequency: 800MHz
memory-data-rate: 400DDR
boot-protocol: bootp
enable-jumper-reset: yes
silent-boot: no

In bold are the items I've found to be odd....

I'm going to upgrade to 5.9 and upgrade the routerboard's firmware as well.. Hopefully this will resolve the problem. Just wanted to check to see if any others were experiencing similar issues and found a resolution.

I'll be opening a support ticket with Mikrotik shortly.

The board is fairly new and has been in service for about 3 months. I can't tell when the problem first happened as the routerboard reboots before the monitoring software can poll the device and detect a problem.

Re: RB/800 - System rebooted because of kernel failure

Posted: Tue Nov 29, 2011 7:11 pm
by honzam
I have the same problem with 5.7 and no current BIOS. Try upgrade and mainly bios
/ system routerboard upgrade

Re: RB/800 - System rebooted because of kernel failure

Posted: Wed Nov 30, 2011 6:56 pm
by wildbill442
I upgraded to 5.9 and upgraded the firmware about 20hrs ago.. Only time will tell if it holds..

Re: RB/800 - System rebooted because of kernel failure

Posted: Thu Dec 01, 2011 7:09 pm
by wildbill442
I upgraded to 5.9 and upgraded the firmware about 20hrs ago.. Only time will tell if it holds..
Well that didn't resolve it. Same problem, "kernel failure" error in the logs a "/system routerboard pr" shows a null field under current-firmware.

I have an open ticket with mikrotik support hopefully a fix will come soon.

Re: RB/800 - System rebooted because of kernel failure

Posted: Fri Dec 02, 2011 6:42 pm
by uldis
what power supply you are using and how many Amps/Volts does it provide and are you using POE? if yes, how long is the cable?

Re: RB/800 - System rebooted because of kernel failure

Posted: Wed Dec 07, 2011 1:01 am
by wildbill442
Uldis - I'm using a Passive POE with a solar setup.

48VDC system

8 x 6VDC AGM 150Ahr Batteries
8 x 175Watt 12 VDC Panels (2 x 48VDC arrays in parallel)
Charge controller

Not sure on amperage, its just drawing whatever is needed. There's more than enough power at this site its completely overkill as it was designed for a much larger scale setup. The ethernet run is about 50-60' total.

I have two other RB800 boards, three total, at this site and this one with the R52Hn cards is the only one exhibiting the symptoms.

As you suggested I'll be replacing the R52Hn cards with another brand, either the F52N-Pro's from UBII or SR71-15 from Ubiquiti. I have my technicians scheduled to do the swap this Friday.

Re: RB/800 - System rebooted because of kernel failure

Posted: Tue Jan 03, 2012 1:50 pm
by i-netp
Hello,

was this problem solved? I'm asking because i have the same. The current-firmware-version (bios) won't be displayed and the router reboots many times with exactly the same message "kernel failure". I have currently version 5.5 running on the board. The board is connected to 24POW. Do i need to install a 48V power-supply? Is this recommended?

Regards

Hans-Peter Straub

Re: RB/800 - System rebooted because of kernel failure

Posted: Tue Jan 03, 2012 3:38 pm
by honzam
upgrade bios to 2.30 http://routerboard.com/fwf/91/mpc8544-2.30.fwf
then in new terminal
/system routerboard upgrade
and then upgrade ROS to version 5.11
http://download2.mikrotik.com/routeros-powerpc-5.11.npk

Re: RB/800 - System rebooted because of kernel failure

Posted: Thu Jan 05, 2012 12:20 pm
by i-netp
I've updated the bios to 2.30 and the RouterOS to 5.11. The Board now runs a works a little longer, but do also a "System reboot because of kernel failure".

And in the Routerboard there is again no current-firmware visible.

------------
[admin@AP] > system routerboard print
routerboard: yes
model: 800
serial-number: 24D301AE1B31
current-firmware:
upgrade-firmware: 2.30
------------

Does someone have any idea?

--
Hans-Peter Straub

Re: RB/800 - System rebooted because of kernel failure

Posted: Thu Jan 05, 2012 2:31 pm
by honzam

Re: RB/800 - System rebooted because of kernel failure

Posted: Sat Jan 07, 2012 6:16 am
by deadyou12
Hello, i need help. i have RB1100AH x2, and i use for router bgp and qos. on first day, the router working good, and uptime 28 hours. suddenly, my router reboot and the logging show : system rebooted because of kernel failure. i bought a new for the router. this is my router health and my routerboard status :

[ade@aline] > system routerboard print
routerboard: yes
model: 1100AHx2
serial-number: 319E02529E5F
current-firmware:
upgrade-firmware: 2.38
[ade@aline] > system health print
fan-mode: manual
use-fan: auxiliary
active-fan: auxiliary
voltage: 12V
current: 945mA
temperature: 36C
cpu-temperature: 41C
power-consumption: 11.3W

What i should have to do for the problem. Thx.

Re: RB/800 - System rebooted because of kernel failure

Posted: Sat Jan 07, 2012 11:11 am
by honzam
There is NO current-firmware. Contact support. I have the same problem with rb711G-5HnD

Re: RB/800 - System rebooted because of kernel failure

Posted: Tue Jul 17, 2012 1:30 pm
by tarekomari
There is NO current-firmware. Contact support. I have the same problem with rb711G-5HnD
I have the same problem, but the router reset it self each 1 min.
not solved yet???????????

Re: RB/800 - System rebooted because of kernel failure

Posted: Sun Aug 11, 2013 3:26 pm
by batot
I was RB435G AP/bridge1/TX=10dBm <------> station bridge 1 RB433
AP/bridge2/TX=10dBm <------> station bridge 2 RB433
All wersion Router OS 5.20 and 6 time per hour disconnect.
Was change all to 5.25 and no dissconect. Uptime 2days ;)
Version Router OS 5.20 was BAD.
Good luck.