On 10/15/2017 10:31 AM, Michael Biebl wrote: > Am 14.10.2017 um 21:48 schrieb Glen B: >> 295 root 20 0 7448 4432 3992 R 41.2 0.9 0:54.81 >> systemd-logind >> 298 message+ 20 0 6260 3636 3268 S 17.6 0.7 0:17.12 >> dbus-daemon > That looks like there is a huge amount of dbus messages sent. > Can you run dbus-monitor --system (as root) to see what those messages are?
That's an interesting command, lots of information was spat out. Here's an excerpt of what was put out: ---- uint32 0 error time=1508114297.985967 sender=:1.0 -> destination=:1.1 error_name=org.freedesktop.systemd1.UnitMasked reply_serial=26352 string "Unit suspend.target is masked." signal time=1508114297.986032 sender=:1.0 -> destination=(null destination) serial=52814 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=UnitNew string "suspend.target" object path "/org/freedesktop/systemd1/unit/suspend_2etarget" signal time=1508114297.986058 sender=:1.0 -> destination=(null destination) serial=52815 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=UnitRemoved string "suspend.target" object path "/org/freedesktop/systemd1/unit/suspend_2etarget" signal time=1508114297.991185 sender=:1.1 -> destination=(null destination) serial=26353 path=/org/freedesktop/login1; interface=org.freedesktop.login1.Manager; member=PrepareForSleep boolean true method call time=1508114297.992516 sender=:1.1 -> destination=org.freedesktop.systemd1 serial=26354 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=StartUnit string "suspend.target" string "replace-irreversibly" method call time=1508114297.993237 sender=:1.0 -> destination=org.freedesktop.DBus serial=52816 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=GetConnectionUnixUser string ":1.1" method return time=1508114297.993292 sender=org.freedesktop.DBus -> destination=:1.0 serial=13188 reply_serial=52816 ---- If I'm understanding this correctly, it looks like it's trying to suspend but is somehow getting confused... On 10/15/2017 4:52 PM, rhkra...@gmail.com wrote: > <Top posting intentionally> > > There was a recent thread where the symptom, in one sense, was somewhat > similar--on a two CPU system, one CPU was using 100% of one CPU with the lid > closed. IIUC, the problem was due to lightdm-gt (or some sub-program). > > Here are the headers from the last message in that thread: > > Re: Debian 9.2 amd64 Xfce lock screen -> 100 %CPU by lightdm-gt+ > From: David Christensen <dpchr...@holgerdanske.com> (resent from debian- > u...@lists.debian.org) > To: debian-user@lists.debian.org > Date: Thu Oct 12 12:41:46 2017 > > Maybe it is worth looking at that thread. I took a look at the thread you referred to, but I'm afraid we're looking at different issues... I don't have any desktop-GUI-related things installed (at least, I'm not supposed to). Thank you both for your responses!
