I was hoping that the CPU issue would be solved in Beta 8… still is a big problem. Did a netinstall as well and same results. Disabled unused packages as well. Half the speed of 2.9.43.
Any idea what may be chewing up the CPU cycles?? Is anyone else experiancing the same?
I found it very urresponsive on 133c for the first wo minutes, then it goes to normal behavior.
It seems that the boot phase is very very slow, in fact in neighborviewer i get 0.0.0.0 on ip address and only after a while i get the ip that it is assigned to a bridge interface.
what packages are enabled on your router?
please use winbox to connect to routerboards with probably low memory.
RB133 should not have any issues.
These are the enabled packages:
Advanced tools
ntp
ppp
routerboard
security
system
wireless
I can now boot into but if I bring up a terminal and try running a command, each command spikes the CPU to 100% and takes quite some time to execute.
Something is not right.
I had the problem on a 112 and downgraded back to 2.9.42.
I reset-configuration then tryed upgrading to 3.0 beta 8 and now everythings is working great.
Do be careful not to load any modules you will not be using.
this is normal behavior as console marks each command with color and parses it while you are typing, so you can see, that you do not have to enter /interface wireless print, but /in wi pr is sufficient
I will try again, using net install with only the packages I need and see if this makes the system stable.
Scratch that… going to Beta 9!
confirmed.
brand new 133c’s upgraded from .34 to beta 9 - 100% CPU load, bad response, but can still get in it. Downgraded immediately to .43
Thought one reason for a terminal session was to reduce load. 
I’m experiencing the same problem with RB112s on 2.9.38 and 2.9.43. While connected via winbox and telnet, I can see the load increase from 2-3 to 100 when I run “/sys reso print” via the telnet session.
At one site, I have three RB112s with single SR2 radios in each. Two of the three RB112s are displaying the same behavior. The installed packages include advanced-tools, ntp, routerboard, security, system, and wireless. All three RB112s have been installed for 2-3 months, and have only recently started doing this.
It’s worth noting that we also recently setup our NMS to polll the RB112s an run this script via telnet…
:local rtid [ /in wi reg find mac-address=xxxxxxxxxxxx ] ; :if ($rtid != "") do={ :local snr [ /in wi reg get $rtid signal-to-noise ] ; :local rawss [ /in wi reg get $rtid signal-strength ] ; :local signal [ :pick $rawss $rtid [:find $rawss dBm ] ] ; :local silence ( $signal - $snr ) ; :local bytes [ /in wi reg get $rtid bytes ] ; :put ( $signal . "," . $silence . "," . $bytes ) }
I’ve stopped the NMS from polling and reset the RB112s, and the behavior stays the same.
I have supout.rif files from both misbehaving RB112s including a before/after reboot set. Mikrotik, let me know if you’re interested in getting a copy of these.