linux-kernel - Re: OpRegion conflicts for Skylake LPSS

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-next>] [day] [month] [year] [list]

Message-ID: <20160426155437.GA10202@lahna.fi.intel.com>
Date:	Tue, 26 Apr 2016 18:54:37 +0300
From:	Mika Westerberg <mika.westerberg@...ux.intel.com>
To:	Ben Gamari <ben@...rt-cactus.org>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
	Jarkko Nikula <jarkko.nikula@...ux.intel.com>
Subject: Re: OpRegion conflicts for Skylake LPSS

On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari wrote:
> 
> While trying to troubleshoot some touchpad issues on a Dell Latitude
> E7470 (namely the touchpad being exposed only as a PS/2 device) I
> noticed that the intel-lpss driver (using a 4.6-rc4 kernel) fails to
> load with,
> 
>     ACPI Warning: SystemMemory range 0x00000000FE028000-0x00000000FE0281FF conflicts with OpRegion 0x00000000FE028000-0x00000000FE028207 (\_SB.PCI0.GEXP.BAR0) (20160108/utaddress-255)
>     ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
>     intel-lpss: probe of INT3446:00 failed with error -16
> 
> The DSDT OpRegion in question looks like this,
> 
>     Scope (_SB.PCI0)
>     {
>         Device (GEXP)
>         {
>             Name (_ADR, One)  // _ADR: Address
>             Name (_STA, 0x0B)  // _STA: Status
>             OperationRegion (BAR0, SystemMemory, SB04, 0x0208)
>             Field (BAR0, DWordAcc, NoLock, Preserve)
>             {
>                 ICON,   32, 
>                 TAR,    32, 
>                 Offset (0x10), 
>                 DATA,   32, 
>                 HCNT,   32, 
>                 LCNT,   32, 
>                 Offset (0x2C), 
>                     ,   5, 
>                 ABRT,   1, 
>                 Offset (0x40), 
>                 RBCK,   32, 
>                 Offset (0x54), 
>                 CLR,    32, 
>                 Offset (0x6C), 
>                 ENB,    1, 
>                 Offset (0x70), 
>                 ACTV,   1, 
>                 TFNF,   1, 
>                     ,   1, 
>                 RFNE,   1, 
>                 Offset (0x7C), 
>                 HOLD,   32, 
>                 Offset (0x9C), 
>                 ENSB,   1, 
>                 Offset (0x204), 
>                 RST,    32
>             }
> 
> It looks very much like these are describing the same device. Perhaps
> the lpss driver should be binding to this ACPI node? Or perhaps this is
> a firmware issue? Any guidance would be greatly appreciated.

Can you send me full acpidump of that machine?