From: Rene Herman <rene.herman@keyaccess.nl>
To: Fabio Comolli <fabio.comolli@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: New conflict message in latest GIT
Date: Tue, 22 Jul 2008 22:00:06 +0200 [thread overview]
Message-ID: <48863C46.1060704@keyaccess.nl> (raw)
In-Reply-To: <b637ec0b0807221156x46d550a1h4180d6d624daeeb@mail.gmail.com>
On 22-07-08 20:56, 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.
[ snip ]
> 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family)
I believe this message in itself needn't be a problem but the code
producing this warning isn't new...
Bjorn, this reminds me of the:
pnp-have-quirk_system_pci_resources-include-io-resources.patch
in Andrew's tree that I need to have my soundcard not fail due to the IO
resource being claimed by PNPACPI. The fact that I needed it was new to
2.6.26 (but going back to 2.6.25 I all of a sudden also needed it there
which made me conclude that some BIOS reconfig had occured).
ACPI isn't doing odd things I hope?
Rene.
next prev parent reply other threads:[~2008-07-22 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 18:56 New conflict message in latest GIT Fabio Comolli
2008-07-22 20:00 ` Rene Herman [this message]
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
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=48863C46.1060704@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.