I am running ROS v3.28 with the wireless test package on a 500 MHz AMD Geode LX CPU
http://www.pcengines.ch/alix3d2.htm
The clock runs ten times too fast and CPU utilization jumps to 60% (was 20% before).
This also screws up the interface statistics, etc…
All is normal as soon as wireless test package is disabled.
supout.rif has been sent to MikroTik
Got a response from Mikrotik support. The answer is that everything is fine with their software and it must be a hardware problem. Of course!
Anyone else experiencing this same issue?
A few versions ago there was a bug with dual core processors that caused the clock to run much faster and the box would eventually crash. I think it was 2-3 times the speed though. That problem was corrected with the next release. I’ve always found occasional issues/incompatibilities with various mb’s/cpu’s on any linux type OS.
Can you downgrade versions? Not sure when last wireless-test change was made.
Now I’m curious - what was added feature for running wireless-test package?
Yes, there are still clock issues with some PC’s.
My Core2Duo machine is running fine with 3.30 wireless-test and 4.2 wireless, but some older Compaq PIII 730MHz has 10 times faster clock (counts 10 seconds instead of one). I contacted support again.
this issue can usually be fixed by a BIOS upgrade. if that doesn’t help, I recommend you to find another PC because clock issues will affect most other features too
Hi Normis,
I’ve made a test lab and the bug appears also with 3.30-wireless-test package. I’m affraid to find the problem again with ver 5.
Clock is ticking normally until I activate nstreme on a wlan interface. When the wlan is in nstreme mode, time is ticking 4 to 10 times faster.
Do you think we can have a ver 4x running correctly, I’m actually blocked with 3.30…
Best regards,
Julien Hoppe
Maybe 4.13 is the solution, we should try it with wileless-nv2 package and turn of nstreme wherever possible. I also have up to 10 x86 machines stuck with 3.30.
Yes 
clock is working fine with 4.13 wireless-nv2 on x86 and nstreme turned on.
Usually on 3.xx with wireless test and 4.xx setting multi-cpu to yes resolve problem with nstreme and clock on single core x86.
On 5.0rc this problem is resolved you can set multi-cpu to no or yes not problem, some old 5.0beta version have been some problem with nstreme and multicpu options.
Where were you before? You told us this now when the clock is working fine with 4.13 
I don’t discover this.
I read this on forum long time ago and use on my x86 routers form first couple 4.xx version. Now in 5.0rc no more problem with clock .
Enlighten me please…!
Where the hell is this “4.13-wireless-nv2” package…?
I downloaded the whole 4.13 torrent… and I see only regular wireless packages…! 
Regards.
