linux-kernel - Re: [PATCH 4.19 025/361] ACPICA: AML interpreter: add region addresses in global list during initialization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 12 Nov 2018 11:25:46 -0800
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Holger Hoffstätte 
        <holger@...lied-asynchrony.com>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Jean-Marc Lenoir <archlinux@...emel.com>,
        Erik Schmauss <erik.schmauss@...el.com>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: [PATCH 4.19 025/361] ACPICA: AML interpreter: add region
 addresses in global list during initialization

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?

thanks,

greg k-h