Arch Linux

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

systemd-journald 100% CPU

Hi there.

I have a problem that is happenning a lot of times since I installed Arch. When I am using my laptop, suddenly all stops working and CPU goes to 100% usage. IN htop, systemd-journald is consuming 100% CPU resources and when I use journalctl -b I get like millions of lines spamming this messages:

Jul 13 10: 18: 58 masarch kernel:  syscopyarea cfg80211 intel_rapl_perf snd sysfillrect usbhid mei_me tpm_crb psmouse input_leds pcspkr tpm_tis i2c_i801 soundcore sysimgblt rfkill mei fb_sys_fops hid hp_wireless tpm_tis_core battery tpm ac evdev wmi mac_hid rng_core drm agpgart ip_tables x_tables ext4 crc32c_gene >
Jul 13 10: 18: 58 masarch kernel: CPU: 0 PID: 274 Comm: kworker/0: 3 Tainted: G        W         5.7.7-arch1-1  # 1
Jul 13 10: 18: 58 masarch systemd-journald[210]: Missed 43 kernel messages

What can I do? How could I resolve that problem? I have searched for similar issues but no solution has worked for me.

loqs

Member

Registered: 2014-03-06

Posts: 18,928

Re: systemd-journald 100% CPU

The actual error is not present in the output you posted.  See General_troubleshooting#Kernel_panics for comparison.  Please use code tags for commands and their outputs.

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Re: systemd-journald 100% CPU

The actual error is not present in the output you posted.  See General_troubleshooting#Kernel_panics for comparison.  Please use code tags for commands and their outputs.

Okay, sorry.
So, how can I boot with this parameter?

systemd.journald.forward_to_console=1 console=tty1

loqs

Member

Registered: 2014-03-06

Posts: 18,928

Re: systemd-journald 100% CPU

See Kernel_parameters,  if the error is not producing a kernel panic then it will be recorded in the journal provided the number of messages does not exceed rate limiting.
Edit:
If you check backwards in the journal to the first time the error was recorded for a boot there should be more output before any rate limiting was triggered.

Last edited by loqs (2020-07-13 12:50:48)

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Re: systemd-journald 100% CPU

See Kernel_parameters,  if the error is not producing a kernel panic then it will be recorded in the journal provided the number of messages does not exceed rate limiting.
Edit:
If you check backwards in the journal to the first time the error was recorded for a boot there should be more output before any rate limiting was triggered.

Thank you!

Using journalctl -b at reboot after error occurs, I have the following errors, but I don´t know if they can be the source of the problem:

