My Asus RT-AX88U is somewhat unstable with this build. Not entirely sure what is going on, can't locate anything odd in the system logs other than a bunch of these messages on a constant repeat;
kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
1-2 times per week Internet Connection will get lost as the WAN DHCP is reporting that there is something wrong with my ISP DHCP Service. Setting a manual WAN IP and the reverting back to DHCP or just a reboot will solve it until it locks up again after some days.
Tried to flash 389.10 Alpha 2 today and did a factory restore without importing my old configuration (just did a nvram set and commit on my dhcp static list so I didn't need to enter all those mac-addresses, hostname's and IP-addresses) and these;
kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Are coming back again. Not sure exactly what these messages are or means or whether they have anything to do with the WAN DHCP struggling 1-2 times per week but I have never had these messages repeating nonstop in the system logs in the past.
EDIT:
I'm certain there is nothing wrong with the ISP DHCP services as I have three ports from the ISP all offering dynamic IPv4 addresses using DHCP and a second is used for my Palo Alto firewall for my site-to-site IPsec connection and this one has been rock solid while my RT-AX88U have reporting "issues" with the same DHCP services four-five times while the Palo Alto has not had any issues whatsoever.
EDIT2:
It's worth mention that these messages in the system log does not seem to change. So it the same one being repeated over and over again, the values in the message does not seem to change;
Mar 1 18:51:07 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 1 18:51:08 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 1 18:51:16 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 1 18:51:34 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 1 18:51:43 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 1 18:51:47 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 1 18:51:56 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
Mar 1 18:52:01 kernel: blog_death_by_timeout: bad timeout value=18446744073709541616, extra_jiffies=30000, idle_jiffies=40000
EDIT3:
Can't really find much about these messages on the web other than some posts on the Asus forums in Chinese without much information or conclusion.
According to the previous Asus RT-AX88U firmware from Asus;
Version 3.0.0.4.384.53292018/12/1363.72 MBytes
ASUS RT-AX88U Firmware version 3.0.0.4.384.5329
Bug fixes and improvement:
- Improved AiMesh stability
- Improved wireless stability in DFS channel
- Fixed WAN detection bug.
Others:
Modified QIS description in HE frame step.
Please unzip the firmware file first then check the MD5 code.
MD5: 486fc04c454a240af75f43dd7de7b4d5
It might look like this is a RT-AX88U specific bug that was fixed in the official firmware in December. I'm not entirely sure if Merlin 384.9 contains said fix?