kworker/0:1+kacpid shows 83% CPU usage.

Condobloke

Well-Known Member
Joined
Apr 30, 2017
Messages
8,180
Reaction score
6,656
Credits
54,576
brian@brian-desktop:~$ ps axch -o cmd,%cpu --sort=-%cpu | head
kworker/0:1+kacpid 83.0
systemd-journal 6.6
brave 6.5
brave 4.8
gnome-terminal- 4.4
brave 2.2
vlc 2.1
brave 1.9
Xorg 1.4
cinnamon 1.3
brian@brian-desktop:~$

---------------------------------------------------------------------
sudo journalctl -b0 -g acpi
[sudo] password for brian:
-- Logs begin at Thu 2022-03-17 12:47:59 AEDT, end at Thu 2022-03-17 12:48:55 A>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F du>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluatin>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F du>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluatin>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F du>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluatin>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F du>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluatin>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F du>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluatin>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F du>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluatin>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F du>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluatin>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F du>
lines 1-23

-- Logs begin at Thu 2022-03-17 12:47:59 AEDT, end at Thu 2022-03-17 12:48:55 AE>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve s>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve s>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve s>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve s>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve s>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve s>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating>
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve s>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due>
lines 1-23

-- Logs begin at Thu 2022-03-17 12:47:59 AEDT, end at Thu 2022-03-17 12:48:55 AED>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating >
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve sy>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating >
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve sy>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating >
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve sy>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating >
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve sy>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating >
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve sy>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating >
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve sy>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due >
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: AE_NOT_FOUND, while evaluating >
Mar 17 12:47:59 brian-desktop kernel: ACPI BIOS Error (bug): Could not resolve sy>
Mar 17 12:47:59 brian-desktop kernel: ACPI Error: Aborting method \_GPE._L6F due >
lines 1-23

and on and on and on......
 


Your kernel worker appears to be working needlessly reporting the ACPI error. Here's an output from one of my machines with lots of ACPI working normally without error and with computer's moderate use:
Code:
[tom@owl ~]$ ps axch -o cmd,%cpu --sort=-%cpu | head
firefox-esr                  9.5
Web Content                  3.2
Web Content                  2.7
Xorg                         1.5
pulseaudio                   1.0
Web Content                  0.9
Web Content                  0.6
Web Content                  0.5
dwm                          0.3
WebExtensions                0.1

And here is kworker output:
Code:
[tom@owl ~]$ ps aux |grep -i -e mem -e kworker
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root           6  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/0:0H-events_highpri]
root          21  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/1:0H-events_highpri]
root          26  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/2:0H-events_highpri]
root          31  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/3:0H-events_highpri]
root          52  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/0:1H-kblockd]
root          61  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/1:1H-kblockd]
root          78  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/u9:0]
root         118  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/3:1H-kblockd]
root         138  0.0  0.0      0     0 ?        I<   10:32   0:00 [kworker/2:1H-kblockd]
root        5258  0.0  0.0      0     0 ?        I    12:38   0:00 [kworker/u8:4-events_unbound]
root        6871  0.1  0.0      0     0 ?        I    13:28   0:02 [kworker/2:0-events_power_efficient]
root        7341  0.1  0.0      0     0 ?        I    13:40   0:01 [kworker/0:0-events]
root        7347  0.0  0.0      0     0 ?        I    13:40   0:01 [kworker/3:2-events]
root        7365  0.0  0.0      0     0 ?        I    13:41   0:00 [kworker/1:2-events]
root        7411  0.0  0.0      0     0 ?        I    13:41   0:00 [kworker/u8:2-events_unbound]
root        7501  0.0  0.0      0     0 ?        I    13:42   0:00 [kworker/2:1-events]
root        7713  0.0  0.0      0     0 ?        I    13:48   0:00 [kworker/3:1-events]
root        7715  0.0  0.0      0     0 ?        I    13:48   0:00 [kworker/0:2-events]
root        7849  0.0  0.0      0     0 ?        I    13:51   0:00 [kworker/1:0-events]
root        8000  0.0  0.0      0     0 ?        I    13:56   0:00 [kworker/1:1-events]
root        8039  0.0  0.0      0     0 ?        I    13:58   0:00 [kworker/u8:0-events_unbound]
tom         8099  0.0  0.0   6288  2248 pts/4    S+   14:01   0:00 grep --color=auto -i -e mem -e kworker

