380.69_2 on AC5300 locked up

[evildoer]

I installed this newest firmware less than a week ago and last night my internet stopped on all devices, and I also could not log into the router itself. Had to power it off and on. Its all working now, but I had to reset all of my logging which was being saved to an external drive. I guess it got corrupted and it would not connect to it.

I had been previously running the second latest firmware for weeks, if not months, with no issues.

 

[HuskyHerder]

I experienced a couple of those, on my AC5300. I did not do a clean install upon my last update. I have not had any of those lockups in the last few days.


* AB-Solution, Skynet installed.

 

[NickBurns]

I posted something similar with upgrade from 69 to 69_2. After the first dozen or so of these events things have stabilized. Still on 69_2.

https://www.snbforums.com/threads/rt-ac5300-random-wifi-restart.44326/

 

[NickBurns]

Scratch that. Checked the logs and it happened again yesterday while I was away.

I am hoping this is a driver issue fixed in the updated bcmdhd driver in the 384 GPL. I am also curious if in 380.69/69_2 perhaps they may have been an undocumented driver update/change that would tie it all together.

Feb 8 11:21:52 kernel: dhdpcie_checkdied: msgtrace address : 0x00000000
Feb 8 11:21:52 kernel: console address : 0x003FFCF0
Feb 8 11:21:52 kernel: Assrt not built in dongle
Feb 8 11:21:52 kernel: TRAP type 0x4 @ epc 0x27c408, cpsr 0x280001d3, spsr 0x280001f2, sp 0x2aacac, lp 0x33f7b, rpc 0x27c408
Feb 8 11:21:52 kernel: Trap offset 0x2aac54, r0 0x200968, r1 0x4, r2 0x2008ec, r3 0x0, r4 0x4, r5 0x0, r6 0x3bd600, r7 0x280001d2
Feb 8 11:21:54 kernel: dhd_detach(): thread:dhd_watchdog_thread:24fe terminated OK
Feb 8 11:21:54 kernel: dhd_detach(): thread:dhd_watchdog_thread:24f7 terminated OK
Feb 8 11:21:54 kernel: dhd_detach(): thread:dhd_watchdog_thread:24f1 terminated OK
Feb 8 11:21:58 kernel: PCI_PROBE: bus 3, slot 0,vendor 14E4, device 4365(good PCI location)
Feb 8 11:21:59 kernel: dhd_attach(): thread:dhd_watchdog_thread:6003 started
Feb 8 11:21:59 kernel: Dongle Host Driver, version 1.363.45.58013 (r651509)
Feb 8 11:21:59 kernel: Compiled in drivers/net/wireless/bcmdhd on Jun 15 2017 at 14:50:24
Feb 8 11:21:59 kernel: Register interface [eth1] MAC: xx:xx:xx:xx:xx:c0
Feb 8 11:21:59 kernel: PCI_PROBE: bus 4, slot 0,vendor 14E4, device 4365(good PCI location)
Feb 8 11:21:59 kernel: dhd_attach(): thread:dhd_watchdog_thread:6009 started
Feb 8 11:22:00 kernel: Dongle Host Driver, version 1.363.45.58013 (r651509)
Feb 8 11:22:00 kernel: Compiled in drivers/net/wireless/bcmdhd on Jun 15 2017 at 14:50:24
Feb 8 11:22:00 kernel: Register interface [eth2] MAC: xx:xx:xx:xx:xx:c4
Feb 8 11:22:00 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Feb 8 11:22:00 kernel: dhd_attach(): thread:dhd_watchdog_thread:600f started
Feb 8 11:22:00 kernel: Dongle Host Driver, version 1.363.45.58013 (r651509)
Feb 8 11:22:00 kernel: Compiled in drivers/net/wireless/bcmdhd on Jun 15 2017 at 14:50:24
Feb 8 11:22:00 kernel: Register interface [eth3] MAC: xx:xx:xx:xx:xx:c8
Feb 8 11:22:01 kernel: IGMP Query send failed
Feb 8 11:22:01 kernel: IGMP Query send failed

 

[evildoer]

Just happened again. Looks like this will happen every 4-5 days requiring a reboot.

 

[HuskyHerder]

I just had another one this morning. I am going to try a clean slate and reinstall. See if that helps. I’m traveling for work so it may be a bit before I can report back.


I seem to recall it’s not recommended to backup and restore settings for a true clean slate. All I mainly care about is my static IP settings. I have a bunch too many to want to type again. 90% are overkill. But me being me I like a nice tidy setup.
Any good way to save those? and I can recreate everything else from scratch.

I did copy them from the page already and with assigned IPs so it could just be a lot of copy n paste for me.
To be honest I know there is a NVRAM save utility. I need to go find the thread and research some.

I don’t know if I should use it for a clean slate and or if it would even backup my desired settings.


Anyone that could give some nudges in the correct direction would be greatly appreciated. Even to say your SOL copy n paste. LOL.

 

[Jack Yaz]

I just had another one this morning. I am going to try a clean slate and reinstall. See if that helps. I’m traveling for work so it may be a bit before I can report back.


I seem to recall it’s not recommended to backup and restore settings for a true clean slate. All I mainly care about is my static IP settings. I have a bunch too many to want to type again. 90% are overkill. But me being me I like a nice tidy setup.
Any good way to save those? and I can recreate everything else from scratch.

I did copy them from the page already and with assigned IPs so it could just be a lot of copy n paste for me.
To be honest I know there is a NVRAM save utility. I need to go find the thread and research some.

I don’t know if I should use it for a clean slate and or if it would even backup my desired settings.


Anyone that could give some nudges in the correct direction would be greatly appreciated. Even to say your SOL copy n paste. LOL.

https://www.snbforums.com/threads/user-nvram-save-restore-utility-r26-2.19521/

To save you some time!

 

[HuskyHerder]

Just adding another thing, that I have noticed.

Every few days my OpenVPN server (#1) will crash and in the GUI its always shown as stopped. Every time it has occurred, I have had to have the Mrs. Restart the server. This happens on different days than my complete router lockup to the best of my knowledge.

I am trying to limp by with it as is..., I am traveling (work) for another week.

I am seeing this from my log. I don't know if its relevant

Feb 12 07:00:00 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 464210
Feb 12 07:50:18 kernel: SysRq : Emergency Sync
Feb 12 07:50:18 kernel: Emergency Sync complete

Edit:

I have found a few topics relating, to the message. I am going to see if my problem persists after several changes,