[systemd-bugs] [Bug 64217] New: Logind occupies 100% CPU after resume

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=64217

          Priority: medium
            Bug ID: 64217
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Logind occupies 100% CPU after resume
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: inkane at chakra-project.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

With systemd 198, (probably 199), 200 and 202 , systemd occupies 100% CPU when
suspending (to RAM or to disk) from KDE – and only when NetworkManager is used.
Restarting systemd-logind solves this, though one needs to manually restart
NetworkManager too.
stracing logind shows
epoll_wait(4, {}, 1, 0)                 = 0
being called multiple times per second. When I attached gdb to systemd-logind
to locate the issue, it showied that logind is cycling around in login/logind.c
(manager_run). The line numbers are from logind as of 202. The output is
available at http://paste.chakra-project.org/4560/
So far I've seen this only affecting us (Chakra Linux), though I don't know how
many distributions besides Arch and us and us have packaged systemd > 197 so
far. As stated above this could only be reproduced on systems suspending from
KDE and using NetworkManager. Users running wicd or using systemctl suspend
were not affected.
Any help with finding the cause of this would be highly appreciated.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130504/352fe970/attachment.html>