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]

Message-ID: <CF6A88132359CE47947DB4C6E1709ED53BB9FBAD@ORSMSX110.amr.corp.intel.com>
Date:   Mon, 12 Nov 2018 20:12:55 +0000
From:   "Schmauss, Erik" <erik.schmauss@...el.com>
To:     Holger Hoffstätte 
        <holger@...lied-asynchrony.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     "stable@...r.kernel.org" <stable@...r.kernel.org>,
        Jean-Marc Lenoir <archlinux@...emel.com>,
        "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>
Subject: RE: [PATCH 4.19 025/361] ACPICA: AML interpreter: add region
 addresses in global list during initialization



> -----Original Message-----
> From: Holger Hoffstätte [mailto:holger@...lied-asynchrony.com]
> Sent: Monday, November 12, 2018 11:42 AM
> To: Schmauss, Erik <erik.schmauss@...el.com>; Greg Kroah-Hartman
> <gregkh@...uxfoundation.org>; linux-kernel@...r.kernel.org
> Cc: stable@...r.kernel.org; Jean-Marc Lenoir <archlinux@...emel.com>;
> Wysocki, Rafael J <rafael.j.wysocki@...el.com>
> Subject: Re: [PATCH 4.19 025/361] ACPICA: AML interpreter: add region
> addresses in global list during initialization
> 
> Hello Erik,
> 
> thanks for responding.
> 
> On 11/12/18 8:01 PM, Schmauss, Erik wrote:
> >> 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.
> >
> > Is there a firmware update available for this machine? If so, you may
> > want to do a firmware update.
> 
> The motherboard is from 2011 and I already installed the last available BIOS
> from 2013 a few years ago. That fixed exactly nothing. :) This was my last
> motherboard from Asus ever, but alas, it's still here and otherwise working,
> so..
> 
> > Also, what is the behavior in kernels 4.16 or older?
> 

Hi,
> Everything just worked - yes, with ACPI spew, but.. ¯\(ツ)/¯
> I understand that the patch might well be "technically correct" and OK for
> mainline/current hardware and will try playing with acpi=.. kernel flags.

It's strange how the driver would load in 4.16 and fail to load with this patch.
I would like to make sure that the driver load behavior is not being changed
from 4.16 or earlier.

Could you send a working dmesg from 4.16 (or earlier) and a failing dmesg with
this stable branch using the same kernel command line parameters for both?

I don't need too much of the spew if it looks the same. I'm more interested in
the initializations and the warning message.

Erik

> 
> thanks,
> Holger