You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using atop in recent aws instances that use ena (t3, c5, m5, probably others) makes the dmesg full of warnings ena: Feature 27 isn't supported every 10 min
From AWS documentation, ena network driver do not support polling nor ethtool requests. Atop is probably query the network driver for their usage or speed and make the ena drive issue the warning.
To supress the warning in the driver, it requires editing the code and recompile, not very friendly, so lets try to make atop more ena friendly.
I can see that atop on those machines do not report usage %, next to the name, so i'm suspecting it is the current network speed query that is failing.
So please either detect that the driver is ena and disable that query, or add a option to disable this driver request, so we can still use atop but keeping dmesg clean.
The text was updated successfully, but these errors were encountered:
Using atop in recent aws instances that use ena (t3, c5, m5, probably others) makes the dmesg full of warnings
ena: Feature 27 isn't supported
every 10 minFrom AWS documentation, ena network driver do not support polling nor ethtool requests. Atop is probably query the network driver for their usage or speed and make the ena drive issue the warning.
To supress the warning in the driver, it requires editing the code and recompile, not very friendly, so lets try to make atop more ena friendly.
I can see that atop on those machines do not report usage %, next to the name, so i'm suspecting it is the current network speed query that is failing.
So please either detect that the driver is ena and disable that query, or add a option to disable this driver request, so we can still use atop but keeping dmesg clean.
The text was updated successfully, but these errors were encountered: