6.10 supout.rif and kernal panics

Dear Mikrotik Gurus;
I learned about the supout.rif viewer so I uploaded a file to look at the logs.
One of my devices had a kernel panic and of the 4 - 6 devices I have updated to 6.10, 80 - 90% of them are having random reboots at least 1 - 2 times a week. One place it reboots every 2 - 3 days 3 - 5 times in one day???

When they were on 6.9 and lower they did not reboot or have kernel panics that I know of.

Is 6.11 coming out? Are there know issues with kernel panics or reboots with 6.10?

I am using RB750G and RB450G routers.

Travis

I get the same thing problem on RB750, RB450, RB1100.
It also happens if the state of a ppp interface changes, 95% of the time it reboot and hangs on, you have to remove the power to get it working again

It is good to know I am not alone

Normis or anyone at Mikrotik

Is this a known issue? Is a fix coming soon??

Anyone?

http://forum.mikrotik.com/t/v6-10-released/74262/214

Kernal failure on my RB951-2n days before with 6.10.

Where is 6.11?? to download?

contact support@mikrotik.com for test release of v6.11

I hear it may be out in a few days? anyways?

We too are seeing this : Just rolled out 250 3G units for coaches, and have the system hang randomly when the PPP interface is reset. Crashes the console too when you type /int ppp-client print

Tickets and Support files, along with full export and all scripts sent to Mikrotik. Upgrading to 6.11 Did not fix for us, in fact, issue is worse as the usb interfaces now randomly disapear and strange ppp-client entries appearing.

Hello,
I have two CCR v6.11 who are doing self-reboots in random time without set watchdog.
Sometimes are hang/freeze and I must pay for DataCenter service to restart power on CCR.
This behaviour I was on 6.4, Support MT give me advice to upgrade, after upgrade reboots are exist after 70h!.
When CCR is hung/freeze then access to all ethernet ports are forbidden/deny and only power reboot are good.

I have 6xCCR:
2x v6.11 with often reboots/hangs
1x v6.4 with hang about 1/mt
3x waiting to be production when this problem will be resolved.

Those problems are reported to Mikrotik Support of course.