linux-kernel - Re: resource piix4_smbus conflicts with ACPI region SMRG

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: <4C04496E.3000303@gmail.com>
Date:	Mon, 31 May 2010 17:42:38 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Richard Tillmore <rtillmore@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: resource piix4_smbus conflicts with ACPI region SMRG

On 05/31/2010 04:12 PM, Richard Tillmore wrote:
> Hi,
>
> I was running 2.6.30 until I had time to update.  Being a long weekend
> I upgraded to 2.6.34-rc6 and noticed a few new messages in dmesg.  I
> then installed 2.6.34 and the messages remain.
>
> PCI: Ignoring host bridge windows from ACPI; if necessary, use
> "pci=use_crs" and report a bug
> ACPI: PCI Root Bridge [PCI0] (0000:00)

This is just an informational message.

>
> ACPI: resource piix4_smbus [io  0x0440-0x0447] conflicts with ACPI
> region SMRG [??? 0x00000440-0x0000044f flags 0x47]
> ACPI: If an ACPI driver is available for this device, you should use
> it instead of the native driver
>
> The system is a Tyan Tiger S1832 motherboard with a P3 850Mhz
> processor running the latest bios.  Everything appears to work
> properly so I am unsure what the messages mean beyond the obvious.  I
> did a little research and was wondering if this is related to the no
> bootmem patches.  I have:

Unless you need to use anything on SMBus (hardware sensors, essentially) 
you don't have to worry about that one. It means that the kernel has 
detected that the BIOS may potentially access the SMBus controller which 
may conflict with usage of the controller from within the OS.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/