Hide Forgot
Version-Release number of selected component (if applicable): NetworkManager-1.2.2-2.fc24.x86_64 Steps to Reproduce: 1. run `top` in a terminal window 2. run `sudo ping -f localhost` in another Actual results: NetworkManager at 100% cpu Expected results: N-M doing something sensible, like less than 20M cpu cycles per second (1%) :) This is corner case, but maybe it also means N-M is draining more battery than it strictly needs during more normal operation.
Can you: nmcli g log level debug ping -f localhost and then grab the debug logs: journalctl -b -u NetworkManager --since="-2m" and attach them to the bug? You can then disable debug logging with: nmcli g log level info
Created attachment 1192434 [details] journalctl -b -u NetworkManager # after ping -f localhost
Created attachment 1192436 [details] journalctl -b -u NetworkManager # after ping -4 -f localhost After looking at the debug log I tried `ping -4 localhost`; it does not trigger the same problem. It looked as if NM is receiving all ICMPv6 packets. Maybe the answer is moar BPF, to limit the received packets to router announcements.
Submitted patch to libndp to filter non-ND messages at kernel level: https://www.redhat.com/archives/libndp-list/2016-August/msg00001.html
libndp patch applied upstream: https://github.com/jpirko/libndp/commit/e8b90ce2d6ebf846cb0c9a3255d4deacf075f9c4
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still affects Fedora 26 :(.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Reproduced on Fedora 28. (Presumably 27 is affected just as 26 was, but I don't have that any more).
Fixed in: https://src.fedoraproject.org/rpms/libndp/c/11af90a535920e3f9cf4b0587ee93893203c0919?branch=master https://koji.fedoraproject.org/koji/taskinfo?taskID=27485775
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.