That ACPI messaging, apart from the effect of kworker's reporting, may not actually be affecting much of the actual power handling of the computer if it shows no symptoms. ACPI is not telling you that it's in conflict with anything. Rather, it looks like it's a repeat of just one issue. I recall such ACPI messages which I've never followed up because no functioning seemed to be impaired, but it may be different in your case. I guess that kworker is faithfully reporting the ACPI error, (like in a loop) but it has no capacity to stop or respond more economically to the seemingly unnecessary repetition. It looks like it's generating so much cruft that the CPU is working needlessly. I imagine what vlc does is a lot more kernel work normally than printing a log entry, but the degree of that kworker output may be the telling factor. In the past, it's a kernel upgrade that has resolved this sort of thing in my case.
 
Last edited by a moderator:
g'day Ben, the workload on this pc is probably average as well. Simple browsing, a few tv shows, linux.org....not exactly high load.

The kernel is the latest 5.13.0-35 (running that now)

I also run 5.4.0-104 from time to time, because I notice an uptick in performance each time I change !
 
I have just chganged kernel to 5.4.0-104

the results are:
brian@brian-desktop:~$ ps axch -o cmd,%cpu --sort=-%cpu | head
brave 18.0
thunderbird 8.4
brave 6.7
Xorg 5.5
brave 4.6
cinnamon 4.1
gnome-terminal- 1.1
brave 0.7
brave 0.6
brave 0.5
brian@brian-desktop:~$
-------------------------------------------------------------------

brian@brian-desktop:~$ grep . -r /sys/firmware/acpi/interrupts/
/sys/firmware/acpi/interrupts/gpe2F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe23: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe51: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe13: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe41: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe03: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe31: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe21: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe78: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe11: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe68: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe01: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe58: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled unmasked
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 STS invalid unmasked
/sys/firmware/acpi/interrupts/gpe48: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe76: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe38: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe66: 5 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe28: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe56: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe18: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe46: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe74: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe08: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe36: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe64: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe26: 0 invalid unmasked
/sys/firmware/acpi/interrupts/error: 0
/sys/firmware/acpi/interrupts/gpe54: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe16: 0 invalid unmasked
/sys/firmware/acpi/interrupts/sci: 5
/sys/firmware/acpi/interrupts/gpe44: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe72: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe06: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe34: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe62: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe24: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe52: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe14: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe42: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe70: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe04: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe32: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe60: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe22: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe50: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe79: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe12: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe40: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe69: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe02: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe30: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe59: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe20: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe49: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe77: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe10: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe39: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe67: 0 enabled unmasked
/sys/firmware/acpi/interrupts/gpe00: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe_all: 5
/sys/firmware/acpi/interrupts/gpe29: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe57: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe19: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe47: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe75: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe09: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe37: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe65: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe27: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe55: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe17: 0 disabled unmasked
/sys/firmware/acpi/interrupts/gpe45: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe73: 0 invalid unmasked
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe07: 0 invalid unmasked
/sys/firmware/acpi/interrupts/sci_not: 0
/sys/firmware/acpi/interrupts/gpe35: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6F: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe63: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe25: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe53: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe15: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe43: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe71: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe05: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe33: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6D: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe61: 0 EN enabled unmasked
brian@brian-desktop:~$ grep . -r /sys/firmware/acpi/interrupts/
/sys/firmware/acpi/interrupts/gpe2F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe23: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe51: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe13: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe41: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe03: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe31: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe21: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe78: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe11: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe68: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe01: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe58: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled unmasked
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 STS invalid unmasked
/sys/firmware/acpi/interrupts/gpe48: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe76: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe38: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0B: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe66: 5 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe28: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe56: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe18: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe46: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe74: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe08: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe36: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe64: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe26: 0 invalid unmasked
/sys/firmware/acpi/interrupts/error: 0
/sys/firmware/acpi/interrupts/gpe54: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe16: 0 invalid unmasked
/sys/firmware/acpi/interrupts/sci: 5
/sys/firmware/acpi/interrupts/gpe44: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe72: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe06: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe34: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe62: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe24: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe52: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe14: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe42: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe70: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe04: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe32: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe60: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe22: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe50: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe79: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe12: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe40: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe69: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe02: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe30: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe59: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe20: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe49: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe77: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe10: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe39: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe67: 0 enabled unmasked
/sys/firmware/acpi/interrupts/gpe00: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe_all: 5
/sys/firmware/acpi/interrupts/gpe29: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe57: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe2A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe19: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe47: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe75: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe09: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe37: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe0A: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe65: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe27: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe55: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe17: 0 disabled unmasked
/sys/firmware/acpi/interrupts/gpe45: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe73: 0 invalid unmasked
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe07: 0 invalid unmasked
/sys/firmware/acpi/interrupts/sci_not: 0
/sys/firmware/acpi/interrupts/gpe35: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6F: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/gpe63: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe25: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe5F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe53: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe15: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe4F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe43: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe7D: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe71: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe05: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe3F: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe33: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe6D: 0 EN enabled unmasked
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid unmasked
/sys/firmware/acpi/interrupts/gpe61: 0 EN enabled unmasked
brian@brian-desktop:~$ ps axch -o cmd,%cpu --sort=-%cpu | head
 
and kworker

brian@brian-desktop:~$ ps aux |grep -i -e mem -e kworker
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 6 0.0 0.0 0 0 ? I< 14:59 0:00 [kworker/0:0H-kblockd]
root 20 0.0 0.0 0 0 ? I< 14:59 0:00 [kworker/1:0H-kblockd]
root 107 0.0 0.0 0 0 ? I< 14:59 0:00 [kworker/u5:0]
root 166 0.1 0.0 0 0 ? I 14:59 0:00 [kworker/0:3-events]
root 188 0.0 0.0 0 0 ? I 14:59 0:00 [kworker/1:2-events]
root 190 0.0 0.0 0 0 ? I< 14:59 0:00 [kworker/1:1H]
root 191 0.0 0.0 0 0 ? I 14:59 0:00 [kworker/u4:3-events_unbound]
root 194 0.1 0.0 0 0 ? D 14:59 0:00 [kworker/u4:4+events_unbound]
root 207 0.0 0.0 0 0 ? I 14:59 0:00 [kworker/u4:5-i915]
root 210 0.0 0.0 0 0 ? D 14:59 0:00 [kworker/u4:8+events_unbound]
root 217 0.0 0.0 0 0 ? I< 14:59 0:00 [kworker/0:1H-events_highpri]
root 365 0.0 0.0 0 0 ? I 15:00 0:00 [kworker/1:4-events]
root 1317 0.2 0.0 0 0 ? I 15:00 0:01 [kworker/0:7-events]
root 3948 0.0 0.0 0 0 ? I 15:06 0:00 [kworker/u4:0-i915]
root 3955 0.0 0.0 0 0 ? I 15:07 0:00 [kworker/0:0-events]
root 3967 0.0 0.0 0 0 ? I 15:07 0:00 [kworker/0:1-events]
root 4058 0.0 0.0 0 0 ? I 15:07 0:00 [kworker/1:0-events]
root 4059 0.0 0.0 0 0 ? I 15:07 0:00 [kworker/1:1-events]
root 4060 0.0 0.0 0 0 ? I 15:07 0:00 [kworker/1:3]
brian 4157 0.0 0.0 8904 652 pts/0 S+ 15:10 0:00 grep --color=auto -i -e mem -e kworker
brian@brian-desktop:~$
 
G'day Brian ... (couldn't resist your greeting :)) I'm running 5.16.0-4-amd64 kernels in most of my machines. They range from 2 to 6 years old with a laptop about a year old. I haven't had any issues, which is not to say that this kernel mightn't have issues on other machines. It's firmware and hardware that's involved.

Your brian-desktop machine looks quite normal with those particular programs running and kworker is not working too hard in the ps output.

If the kernel was showing excessive kworker output of gpe messages (which used to be called a "gpe storm") there's suggestions online about both scripts and kernel parameters to control it. I've never used any scripts. I have used the kernel option: acpi=off, but that may not be appropriate in all cases.
 
