https://bugzilla.kernel.org/show_bug.cgi?id=204807 Artem S. Tashkinov (aros@xxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |torvalds@linux-foundation.o | |rg Resolution|INVALID |--- --- Comment #34 from Artem S. Tashkinov (aros@xxxxxxx) --- (In reply to Matthew Garrett from comment #33) > This isn't a bug - the ACPI tables claim the resource in question, and > there's no way we can verify there are no conflicts between ACPI methods > that touch that range and the native driver. If you're confident that this > is safe on your system then you can boot with acpi_enforce_resources=lax, > but we can't make that the default. This will still produce the warning, but > the driver will be permitted to load. This bug needs to be fixed because 1) It doesn't affect Windows 2) Average people will never know how to deal with issue 3) I cannot ask my motherboard vendor (ASUS) to fix this issue in BIOS because they don't provide support for Linux - they barely provide any support at all. OoB experience of Linux users should not be "I don't get any sensors output, how to fix that?" Most users don't even know what and how to Google. They don't know about dmesg either. That's an effing horrible attitude. I'm CC'ing Linus because I absolutely hate what's going on. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
