From: Frans Pop <elendil@planet.nl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, Rene Herman <rene.herman@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: [bisected][resend] pnp: Huge number of "io resource overlap" messages
Date: Thu, 11 Sep 2008 18:58:47 +0200 [thread overview]
Message-ID: <200809111858.48872.elendil@planet.nl> (raw)
In-Reply-To: <200809101534.27688.bjorn.helgaas@hp.com>
[-- Attachment #1: Type: text/plain, Size: 2918 bytes --]
On Wednesday 10 September 2008, Bjorn Helgaas wrote:
> Are there any BIOS setup options related to them?
The BIOS setup has no options to enable/disable these devices.
The only option I can see that could be relevant is:
=CONFIGURATION=
Device Config. = [Setup by OS | All Devices]
This was set to "Setup by OS".
[me reboots with that option changed]
Hmm. If I change that option to "All devices" the "io resource overlap"
messages disappear!
> If I were trying to figure out where we assign resources, I'd probably
> boot with "pci=earlydump" and sprinkle calls to early_dump_pci_device()
> in pcibios_resource_survey(), and drill down from there.
Attached are two logs with PCI debugging enabled and extra "early dumps"
included in the following places (changes in includes omitted):
+++ b/arch/x86/pci/i386.c
@@ -31,6 +31,7 @@
@@ -224,9 +225,11 @@ static int __init pcibios_assign_resources(void)
void __init pcibios_resource_survey(void)
{
DBG("PCI: Allocating resources\n");
+ early_dump_pci_devices();
pcibios_allocate_bus_resources(&pci_root_buses);
pcibios_allocate_resources(0);
pcibios_allocate_resources(1);
+ early_dump_pci_devices();
}
+++ b/sound/pci/intel8x0.c
@@ -41,6 +41,7 @@
@@ -2799,6 +2800,7 @@ static int __devinit snd_intel8x0_create(struct snd_card *card,
if ((err = pci_enable_device(pci)) < 0)
return err;
+ early_dump_pci_devices();
chip = kzalloc(sizeof(*chip), GFP_KERNEL);
if (chip == NULL) {
The "Setup by OS" log does show the following _after_ the PNP quirks:
pci 0000:00:1f.5: BAR 2: got res [0x2c080800-0x2c0809ff] bus [0x2c080800-0x2c0809ff] flags 0x20200
pci 0000:00:1f.5: BAR 2: moved to bus [0x2c080800-0x2c0809ff] flags 0x20200
pci 0000:00:1f.5: BAR 0: got res [0x1000-0x10ff] bus [0x1000-0x10ff] flags 0x20101
pci 0000:00:1f.5: BAR 0: moved to bus [0x1000-0x10ff] flags 0x20101
pci 0000:00:1f.5: BAR 3: got res [0x2c080a00-0x2c080aff] bus [0x2c080a00-0x2c080aff] flags 0x20200
pci 0000:00:1f.5: BAR 3: moved to bus [0x2c080a00-0x2c080aff] flags 0x20200
pci 0000:00:1f.6: BAR 0: got res [0x1400-0x14ff] bus [0x1400-0x14ff] flags 0x20101
pci 0000:00:1f.6: BAR 0: moved to bus [0x1400-0x14ff] flags 0x20101
pci 0000:00:1f.6: BAR 1: got res [0x1800-0x187f] bus [0x1800-0x187f] flags 0x20101
pci 0000:00:1f.6: BAR 1: moved to bus [0x1800-0x187f] flags 0x20101
pci 0000:00:1f.5: BAR 1: got res [0x1880-0x18bf] bus [0x1880-0x18bf] flags 0x20101
pci 0000:00:1f.5: BAR 1: moved to bus [0x1880-0x18bf] flags 0x20101
The diff between the logs is quite clear and illumination. It also shows
differences in the "early dumps". Hope you can tell more from that.
If you'd like me to do more instrumentation, please let me know.
I guess I'll leave that BIOS option in the "All devices" setting. However,
I doubt I'm the only person who has it in the "Setup by OS" setting.
Cheers,
FJP
[-- Attachment #2: all-devices.dmesg.gz --]
[-- Type: application/x-gzip, Size: 10681 bytes --]
[-- Attachment #3: setup-by-os.dmesg.gz --]
[-- Type: application/x-gzip, Size: 11469 bytes --]
next prev parent reply other threads:[~2008-09-11 16:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 10:50 [bisected][resend] pnp: Huge number of "io resource overlap" messages Frans Pop
2008-09-09 11:22 ` Rene Herman
2008-09-09 15:30 ` Bjorn Helgaas
2008-09-09 16:26 ` Frans Pop
2008-09-09 17:40 ` Bjorn Helgaas
2008-09-09 18:31 ` Rene Herman
2008-09-18 5:10 ` Bjorn Helgaas
2008-09-20 23:49 ` Frans Pop
2008-09-20 23:56 ` Bjorn Helgaas
2008-09-26 21:40 ` [Bug #11550] " Bjorn Helgaas
2008-09-27 15:16 ` Frans Pop
2008-09-27 20:53 ` Ingo Molnar
2009-03-04 20:17 ` Frans Pop
2009-03-04 21:53 ` Bjorn Helgaas
2009-03-20 2:07 ` Jesse Barnes
2009-03-23 15:46 ` Bjorn Helgaas
2008-09-10 7:39 ` [bisected][resend] " Frans Pop
2008-09-10 21:34 ` Bjorn Helgaas
2008-09-11 16:58 ` Frans Pop [this message]
2008-11-07 9:51 ` Frans Pop
2008-11-07 10:00 ` Ingo Molnar
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=200809111858.48872.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=rene.herman@gmail.com \
--cc=tglx@linutronix.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