From: The Holy ettlz <theholyettlz@googlemail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: "I/O resource 0000:00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI region SMBI"
Date: Mon, 29 Dec 2008 14:42:17 +0000 [thread overview]
Message-ID: <1230561737.2328.7.camel@rhapsody> (raw)
In-Reply-To: <20081229143508.GD31266@srcf.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On Mon, 2008-12-29 at 14:35 +0000, Matthew Garrett wrote:
> On Mon, Dec 29, 2008 at 02:27:52PM +0000, The Holy ettlz wrote:
> > Hello,
> >
> > I see the following in dmesg. I don't know how report-worthy it is, but
> > anyway:
> >
> > ACPI: I/O resource 0000:00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI
> > region SMBI
> > [0x1c00-0x1c0f]
> > ACPI: Device needs an ACPI driver
>
> Your ACPI tables use the smbus controller themselves, so using a native
> Linux driver could potentially result in race conditions and bizarre
> failures. If you're not trying to use your smbus controller directly
> then it's not really an issue.
Well, i2c-i801 is loaded:
i915 67080 2
drm 201328 3 i915
i2c_i801 17820 0
i2c_core 29216 2 drm,i2c_i801
Should I be worried?
James
--
The Holy ettlz TheHolyettlz@googlemail.com
PGP key ID: 03F94B5D
-----------------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-29 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 14:27 "I/O resource 0000:00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI region SMBI" The Holy ettlz
2008-12-29 14:35 ` Matthew Garrett
2008-12-29 14:42 ` The Holy ettlz [this message]
2008-12-29 14:45 ` 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=1230561737.2328.7.camel@rhapsody \
--to=theholyettlz@googlemail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/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