I could take a Timeshift snapshot now..... run whatever the command is to " acpi=off".......see what that brings about....and if dramas happen...Restore the Timeshift snapshot ?

Does that even sound feasible ?

What dramas are likely to ensue?....why is acpi off, not appropriate?

This pc is around 2013 vintage...motherboard is original....only update is nvme (m.2) card. 16GB ram
 
Turning acpi off in a desktop will likely have much fewer consequences than in a laptop which has power management controlling sleeping, battery and temperature among other things. I've never turned it off on a laptop ... that's where is not so appropriate. With a desktop it's easy to try and easy to restore through adding the kernel option after hitting "e" at the grub menu which will give you access to the linux command line. When you add the "acpi=off" to the linux line, boot up by hitting cntrl+x, you will get rid of acpi power management issues but in modern desktops you might get reduced resolution because of the power demands of video cards, and the temperature sensoring probably won't work, but the machine should still work quite properly in its fundamentals with networking and the usual programs. There may be other issues which I'm just not familiar with. The main reason for using that kernel option to get rid of intractable acpi issues rather than it be used as normal practice. Anyway, having added the kernel option to the linux line from grub, it will only apply for that boot and the next boot up will return to the normal boot up from before that option was applied.
 
The result of : sudo journalctl -b0 -g acpi

is repeated from the start at 16:49, until 16:52.

I have only included the first and last.....there were far too many for the site to show

Temp sensor still responds.
1647497874188.png






root@brian-desktop:/home/brian# sudo journalctl -b0 -g acpi
-- Logs begin at Thu 2022-03-17 16:49:15 AEDT, end at Thu 2022-03-17 16:52:07 A>
Mar 17 16:49:15 brian-desktop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.>
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000005fc33000-0x0000>
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000007ebab000-0x0000>
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000007f39a000-0x0000>
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000005fc330>
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000007ebab0>
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000007f39a0>
Mar 17 16:49:15 brian-desktop kernel: efi: ACPI=0x7f331000 ACPI 2.0=0x7f33100>
Mar 17 16:49:15 brian-desktop kernel: Kernel command line: BOOT_IMAGE=/boot/vml>
Mar 17 16:49:15 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x5f>
Mar 17 16:49:15 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x7e>
Mar 17 16:49:15 brian-desktop kernel: ACPI: Interpreter disabled.
Mar 17 16:49:15 brian-desktop kernel: pnp: PnP ACPI: disabled
Mar 17 16:49:15 brian-desktop kernel: ACPI: <n/a>: failed to evaluate _DSM (0x1>
Mar 17 16:49:15 brian-desktop systemd[1]: Started ACPI Events Check.
Mar 17 16:49:15 brian-desktop systemd[1]: Listening on ACPID Listen Socket.
Mar 17 16:49:15 brian-desktop systemd[1]: Started ACPI event daemon.
Mar 17 16:52:07 brian-desktop sudo[3604]: root : TTY=pts/0 ; PWD=/home/bria>
lines 1-19/19 (-- Logs begin at Thu 2022-03-17 16:49:15 AEDT, end at Thu 2022-03-17 16:52:07 AE>
Mar 17 16:49:15 brian-desktop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4>
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000005fc33000-0x00000>
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000007ebab000-0x00000>
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000007f39a000-0x00000>
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000005fc3300>
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000007ebab00>
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000007f39a00>
Mar 17 16:49:15 brian-desktop kernel: efi: ACPI=0x7f331000 ACPI 2.0=0x7f331000>
Mar 17 16:49:1




-- Logs begin at Thu 2022-03-17 16:49:15 AEDT, end at Thu 2022-03-17 16:52:07 AEDT. --
Mar 17 16:49:15 brian-desktop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic root=UUID=5c8cbdbd-b1bd-458e-a8ef-335b9442d8c7 ro quiet splash acpi=off
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000005fc33000-0x000000005fc33fff] ACPI NVS
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000007ebab000-0x000000007f399fff] ACPI NVS
Mar 17 16:49:15 brian-desktop kernel: BIOS-e820: [mem 0x000000007f39a000-0x000000007f3fefff] ACPI data
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000005fc33000-0x000000005fc33fff] ACPI NVS
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000007ebab000-0x000000007f399fff] ACPI NVS
Mar 17 16:49:15 brian-desktop kernel: reserve setup_data: [mem 0x000000007f39a000-0x000000007f3fefff] ACPI data
Mar 17 16:49:15 brian-desktop kernel: efi: ACPI=0x7f331000 ACPI 2.0=0x7f331000 SMBIOS=0xf05e0 MPS=0xfc410 MOKvar=0x7bc87000
Mar 17 16:49:15 brian-desktop kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic root=UUID=5c8cbdbd-b1bd-458e-a8ef-335b9442d8c7 ro quiet splash acpi=off
Mar 17 16:49:15 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x5fc33000-0x5fc33fff] (4096 bytes)
Mar 17 16:49:15 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x7ebab000-0x7f399fff] (8318976 bytes)
Mar 17 16:49:15 brian-desktop kernel: ACPI: Interpreter disabled.
Mar 17 16:49:15 brian-desktop kernel: pnp: PnP ACPI: disabled
Mar 17 16:49:15 brian-desktop kernel: ACPI: <n/a>: failed to evaluate _DSM (0x1001)
Mar 17 16:49:15 brian-desktop systemd[1]: Started ACPI Events Check.
Mar 17 16:49:15 brian-desktop systemd[1]: Listening on ACPID Listen Socket.
Mar 17 16:49:15 brian-desktop systemd[1]: Started ACPI event daemon.
Mar 17 16:52:07 brian-desktop sudo[3604]: root : TTY=pts/0 ; PWD=/home/brian ; USER=root ; COMMAND=/usr/bin/journalctl -b0 -g acpi
~
~
~
~
lines 1-19/19 (END)


