been running for 4 days, no hiccups at all
Okay, I'll give it a try.
been running for 4 days, no hiccups at all
just installed latest stable version 3.0.0.4.342
i did some cleaning after update and since then, there is no line in log...
wifi is ok, but i think, in v334 it was more stable (40/40 -> 50/15) on my phone...
You could use the restoration tool to flash again the newest firmware in the router's rescue mode.Installed .342 last night and today encountered the "kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=451!" again like in former firmware builds This causes a drop of connection to the internet. The lines with the dots were inserted while posting this because of the length of this reply. But overall it takes 1m2s before it seems to stop and the first log entry is when I add a manual assigned IP around the DHCP list at 23.48pm.
Feb 9 13:26:31 nmbd[2145]: Samba name server RT-N56U is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.1
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=451!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=452!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=453!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=454!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=455!
Feb 9 14:12:04 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=456!
.............
Feb 9 14:12:06 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=700!
Feb 9 14:12:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=701!
Feb 9 14:12:06 kernel: Qidx(0), not enough space in MgmtRing, MgmtRingFullCount=702!
Feb 9 14:12:53 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4095!
Feb 9 14:12:53 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4096!
.............
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4559!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4560!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4561!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCoFullCount=4570!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4571!
Feb 9 14:13:06 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4572!
.............
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4992!
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4993!
Feb 9 14:13:14 kernel: Qidx(1), not enough space in MgmtRing, MgmtRingFullCount=4994!
Feb 9 23:48:00 rc_service: httpd 2127:notify_rc restart_net_and_phy
you can always try:
http://192.168.1.1/Main_AdmStatus_Content.asp
type :
mtd-erase -d nvram
then
reboot
be aware, you settings will be lost
you can always try:
http://192.168.1.1/Main_AdmStatus_Content.asp
type :
mtd-erase -d nvram
then
reboot
be aware, you settings will be lost
Flashed from 206 to 342 yesterday and so far I had no problems (been 18 hours). No slow downs or no drops or no "Qidx(0), not enough space in MgmtRing, MgmtRingFullCount" messages in log.
I had all kinds of weird problems with previous stable releases, but this one seems fine. I'll report back if anything happens.
Interesting, this is the first release where I've seen the MgmtRing messages in the router log, haven't seen them in previous Asus releases. Also, the "System Log" tab doesn't work on Chrome with .342
System Log tab is working fine for me on .342 with Win XP, Win 7 and Win 8 (64bit) using chrome. (And I know because I am constantly checking for these MgmtRing issues when my network randomly stops working properly.
From a few of the comments above, I might try wiping and physically unplugging the router, before manually reconfiguring, to see if there's a buggy setting from one of the previous firmwares I have flashed. I don't have high hopes though. My MgmtRing count was up to 7000+ in under 12 hours yesterday.
I tried that, even flashed a couple of times, erased the nvram a couple of times, power-cycled it, tried the reset button, tried everything I could think of, recycled my browser after dumping the cache, rebooted my computer, and the "System Log" tab wouldn't work for me in Chrome. I did find it amazing, which is why I spent so much time trying to get it to work. And then I got the MgmtRing errors, and I decided that I'd spent enough time with that version of the firmware.
As a last resort, I just flashed .342 from "Recovery Mode", cleared the nvram, used the reset button, and power-cycled (belt and suspenders *smile*), and now the "System Log" tab is working with the Chrome browser. If I don't get the "MgmtRing" errors, then I'll be happy. IPv6 is also working fine.
Hi RogerSC !
Could you post here the telnet command line for clearing nvram ?
Thanks !
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!