Asus RT-AC5300 Instability/repeating error (?) in logs

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
Craymond
DD-WRT Novice


Joined: 15 Oct 2018
Posts: 22

PostPosted: Fri Nov 11, 2022 15:41    Post subject: Reply with quote
Thank you both! I will keep the Bluetooth coexistence mode off. As far as radius, I did check and the only mention I can see of radius is it's own tab under the wireless settings, can confirm it is disabled. I am wondering if the error is worth going through a full reset again? I might try and see if I can go back to Asus factory firmware and then reflash back to ddwrt this weekend to try to get a "clean install".
Sponsor
Hapi12021
DD-WRT User


Joined: 22 Jul 2021
Posts: 84

PostPosted: Fri Nov 11, 2022 16:07    Post subject: Reply with quote
While it’s possible to switch back and forth from AsusWRT / Merlin and DD-WRT, I wouldn’t recommend doing it frequently or for just a settings refresh. Each time you go back and forth, you risk bricking the device as it reformats the flash and needs to be done in recovery mode. Not worth it in my opinion.

An “nvram erase && reboot,” followed up by either a “reset to defaults” in the GUI or WPS button reset will clear everything out. As I said upthread, it sometimes takes two or three passes to get everything back to defaults. At least that has been my experience.

Also, I’ll point out again to keep an eye on your configuration storage and to not exceed 64KiB.
Craymond
DD-WRT Novice


Joined: 15 Oct 2018
Posts: 22

PostPosted: Fri Nov 11, 2022 16:41    Post subject: Reply with quote
Good to know! That command "nvram erase && reboot,” do I just paste that in the Administration > Commands box, then follow it up with full reset? I figure I've already come this far I might as well try this a few times then manually reconfig again
Hapi12021
DD-WRT User


Joined: 22 Jul 2021
Posts: 84

PostPosted: Fri Nov 11, 2022 18:47    Post subject: Reply with quote
To be safe, issue the “nvram erase && reboot” from the command line inside a telnet or ssh session. Doing it from inside the GUI makes the web server (httpd) process the parent, and bad things can happen during a destructive operation when the parent process exits uncleanly, as in a situation where you run a command and immediately reboot.

The double ampersand “&&” is a shell logical operation that says: only do “Y” if “X” completed with exit status 0 (successfully). There are circumstances, however, especially when dealing with low-level hardware operations, where the system doesn’t perform the operation atomically. It would actually be better to add a slight delay to let the system flush any pending calls and hardware perform any I/O resets before you reboot: “nvram erase && sleep 10 && reboot”

Most of the time it will work without any concerns from the GUI, but the nature of asynchronous processing means that maybe the kernel kills httpd, for reboot, before the operation finishes, and Unix, in general, will terminate the running process if STDIN closes during execution, with certain exceptions.

Terminals are some of the lowest-level processes that run, and there are some exceptions in the code to prevent shutting down if child processes are still running, so safer to do it there.


Last edited by Hapi12021 on Fri Nov 11, 2022 18:57; edited 1 time in total
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Fri Nov 11, 2022 18:53    Post subject: Reply with quote
I'm assuming you run these commands in Administration tab Commands tab (which is wrong). The Web interface has such mechanisms in place already, in administration > Firmware > After flashing when you are upgrading and Administration > Factory defaults.
_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)
Craymond
DD-WRT Novice


Joined: 15 Oct 2018
Posts: 22

PostPosted: Mon Nov 14, 2022 17:34    Post subject: Reply with quote
Thank you both for the explanations, as well as reccommendations on next steps. This weekend I did multiple resets, maybe 5? I did a mixture of hard resetting nvram with wps button, as well as reflashing to latest version of ddwrt r50841, and eventually reconfigured from scratch. My nvram usage did go down at the end of the process, from 53kb to 50, however I still get random restarts. I am wondering if this is just end of life for the router. I am now thinking I need to look for a new router...I work from home and cannot have internet cut out randomly. Anyone have any suggestions? Preferably triband?
Hapi12021
DD-WRT User


Joined: 22 Jul 2021
Posts: 84

