Reboot did not reset uptime or reduce RAM used

[Lee MacMillan]

I rebooted my AX-86U today, 37 days after flashing the latest firmware. To my surprise, and for the first time ever, my RAM usage remained at around 658MB (generally it's around 540MB after a reboot) and it didn't reset the uptime. I rebooted again with the same result. What would cause this? Next step will be to unplug it but I've never experienced this before. My setup is very simple, just 2 wired and maybe 18 wireless clients. No scripts, extenders. I do have a USB stick attached and noticed a day or two ago that it no longer shows up in Windows explorer. I don't remember that last time I copied a file to it but I'm pretty sure I've done it since I flashed the latest firmware.

 

[ColinTaylor]

Look in the router's System Log. If your router has actually rebooted it will be obvious. If not that would explain the uptime anomaly.

 

[Lee MacMillan]

I unplugged it and that did the trick. And my USB stick is again visible. Wondering why the reboot function didn't work.

 

[ColinTaylor]

Wondering why the reboot function didn't work.

Yes, strange. If only there were some sort of Log of System activity that might have provided a clue.

 

[Lee MacMillan]

Yes, strange. If only there were some sort of Log of System activity that might have provided a clue.

The system log only showed what it always shows which is when I go into and out of sleep. Here is the log from today. I rebooted twice from the GUI around 1:00. It was 5:28 when I pulled the plug.

Sep 30 11:30:12 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 11:48:01 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 12:01:42 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 12:52:33 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 12:54:54 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 12:56:58 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 12:59:27 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 13:15:41 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 13:32:04 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 14:35:26 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 14:44:08 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 15:33:24 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 15:59:04 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 17:28:42 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 100 mbps full duplex
Sep 30 17:28:44 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 17:28:46 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 100 mbps full duplex
Sep 30 17:28:50 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 17:28:53 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
May 5 01:05:10 kernel: brcmboard registered
May 5 01:05:10 kernel: bcmswlpbk0 (Ext switch port: 8) (Logical Port: 8) Virtual link DOWN
May 5 01:05:10 kernel: broadcomThermalDrv brcm-therm: init (CPU count 4 4 4 4)
May 5 01:05:10 kernel: bcmswlpbk0 (Ext switch port: 8) (Logical Port: 8) Virtual link UP
May 5 01:05:10 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex
May 5 01:05:12 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link Up at 100 mbps full duplex
May 5 01:05:13 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
May 5 01:05:13 Mastiff: init
Sep 30 17:39:10 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 18:01:18 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex

 

[ColinTaylor]

I suspect the cause of the problem happened around the time it stopped showing up in Windows Explorer.

 

[Lee MacMillan]

I suspect the cause of the problem happened around the time it stopped showing up in Windows Explorer.

If the USB sticks disappears from Explorer again (and this was the first time ever), I'll just pull the plug.

 

[drinkingbird]

The system log only showed what it always shows which is when I go into and out of sleep. Here is the log from today. I rebooted twice from the GUI around 1:00. It was 5:28 when I pulled the plug.

Sep 30 11:30:12 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 11:48:01 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 12:01:42 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 12:52:33 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 12:54:54 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 12:56:58 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 12:59:27 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 13:15:41 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 13:32:04 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 14:35:26 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 14:44:08 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 15:33:24 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
Sep 30 15:59:04 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 17:28:42 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 100 mbps full duplex
Sep 30 17:28:44 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 17:28:46 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 100 mbps full duplex
Sep 30 17:28:50 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 17:28:53 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
May 5 01:05:10 kernel: brcmboard registered
May 5 01:05:10 kernel: bcmswlpbk0 (Ext switch port: 8) (Logical Port: 8) Virtual link DOWN
May 5 01:05:10 kernel: broadcomThermalDrv brcm-therm: init (CPU count 4 4 4 4)
May 5 01:05:10 kernel: bcmswlpbk0 (Ext switch port: 8) (Logical Port: 8) Virtual link UP
May 5 01:05:10 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link Up at 1000 mbps full duplex
May 5 01:05:12 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link Up at 100 mbps full duplex
May 5 01:05:13 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex
May 5 01:05:13 Mastiff: init
Sep 30 17:39:10 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link DOWN.
Sep 30 18:01:18 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) (phyId: 9) Link Up at 1000 mbps full duplex

I've had cases where clicking the reboot button did not actually reboot the router though the GUI made it appear to. Not recently, but there are definitely scenarios where that can happen. I prefer to just power cycle it or issue the command in SSH.