Messages in this thread | | | Subject | Re: [PATCH 4.19 025/361] ACPICA: AML interpreter: add region addresses in global list during initialization | From | Holger Hoffstätte <> | Date | Mon, 12 Nov 2018 21:03:25 +0100 |
| |
On 11/12/18 8:25 PM, Greg Kroah-Hartman wrote: > On Mon, Nov 12, 2018 at 07:30:57PM +0100, Holger Hoffstätte wrote: >> On 11/11/18 11:16 PM, Greg Kroah-Hartman wrote: >>> 4.19-stable review patch. If anyone has any objections, please let me know. >> >> As probably expected this patch causes problems. In my case one server >> can no longer load the nct6775 hwmon module, which means the fan cannot be >> monitored, and therefore my monitoring system promptly starts spamming me with >> alerts that my fan has failed - which is of course not true. >> >> --snip-- >> Nov 12 18:08:56 tux kernel: nct6775: Found NCT6776D/F or compatible chip at 0x2e:0x290 >> Nov 12 18:08:56 tux kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x >> Nov 12 18:08:56 tux kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver >> --snip-- >> >> This is certainly caused by my old BIOS and its broken ACPI implementation, >> however since it's working perfectly fine otherwise I see no reason to replace >> it. That being said, I must be able to monitor my fan, so for now reverting >> the patch immediately "fixed" the problem for me - the fan entries appeared >> in sysfs again after successfully loading the module. >> >> Idea, workarounds or patches welcome. > > So Linus's tree is also "broken" for your hardware?
Not tested yet (should I?) but I assume it will be, since it seems to be my old BIOS' ACPI implemnetation's fault. As I wrote to Erik, I just added acpi_enforce_resources=lax to the boot flags, and as expected it gives a warning for the hwmon module, but still lets it pass and work, as before or with the patch reverted. So I'm good for now.
thanks, Holger
| |