PostPosted: Mon Nov 14, 2022 18:35    Post subject: Reply with quote
Craymond wrote:
Thank you both for the explanations, as well as reccommendations on next steps. This weekend I did multiple resets, maybe 5? I did a mixture of hard resetting nvram with wps button, as well as reflashing to latest version of ddwrt r50841, and eventually reconfigured from scratch. My nvram usage did go down at the end of the process, from 53kb to 50, however I still get random restarts. I am wondering if this is just end of life for the router. I am now thinking I need to look for a new router...I work from home and cannot have internet cut out randomly. Anyone have any suggestions? Preferably triband?


Try flashing a slightly older build, like from June ‘22 and see if problems persist. I personally think instability on this device has gone up since then, but at least you would have one more data point if it’s the hardware or not.
Craymond
DD-WRT Novice


Joined: 15 Oct 2018
Posts: 22

PostPosted: Mon Nov 14, 2022 20:57    Post subject: Reply with quote
Hapi12021 wrote:
Craymond wrote:
Thank you both for the explanations, as well as reccommendations on next steps. This weekend I did multiple resets, maybe 5? I did a mixture of hard resetting nvram with wps button, as well as reflashing to latest version of ddwrt r50841, and eventually reconfigured from scratch. My nvram usage did go down at the end of the process, from 53kb to 50, however I still get random restarts. I am wondering if this is just end of life for the router. I am now thinking I need to look for a new router...I work from home and cannot have internet cut out randomly. Anyone have any suggestions? Preferably triband?


Try flashing a slightly older build, like from June ‘22 and see if problems persist. I personally think instability on this device has gone up since then, but at least you would have one more data point if it’s the hardware or not.


I think my next steps are going to be to try your suggestion of older build. Failing that, I'll try to revert back to stock firmware. If it still doesn't work I'll have my answer.
Hapi12021
DD-WRT User


Joined: 22 Jul 2021
Posts: 84

PostPosted: Tue Nov 15, 2022 0:14    Post subject: Reply with quote
Please try, and also post whatever error messages persist in the system log.

Make sure you are also using the non-experimental firmware, as the experimental does not seem at all stable.

You can also try to reset to defaults and use the barest minimum config, of just SSID and WPA2 changes to see if parts of your config are triggering the errors / restarts. Also, in terms of restarts is the whole router rebooting, or just watchdog restarting the Wi-Fi and nas services?

There’s still some level of detail missing from the description of the problem.
Craymond
DD-WRT Novice


Joined: 15 Oct 2018
Posts: 22

