reboot bug on beta7

when I do a soft reboot on beta7 the board lookup and dosen’s bootup again. I have to power cycle it. it is an old 511 board.

Regards
Ros

you have tried only this one or some other board also?

only this one at the moment. The firmware has been upgraded to 2.8.

on 133c works ok.

Everyhting i do seems to push it to 100% cpu utilizzation but it seems to work fine.
Each character i type on new trerminal box push the cpu to 100%, but then come back to zero…

Hope it is going to be workable on the field.

Ros

this is due to color console :unamused: it takes some resources, but only when you are logged in, and it is more easier to work in console if these color markings are used (at least for me), so i think, that it is ok

hope you will be able to fix the reboot issue on the old 511 because i have a bunch of them.

Reagrds
Ros

Restarting system.


RouterBOOT booter 2.8

RouterBoard 512

CPU frequency: 330 MHz
  Memory size:  32 MB

Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Starting...
insmod: cannot insert `/lib/modules/2.6.20/misc/fancon.ko': Success (1): Success
modprobe: failed to load module fancon
Starting services...

MikroTik 3.0beta7
MikroTik Login:

Not sure what fancon module is but the rb boots OK otherwise.

RouterBoard 112

Press any key within 2 seconds to enter setup..
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Starting...
insmod: cannot insert `/lib/modules/2.6.20/misc/fancon.ko': Success (1): Success
modprobe: failed to load module fancon
Starting services...

MikroTik 3.0beta7
MikroTik Login:

Firmware 2.7

Have same issue here on my test board but unlike yours, this one does not run correctly, extremely difficult to get logged into Winbox or via serial.

If I downgrade the issue clears up.

2Mikrotik guys

If you are using 2.6.20 kernel, and sch_htb or mirred(iproute2 action) - check please netdev maillist, i report few critical bugs in them and they are fixed in git tree. They can cause kernel panic.