Bug 215101
Summary: | ASUS PRIME TRX40-PRO: "ACPI BIOS Error (bug): Failure creating named object" | ||
---|---|---|---|
Product: | ACPI | Reporter: | Juan Simón (decedion) |
Component: | ACPICA-Core | Assignee: | acpi_acpica-core (acpi_acpica-core) |
Status: | NEEDINFO --- | ||
Severity: | normal | CC: | cdrcat, kernal, kernelorg, kewkdb, mohammadmtay, mys721tx, nucleo, rui.zhang, vincent.coleaux, wally |
Priority: | P1 | ||
Hardware: | AMD | ||
OS: | Linux | ||
Kernel Version: | 5.15.4 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
ACPI dump from debian10/kernel4.19.0-18-amd64
acpidump_Debian10_4.19.0-18-amd64.txt acpidump_arch_6.0.2-arch1-1.txt |
Description
Juan Simón
2021-11-22 13:36:41 UTC
Same issue here with: Debian 11 (kernel 5.15) Motherboard Asus Prime TRX40-PRO S BIOS version: 1502 Please attach the acpidump output. Created attachment 301239 [details]
ACPI dump from debian10/kernel4.19.0-18-amd64
ACPI dump from debian10/kernel4.19.0-18-amd64
Motherboard Asus Prime TRX40-PRO S
BIOS version: 1502
This is caused by bogus firmware. One of the SSDT table is trying to create the \_SB.I2CA.WT1A and some other objects, which have already been defined. Did you observe any functionality issue? If no, I'd prefer to close this bug report as there is nothing we can do in Linux kernel to avoid this BIOS bug. Thanks for the feedback. I was in touch with Asus regarding this issue: they claim it is related to Linux because it doesn't occur with Microsoft Windows. I could not double-check this though... What would be the best way to prove them it is a firmware issue? Would you have some more details I can share with them regarding this? There are some issues with USB audio on this motherboard. One of them was worked around with a kernel quirk: https://bugzilla.kernel.org/show_bug.cgi?id=210783 Audio works for me but I only have a basic stereo setup. Based on what you have found out, could this bug be linked to USB/audio functionalities? In dsdt WT1A device object is defined under \_SB.I2CA Scope (I2CA) { Device (WT1A) { ... } } However, in ssdt3 Scope (\_SB.I2CA) { Device (WT1A) { ... } } It is redefining the \_SB.I2CA.WT1A object. (In reply to Vincent from comment #5) > Thanks for the feedback. I was in touch with Asus regarding this issue: they > claim it is related to Linux because it doesn't occur with Microsoft > Windows. That is probably because Windows never dumps these messages... > I could not double-check this though... > What would be the best way to prove them it is a firmware issue? Would you > have some more details I can share with them regarding this? I don't know if the above helps or not. > > There are some issues with USB audio on this motherboard. > One of them was worked around with a kernel quirk: > https://bugzilla.kernel.org/show_bug.cgi?id=210783 > Audio works for me but I only have a basic stereo setup. > > Based on what you have found out, could this bug be linked to USB/audio > functionalities? I don't know, this could cause problem to some I2C devices. (In reply to Zhang Rui from comment #6) > In dsdt WT1A device object is defined under \_SB.I2CA > [...code...] > However, in ssdt3 > [...code...] > It is redefining the \_SB.I2CA.WT1A object. Although it appears to be a *different* object collision (`\_SB.PC00.SAT0.PRT0.PWRG` from `20210730/dswload2-326`), a similar issue was reported at https://bugs.launchpad.net/acpi/+bug/1978398 for Ubuntu 22.04 running the 5.15.x kernel. In my case, this occurs on a Lenovo Thinkpad P17 (Model: 20YU0066US). > Did you observe any functionality issue? > If no, I'd prefer to close this bug report as there is nothing we can do in > Linux kernel to avoid this BIOS bug. While I have yet to notice any regressions in functionality or stability and am therefore not particularly worried about an actual fix, I have experienced issues *hiding* this ring buffer message, as I want to present a "streamlined," "pleasant" bootup experience. More specifically, why does this message punch through the "quiet" boot option? Is there any way to quiet it without resorting to `quiet loglevel=n` (which, if aggressive enough, could easily hide other issues that may crop up in the future that I *do* want to be notified of)? > This is caused by bogus firmware. I'm unfamiliar with how the kernel handles ACPI, so for my own information, can you clarify what you mean by "firmware?" IE, do you mean to say that the error is actually propagating from the firmware active on the hardware device, or do you mean the error is being caused by some official/community/other created firmware blob loaded by the kernel for specific hardware? If the former: is there a way to silence anything propagated from the firmware but not other important kernel warnings? If the latter: what is the source of these firmware blobs? --- Thanks for any help you can provide! This bug effects me too, I submitted a bug report here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979030 I think that has more information and log files, hope it helps FYI: I am just getting a similar error and I believe it is because I just disabled the sleep states in the BIOS on my Dell XPS-15 9570. IF you get this error then perhaps check your BIOS settings. The first two error lines in the log are "kernel: ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)" and "kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)". I could be wrong, sorry, I didn't change BIOS settings back to test. Created attachment 303046 [details]
acpidump_Debian10_4.19.0-18-amd64.txt
I am getting the same error over I2C on a Gigabyte TRX40 DESIGNARE with F6 firmware and kernel 6.0.2.
[ 0.286865] ACPI: Added _OSI(Module Device)
[ 0.286866] ACPI: Added _OSI(Processor Device)
[ 0.286867] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.286867] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.286869] ACPI: Added _OSI(Linux-Dell-Video)
[ 0.286869] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[ 0.286870] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[ 0.312193] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT1A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312200] fbcon: Taking over console
[ 0.312206] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312209] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312211] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT1A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312214] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312217] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312218] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT2A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312222] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312224] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312225] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT2A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312229] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312231] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312233] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT3A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312236] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312238] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312239] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT3A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312243] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312245] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312246] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT4A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312250] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312253] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312254] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT4A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312258] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312260] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312262] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT5A], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312265] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312268] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312271] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT1B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312274] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312277] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312278] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT1B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312282] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312284] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312286] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT2B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312289] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312292] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312293] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT2B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312297] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312299] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312301] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT3B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312304] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312307] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312308] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT3B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312312] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312314] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312316] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT4B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312319] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312322] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312323] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT4B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312327] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312329] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312331] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT5B], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312334] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312337] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312340] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT1C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312343] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312346] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312347] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT1C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312351] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312353] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312355] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT2C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312358] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312361] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312362] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT2C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312366] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312368] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312370] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT3C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312373] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312376] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312377] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT3C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312381] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312383] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312385] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT4C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312388] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312391] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312392] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT4C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312396] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312398] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312400] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT5C], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312403] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312406] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312409] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT1D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312412] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312415] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312416] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT1D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312420] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312422] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312424] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT2D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312427] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312430] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312431] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT2D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312435] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312437] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312439] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT3D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312442] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312445] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312446] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT3D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312450] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312452] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312454] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT4D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312457] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312460] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312461] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT4D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312465] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312467] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312469] ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT5D], AE_ALREADY_EXISTS (20220331/dswload2-326)
[ 0.312472] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[ 0.312475] ACPI: Skipping parse of AML opcode: Device (0x5B82)
[ 0.312589] ACPI: 9 ACPI AML tables successfully acquired and loaded
[ 1.857579] ACPI: Interpreter enabled
[ 1.857593] ACPI: PM: (supports S0 S3 S4 S5)
[ 1.857594] ACPI: Using IOAPIC for interrupt routing
Created attachment 303047 [details]
acpidump_arch_6.0.2-arch1-1.txt
(In reply to cdrcat from comment #9) > FYI: I am just getting a similar error and I believe it is because I just > disabled the sleep states in the BIOS on my Dell XPS-15 9570. IF you get > this error then perhaps check your BIOS settings. The first two error lines > in the log are "kernel: ACPI BIOS Error (bug): Failure creating named object > [_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326)" > and "kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog > (20210730/psobject-220)". I could be wrong, sorry, I didn't change BIOS > settings back to test. You might be on to something. I am getting similar errors on my Asus FA507RC laptop with amd ryzen 7. On this laptop, there are no useful sleep states. From the user's vantage point the laptop can be either on, or off. There is no way for me to change this in the BIOS. (I regret buying the laptop for this reason.) cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 25 model : 68 model name : AMD Ryzen 7 6800H with Radeon Graphics stepping : 1 microcode : 0xa404101 power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] In dmesg: ACPI: PM: (supports S0 S4 S5) Here are some error messages: Kernel: 5.19.17 #1-NixOS SMP PREEMPT_DYNAMIC ACPI: Added _OSI(Module Device) ACPI: Added _OSI(Processor Device) ACPI: Added _OSI(3.0 _SCP Extensions) ACPI: Added _OSI(Processor Aggregator Device) ACPI: Added _OSI(Linux-Dell-Video) ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GP19.NHI0._RST], AE_ALREADY_EXISTS (20220331/dswload2-326) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220) ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014) ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GP19.NHI1._RST], AE_ALREADY_EXISTS (20220331/dswload2-326) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220) ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014) ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.WWAN], AE_NOT_FOUND (20220331/dswload2-162) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220) ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010) ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP5.RTL8], AE_NOT_FOUND (20220331/dswload2-162) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220) ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010) ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP6.WLAN], AE_ALREADY_EXISTS (20220331/dswload2-326) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220) ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x5B82) ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP7.DEV0], AE_NOT_FOUND (20220331/dswload2-162) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220) ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010) ACPI: 22 ACPI AML tables successfully acquired and loaded ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored ACPI: USB4 _OSC: OS supports USB3+ DisplayPort+ PCIe+ XDomain+ ACPI: USB4 _OSC: OS controls USB3+ DisplayPort+ PCIe+ XDomain+ ACPI: EC: EC started ACPI: EC: interrupt blocked ACPI: EC: EC_CMD/EC_SC=0x66, EC_DATA=0x62 ACPI: \_SB_.PCI0.SBRG.EC0_: Boot DSDT EC used to handle transactions ACPI: Interpreter enabled ACPI: PM: (supports S0 S4 S5) ACPI: Using IOAPIC for interrupt routing Also, when I try to for example modprobe amd_pstate I get many errors that look similar: ACPI BIOS Error (bug): Could not resolve symbol [^PCI0.GPP0.PEGP.EDP1], AE_NOT_FOUND (20220331/psargs-330) ACPI Error: Aborting method \_SB.BRTN due to previous error (AE_NOT_FOUND) (20220331/psparse-529) ACPI Error: Aborting method \_SB.PCI0.SBRG.EC0.QLIB due to previous error (AE_NOT_FOUND) (20220331/psparse-529) ACPI Error: Aborting method \_SB.PCI0.SBRG.EC0._Q18 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) I hope this information can help the bug forward. This is my first message on the kernel.org bugzilla. Please let me know if I should have formatted this message differently, or if you prefer these errors in an attachment rather than inline. Also, feel free to request for more information (full dmesg output perhaps). Thank you. Mark van Dijk I wanted to chime in on this and provide any help via logs or whatever. Google led me here based on my search of: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT5D], AE_ALREADY_EXISTS (20220331/dswload2-326) I get this error in my boot log for linux (pop_os). However, I've been having a crash in Windows 11 which I have not been able to solve. When I review the logs in windows it gives me: Error Code 56 ACPI 15 Application Popup Error I'm running a Asus Zenith II Extreme Alpha. Let me know what I can provide to help with this. This looks like a pretty old thread but I just wanted to stop in and give my two cents. I have been working on installing Proxmox on a little ASUS PN50-B. It is similar to an Intel NUC in size (Ryzen 7 4800U, 64GB RAM, 512GB SSD). I was having this same issue after installing Proxmox 8.0.2 (Debian 12) on this system. Upon getting this error, the network card would stop working during boot. I had it right next to the switch for troubleshooting to see when the switch would die off. I saw some comments in other forums that mentions they made changes to the storage in BIOS (ACPI settings). This device is limited in BIOS options so as I just installed, I tried a different drive format on install. My initial install was as XFS. This is when my NIC would not work post-boot. After installing with EXT4, I still receive the errors on boot, but post-boot, I have a working NIC. I am not deep into kernel things, but thought I would mention this if anyone else was able to replicate success with this change. Hope this helps someone! |