LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   System halts after 1-2 days ACPI BIOS Error? (https://www.linuxquestions.org/questions/linux-kernel-70/system-halts-after-1-2-days-acpi-bios-error-4175717363/)

jkcray 10-02-2022 09:23 AM

System halts after 1-2 days ACPI BIOS Error?
 
Hello.
I'm running Ubuntu 22.04 on
Code:

uname -a
Linux kinsella-OptiPlex-5060 5.15.0-48-generic #54-Ubuntu SMP Fri Aug 26 13:26:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

It is fully updated to Ubuntu 22.04.1 LTS

Every 24-48 hours my system halts. When I look at the output from dmesg I see multiple error messages of the form
Code:

ACPI BIOS Error
Here is the output from sudo dmesg -T --level=err

Code:

[Sun Oct  2 14:28:25 2022] x86/cpu: SGX disabled by BIOS.
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR08._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR09._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR10._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[Sun Oct  2 14:28:25 2022] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
[Sun Oct  2 14:28:25 2022] ACPI Error: Aborting method \_SB.PR11._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

Am I correct in supposing that the dmesg error messages point to the problem?

I have done some searching online and came across a suggestion that the above is an issue for kernel 5.15 and is resolved in 5.18.

But I'd like to stay with my LTS Ubuntu release if possible.

Any advice very welcome.

Ser Olmy 10-02-2022 06:25 PM

No, the ACPI error is very unlikely to be related to your issue. "Could not resolve symbol" errors are extremely common.

When you say your system "halts," do you mean it freezes, or does the kernel crash ("panic") and you have to reset/power cycle to restart?

jkcray 10-03-2022 03:06 AM

Quote:

Originally Posted by Ser Olmy (Post 6383978)
No, the ACPI error is very unlikely to be related to your issue. "Could not resolve symbol" errors are extremely common.

When you say your system "halts," do you mean it freezes, or does the kernel crash ("panic") and you have to reset/power cycle to restart?

Thanks.

The first time,the system displayed a black screen and seemed to have powered down. The second time, a few days later, the desktop was displayed but the system had frozen.

In both cases, I couldn't ssh in to the system.

Interesting (to me) the output from

Code:

sudo dmesg -T --level=err
is now empty.

I'll post again if the system freezes again.

Jan K. 10-03-2022 04:08 AM

I'm pretty sure, I recently saw a bunch of acpi fixes in the kernel changelog...

Ser Olmy 10-03-2022 11:23 AM

Quote:

Originally Posted by Jan K. (Post 6384026)
I'm pretty sure, I recently saw a bunch of acpi fixes in the kernel changelog...

And you will continue to see that in just about every changelog going forward, as ACPI is a mess and new motherboards with new and exiting ACPI bugs keeps being releases.

ACPI bugs can in some cases cause problems with suspend/resume as well as power saving in general (after all, that's what it does), but it will almost certainly not cause hangs/lockups/freezes, kernel panics, or application crashes.

Ser Olmy 10-03-2022 11:28 AM

Quote:

Originally Posted by jkcray (Post 6384021)
The first time,the system displayed a black screen and seemed to have powered down. The second time, a few days later, the desktop was displayed but the system had frozen.

I'm willing to bet it's not ACPI-related.

It could be a kernel bug, but it's much more likely to be a hardware issue, typically related to either power, RAM, or cooling.

I'd recommend checking your PSU and motherboard for bad capacitors. If all seems good, run memtest86 for a few hours.

Jan K. 10-03-2022 06:26 PM

Well, why not just try a new kernel?

Could be interesting for others as well...

jkcray 10-04-2022 07:08 AM

Quote:

Originally Posted by Ser Olmy (Post 6384112)
I'm willing to bet it's not ACPI-related.

It could be a kernel bug, but it's much more likely to be a hardware issue, typically related to either power, RAM, or cooling.

I'd recommend checking your PSU and motherboard for bad capacitors. If all seems good, run memtest86 for a few hours.

Bizarre discovery.

memtest86+ doesn't appear on my grub menu (obtained when booting with Shift key pressed).

This is weird?

A config choice missed when upgrading to 22.04?


Any suggestions?

Thanks.


All times are GMT -5. The time now is 01:47 AM.