Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4478745imu; Mon, 12 Nov 2018 11:43:18 -0800 (PST) X-Google-Smtp-Source: AJdET5dDKpFkPZvoXvGb8PEeUt/MoYwHyPNPZxkb6cA3Lk1V2YUIN/mIrvxyxSGoa8iq4UorI8pU X-Received: by 2002:a17:902:5ac7:: with SMTP id g7mr2160132plm.212.1542051798762; Mon, 12 Nov 2018 11:43:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542051798; cv=none; d=google.com; s=arc-20160816; b=NgQKZjTzsaq2zY9ZE5RGTpcPHeFddyItS1l/QjKNpYsDqWaeE8SsiXE6pfXmiHw3cj hU0hMwFBxexvgPaeVxXN6y1P9/ogzsCirxiOD4OGysCxCuI00zaArWDheNYdiB5npacY 5abmii9kT4eCVGNkxjP6Sub6b5a6nNemkTWntMrpOkKwRpaNLbDtuDbXcEEciBpuVbRW hl09hukKCrYinAc9aSUEYf1DEj4hcOhxaN9aQBBzgx60oqt5D1rGtmTpllssiN3gfmHT ZaNUXLO2wOOGHxRUFLrhp/v4yJR9utmSwYxXpFW0O/2C9crVeRH67AV5hU7JVCaFKhNZ 7kDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject; bh=X6C2+8kK9WrHPAR1zudsDT06tXvNdMBt/a0vu66rEjY=; b=BoXYmtti4abV6VC2o+Y6dYuIylILQgD4mQszL80jnzO1T4qECbXZGg2UY41YeZqtrO RMQs841t16GWS1ETpMkj3UTnyXxmk8c4TLptoWUbpq9NJ/ekVtyDnSKonBQrqUuN8rFi bwjaFFWYvcnt5MO7nvqEPjhk2udfjfIcRkaz8CCf8XxqeEvGW/F1yBrt85McJGBIXEvd SlVsmGxIu1BVKbwEYUDq66zMEcrNfprtZCer3Tk03T+EDWwy0pk0ywxja4tvTAYALj0m 8iEVre3cWvs8JLEJ8oE2s55YCG2QQhH9DvKZJ/ZrsSGwZuZ2WGC+7LYUNAtJd2ysWrKJ MtPA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 91-v6si18750126plc.409.2018.11.12.11.43.03; Mon, 12 Nov 2018 11:43:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728119AbeKMFgl (ORCPT + 99 others); Tue, 13 Nov 2018 00:36:41 -0500 Received: from mail02.iobjects.de ([188.40.134.68]:53922 "EHLO mail02.iobjects.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725749AbeKMFgl (ORCPT ); Tue, 13 Nov 2018 00:36:41 -0500 Received: from tux.wizards.de (p3EE2F45F.dip0.t-ipconnect.de [62.226.244.95]) by mail02.iobjects.de (Postfix) with ESMTPSA id 1C08F4160F7C; Mon, 12 Nov 2018 20:42:00 +0100 (CET) Received: from [192.168.100.223] (ragnarok.applied-asynchrony.com [192.168.100.223]) by tux.wizards.de (Postfix) with ESMTP id 992A5F0161C; Mon, 12 Nov 2018 20:41:59 +0100 (CET) Subject: Re: [PATCH 4.19 025/361] ACPICA: AML interpreter: add region addresses in global list during initialization To: "Schmauss, Erik" , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" Cc: "stable@vger.kernel.org" , Jean-Marc Lenoir , "Wysocki, Rafael J" References: <20181111221619.915519183@linuxfoundation.org> <20181111221623.163909820@linuxfoundation.org> <9da1c8e8-d237-11b3-8918-859a4bbdbcc4@applied-asynchrony.com> From: =?UTF-8?Q?Holger_Hoffst=c3=a4tte?= Organization: Applied Asynchrony, Inc. Message-ID: <341e972a-d941-f44e-73b9-926ac6cf0ccf@applied-asynchrony.com> Date: Mon, 12 Nov 2018 20:41:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? 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. thanks, Holger