Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
NetworkManager
NetworkManager
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 146
    • Issues 146
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • NetworkManager
  • NetworkManagerNetworkManager
  • Issues
  • #123

Closed
Open
Opened Feb 14, 2019 by Qu Wenruo@adam900710

100% CPU usage for Network Manager process, may be due to IPv6 neighbor discovery

Hi,

I recently find that NetworkManager process will take 100% CPU (one CPU thread) for no obvious reason.

I have changed the log level to DEBUG, and around the 100% CPU usage duration, the only interesting event is: adam-pc NetworkManager[11365]: [1550140076.3784] ndisc-lndp[0x560ac3ce50e0,"eth0"]: processing libndp events

And strace only shows NetworkManager is writing tons of "\1\0\0\0\0\0\0\0" to fd 3, however since I'm attaching to running NetworkManager, I can't know where fd 3 is binded. From procfs, fd 3 of that running NetworkManager process is just an anonymous inode.

Now I have disabled IPv6 completely and sees no problem for over 1 day. But I really hope to use IPv6, have tried "auto (DHCP only)", that seems to ignore neighbor discovery, but also ignored my default route advertising. "Auto (address only)" makes my default route work, but also accepts neighbor discovery.

How can I further pinning down the bug?

The version of NM is 1.14.5dev+17+gba83251b-2.

Thanks

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: NetworkManager/NetworkManager#123