PostPosted: Tue Nov 15, 2022 2:43    Post subject: Reply with quote
When I went into syslog just now the logs only existed from the moment I logged into ddwrt and I had a wall of yellow, see below. Mostly though either the wifi seems to soft reboot, or the whole router reboots. Its difficult to figure out whats happening. I don't think I have any watchdogs running, except to reboot every 24 hours. The logs below are not what I normally find, usually its just 1 or 2 timeout errors, repeating over and over.

Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.693660] httpd: page allocation failure: order:6, mode:0x2084020
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.700096] CPU: 0 PID: 7830 Comm: httpd Tainted: P 4.4.302-st25 #8210
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.707962] Hardware name: Northstar Prototype
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.712415] Backtrace:
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.714889] [<800117bc>] (dump_backtrace) from [<80011a40>] (show_stack+0x18/0x1c)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.722468] r7:00000000 r6:60000013 r5:00000000 r4:8055ca04
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.728177] [<80011a28>] (show_stack) from [<8001398c>] (dump_stack+0x94/0xa8)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.735427] [<800138f8>] (dump_stack) from [<800c5128>] (warn_alloc_failed+0xe4/0x114)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.743358] r7:00000000 r6:00000000 r5:00000006 r4:02084020
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.749064] [<800c5048>] (warn_alloc_failed) from [<800c6068>] (__alloc_pages_nodemask+0x1a4/0x8ac)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.758129] r3:00000000 r2:00000000
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.761723] r6:00000000 r5:8054d420 r4:02084020
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.766375] [<800c5ec4>] (__alloc_pages_nodemask) from [<800c691c>] (alloc_kmem_pages+0x20/0xac)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.775170] r10:00000000 r9:00020000 r8:00000001 r7:874e3f78 r6:02084020 r5:00000006
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.783057] r4:00020001
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.785603] [<800c68fc>] (alloc_kmem_pages) from [<800dbc04>] (kmalloc_order+0x1c/0x34)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.793623] r7:874e3f78 r6:02080020 r5:874e3f78 r4:00020001
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.799337] [<800dbbe8>] (kmalloc_order) from [<800f9b18>] (__kmalloc+0x194/0x1e4)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.806933] [<800f9984>] (__kmalloc) from [<8003ec10>] (MMALLOC+0x1c/0x30)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.813817] r9:00020000 r8:00000001 r7:874e3f78 r6:76b85cc0 r5:874e3f78 r4:00020001
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.821619] [<8003ebf4>] (MMALLOC) from [<8003ec4c>] (dev_nvram_read+0x28/0x278)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.829031] r5:874e3f78 r4:00020000
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.832638] [<8003ec24>] (dev_nvram_read) from [<8010503c>] (__vfs_read+0x30/0xd4)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.840216] r9:00020000 r8:00000001 r7:874e3f78 r6:8003ec24 r5:874e3f78 r4:87983300
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.848019] [<8010500c>] (__vfs_read) from [<80105778>] (vfs_read+0x90/0x160)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.855170] r7:874e3f78 r6:ffffe000 r5:76b85cc0 r4:87983300
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.860875] [<801056e8>] (vfs_read) from [<8010619c>] (SyS_read+0x58/0xcc)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.867763] r9:00000000 r8:00000000 r7:76b85cc0 r6:00020000 r5:87983300 r4:87983301
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.875567] [<80106144>] (SyS_read) from [<800095a0>] (ret_fast_syscall+0x0/0x40)
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.883057] r9:874e2000 r8:80009764 r7:00000003 r6:76b459fc r5:00000000 r4:00000000
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.891305] Mem-Info:
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.893608] active_anon:658 inactive_anon:0 isolated_anon:0
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.893608] active_file:1520 inactive_file:2334 isolated_file:0
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.893608] unevictable:19 dirty:0 writeback:0 unstable:0
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.893608] slab_reclaimable:454 slab_unreclaimable:1836
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.893608] mapped:1069 shmem:0 pagetables:64 bounce:0
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.893608] free:94802 free_pcp:315 free_cma:0
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.926450] Normal free:4532kB min:1384kB low:1728kB high:2076kB active_anon:296kB inactive_anon:0kB active_file:504kB inactive_file:404kB unevictable:76kB isolated(anon):0kB isolated(file):0kB present:131072kB managed:120500
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.970468] lowmem_reserve[]: 0 3072 3072
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33513.975467] HighMem free:374740kB min:384kB low:1516kB high:2648kB active_anon:2336kB inactive_anon:0kB active_file:5576kB inactive_file:8932kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:393216kB managed:39
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.019058] lowmem_reserve[]: 0 0 0Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.022943] Normal: 95*4kB (UME) 98*8kB (UME) 66*16kB (UME) 51*32kB (UME) 11*64kB (UM) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 4556kB
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.036885] HighMem: 27*4kB (UM) 11*8kB (UM) 5*16kB (UM) 2*32kB (U) 0*64kB 1*128kB (U) 2*256kB (UM) 2*512kB (U) 2*1024kB (UM) 3*2048kB (UM) 89*4096kB (M) = 374740kB
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.053265] 3879 total pagecache pages
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.057069] 0 pages in swap cache
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.060505] Swap cache stats: add 0, delete 0, find 0/0
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.065855] Free swap = 0kB
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.068879] Total swap = 0kB
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.071918] 131072 pages RAM
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.074878] 98304 pages HighMem/MovableOnly
Nov 14 21:35:07 Asus RT-AC5300 kern.warn kernel: [33514.079320] 2643 pages reserved
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.472384] httpd: page allocation failure: order:6, mode:0x2084020
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.478742] CPU: 0 PID: 7840 Comm: httpd Tainted: P 4.4.302-st25 #8210
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.486589] Hardware name: Northstar Prototype
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.491037] Backtrace:
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.493510] [<800117bc>] (dump_backtrace) from [<80011a40>] (show_stack+0x18/0x1c)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.501090] r7:00000000 r6:60000013 r5:00000000 r4:8055ca04
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.506799] [<80011a28>] (show_stack) from [<8001398c>] (dump_stack+0x94/0xa8)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.514047] [<800138f8>] (dump_stack) from [<800c5128>] (warn_alloc_failed+0xe4/0x114)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.521980] r7:00000000 r6:00000000 r5:00000006 r4:02084020
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.527687] [<800c5048>] (warn_alloc_failed) from [<800c6068>] (__alloc_pages_nodemask+0x1a4/0x8ac)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.536750] r3:00000000 r2:00000000
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.540344] r6:00000000 r5:8054d420 r4:02084020
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.544997] [<800c5ec4>] (__alloc_pages_nodemask) from [<800c691c>] (alloc_kmem_pages+0x20/0xac)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.553801] r10:00000000 r9:00020000 r8:00000001 r7:824cdf78 r6:02084020 r5:00000006
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.561686] r4:00020001
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.564234] [<800c68fc>] (alloc_kmem_pages) from [<800dbc04>] (kmalloc_order+0x1c/0x34)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.572254] r7:824cdf78 r6:02080020 r5:824cdf78 r4:00020001
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.577967] [<800dbbe8>] (kmalloc_order) from [<800f9b18>] (__kmalloc+0x194/0x1e4)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.585563] [<800f9984>] (__kmalloc) from [<8003ec10>] (MMALLOC+0x1c/0x30)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.592446] r9:00020000 r8:00000001 r7:824cdf78 r6:76a752b0 r5:824cdf78 r4:00020001
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.600248] [<8003ebf4>] (MMALLOC) from [<8003ec4c>] (dev_nvram_read+0x28/0x278)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.607653] r5:824cdf78 r4:00020000
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.611258] [<8003ec24>] (dev_nvram_read) from [<8010503c>] (__vfs_read+0x30/0xd4)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.618837] r9:00020000 r8:00000001 r7:824cdf78 r6:8003ec24 r5:824cdf78 r4:87983300
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.626640] [<8010500c>] (__vfs_read) from [<80105778>] (vfs_read+0x90/0x160)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.633790] r7:824cdf78 r6:ffffe000 r5:76a752b0 r4:87983300
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.639496] [<801056e8>] (vfs_read) from [<8010619c>] (SyS_read+0x58/0xcc)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.646385] r9:00000000 r8:00000000 r7:76a752b0 r6:00020000 r5:87983300 r4:87983301
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.654190] [<80106144>] (SyS_read) from [<800095a0>] (ret_fast_syscall+0x0/0x40)
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.661686] r9:824cc000 r8:80009764 r7:00000003 r6:76b459fc r5:00000000 r4:00000000
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.669738] Mem-Info:
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.672176] active_anon:641 inactive_anon:0 isolated_anon:0
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.672176] active_file:1512 inactive_file:1695 isolated_file:0
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.672176] unevictable:19 dirty:0 writeback:0 unstable:0
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.672176] slab_reclaimable:313 slab_unreclaimable:1836
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.672176] mapped:1071 shmem:0 pagetables:64 bounce:0
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.672176] free:95521 free_pcp:390 free_cma:0
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.704634] Normal free:5024kB min:1384kB low:1728kB high:2076kB active_anon:296kB inactive_anon:0kB active_file:520kB inactive_file:396kB unevictable:76kB isolated(anon):0kB isolated(file):0kB present:131072kB managed:120500
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.748365] lowmem_reserve[]: 0 3072 3072
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.753107] HighMem free:377076kB min:384kB low:1516kB high:2648kB active_anon:2320kB inactive_anon:0kB active_file:5528kB inactive_file:6384kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:393216kB managed:39Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.796695] lowmem_reserve[]: 0 0 0
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.800230] Normal: 99*4kB (UME) 117*8kB (UME) 74*16kB (UME) 52*32kB (UME) 13*64kB (UME) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 5012kB
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.813946] HighMem: 182*4kB (M) 74*8kB (UM) 36*16kB (UM) 13*32kB (UM) 8*64kB (UM) 0*128kB 2*256kB (UM) 2*512kB (U) 2*1024kB (UM) 3*2048kB (UM) 89*4096kB (M) = 377096kB
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.829510] 3211 total pagecache pages
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.833263] 0 pages in swap cache
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.836783] Swap cache stats: add 0, delete 0, find 0/0
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.842018] Free swap = 0kB
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.845169] Total swap = 0kB
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.848199] 131072 pages RAM
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.851303] 98304 pages HighMem/MovableOnly
Nov 14 21:35:10 Asus RT-AC5300 kern.warn kernel: [33516.855705] 2643 pages reserved
Nov 14 21:35:37 Asus RT-AC5300 daemon.info httpd[2079]: [httpd] : Authentication fail
Nov 14 21:36:07 Asus RT-AC5300 daemon.info httpd[2079]: [httpd] : Authentication fail
Nov 14 21:36:38 Asus RT-AC5300 daemon.info httpd[2079]: [httpd] : Authentication fail
Nov 14 21:37:09 Asus RT-AC5300 daemon.info httpd[2079]: [httpd] : Authentication fail
Nov 14 21:37:40 Asus RT-AC5300 daemon.info httpd[2079]: [httpd] : Authentication fail
Nov 14 21:38:10 Asus RT-AC5300 daemon.info httpd[2079]: [httpd] : Authentication fail
Nov 14 21:38:41 Asus RT-AC5300 daemon.info httpd[2079]: [httpd] : Authentication fail
Hapi12021
DD-WRT User


