From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Frans Pop <elendil@planet.nl>
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: Wed, 10 Sep 2008 15:34:27 -0600 [thread overview]
Message-ID: <200809101534.27688.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200809100939.17045.elendil@planet.nl>
On Wednesday 10 September 2008 01:39:15 am Frans Pop wrote:
> On Tuesday 09 September 2008, Bjorn Helgaas wrote:
> > If the PCI device isn't fully initialized, it doesn't seem right to
> > check it for resource conflicts. But I don't know how to tell that.
> >
> > Can you figure out where the 1f.5 and 1f.6 resources get assigned?
>
> If the approach suggested by Rene feasible or would you still like me to
> get this info? In the last case I'll need some pointers where exactly to
> look.
Checking pci_resource_start() for zero would certainly work
in your particular case. But I don't know enough about PCI to
know whether that's always safe.
Matthew Wilcox suggested that the BARs may be zero because the BIOS
has "disabled" those two devices. Are there any BIOS setup options
related to them? I know you need to use at least the sound device,
so I'm not suggesting that Linux should leave it disabled; I'm just
trying to learn more about the situation.
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.
Bjorn
next prev parent reply other threads:[~2008-09-10 21:34 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 [this message]
2008-09-11 16:58 ` Frans Pop
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=200809101534.27688.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=elendil@planet.nl \
--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 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.