[SOLVED] (ish) systemd-journald high CPU usage after crash...

LucetLux · 2013-12-15 15:41:11

Well, as you can probably guess from the title I have no idea what is going on with my system.

Yesterday suddenly my system hanged, I left it like that for a while but it wouldn't respond to any input, so I just hard restarted it. After that opengl wasn't working on kde for whatever reason and everything was just running like crap, I reinstalled the kernel, which rebuilt all its dependencies including the catalyst kernel module, then I restarted, and at least I got rid of the opengl problems, but now, after 10 minutes or so everything just starts slowing down, and some applications just close with no warning.

I went to ksysguard and the first thing I noticed is that systemd-journald is always on 33% cpu usage, and around 200mb memory usage, I have a triple core cpu, and over time one of them is always at 100% usage, it seems to switch periodically between either of the first 2 cores.

Anyway, that is that, then I also noticed that I can't get to root, if I run sudo I get the password prompt but after that it just does nothing, same with su, therefore I can't check journalctl.

Any ideas on what could be causing this and how to solve it would be appreciated.
Thanks in advance.

Last edited by LucetLux (2013-12-20 02:29:19)

LucetLux · 2013-12-15 15:44:56

And as unexpectedly as this began it suddenly stopped...

systemd-journald is back to normal cpu usage of about 0 and I can now access root.

The output of journalctl:

-- Logs begin at Sat 2013-11-16 01:14:35 UYST, end at Sun 2013-12-15 13:45:44 UYST. --
Nov 16 01:14:34 badass-pc systemd[559]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
Nov 16 01:14:34 badass-pc systemd[559]: Mounted /sys/kernel/config.
Nov 16 01:14:34 badass-pc systemd[559]: Stopped target Sound Card.
Nov 16 01:14:34 badass-pc systemd[559]: Starting Default.
Nov 16 01:14:34 badass-pc systemd[559]: Reached target Default.
Nov 16 01:14:34 badass-pc systemd[559]: Startup finished in 31ms.
Nov 16 01:14:35 badass-pc /etc/gdm/Xsession[565]: /etc/gdm/Xsession: Beginning session setup...
Nov 16 01:14:35 badass-pc /etc/gdm/Xsession[565]: localuser:blacklotus being added to access control list
Nov 16 01:14:35 badass-pc /etc/gdm/Xsession[565]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /usr/bin/startkde
Nov 16 01:14:37 badass-pc /etc/gdm/Xsession[565]: cat: /proc/621/comm: No such file or directory
Nov 16 01:14:38 badass-pc /etc/gdm/Xsession[565]: startkde: Starting up...
Nov 16 01:14:39 badass-pc /etc/gdm/Xsession[565]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Nov 16 01:14:39 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Nov 16 01:14:39 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Nov 16 01:14:41 badass-pc /etc/gdm/Xsession[565]: kbuildsycoca4 running...
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: NetworkManagerQt "kded" ( 633 ) void NetworkManager::SettingsPrivate::init() : New Connections list
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: NetworkManagerQt "kded" ( 633 ) void NetworkManager::SettingsPrivate::init() :   "/org/freedesktop/NetworkManager/Settings/0"
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: NetworkManagerQt "kded" ( 633 ) void NetworkManager::SettingsPrivate::init() : New Connections list
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: NetworkManagerQt "kded" ( 633 ) void NetworkManager::NetworkManagerPrivate::init() : Active connections:
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: NetworkManagerQt "kded" ( 633 ) void NetworkManager::NetworkManagerPrivate::init() :      "/org/freedesktop/NetworkManager/ActiveConnection/0"
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: NetworkManagerQt "kded" ( 633 ) void NetworkManager::NetworkManagerPrivate::init() : Device list
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: NetworkManagerQt "kded" ( 633 ) void NetworkManager::NetworkManagerPrivate::init() :    "/org/freedesktop/NetworkManager/Devices/0"
Nov 16 01:14:43 badass-pc /etc/gdm/Xsession[565]: ModemManagerQt "kded" ( 633 ) void ModemManager::ModemManagerPrivate::init() : Error getting device list:  "org.freedesktop.DBus.Error.Service
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.6'
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: "/org/freedesktop/UDisks2/drives/HL_DT_ST_DVDRAM_GSA_H42N_K0C6C4A5412" : property "Drive" does not exist
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: "/org/freedesktop/UDisks2/drives/TOSHIBA_DT01ACA200_13UG2N1AS" : property "Drive" does not exist
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: "/org/freedesktop/UDisks2/drives/WDC_WD10EZEX_22RKKA0_WD_WMC1S1706705" : property "Drive" does not exist
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: "/org/freedesktop/UDisks2/drives/TOSHIBA_DT01ACA200_13UG2N1AS" : property "DeviceNumber" does not exist
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: "/org/freedesktop/UDisks2/drives/TOSHIBA_DT01ACA200_13UG2N1AS" : property "Device" does not exist
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: "/org/freedesktop/UDisks2/drives/WDC_WD10EZEX_22RKKA0_WD_WMC1S1706705" : property "DeviceNumber" does not exist
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: "/org/freedesktop/UDisks2/drives/WDC_WD10EZEX_22RKKA0_WD_WMC1S1706705" : property "Device" does not exist
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: kded(633)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Nov 16 01:14:44 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.40'
Nov 16 01:14:45 badass-pc /etc/gdm/Xsession[565]: kded(633) PowerDevil::Core::loadProfile: The profile  "AC" tried to activate "DimDisplay" a non existent action. This is usually due to an ins
Nov 16 01:14:46 badass-pc /etc/gdm/Xsession[565]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Nov 16 01:14:46 badass-pc /etc/gdm/Xsession[565]: kwin(668) KWin::Extensions::init:  non_native_pixmaps:  false
Nov 16 01:14:46 badass-pc /etc/gdm/Xsession[565]: kwin(668) KWin::Xcb::Extensions::init: Extensions: shape: 0x "11"  composite: 0x "4"  render: 0x "b"  fixes: 0x "50"  randr: 0x "14"  sync: 0x
Nov 16 01:14:46 badass-pc /etc/gdm/Xsession[565]: kwin(668) KDecorationPlugins::canLoad: kwin : path  "/usr/lib/kde4/kwin3_oxygen.so"  for  "kwin3_oxygen"
Nov 16 01:14:46 badass-pc /etc/gdm/Xsession[565]: kwin(668): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed"

Last edited by LucetLux (2013-12-15 15:49:33)

LucetLux · 2013-12-15 16:06:37

I could say this just solved itself, but if anyone could give me a reason as to why this happened in the first place it would make me happier

LucetLux · 2013-12-20 00:46:25

It's happening again... Any idea why ?

This seems to be my problem exactly :
https://bugs.archlinux.org/task/33450

edit:
I just had to hard reset, after 2 minutes or so it started again, and I could stop it before it hanged my system again, but that isn't really solving it is it ?

I noticed there are like 20 systemd-coredump processed running, what the hell...

Last edited by LucetLux (2013-12-20 01:40:26)

cfr · 2013-12-20 01:55:32

Did you take the advice suggested in that bug report? That is, disable the functionality in sysctl and/or gripe upstream? (Or see if there's already an upstream bug?)

LucetLux · 2013-12-20 02:05:46

I don't really understand any of it.
/usr/lib/sysctl.d/coredump.conf doesn't even exist in my system, so there's nothing I can do there.

If I run these:
$ printf 'int main(void) { int *i = 0; *i = 10; return 0; }' | gcc -x c -
$ for x in {1..100}; do ./a.out; done

Which I have no idea what they do, I get spammed by "Segmentation fault (core dumped)".

I have no idea of either what's going on or of what I'm doing.

Not being able to use sudo after 5 minutes from the latest reboot isn't helping either...

edit: For some reason my coredump.conf is actually named 50-coredump.conf, I commented out the last line, it looks like systemd-journald is back to normal usage, I still don't understand what's going on... Neither do I understand if there's any downside to disabling this function, nor why this problem started in the first place.
At least my system is usable now, thanks for your help.

btw: now that I look at it, virtuoso-t seems to be popping at around 20% cpu usage, then it vanished for a few seconds, then it's back, I don't know if that's considered normal either.

Last edited by LucetLux (2013-12-20 02:26:35)

Arch Linux

#1 2013-12-15 15:41:11

[SOLVED] (ish) systemd-journald high CPU usage after crash...

#2 2013-12-15 15:44:56

Re: [SOLVED] (ish) systemd-journald high CPU usage after crash...

#3 2013-12-15 16:06:37

Re: [SOLVED] (ish) systemd-journald high CPU usage after crash...

#4 2013-12-20 00:46:25

Re: [SOLVED] (ish) systemd-journald high CPU usage after crash...

#5 2013-12-20 01:55:32

Re: [SOLVED] (ish) systemd-journald high CPU usage after crash...

#6 2013-12-20 02:05:46

Re: [SOLVED] (ish) systemd-journald high CPU usage after crash...

Board footer