From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Fabio Comolli" <fabio.comolli@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Rene Herman <rene.herman@keyaccess.nl>,
Andrew Morton <akpm@osdl.org>, Thomas Renninger <trenn@suse.de>,
Jean Delvare <khali@linux-fr.org>
Subject: Re: New conflict message in latest GIT
Date: Wed, 23 Jul 2008 12:56:42 -0600 [thread overview]
Message-ID: <200807231256.42743.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <b637ec0b0807221156x46d550a1h4180d6d624daeeb@mail.gmail.com>
On Tuesday 22 July 2008 12:56:36 pm Fabio Comolli wrote:
> Linus' GIT tree 2.6.26-05752-g93ded9b shows this message:
>
> i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
> ACPI: I/O resource 0000:00:1f.3 [0x18e0-0x18ff] conflicts with ACPI
> region SMBI [0x18e0-0x18ef]
> ACPI: Device needs an ACPI driver
>
> There is no equivalent in 2.6.26 or previous kernels.
The "ACPI: I/O resource ... conflicts with ..." message was added by
Thomas:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=df92e695998e1bc6e426a840eb86d6d1ee87e2a5
That conflict checking infrastructure was in 2.6.26, but Jean's
change to make the i801_smbus driver use it didn't happen until
about a week ago:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=54fb4a05af0a4b814e6716cfdf3fa97fc6be7a32
The message is telling us that the i801_smbus driver thinks it owns
the 0x18e0-0x18ff region, but there's also an ACPI opregion that
references that region. There's no coordination between ACPI and
the i801_smbus driver, so there may be issues where nearly
simultaneous accesses cause incorrect behavior, e.g,. one may
read the wrong value from a temperature sensor. That, of course,
can lead to more serious things like unintended machine shutdowns.
I don't have any ideas about how to address this. I think Thomas's
intent was to collect better information for unreproducible bugs.
(Maybe this sort of conflict should even set a taint flag?)
Bjorn
next prev parent reply other threads:[~2008-07-23 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 18:56 Fabio Comolli
2008-07-22 20:00 ` Rene Herman
2008-07-22 20:14 ` Rene Herman
2008-07-23 7:17 ` Fabio Comolli
2008-07-23 8:01 ` Rene Herman
2008-07-23 18:11 ` Fabio Comolli
2008-07-23 18:38 ` Rene Herman
2008-07-23 18:56 ` Bjorn Helgaas [this message]
2008-07-23 19:50 ` Fabio Comolli
2008-08-09 16:13 ` Jean Delvare
2008-08-09 16:32 ` Fabio Comolli
2008-08-09 17:03 ` Jean Delvare
2008-08-09 18:46 ` Fabio Comolli
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=200807231256.42743.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@osdl.org \
--cc=fabio.comolli@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=trenn@suse.de \
/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
all inboxes | Powered by JetHome®