-- Logs begin at Mon 2020-07-13 12:32:21 CEST, end at Mon 2020-07-13 12:56:47 CEST. --
Jul 13 12:56:16 masarch kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Jul 13 12:56:16 masarch kernel:  #3
Jul 13 12:56:16 masarch kernel: pmd_set_huge: Cannot satisfy [mem 0xe0000000-0xe0200000] with a huge-page mapping due to MTRR override.
Jul 13 12:56:16 masarch kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 13 12:56:16 masarch kernel: platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
Jul 13 12:56:16 masarch kernel: acpi MSFT0101:00: platform device creation failed: -16
Jul 13 12:56:16 masarch kernel: ata1.00: supports DRM functions and may not be fully accessible
Jul 13 12:56:16 masarch kernel: ata1.00: supports DRM functions and may not be fully accessible
Jul 13 12:56:16 masarch kernel: usb: port power management may be unreliable
Jul 13 12:56:16 masarch systemd-journald[221]: Journal started
Jul 13 12:56:16 masarch systemd-journald[221]: Runtime Journal (/run/log/journal/32064d8bb17746ea9937e212bcde8e34) is 6.2M, max 50.0M, 43.7M free.
Jul 13 12:56:16 masarch systemd-journald[221]: Time spent on flushing to /var/log/journal/32064d8bb17746ea9937e212bcde8e34 is 955us for 11 entries.
Jul 13 12:56:16 masarch systemd-journald[221]: System Journal (/var/log/journal/32064d8bb17746ea9937e212bcde8e34) is 50.0M, max 50.0M, 0B free.
Jul 13 12:56:16 masarch kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Jul 13 12:56:16 masarch kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Jul 13 12:56:16 masarch kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Jul 13 12:56:16 masarch kernel: wmi_bus wmi_bus-PNP0C14:00: WQ data block query control method not found
Jul 13 12:56:16 masarch kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:02)
Jul 13 12:56:16 masarch kernel: tpm_crb MSFT0101:00: [Firmware Bug]: Bad ACPI memory layout
Jul 13 12:56:16 masarch kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Jul 13 12:56:16 masarch kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized!
Jul 13 12:56:16 masarch kernel: uvcvideo 1-5:1.0: Entity type for entity Extension 3 was not initialized!
Jul 13 12:56:16 masarch kernel: uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized!
Jul 13 12:56:16 masarch kernel: uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized!
Jul 13 12:56:16 masarch kernel: iwlwifi 0000:02:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
Jul 13 12:56:17 masarch kernel: thermal thermal_zone3: failed to read out thermal zone (-61)
Jul 13 12:56:18 masarch kernel: iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
Jul 13 12:56:18 masarch kernel: [Firmware Bug]: ACPI(PXSX) defines _DOD but not _DOS
Jul 13 12:56:18 masarch kernel: iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
Jul 13 12:56:18 masarch NetworkManager[338]: <warn>  [1594637778.4235] sup-iface[f6373fbaa94e3f32,0,wlp2s0]: call-p2p-cancel: failed with P2P cancel failed
Jul 13 12:56:18 masarch systemd-udevd[243]: controlC0: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
Jul 13 12:56:22 masarch kernel: kauditd_printk_skb: 21 callbacks suppressed
Jul 13 12:56:26 masarch ntpd[351]: bind(23) AF_INET6 fe80::545b:7347:513e:ccdc%2#123 flags 0x11 failed: Cannot assign requested address
Jul 13 12:56:26 masarch ntpd[351]: unable to create socket on wlp2s0 (4) for fe80::545b:7347:513e:ccdc%2#123
Jul 13 12:56:47 masarch kernel: kauditd_printk_skb: 13 callbacks suppressed.

loqs

Member

Registered: 2014-03-06

Posts: 18,928

Re: systemd-journald 100% CPU

Please post the output of `journalctl -b` with the issue to a pastebin.

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Re: systemd-journald 100% CPU

Please post the output of `journalctl -b` with the issue to a pastebin.

The same that I have posted in my last message?

loqs

Member

Registered: 2014-03-06

Posts: 18,928

Re: systemd-journald 100% CPU

I expected the output you posted was from

journalctl -p4 -b

i.e. it was filtering to show only messages with priority of warning or above for the current boot.  I wanted all messages for the current boot,  provided it had the issue.

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Re: systemd-journald 100% CPU

I expected the output you posted was from

journalctl -p4 -b

i.e. it was filtering to show only messages with priority of warning or above for the current boot.  I wanted all messages for the current boot,  provided it had the issue.

Here it is https://hastebin.com/ayolohocuc.coffeescript

loqs

Member

Registered: 2014-03-06

Posts: 18,928

Re: systemd-journald 100% CPU

The journal posted was for a boot without the issue.

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Re: systemd-journald 100% CPU

The journal posted was for a boot without the issue.

How can I search for a boot with the error?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,044

Re: systemd-journald 100% CPU

Since you already know a time when this happened (OP), compare

journalctl --list-boots

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

M4RC0Sx

Member

Registered: 2020-06-29

Posts: 13

Re: systemd-journald 100% CPU

Since you already know a time when this happened (OP), compare

journalctl --list-boots

Looks like I will have to wait until the error appears again because when I watch the entire journal of the error boot, there are only missed kernel messages.