Posted: Fri Nov 04, 2022 20:15 Post subject: Asus RT-AC5300 Instability/repeating error (?) in logs
Hello, I recently moved off of an old KONG build, and am currently on r50595. I wish I could remember the old KONG build version, but It was lost when the router started to act weird (one of the 5ghz networks disappeared from the settings page), so I figured I would update the firmware. This fixed my original issue, but now I have a problem that I can only describe as instability? Sometimes my internet drops on the 2.4 ghz band for a few seconds and reconnects, while other times it seems like the router reboots, but not fully reboots. What I mean by that is my wired connection is unaffected, the lights on the router seem normal, but the syslogs seem to start over (starting in December as a default date until it checks against the dns server). Its really weird. Ive been trying to keep an eye on it, and I noticed sometimes the router logs start to spiral (see below) with the same text over and over. Is this something that could cause the symptoms described? What other information would be helpful for me to provide? Or am I looking too closely into trying to figure out my issue and should just close syslogs...lol.
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.785566] ttraff: page allocation failure: order:6, mode:0x2084020
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.791956] CPU: 1 PID: 1196 Comm: ttraff Tainted: P 4.4.302-st25 #8022
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.799893] Hardware name: Northstar Prototype
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.804340] Backtrace:
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.806813] [<800117bc>] (dump_backtrace) from [<80011a40>] (show_stack+0x18/0x1c)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.814393] r7:00000000 r6:60000013 r5:00000000 r4:8055ca04
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.820103] [<80011a28>] (show_stack) from [<8001398c>] (dump_stack+0x94/0xa8)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.827351] [<800138f8>] (dump_stack) from [<800c5128>] (warn_alloc_failed+0xe4/0x114)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.835282] r7:00000000 r6:00000000 r5:00000006 r4:02084020
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.840989] [<800c5048>] (warn_alloc_failed) from [<800c6068>] (__alloc_pages_nodemask+0x1a4/0x8ac)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.850053] r3:00000000 r2:00000000
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.853648] r6:00000000 r5:8054d420 r4:02084020
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.858300] [<800c5ec4>] (__alloc_pages_nodemask) from [<800c691c>] (alloc_kmem_pages+0x20/0xac)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.867105] r10:00000000 r9:00020000 r8:00000001 r7:82a21f78 r6:02084020 r5:00000006
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.874991] r4:00020001
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.877537] [<800c68fc>] (alloc_kmem_pages) from [<800dbc04>] (kmalloc_order+0x1c/0x34)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.885557] r7:82a21f78 r6:02080020 r5:82a21f78 r4:00020001
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.891270] [<800dbbe8>] (kmalloc_order) from [<800f9b18>] (__kmalloc+0x194/0x1e4)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.898858] [<800f9984>] (__kmalloc) from [<8003ec10>] (MMALLOC+0x1c/0x30)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.905742] r9:00020000 r8:00000001 r7:82a21f78 r6:76d930f0 r5:82a21f78 r4:00020001
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.913543] [<8003ebf4>] (MMALLOC) from [<8003ec4c>] (dev_nvram_read+0x28/0x278)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.920947] r5:82a21f78 r4:00020000
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.924554] [<8003ec24>] (dev_nvram_read) from [<8010503c>] (__vfs_read+0x30/0xd4)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.932140] r9:00020000 r8:00000001 r7:82a21f78 r6:8003ec24 r5:82a21f78 r4:82958f00
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.939943] [<8010500c>] (__vfs_read) from [<80105778>] (vfs_read+0x90/0x160)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.947094] r7:82a21f78 r6:ffffe000 r5:76d930f0 r4:82958f00
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.952800] [<801056e8>] (vfs_read) from [<8010619c>] (SyS_read+0x58/0xcc)
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.959689] r9:00000000 r8:00000000 r7:76d930f0 r6:00020000 r5:82958f00 r4:82958f00
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.967492] [<80106144>] (SyS_read) from [<800095a0>] (ret_fast_syscall+0x0/0x40)Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.974991] r9:82a20000 r8:80009764 r7:00000003 r6:7e9b7adc r5:00000000 r4:00000000
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.982919] Mem-Info:
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.985289] active_anon:649 inactive_anon:0 isolated_anon:0
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.985289] active_file:564 inactive_file:998 isolated_file:0
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.985289] unevictable:13 dirty:0 writeback:0 unstable:0
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.985289] slab_reclaimable:246 slab_unreclaimable:1860
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.985289] mapped:1130 shmem:0 pagetables:69 bounce:0
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.985289] free:98107 free_pcp:366 free_cma:0
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.017504] Normal free:9468kB min:1384kB low:1728kB high:2076kB active_anon:192kB inactive_anon:0kB active_file:164kB inactive_file:56kB unevictable:52kB isolated(anon):0kB isolated(file):0kB present:131072kB managed:120500k
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.060787] lowmem_reserve[]: 0 3072 3072
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.064854] HighMem free:382904kB min:384kB low:1516kB high:2648kB active_anon:2404kB inactive_anon:0kB active_file:2092kB inactive_file:3936kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:393216kB managed:39
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.108138] lowmem_reserve[]: 0 0 0
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.111671] Normal: 181*4kB (UE) 143*8kB (U) 70*16kB (UM) 96*32kB (UME) 45*64kB (UME) 4*128kB (UE) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 9452kB
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.125348] HighMem: 146*4kB (M) 40*8kB (UM) 15*16kB (UM) 30*32kB (UM) 48*64kB (M) 19*128kB (UM) 4*256kB (M) 3*512kB (UM) 2*1024kB (UM) 3*2048kB (UM) 89*4096kB (M) = 382904kB
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.141150] 1575 total pagecache pages
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.144905] 0 pages in swap cache
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.148234] Swap cache stats: add 0, delete 0, find 0/0
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.153467] Free swap = 0kB
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.156357] Total swap = 0kB
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.159237] 131072 pages RAM
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.162117] 98304 pages HighMem/MovableOnly
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43889.166314] 2643 pages reserved
As I grabbed that text from the logs I experienced a full reboot unexpectedly. I don't know if the error ran its course and it was inevitably going to reboot or if me reading the log was the straw that broke the camel's back....but it seemed like good context to include.
One possibility is that going from an old build to new, that a total wipe of all settings and manual restore (re-entry via GUI) might be necessary.
Another, is a possible memory leak. Would probably need to capture process statistics every minute until failure to get an idea of which process(es) are not freeing RAM. But, try the first suggestion, before starting traces and captures.
Is there any special reason why you're using ttraff? I would disable it, hard reset, and re-configure from scratch.
Craymond wrote:
Code:
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.785566] ttraff: page allocation failure: order:6, mode:0x2084020
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.791956] CPU: 1 PID: 1196 Comm: ttraff Tainted: P 4.4.302-st25 #8022
_________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
One possibility is that going from an old build to new, that a total wipe of all settings and manual restore (re-entry via GUI) might be necessary.
Another, is a possible memory leak. Would probably need to capture process statistics every minute until failure to get an idea of which process(es) are not freeing RAM. But, try the first suggestion, before starting traces and captures.
I can confirm that was my process when making the update, and that it was not fun to go through all the settings again
Is there any special reason why you're using ttraff? I would disable it, hard reset, and re-configure from scratch.
Craymond wrote:
Code:
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.785566] ttraff: page allocation failure: order:6, mode:0x2084020
Nov 4 16:12:49 Asus RT-AC5300 kern.warn kernel: [43888.791956] CPU: 1 PID: 1196 Comm: ttraff Tainted: P 4.4.302-st25 #8022
Thanks for the tip! I am probably missing it, but could let me know how to change this setting? I have paged through all the settings a few times, however I am not seeing it. It might not be showing as an option due to my particular router though?
**EDIT** Nevermind, I found it! Will monitor, thank you!
One possibility is that going from an old build to new, that a total wipe of all settings and manual restore (re-entry via GUI) might be necessary.
Another, is a possible memory leak. Would probably need to capture process statistics every minute until failure to get an idea of which process(es) are not freeing RAM. But, try the first suggestion, before starting traces and captures.
I can confirm that was my process when making the update, and that it was not fun to go through all the settings again
There are a few different ways to reset system settings. I’m not totally convinced they all perform the same level of preening. The command-line “nvram erase && reboot,” does not faithfully seem to restore to an OOB experience. The GUI checkbox to restore to defaults seems more reliable.
Better yet, is the holding of the WPS or reset button on boot. This seems the most effective, but sometimes takes two or three passes before it’s completely back to defaults.
And, as a precaution, keep your configuration below 64KiB to ensure you don’t hit the NVRAM boot bug that seems to affect these units. Exceeding 64KiB seemingly causes the configuration to be truncated when read into memory for the purpose of booting, with unpredictable outcome.
One possibility is that going from an old build to new, that a total wipe of all settings and manual restore (re-entry via GUI) might be necessary.
Another, is a possible memory leak. Would probably need to capture process statistics every minute until failure to get an idea of which process(es) are not freeing RAM. But, try the first suggestion, before starting traces and captures.
I can confirm that was my process when making the update, and that it was not fun to go through all the settings again
There are a few different ways to reset system settings. I’m not totally convinced they all perform the same level of preening. The command-line “nvram erase && reboot,” does not faithfully seem to restore to an OOB experience. The GUI checkbox to restore to defaults seems more reliable.
Better yet, is the holding of the WPS or reset button on boot. This seems the most effective, but sometimes takes two or three passes before it’s completely back to defaults.
And, as a precaution, keep your configuration below 64KiB to ensure you don’t hit the NVRAM boot bug that seems to affect these units. Exceeding 64KiB seemingly causes the configuration to be truncated when read into memory for the purpose of booting, with unpredictable outcome.
YMMV
I took your advice and began again. I looked into this particular router and found that resetting to factory in the firmware is the way to go, as a 30/30/30 throws this model into recovery mode.
Im still monitoring, but so far it seems that while my stability is slightly better, my 2.4ghz network is very slow. I have used WiFi Analyzer to go pick channel 6, but what was 60mbps down/20mbps up, is only 15/20.
Im actually trying to find the old KONG build I had, I have no idea if its still on the website, but it "just worked" for years and im kicking myself for not writing the build number down.
Something else I am noticing is that my Apple watch cannot get an internet connection on the 2.4ghz network, but my phone can. Just incase that is helpful for diagnosis. Super weird.
I took your advice and began again. I looked into this particular router and found that resetting to factory in the firmware is the way to go, as a 30/30/30 throws this model into recovery mode.
Im still monitoring, but so far it seems that while my stability is slightly better, my 2.4ghz network is very slow. I have used WiFi Analyzer to go pick channel 6, but what was 60mbps down/20mbps up, is only 15/20.
Im actually trying to find the old KONG build I had, I have no idea if its still on the website, but it "just worked" for years and im kicking myself for not writing the build number down.
There is no 30/30/30 on this unit. The reset procedure is to hold the WPS button while booting. Holding the reset button on this unit, during boot, will put it into recovery. Each unit is a little different, but the above works for the AC5300.
Craymond wrote:
Something else I am noticing is that my Apple watch cannot get an internet connection on the 2.4ghz network, but my phone can. Just incase that is helpful for diagnosis. Super weird.
Your 2.4GHz issues sound like your radio setup has some incompatible settings enabled. Can you tell us the settings for that radio, which are enabled and which are disabled?
I solved the Apple watch issues, it was my error not the router. Not sure how this is going to format, but I have attached a screen shot of my 2.4ghz settings.
I’d put the network mode back to default from “N-only,” and set the channel width back to 20MHz unless you have devices that support 40MHz and zero interference around you. Apple devices disable support for 40MHz on 2.4GHz, anyway.
You can enable implicit beam forming since it’s passive on 2.4GHz. Disable explicit beam forming, as almost no 2.4 clients can support MIMO and the ability to beam form. Implicit beam forming will give you a boost as the AP does its own signal processing for different clients, which doesn’t need active support on the client.
If you’ve altered settings in the advanced tab, set them back to defaults with the exception of the beacon interval. Set that at 75 or 100 for noisy networks. You can also enable short preamble, which adds a little bit, but disables support for 802.11b devices, which most people no-longer possess.
Try those settings and see if it improves stability.
I’d put the network mode back to default from “N-only,” and set the channel width back to 20MHz unless you have devices that support 40MHz and zero interference around you. Apple devices disable support for 40MHz on 2.4GHz, anyway.
You can enable implicit beam forming since it’s passive on 2.4GHz. Disable explicit beam forming, as almost no 2.4 clients can support MIMO and the ability to beam form. Implicit beam forming will give you a boost as the AP does its own signal processing for different clients, which doesn’t need active support on the client.
If you’ve altered settings in the advanced tab, set them back to defaults with the exception of the beacon interval. Set that at 75 or 100 for noisy networks. You can also enable short preamble, which adds a little bit, but disables support for 802.11b devices, which most people no-longer possess.
Try those settings and see if it improves stability.
I appreciate your help, I have made these changes, and also think I found a chunk of my issue. When I setup the new build, I looked up the recommended setting for the bluetooth coexistence mode on the advanced menu in the advance wifi settings wiki. It suggests using "Preemption" and I figured that makes sense, I have a Bluetooth keyboard and mouse. I disabled it and i'm back to 70+mbps downspeed on the 2.4 band.
Will continue to monitor stability. Something I am seeing in the logs is an error that reads over and over:
I appreciate your help, I have made these changes, and also think I found a chunk of my issue. When I setup the new build, I looked up the recommended setting for the bluetooth coexistence mode on the advanced menu in the advance wifi settings wiki. It suggests using "Preemption" and I figured that makes sense, I have a Bluetooth keyboard and mouse. I disabled it and i'm back to 70+mbps downspeed on the 2.4 band.
Will continue to monitor stability. Something I am seeing in the logs is an error that reads over and over:
Not sure if I should care about it though, or its normal.
Do you have 802.1X / RADIUS authentication enabled? Either on the “Administration” page (towards the bottom), or in the wireless security page? If not, it sounds like you may yet still have some garbage left in NVRAM from the reset.
Yes, co-existence mode will slow things down, as it cuts the transmit rate in half to every other frame so that Bluetooth devices can occupy the other frames. It’s generally not necessary anymore as Bluetooth has used its own mitigation since BT4.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Fri Nov 11, 2022 15:20 Post subject:
Bluetooth coexistence is needed only when the the WiFi channel frequency is crossing even then only if things are so close that interference is noticed.
Code:
Bluetooth Frequency Allocations/Frequency Bands
US, Europe,
etc 2.4 to 2.4835 GHz f = 2.402 + n, MHz (n = 0 to 78)
Japan 2.471 to 2.497 GHz f = 2.473 + n, MHz (n = 0 to 22)
Spain 2.445 to 2.475 GHz f = 2.449 + n, MHz (n = 0 to 22)
France 2.4465 to 2.4835 GHz f = 2.454 + n, MHz (n = 0 to 22)
