Hi, i did a dirty upgrade from 348.18 to 348.19 on ax88u and now it restart randomly. Some times one cpu is 100% and in top show this:
Code:
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
35 2 user SW 0 0.0 0 24.9 [skb_free_task]
This statement is not correct. Have tested a little more, and
v. 19 on RT-AX88U is the culprit, where I cannot access the
Internet.
Right now.... back on v. 18 on both routers :-(
I no
I am having the same issue, along with the red light being on the RT-AX88U. I had to do factor reset and ran into many issues attempting to re-establish my mesh to my RT-AX58U (Wired). When you are applying the patch on the AX88U should you format the JFFS during the reboot ? I have not tried this because happy wife happy life rule applied, went back to 384.18 no issues.
I am a long time watcher, first time poster.
I am happy to see I am not the only one with issues with this update to 384.19 on my AX88U. I was about to submit a warranty repair for the router until I saw many people with issues as well.
I should mention, I've been flashing the Merlin builds on my AX88U since the beta versions of 384.15 without issues... I've been happily alpha and beta testing Merlin builds, sometimes with small bugs (to be expected) nothing this serious though.
This version has been a complete s**t-show (pardon my language) for me since the Alphas of 384.19!!!
For whatever reason, once I get any version of 384.19 (Alpha, beta or release) on my AX88U, it randomly reboots anywhere from every 3 minutes to every 12 minutes without any action on my part. I'm just watching the lights on the router, not even logged into the webUI.
I tried to reformat JFFS multiple times without luck, did multiple factory resets (using both the reset button on the webUI and the WPS method) and reconfiguring from scratch without luck, and also tried to use the Asus firmware restoration utility and rescue mode to re-flash the firmware down and back up again still with issues....
(Every time reconfiguring from scratch on any big firmware jump, i.e 384.18 to 384.19) and still having the random reboot issues - It's still very unstable and restarting every 3 minutes after reconfiguring from scratch.
I am configuring the device to use with WAN Aggregation and Static IP without PPPOE... (No UPNP Enabled, No NAT Enabled, No Firewalls, No AI Protection, No QoS, No IPV6..)
It's a very simplistic configuration as it's behind my own custom built Pfsense router doing most of the actual work, this is mostly acting as a simple AP, but it's in router mode for WAN aggregation so I can get the full 1.5Gbit/s over WiFi 6).
What's interesting is downgrading back to 384.18 is flawless and is the latest merlin firmware I can use this far. and upgrading to the ASUS official build of: Version 3.0.0.4.384.9566 also works flawlessly. (After reconfiguring from scratch)
Also noticed that every time the router reboots after being reconfigured on 384.19, that logs mention kernel errors on May 5th, and then continues to update the logs with the accurate date of August 16th...
After the 3 minutes pass, it will reboot again, and all the logs are once again flooded with kernel errors from "May 5th."
I would of grabbed some more details, but I only had 2 hours to play around with this last night as I live in a house with 5 people and 42 connected devices and I only get a few hours window to do these upgrades while people sleep or they get angry lol.
@RMerlin let me know if you need more details for replicating the problem.
I am wondering if there could be some kind of unforeseen bug with the code in relation to the maintenance done on the nt_center database on first boot of the newer AX88U code...?
I want to say none of this is an attack against
@RMerlin or ASUS, as I've been forever grateful of all the work done! I am just looking to provide feedback and assist wherever possible. This is the first time a bug/issue has made it to the final release for me that still wasn't reported or identified before in the alpha's/beta's, so I figured i'd chime in.