ACPI Error fills up syslog fast


Go to solution Solved by JorgeB,

Recommended Posts

My syslog gets flooded with the following error:

 

Mar 11 07:35:06 Fileserver kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
Mar 11 07:35:06 Fileserver kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)
Mar 11 07:35:06 Fileserver kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)
Mar 11 07:35:06 Fileserver kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
Mar 11 07:35:06 Fileserver kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)
Mar 11 07:35:06 Fileserver kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)
Mar 11 07:35:06 Fileserver kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20220331/dswload2-477)
Mar 11 07:35:06 Fileserver kernel: ACPI Error: Aborting method \_SB.PC00.PEG1.PEGP._DSM due to previous error (AE_ALREADY_EXISTS) (20220331/psparse-529)
Mar 11 07:35:06 Fileserver kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)

 

i get rid of syslog.1 and syslog.2 if they get to big and FixCommonProblems nags about it. But this can't be the way to handle this?!
Bios is already the latest installed. Any advice would be much appreciated.

diagnostics-20230311-0735.zip

Link to comment

Following, as I am experiencing a similar issue. 
 

Quote

Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.POT3._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.PO11._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.POT4._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.PO12._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid kernel: ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.POT5._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20220331/psparse-529) Mar 16 17:58:26 UnRaid 


Removed some lines, as it's ~22 lines long. For my system, I'm using an R9 5900 (non-x), which is not listed as supported by my board, but this issue has only recently started for me. I was getting >4 month uptime until about 2 months ago. Nothing has changed since then, other than updating plugins and whatnot.

Based on "SB.PCI0" in the error, it looks like it's related to a PCIe device? PCI0 is where my X520-DA2 is located currently. When my server goes offline, I am unable to reach it via the network. I haven't been home when this occurs to see if it is responsive other than network. Like other posts, there doesn't appear to be anything in /var/log/syslog (and by extension, /boot/logs) that states anything about a kernel issue, and the ACPI issue only reads during boot.

If nothing else, I hope that my diagnostics have similarities to OP's so that we can find a solution.

unraid-diagnostics-20230316-1819.zip

Link to comment
  • 3 weeks later...
  • 2 weeks later...
On 4/13/2023 at 6:44 AM, ezek1el3000 said:

I removed the GPU Statistics Plugin by b3rs3rk and the error doesn't pop up anymore in my syslog. Syslog got spammed while i was on the Dashboard. On every other Tab, no errors. So I thought if PEG1 is mentioned in the error message then it should have something to do with the GPU.

I was having an:

 

unRAID kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG1.PEGP._DSM.USRG], AE_ALREADY_EXISTS (20220331/dsfield-184)

 

Removing the GPU Statistics Plugin solved that bug as well.

Link to comment

If you want to keep the GPU Statistics Plugin but want to avoid log overflow set "UI Automatic Refresh / Interval (Milliseconds)" to 10000 or so. That way you can keep the nice statistics on you dashboard and avoid the log overflow. In case you don't mind the occasionally ACPI error in your syslog.

Link to comment
  • 1 month later...
  • 6 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.