I am tempted to put it in place permanently

  • sudo nano /etc/default/grub
  • Change line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"
  • Ctrl-X, press Y and then Enter to save and exit.
  • sudo update-grub
  • Reboot
 
Thanks for those results. The "poweroff" command may be affected which may necessitate using the physical power button. Good to know about the sensors. With these issues I sort of always hope the new kernels resolve things so I tend to upgrade them quite regularly.
 
Testing power off now
 
You were quite right...power off is affected...

However ....just a slight tap on the physical power button sees it on its way

I will make the change permanent, and learn to live with it.
 
Done.

Thanks for your help, Ben

Much Appreciated.
 
I spoke too soon

I closed the pc down after the post above, and it shutdown completely all of its own accord....no physical power button necessary

I have just booted back up again , and the acpi error/kworker etc is back to 86.8%

I reworked the permanent fix....

  • sudo nano /etc/default/grub
  • Change line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"
  • Ctrl-X, press Y and then Enter to save and exit.
  • sudo update-grub
  • Reboot
It does not survive a shut down and power back up

brian@brian-desktop:~$ ps axch -o cmd,%cpu --sort=-%cpu | head
kworker/0:0-rcu_gp 74.0
kworker/0:1+kacpid 34.1
systemd-journal 5.0
brave 3.2
thunderbird 3.0
cinnamon 1.8
Xorg 1.7
brave 1.5
brave 1.4
kworker/0:3-events 0.7
brian@brian-desktop:~$
----------------------------------------------------

brian@brian-desktop:~$ ps axch -o cmd,%cpu --sort=-%cpu | head
kworker/0:0-rcu_gp 62.4
kworker/0:1+kacpid 50.5
systemd-journal 5.0
brave 3.4
thunderbird 2.7
Xorg 1.7
cinnamon 1.7
brave 1.6
brave 1.3
kworker/0:3-events 0.6
brian@brian-desktop:~$

--------------------------------------------------------

GRUB_DEFAULT="0"
#GRUB_TIMEOUT_STYLE="hidden"
GRUB_TIMEOUT="3"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off"
GRUB_CMDLINE_LINUX=""
-------------------------------------------------------------

silly question.....should the acpi be in Capitals...ACPI ?
 
It needn't be in caps.

If you don't mind some interjection, I'd try adding 'noapic' to that as well.

