RT-AX82U famous aaews Tainted error log

[HammerJoe]

I have a RT-AX82U and I am using the latest 3004.388.9_2 version available for this router and I checked the log the other day and I notice the error :
kernel: potentially unexpected fatal signal 11.
Jun 10 20:04:02 kernel: CPU: 0 PID: 18319 Comm: aaews Tainted: P O 4.1.52 #1
Jun 10 20:04:02 kernel: potentially unexpected fatal signal 11.
Jun 10 20:04:02 kernel: CPU: 1 PID: 18314 Comm: aaews Tainted: P O 4.1.52 #1

I researched a bit and there are other similar errors for DCD and SIGSERV, but not for aaews.
The router is used as wireless device only, no aiprotection and qos is off just in case.
I wonder what could be causing this error?
Also did a factory reset.

 

[bennor]

I have a RT-AX82U and I am using the latest 3004.388.9_2

To clarify do you really have a RT-AX82U? That model doesn't appear to be supported by Asus-Merlin, but is supported by the Gnuton fork of Asus-Merlin. If you really have a RT-AX82U, do you have a v1 or v2? The latest stable GNuton firmware for the RT-AX82U v1 and v2 is 3004.388.8_4-gnuton1 (January 11, 2025).

 

[HammerJoe]

Its the V1 version of the router and its using the latest gnuton firmware.
My question was more broad in understanding what does AAWES do to figure out what is causing the error.

 

[aex.perez]

Its the V1 version of the router and its using the latest gnuton firmware.
My question was more broad in understanding what does AAWES do to figure out what is causing the error.

This might help you answer that

Solved - aaews open two port random

Hello, first of all, apologize for my English. I tell you my situation. I don't have much router experience. I currently have the following connection. ONT --> RT-AX82U(Firmware:388.2_2_0-gnuton1) 192.168.2.x --> Lan4 to wan port RT-AC66U B1 192.168.1.x ( Firmware:386.12) static wan port...

www.snbforums.com

 

[Morpheus2020]

My AX82U running Asuswrt 388_25035 also has this "aaews tainted". This issue has been going on for over a month.
My BE88U ruuning Asuswrt-Merlin 102.4 also has this "aaews tainted".

Aaews is a program of Asusnat. I guess the server sent wrong data to the router.

 

[HammerJoe]

I think I found the issue for my router.
In Administration-Policy I withdrew "For AiProtection, Parental Control(Web&Apps Filter), Traffic Analyzer, Apps analyzer, Adaptive QoS/Game boost, Web history:"
The error went away.
After a few hours without seeing the error show up in the logs I turned traffic Analyzer on, which brought back the message in the policy menu and since it still has not produced an error.
So Withdrawing that certificate seems to have updated whatever aaews needed.
I am still keeping an eye to see if the tainted message comes back.

 

[RMerlin]

"Tainted" has absolutely nothing to do with the aaews process. You need to read this line like this:

CPU: 0
PID: 18319
Comm: aaews
Tainted: P O

P: kernel uses Proprietary (non-GPL) kernel modules
O: kernel uses out-of-tree (not part of the Kernel source code tree) modules

 

[Morpheus2020]

I think I found the issue for my router.
In Administration-Policy I withdrew "For AiProtection, Parental Control(Web&Apps Filter), Traffic Analyzer, Apps analyzer, Adaptive QoS/Game boost, Web history:"
The error went away.
After a few hours without seeing the error show up in the logs I turned traffic Analyzer on, which brought back the message in the policy menu and since it still has not produced an error.
So Withdrawing that certificate seems to have updated whatever aaews needed.
I am still keeping an eye to see if the tainted message comes back.

Aaews is a component of Asusnat and has nothing to do with TrendMirco's Ai Protection and Adapive QoS.
This error is very rare and you may need to observe it for a few days or even a month before you encounter it. Of course, you may also encounter it within 24 hours.

 

[HammerJoe]

Aaews is a component of Asusnat and has nothing to do with TrendMirco's Ai Protection and Adapive QoS.
This error is very rare and you may need to observe it for a few days or even a month before you encounter it. Of course, you may also encounter it within 24 hours.

All I can tell is that the aaews issue went away when I withdrew the policy. I understand that it has something to do with qos, aisecurity and traffic analyzer, which I already had off to find the aaews trigger.
After that I turned the traffic analyzer on again and the error didnt come back. My only guess about this is that when I withdrew the policy, it updated some config file with a proper value that aawes can handle.