From: Robert Hancock <hancockrwd@gmail.com>
To: Richard Tillmore <rtillmore@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: resource piix4_smbus conflicts with ACPI region SMRG
Date: Mon, 31 May 2010 17:42:38 -0600 [thread overview]
Message-ID: <4C04496E.3000303@gmail.com> (raw)
In-Reply-To: <AANLkTinmBxzM4IEgrY6gqokDhLJDrVyKd0cu75VaFR8Q@mail.gmail.com>
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.
next prev parent reply other threads:[~2010-05-31 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 22:12 resource piix4_smbus conflicts with ACPI region SMRG Richard Tillmore
2010-05-31 23:42 ` Robert Hancock [this message]
2010-06-01 2:36 ` Richard Tillmore
2010-06-01 3:13 ` Robert Hancock
2010-06-03 23:50 ` Richard Tillmore
2010-06-04 0:05 ` Matthew Garrett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C04496E.3000303@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtillmore@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox