Community discussions

MikroTik App
 
lllegal
just joined
Topic Author
Posts: 2
Joined: Sun Aug 20, 2006 11:11 pm

crashin rb532 and 2.9.29

Wed Aug 30, 2006 6:22 am

this is what's in log:
jan/01/2000 02:00:28 system,error,critical System rebooted because of kernel failure
jan/01/2000 02:00:28 system,error,critical router was rebooted without proper shutdown (cause 1)

and this is all I got on terminal buffer:

unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580
unaligned data access at 0x801b2570
unaligned data access at 0x801b2580

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash
eth3: Error, poll already scheduled

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

pan<4>unaligned data access at 0x80108a90
unaligned data access at 0x80108a90
unaligned data access at 0x80108a90
unaligned data access at 0x80108a90
unaligned data access at 0x80108a90
unaligned data access at 0x80108a90
unaligned data access at 0x80108a90
unaligned data access at 0x80108a90
unaligned data access at 0x80108a90

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash
unaligned data access at 0x8010c148

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping pani<7>
panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flash

panicSaver: dumping panic to flas<4>unaligned data access at 0x80120cc4

panicSaver: dumping panic to flash


RouterBOOT booter 1.13

RouterBoard 532

CPU frequency: 198 MHz
Memory size: 32 MB

Press any key within 1 seconds to enter setup.
writing settings to flash... OK
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Starting...
Starting services...
MikroTik 2.9.29



the problem arises when uploading from host wireless to ftp server (next hop). I also had crappy performance and 50% load at 100Kbit/s traffic only although the cpu is downclocked to even make 2 high power mPCI card work (at 100mW) + 1 cm9 on rb564 daughterboard (using 30W original poe in power jack)


unbelivable crap (I got myself into ;P this time)

can anyone assist ?


Also (second question) is there a way to make the board switch instead of bridging as I really need no bridges soon, but would like to use the existing ports on high tower, bonding+broadcast or is there another option besides bridge ?
 
karyal
Member Candidate
Member Candidate
Posts: 168
Joined: Sat Nov 12, 2005 12:09 pm

Re: crashin rb532 and 2.9.29

Sun Sep 03, 2006 12:07 pm

Don't know if can help, but when i had such problems (kernel failure with RB and more than a single or two radios) the problems seemed to be related to power.
I've found that the solution was to avoid using mure than two cards on a single routerboard when possible (it's ok with low usage, but as it increases you get cpu load problems), and in case of more radios use 48v power supplies instead of 12/18.
Bye,
Ricky

Who is online

Users browsing this forum: No registered users and 21 guests