Joined: 22 Jul 2021
Posts: 84

PostPosted: Tue Nov 15, 2022 3:06    Post subject: Reply with quote
Yeah, try the older build I suggested. This may be a kernel bug. Have you been changing sysctl parameters at all?

There are two you can try:

vm.min_free_kbytes = 256000
vm.zone_reclaim_mode = 1

I generally have to set vm.swappiness = 1 as well to prevent OOMs in some cases.

But you shouldn't have to be tuning the kernel on a bone-stock config unless you are doing a lot of other tasks / network operations.

So, try the older build, if that works, you know it's the software's fault. Then maybe go back to current and try the tunables I just mentioned. However, if you see these errors on the older build and with a minimal config, I would hate to say, but it may be failed RAM.

What are your system temperature readings when the router is idle?
Craymond
DD-WRT Novice


Joined: 15 Oct 2018
Posts: 22

PostPosted: Tue Nov 15, 2022 4:25    Post subject: Reply with quote
Hapi12021 wrote:
Yeah, try the older build I suggested. This may be a kernel bug. Have you been changing sysctl parameters at all?

There are two you can try:

vm.min_free_kbytes = 256000
vm.zone_reclaim_mode = 1

I generally have to set vm.swappiness = 1 as well to prevent OOMs in some cases.