It should also be noted that these should be temporary settings, used only long enough for the problem to be resolved upstream. Power management will be among the things affected by adding these two kernel parameters.
 
really weird.

I actually typed into etc/default/grub...noacpi.....thinking you had just made a typo.

I then rebooted.

pc would not shut down...stopped at the mint logo....so I held the power button until it died

Restarted.
brian@brian-desktop:~$ ps axch -o cmd,%cpu --sort=-%cpu | head
thunderbird 21.7
brave 12.4
cinnamon 7.6
brave 5.5
gnome-terminal- 5.0
brave 4.8
Xorg 3.9
brave 3.0
brave 2.8
brave 2.7
brian@brian-desktop:~$

rebooted again...same htingie with power button etc...same result at terminal

I then ran : sudo journalctl -b0 -g acpi

and got:
brian@brian-desktop:~$ sudo journalctl -b0 -g acpi
[sudo] password for brian:
-- Logs begin at Fri 2022-03-18 05:34:18 AEDT, end at Fri 2022-03-18 05:39:42 A>
Mar 18 05:34:18 brian-desktop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.>
Mar 18 05:34:18 brian-desktop kernel: BIOS-e820: [mem 0x000000005fc33000-0x0000>
Mar 18 05:34:18 brian-desktop kernel: BIOS-e820: [mem 0x000000007ebab000-0x0000>
Mar 18 05:34:18 brian-desktop kernel: BIOS-e820: [mem 0x000000007f39a000-0x0000>
Mar 18 05:34:18 brian-desktop kernel: reserve setup_data: [mem 0x000000005fc330>
Mar 18 05:34:18 brian-desktop kernel: reserve setup_data: [mem 0x000000007ebab0>
Mar 18 05:34:18 brian-desktop kernel: reserve setup_data: [mem 0x000000007f39a0>
Mar 18 05:34:18 brian-desktop kernel: efi: ACPI=0x7f331000 ACPI 2.0=0x7f33100>
Mar 18 05:34:18 brian-desktop kernel: Kernel command line: BOOT_IMAGE=/boot/vml>
Mar 18 05:34:18 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x5f>
Mar 18 05:34:18 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x7e>
Mar 18 05:34:18 brian-desktop kernel: ACPI: Interpreter disabled.
Mar 18 05:34:18 brian-desktop kernel: pnp: PnP ACPI: disabled
Mar 18 05:34:18 brian-desktop kernel: ACPI: <n/a>: failed to evaluate _DSM (0x1>
Mar 18 05:34:18 brian-desktop systemd[1]: Started ACPI Events Check.
Mar 18 05:34:18 brian-desktop systemd[1]: Listening on ACPID Listen Socket.
Mar 18 05:34:18 brian-desktop systemd[1]: Started ACPI event daemon.
Mar 18 05:39:42 brian-desktop sudo[3911]: brian : TTY=pts/0 ; PWD=/home/bria>
lines 1-19/19 (END)

the above is repeated many times.

Gonna shut down and restart again.
 
restarted. Had to use power button to completely shut down
ps axch -o cmd,%cpu --sort=-%cpu | head

brian@brian-desktop:~$ ps axch -o cmd,%cpu --sort=-%cpu | head
thunderbird 34.3
cinnamon 7.5
gnome-terminal- 4.6
Xorg 4.2
nemo-desktop 2.2
Web Content 1.1
Web Content 0.7
systemd 0.6
mintUpdate 0.5
systemd-udevd 0.3
brian@brian-desktop:~$

brian@brian-desktop:~$ sudo journalctl -b0 -g acpi
[sudo] password for brian:
-- Logs begin at Fri 2022-03-18 05:44:58 AEDT, end at Fri 2022-03-18 05:48:30 A>
Mar 18 05:44:58 brian-desktop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.>
Mar 18 05:44:58 brian-desktop kernel: BIOS-e820: [mem 0x000000005fc33000-0x0000>
Mar 18 05:44:58 brian-desktop kernel: BIOS-e820: [mem 0x000000007ebab000-0x0000>
Mar 18 05:44:58 brian-desktop kernel: BIOS-e820: [mem 0x000000007f39a000-0x0000>
Mar 18 05:44:58 brian-desktop kernel: reserve setup_data: [mem 0x000000005fc330>
Mar 18 05:44:58 brian-desktop kernel: reserve setup_data: [mem 0x000000007ebab0>
Mar 18 05:44:58 brian-desktop kernel: reserve setup_data: [mem 0x000000007f39a0>
Mar 18 05:44:58 brian-desktop kernel: efi: ACPI=0x7f331000 ACPI 2.0=0x7f33100>
Mar 18 05:44:58 brian-desktop kernel: Kernel command line: BOOT_IMAGE=/boot/vml>
Mar 18 05:44:58 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x5f>
Mar 18 05:44:58 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x7e>
Mar 18 05:44:58 brian-desktop kernel: ACPI: Interpreter disabled.
Mar 18 05:44:58 brian-desktop kernel: pnp: PnP ACPI: disabled
Mar 18 05:44:58 brian-desktop kernel: ACPI: <n/a>: failed to evaluate _DSM (0x1>
Mar 18 05:44:59 brian-desktop systemd[1]: Started ACPI Events Check.
Mar 18 05:44:59 brian-desktop systemd[1]: Listening on ACPID Listen Socket.
Mar 18 05:44:59 brian-desktop systemd[1]: Started ACPI event daemon.
Mar 18 05:48:30 brian-desktop sudo[3909]: brian : TTY=pts/0 ; PWD=/home/brian

First one ^^^^


-- Logs begin at Fri 2022-03-18 05:44:58 AEDT, end at Fri 2022-03-18 05:48:30 AEDT. --
Mar 18 05:44:58 brian-desktop kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic root=UUID=5c8cbdbd-b1bd-458e-a8ef-335b9442d8c7 r>
Mar 18 05:44:58 brian-desktop kernel: BIOS-e820: [mem 0x000000005fc33000-0x000000005fc33fff] ACPI NVS
Mar 18 05:44:58 brian-desktop kernel: BIOS-e820: [mem 0x000000007ebab000-0x000000007f399fff] ACPI NVS
Mar 18 05:44:58 brian-desktop kernel: BIOS-e820: [mem 0x000000007f39a000-0x000000007f3fefff] ACPI data
Mar 18 05:44:58 brian-desktop kernel: reserve setup_data: [mem 0x000000005fc33000-0x000000005fc33fff] ACPI NVS
Mar 18 05:44:58 brian-desktop kernel: reserve setup_data: [mem 0x000000007ebab000-0x000000007f399fff] ACPI NVS
Mar 18 05:44:58 brian-desktop kernel: reserve setup_data: [mem 0x000000007f39a000-0x000000007f3fefff] ACPI data
Mar 18 05:44:58 brian-desktop kernel: efi: ACPI=0x7f331000 ACPI 2.0=0x7f331000 SMBIOS=0xf05e0 MPS=0xfc410 MOKvar=0x7bc7b000
Mar 18 05:44:58 brian-desktop kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-104-generic root=UUID=5c8cbdbd-b1bd-458e-a8ef-335b944>
Mar 18 05:44:58 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x5fc33000-0x5fc33fff] (4096 bytes)
Mar 18 05:44:58 brian-desktop kernel: PM: Registering ACPI NVS region [mem 0x7ebab000-0x7f399fff] (8318976 bytes)
Mar 18 05:44:58 brian-desktop kernel: ACPI: Interpreter disabled.
Mar 18 05:44:58 brian-desktop kernel: pnp: PnP ACPI: disabled
Mar 18 05:44:58 brian-desktop kernel: ACPI: <n/a>: failed to evaluate _DSM (0x1001)
Mar 18 05:44:59 brian-desktop systemd[1]: Started ACPI Events Check.
Mar 18 05:44:59 brian-desktop systemd[1]: Listening on ACPID Listen Socket.
Mar 18 05:44:59 brian-desktop systemd[1]: Started ACPI event daemon.
Mar 18 05:48:30 brian-desktop sudo[3909]: brian : TTY=pts/0 ; PWD=/home/brian ; USER=root ; COMMAND=/usr/bin/journalctl -b0 -g acpi
Last one^^^^^
 
I still have not changed noacpi to noapic
 

Members online


Top