[RESOLVED] Cpu usage over 200% on fresh installation of arch

jfab · 2024-02-11 19:09:08

Yesterday I updated my system with pacman -Syu to linux l 6.7.4 and the computer became very slow. Powertop was showing some acpi interrumpt process using a lot of CPU (like here https://ibb.co/Ct2X7s7, almost 200% cpu usage with almost no processes running) and journalctl had a lot of ACPI errors.

I tried to search everywhere for this error and got tired. I wiped my computer and re installed from scratch (with the arch install script). To my surprise the issue persists on a fresh install of arch. I am now running Manjaro and the issue is gone.

This issue is wm/de dependent as I tried to install arch multiple ways with different de/wm and it didn't work either. This issue was even present in the tty and without installing too much packages after a fresh install.

I tried adding the kernel parameters "pci=nommconf" and "acpi=off" with no success, and in that case my computer didn't even boot. I also tried booting with linux-lts with no luck.

My laptop is a VivoBook_ASUSLaptop E406NA_L406NA 1.0.

Images of powertop, neofetch and journalctl errros are here:

Journalctl:
https://ibb.co/5B9NnB4

Powertop:
https://ibb.co/S7k5Psc

Neofetch (I'm in Manjaro now):
https://ibb.co/MZLB9D4

Last edited by jfab (2024-04-08 22:19:00)

seth · 2024-02-11 20:55:10

Don't post photos of the text on your monitor, post the text.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

jfab · 2024-02-12 00:58:51

As I said I installed Manjaro since the computer with arch is VERY slow. Even running commands on the terminal is slow, that is why I didn't upload the text.

seth · 2024-02-12 08:57:19

Then this here is completely pointless - it's impossible to give you meaningful advice based solely on https://i.ibb.co/yWRwYWP/journalctl.webp
You could test the LTS kernel (because manjaro likely defaults to that) but that's just a guess and no matter what: you'll have to produce meaningful data from the problematic system.

jfab · 2024-02-13 14:32:47

Ok, I reinstalled arch and got the same error. Here is journalctl -b: https://0x0.st/HdwG.txt

Powertop still outputs 200%+ cpu usage. Most intense processes are systemd-journal and acpi

Last edited by jfab (2024-02-13 14:33:44)

seth · 2024-02-13 14:47:56

Add

pci=noaer

to the https://wiki.archlinux.org/title/Kernel_parameters
The journal actually isn't complete and barely contains anything but the insane amount of ACPI error

journald sucks at burst handling, that's what's most likely driving your CPU - we'll still need the actual head of a journal, preferably from a run w/o noaer but maybe it's possible to spot the problem despite.

jfab · 2024-02-13 18:32:17

I added the kernel parameter and journalctl outputs the same things

seth · 2024-02-13 19:59:45

We'll still need a full journal - did you try to boot the LTS kernel?
You could also boot "noacpi", but that will prevent a couple of features (proper rebooting) and also not give us any hint about what's causing this.

For google:

Feb 13 08:08:03 jfab kernel: ACPI Error: No handler or method for GPE 0A, disabling event (20230628/evgpe-839)
Feb 13 08:08:03 jfab kernel: ACPI Error: No handler or method for GPE 0B, disabling event (20230628/evgpe-839)
Feb 13 08:08:03 jfab kernel: ACPI Error: No installed handler for fixed event - PM_Timer (0), disabling (20230628/evevent-255)
Feb 13 08:08:03 jfab kernel: ACPI Error: No installed handler for fixed event - PowerButton (2), disabling (20230628/evevent-255)
Feb 13 08:08:03 jfab kernel: ACPI Error: No installed handler for fixed event - SleepButton (3), disabling (20230628/evevent-255)
Feb 13 08:08:03 jfab kernel: ACPI Error: Could not disable RealTimeClock events (20230628/evxfevnt-243)

jfab · 2024-02-13 20:27:08

I added noacpi and booted with the LTS kernel with no luck. Nothing changes and even though the option "noacpi" is added, I still get ACPI errors on journalctl. In powertop, acpi and systemd-journald are still the top processes. An average of 200% CPU use. This is a fresh minimal arch install.

Adding the option pci=nommconf doesnt help either, and it makes the computer not start. I found this advice on https://askubuntu.com/questions/1171355 … -evgpe-835 with a similar issue on ubuntu.

Last edited by jfab (2024-02-13 20:40:05)

seth · 2024-02-13 20:39:54

Sorry "pci=noacpi" or "acpi=off", noacpi is long gone…
You can also try "pci=nommconf"

Last edited by seth (2024-02-13 20:40:47)

jfab · 2024-02-13 20:40:48

I added also acpi=off and still no difference. "pci=nommconf" makes the computer not start.

seth · 2024-02-13 20:43:22

Try "pci=noacpi" and we'll need a complete journal. Not just the tail showing the failure.
In doubt check what parameters manjaro added to the commandline and make sure that you're actually effectively adding those parameters (cat /proc/cmdline)

Oh, and cc: is there a parallel windows installation?

Last edited by seth (2024-02-13 20:44:40)

jfab · 2024-02-13 20:51:43

There is no parallel windows installation, it is a fresh arch install, I wiped all the disk. What do you mean about manjaro adding parameters? I already uninstalled manjaro. How do I upload the complete journal? I wrote "sudo journalctl -b | curl -F 'file=@-' 0x0.st" and the command terminated with that output.

seth · 2024-02-13 21:06:37

Feb 13 08:08:03 jfab systemd-journald[178]: Missed 204956 kernel messages

The acpi might be spamming the journal so fast that you're loosing the entire relevant part…

Does "pnpacpi=off" help?

jfab · 2024-02-13 21:24:13

After adding pnpacpi=off, the computer doesn't respond. (When trying to login, the keyboard and the tty freeze)

seth · 2024-02-13 22:05:06

Do you have a "PNP OS" like BIOS option? Or an external keyboard? Or does it help to also add "i8042.dumbkbd"?
Also do you use any kind of "acpi_osi=" override? (The general kernel commandline would be useful to see)

jfab · 2024-02-15 00:29:06

Here is a photo of the kernel options: https://ibb.co/YQsHWRt

Adding the option i8042.dumbkbd does not help.

jfab · 2024-02-23 02:42:32

Fresh install of arch with linux 6.7.5 does not solve the problem. Other distributions don't have this problem and are installed just fine on my laptop.

seth · 2024-02-23 08:34:26

Do "other distributions" also ship the 6.7 kernel?
How "fresh"? Only kernel and bash?
Do you have the same problem w/ the install iso as well? Or when booting the rescue.target?

Edit:
https://github.com/linux-surface/linux- … 1912755002
It also seems related to the LID switch on that thread.
Do you boot w/ the lid open or closed?

https://bugzilla.redhat.com/show_bug.cgi?id=1329910#c3 has it down to sp5100_tco

module_blacklist=sp5100_tco

And I assume you've seen https://askubuntu.com/questions/1171355 … -evgpe-835

Wrt

I added also acpi=off and still no difference.

This actually strongly suggests that at least at time the kernel parameters were not applied at all, you cannot get acpi errors when the acpi subsystem is deactivated.

Last edited by seth (2024-02-23 09:16:58)

jfab · 2024-02-23 14:16:52

You are right, the other distributions I installed do not ship with
linux 6.7, both void and manjaro come with previous versions.

Completely fresh arch install, minimal installation with the arch
installer, no window manager and just neovim and powertop as additional
packages

I do NOT have the problem in the arch iso.

I boot with the lid open.

I do not how it would be possible that the kernel parameters didn't get applied, I followed https://wiki.archlinux.org/title/Kernel_parameters#GRUB in order to apply them. As for the new options, adding module_blacklist=sp5100_tco didn't help either. systemd-journald appears at the top process in powertop.

Update: adding acpi=off makes arch not boot

Last edited by jfab (2024-02-23 15:00:40)

seth · 2024-02-23 15:27:08

I do NOT have the problem in the arch iso.

Did you install the other distros or try to run them from a usb key?

adding acpi=off makes arch not boot

Not even into the rescue target?

I do not how it would be possible that the kernel parameters didn't get applied

Did you run grub-mkconfig after applying them (though apparently acpi=off does something)

You can check the current kernel w/ "uname -a" and the applied parameters w/ "cat /proc/cmdline"

and powertop as additional packages

Incl. powertop autotune? wrt the TLP hints in one of the linked threads, that sounds suspicious.

seth · 2024-02-23 16:54:42

There's *strong* indication for this being a 6.7 regression: https://bbs.archlinux.org/viewtopic.php?id=293140
Make absolutely sure to have tried the LTS kernel.

jfab · 2024-02-23 17:22:13

With rescue target you mean adding systemd.unit=rescue.target to the kernel params? If so, it doesnt help either.

I dont add the kernel parameters permanently because as I have said the computer doesnt boot on some cases, so I just edit the kernel params from grub directly

Powertop --auto-tune doesn't run, it ends with
"Cannot load from file /var/cache/powertop/saved_parameters.powertop"

I will re install arch once again with the lts kerel

Update: didnt work

Last edited by jfab (2024-02-23 18:06:06)

seth · 2024-02-24 08:06:23

https://bbs.archlinux.org/viewtopic.php … 4#p2152774 suggests is /has/ to be 6.6.14, newer kernels exhibit the same issue.

jfab · 2024-03-07 14:02:27

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 4#p2152774 suggests is /has/ to be 6.6.14, newer kernels exhibit the same issue.

No updates on this issue? I still have the same problem with the newest arch.

Arch Linux

#1 2024-02-11 19:09:08

[RESOLVED] Cpu usage over 200% on fresh installation of arch

#2 2024-02-11 20:55:10

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#3 2024-02-12 00:58:51

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#4 2024-02-12 08:57:19

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#5 2024-02-13 14:32:47

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#6 2024-02-13 14:47:56

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#7 2024-02-13 18:32:17

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#8 2024-02-13 19:59:45

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#9 2024-02-13 20:27:08

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#10 2024-02-13 20:39:54

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#11 2024-02-13 20:40:48

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#12 2024-02-13 20:43:22

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#13 2024-02-13 20:51:43

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#14 2024-02-13 21:06:37

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#15 2024-02-13 21:24:13

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#16 2024-02-13 22:05:06

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#17 2024-02-15 00:29:06

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#18 2024-02-23 02:42:32

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#19 2024-02-23 08:34:26

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#20 2024-02-23 14:16:52

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#21 2024-02-23 15:27:08

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#22 2024-02-23 16:54:42

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#23 2024-02-23 17:22:13

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#24 2024-02-24 08:06:23

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

#25 2024-03-07 14:02:27

Re: [RESOLVED] Cpu usage over 200% on fresh installation of arch

Board footer