[RFC] dhcpcd: fix high cpu usage #15858
Closed
Conversation
As reported on IRC, some users are experiencing high CPU usage when using eduroam and/or suspending/resuming their machines. This update includes a few upstream changes that should possibly address this situation: 1. Runs the STOPPED hook on interfaces when a timeout occurs. 2. Includes an upstreamed musl patch. 3. Validates RTM_DELADDR/RTM_NEWADDR messages for both IPv6 and IPv4. I believe the last change most directly addresses the high CPU usage situation.
|
Hmm... unfortunately, I just experienced the high CPU usage situation with this package... so the patches are no sufficient for solving this problem. It may be worth reverting back to 8.0.6 until this is resolved. |
|
Happens here with my ThinkPad T470. Eventually it fails to renew my IP address and I then have no network. dhcpcd fails to restart or stop if requested through sv command. I have to reboot. No interesting messages appear in socklog. |
|
As another data point, i'm experiencing the same issues as @jmai444 (albeit on an IdeaPad 310). |
|
Just revert to 8.0.6 for now... #15885 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
As reported on IRC, some users are experiencing high CPU usage when
using eduroam and/or suspending/resuming their machines. This update
includes a few upstream changes that should possibly address this
situation:
Runs the STOPPED hook on interfaces when a timeout occurs.
Includes an upstreamed musl patch.
Validates RTM_DELADDR/RTM_NEWADDR messages for both IPv6 and IPv4.
I believe the last change most directly addresses the high CPU usage
situation.