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

FS#2230 - kworker spikes 100% cpu every 2 second. #7161

Closed
openwrt-bot opened this issue Apr 9, 2019 · 3 comments
Closed

FS#2230 - kworker spikes 100% cpu every 2 second. #7161

openwrt-bot opened this issue Apr 9, 2019 · 3 comments
Labels

Comments

@openwrt-bot
Copy link

shelterx:

Seems to happen on ar8xxx based devices, like Netgear R7800 and R7500
Also affects TP-LINK Archer C7(v4)

Present in OpenWrt SNAPSHOT, r9798-549d44736a
Also in OpenWRT 18.06 according to @nm who tried that build, but the cpu spikes seem to be 20% but they do exist.

Seems like the cpu spikes are partly because of this [[https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=d6366ce3665f010a7ae7061a557689643073040a|commit]]
But according to the author of the original [[https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=eff3549c5883a9abc5dbff00c084cabbcfdf4437|commit]] that removed the get_port_stats() function, reading counters are very very slow so the question is if they should be removed again, or at least have an option to disable the MiB counter checks.

For more details have have a look at the last 15 or so posts in this thread,
https://forum.openwrt.org/t/netgear-r7800-exploration-ipq8065-qca9984/285/1544
Thanks to eveyone in the thread where this issue was brought up.

@openwrt-bot
Copy link
Author

ynezz:

FYI, Guo was fast and he has already prepared possible fix #1984 so if you're brave enough and would like to test the WIP, you're welcome.

@openwrt-bot
Copy link
Author

shelterx:

Thanks for giving the link to the commits.
I've tried it and things are much better.
CPU spikes still happen but they're back at 20%, I guess if we want MiB counters and working LEDS we have to live with it, unless it can be optimized further.

One can always disable MiB counters with swconfig, that apparently breaks the LEDs but it also makes the cpu spikes go away.

@openwrt-bot
Copy link
Author

wulfy23:

it is good... no spikes... :)

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

No branches or pull requests

1 participant