Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

atop on aws: "ena: Feature 27 isn't supported" #46

Open
danielmotaleite opened this issue Jan 2, 2019 · 0 comments
Open

atop on aws: "ena: Feature 27 isn't supported" #46

danielmotaleite opened this issue Jan 2, 2019 · 0 comments

Comments

@danielmotaleite
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant