Bug#788622: systemd-logind regularly eats over 20% of system resources
Michael Biebl
biebl at debian.org
Sat Jun 13 17:52:11 BST 2015
Am 13.06.2015 um 18:39 schrieb Martin-Éric Racine:
> 2015-06-13 18:42 GMT+03:00 Michael Biebl <biebl at debian.org>:
>> Can you run "udevadm monitor"
>
> Endless series of these:
>
> KERNEL[4312.794011] change
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0
> (power_supply)
> UDEV [4312.799277] change
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0
> (power_supply)
No other events related to the drm subsystem?
logind subscribes to various udev events [1], and if your system
produces a huge amount of them, it's quite possible that this takes some
amount of CPU time.
Can you also boot with systemd.log_level=debug on the kernel command
line and attach the log from
journalctl -u systemd-logind
[1] https://github.com/systemd/systemd/blob/master/src/login/logind.c#L834
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150613/13939259/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list