Bug 198877
| Summary: | Lot of ACPI Errors (AE_NOT_FOUND) on Dell XPS 15 9550 with newer BIOS | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | Enrico Tagliavini (enrico.tagliavini) |
| Component: | BIOS | Assignee: | Zhang Rui (rui.zhang) |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | pachoramos1, rui.zhang, yu.c.chen |
| Priority: | P1 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| Kernel Version: | 4.15.3 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
kernel 4.15.3 dmesg output on Dell XPS 15 9550 with BIOS 1.6.1
acpidump output Dell XPS 15 9550 BIOS 1.6.1 acpidump binary output Dell XPS 15 9550 BIOS 1.6.1 |
||
Created attachment 274345 [details]
acpidump output Dell XPS 15 9550 BIOS 1.6.1
Created attachment 274347 [details]
acpidump binary output Dell XPS 15 9550 BIOS 1.6.1
Attaching the binary format as well, in case it's useful
After reading https://bugzilla.redhat.com/show_bug.cgi?id=1413342#c43 I think this would be better to be moved to BIOS. I was also wonder about what was said in the mentioned comment: if this is a firmware bug and we force it to use the same path as Windows, how is Windows dealing with such bugs? I'm concerned this is another case like the PCIE ASPM where the expected behavior was different from what Windows usually does. Still a firmware bug, but there might be something that can be done kernel side to fix it. *** This bug has been marked as a duplicate of bug 109511 *** |
Created attachment 274343 [details] kernel 4.15.3 dmesg output on Dell XPS 15 9550 with BIOS 1.6.1 Lots of ACPI errors started happening after I updated the BIOS on my Dell XPS 15. I skipped quite a few updates so am not sure which one started the issue. For the same reason I'm not sure if there was a working kernel and an update started showing the issue. However I'm 100% this started showing after a BIOS update as I can see the errors printed during boot. Now I updated to BIOS 1.6.1 which contains the fixes for Spectre and Meltdown (so quite an important one) and the issue is still present. Since downgrade is not an option anymore due to the security issues (including also the Intel ME one from few months ago), I'm reporting it here. OS is Fedora 27