Rsyslog using on average 27% of my cpu

Ask Fedora
1

I recently set up fedora server 41 to be a media server on a pretty old CPU and motherboard I had around. I noticed that rsyslogd is using about 27% of my CPU on average. It’s not causing any actual issues as I’m not using it for anything too CPU intensive, but logging using a quarter of my CPU made it seem like something was wrong. I ran journalctl -f and it looks like there a lot of the same 3 error messages, shown below, coming in.

I followed instructions from the link in this post, but I’m still having the issue. I’m not sure that the workaround in the link was actually applied.

Here are the logs that are being repeated.

ACPI BIOS Error (bug): Could not resolve symbol [\_GPE._L6F.PGRT], AE_NOT_FOUND (20240827/psargs-
ACPI Error: Aborting method \_GPE._L6F due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
ACPI Error: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20240827/evgpe-511)

Can anyone help me figure out the issue? Thanks for your help!

2

Read this https://www.linux.org/threads/kworker-0-1-kacpid-shows-83-cpu-usage.39623/page-2 suggests adding acpi_mask_gpe=0x6F to the kernel command line might stop the reports.

And this was also suggested to jave the sane effect

echo "disable" > /sys/firmware/acpi/interrupts/gpe6F

But would not stop the reports until you run that command.

Also if you do not use the legacy style log files in /var/log then just dnf remove rsyslog and use journalctl exclusively. Which is what I have done on all my fedora server installs.

1 Like
3

I tried using this and it looks like it stopped the logs, but after rebooting the same log kept coming. Do I need to run this every time I restart? Is there a way to make this persist between reboots if so? Thanks for your help.

4

Yes, the line you wrote will be forgotten after each reboot.

For a permanent solution, please add the respective statement to the kernel command line as stated by Barry above, which will make the solution persistent.

1 Like
5

Thank you Barry and Christian for the help, I’ve got it all working perfectly now. I added the acpi_mask_gpe=0x6F to the wrong spot the first time.

For anyone in the future, to make this persist across reboots add GRUB_CMDLINE_LINUX_DEFAULT="acpi_mask_gpe=0x6F" to /etc/default/grub/ and then run sudo grub2-mkconfig -o /boot/grub2/grub.cfg and then reboot.

6

FYI it is simpler to use grubby command’s add arg feature.
Also it is not necessary to use grub2-mkconfig.

1 Like
7

Ahh cool thanks. I didn’t know that was a thing. Still relatively new to Linux. I’ll definitely make sure to use it next time I have to fiddle with things.