March 11, 20233 yr 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
March 11, 20233 yr Community Expert This is usually a BIOS problem, if it's up to date probably not much else you can do, a newer kernel might also help when a new Unraid release is available.
March 11, 20233 yr Author New kernel? How often does that happen? Is it ok to delete the syslog.1 and .2 with a script occasionally? Or would it break things?
March 11, 20233 yr Community Expert Solution 33 minutes ago, ezek1el3000 said: How often does that happen? v6.12 is expected soon, it will use kernel 6.1 or higher. 33 minutes ago, ezek1el3000 said: Is it ok to delete the syslog.1 and .2 with a script occasionally? Yes.
March 16, 20233 yr 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
April 7, 20233 yr did you figure out a fix for this? im having the same issue and erros. My mobo is a rog b660-i
April 13, 20233 yr Author I did not. I am currently deleting the syslog.1 and .2 every day via Userscripts. Latest Bios Update did not fix the error. Hopefully v6.12 and a new kernel fix things. But what I have read it is a hardware / bios problem which can actually only be solved by the manufacturer.
April 13, 20233 yr Author 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.
April 26, 20233 yr 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.
April 26, 20233 yr Author 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.
April 30, 20233 yr As another data point; this does not seem to affect all nvidia GPUs. I'm running the plugin on 6.11.5 w/ a Quadro P2200 and there are no such logs in syslog.
June 17, 20233 yr Author I updated from 6.11.5 to 6.12 and unfortunately the error still occurs. Syslog keeps showing the same error
January 12, 20242 yr Author Not really. Just ignore the error and occasionally delete the syslog. A BIOS update might help though.
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.