But you shouldn't have to be tuning the kernel on a bone-stock config unless you are doing a lot of other tasks / network operations.

So, try the older build, if that works, you know it's the software's fault. Then maybe go back to current and try the tunables I just mentioned. However, if you see these errors on the older build and with a minimal config, I would hate to say, but it may be failed RAM.

What are your system temperature readings when the router is idle?


I haven't made any of the changes yet, I'll hopefully be able to in a day or so. But here is a screen shot of my idle temps:



767F9A2E-D28D-422D-BAEB-B326BF6A3077.jpeg
 Description:
 Filesize:  287 KB
 Viewed:  1644 Time(s)

767F9A2E-D28D-422D-BAEB-B326BF6A3077.jpeg


Craymond
DD-WRT Novice


Joined: 15 Oct 2018
Posts: 22

PostPosted: Wed Nov 16, 2022 4:38    Post subject: Reply with quote
I have loaded an older build, v3.0-r49049 std (06/02/22). Will monitor for issues. Off the bat, Im not seeing a timeout error, but I am seeing this new one that seems related to the GUI skin. I tried a different skin, error persisted. I have a wall of this same error, it is highlighted in red:

daemon.err httpd[2053]: [httpd] : Request Error Code 404: The file style/elegant/colorscheme.css was not found.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12877
Location: Netherlands

PostPosted: Wed Nov 16, 2022 8:40    Post subject: Reply with quote
About your original problem, I do not know what you are doing with the router but maybe you are running out of memory?

Try to use a USB stick with SWAP file of 1 or 2 GB

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Craymond
DD-WRT Novice


Joined: 15 Oct 2018
Posts: 22

PostPosted: Wed Nov 16, 2022 19:06    Post subject: Reply with quote
egc wrote:
About your original problem, I do not know what you are doing with the router but maybe you are running out of memory?

Try to use a USB stick with SWAP file of 1 or 2 GB


Thanks I will see if I have a usb lying around but I don't think I do honestly. Looking at the picture above, I think I'm only using 25% of my memory, but I could be reading it wrong, or the router has memory spikes? As far as my config, it feels tame to me. I use a ddns service, and pihole setup using the sticky in the forum, example 1 from here https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=331414 . Pihole runs on a raspberry pi 4. The majority of my network traffic is wired.
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum