Bug 202527
Summary: | ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191) | ||
---|---|---|---|
Product: | ACPI | Reporter: | Maciej Grochowski (maciej.grochowski89) |
Component: | ACPICA-Core | Assignee: | acpi_acpica-core (acpi_acpica-core) |
Status: | CLOSED CODE_FIX | ||
Severity: | high | CC: | erik.kaneda, rui.zhang |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | 4.15.0-45 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | ACPI DUMP |
Before reporting this as a FW error, try updating to a kernel 4.17 or later. Some of these might ACPI errors might disappear. Correct I updated to the 4.18.0-15 on this Ubuntu board and ACPI Error disappeared, however NIC disappeared as well... Will try few other newer versions. You may want to file a separate bug for the NIC with ubuntu and see if they can direct you to the correct person Also, please post a full dmesg of the 4.18 Hi Erik, Thank you for the help. Currently I got update from FW supplier and they are going to deliver updated FW image. I believe before that happened there is no point to continue investigation. I will update this ticket once I will test new image with at least few kernel revisions. Bug closed as the ACPI errors are gone. Please file a new bug for the NIC issue. |
Created attachment 281067 [details] ACPI DUMP On the new laptop motherboard ACPI errors, I updated BIOS to the newest revision according to producer, but still getting these errors: kernel: [ 0.069799] ACPI: Added _OSI(Module Device) kernel: [ 0.069799] ACPI: Added _OSI(Processor Device) kernel: [ 0.069799] ACPI: Added _OSI(3.0 _SCP Extensions) kernel: [ 0.069799] ACPI: Added _OSI(Processor Aggregator Device) kernel: [ 0.069799] ACPI: Added _OSI(Linux-Dell-Video) kernel: [ 0.069799] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) kernel: [ 0.069799] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) kernel: [ 0.069799] ACPI: Added _OSI(Linux) kernel: [ 0.076261] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191) kernel: [ 0.076272] No Local Variables are initialized for Method [PXSX] kernel: [ 0.076275] No Arguments are initialized for method [PXSX] kernel: [ 0.076278] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252) kernel: [ 0.076284] ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170831/psparse-550) kernel: [ 0.078106] ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191) kernel: [ 0.078114] No Local Variables are initialized for Method [PXSX] kernel: [ 0.078116] No Arguments are initialized for method [PXSX] kernel: [ 0.078119] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252) kernel: [ 0.078124] ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170831/psparse-550) kernel: [ 0.079940] ACPI Error: [_SB_.PCI0.RP13.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload2-191) kernel: [ 0.079947] No Local Variables are initialized for Method [PXSX] kernel: [ 0.079950] No Arguments are initialized for method [PXSX] kernel: [ 0.079953] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170831/psobject-252) kernel: [ 0.079957] ACPI Error: Method parse/execution failed \_SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20170831/psparse-550) kernel: [ 0.085325] ACPI Error: [\_SB_.PCI0.RP05.PXSX.WIST] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) kernel: [ 0.085336] No Local Variables are initialized for Method [CNDP] kernel: [ 0.085340] No Arguments are initialized for method [CNDP] kernel: [ 0.085343] ACPI Error: Method parse/execution failed \CNDP, AE_NOT_FOUND (20170831/psparse-550) kernel: [ 0.085351] ACPI Error: Method parse/execution failed \, AE_NOT_FOUND (20170831/psparse-550) kernel: [ 0.085719] ACPI: Executed 57 blocks of module-level executable AML code In attachment ACPI dump from utility. Could you take a look on that and check if from kernel perspective that is ok? I am thinking if I need to report it to as FW bug...