From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Len Brown <len.brown@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Adam Belay <ambx1@neo.rr.com>
Subject: Re: ACPIPNP and too large IO resources
Date: Wed, 05 Jul 2006 22:53:46 +0200 [thread overview]
Message-ID: <44AC26DA.1010901@drzeus.cx> (raw)
In-Reply-To: <200607051047.40734.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
> Thanks for the report!
>
Np. Gave me an excuse to try out git bisect. ;)
> It sounds like this might be the same problem as
> http://bugzilla.kernel.org/show_bug.cgi?id=6292
>
> In short, you probably have a bridge device that consumes the
> entire 0x0-0xffff I/O port range and produces some or all of that
> range for downstream PNP devices. PNP doesn't know what to do
> with these windows that are both consumed by the bridge and made
> available to downstream devices, so it just marks them as being
> already reserved.
>
Ah, that explains things.
> Matthieu Castet wrote a nice patch (attached) that makes PNP just
> ignore those windows. Can you try it and see whether it fixes
> the problem you're seeing? This patch is already in -mm, but not
> yet in mainline. We might need to consider this patch as
> 2.6.18 material if it resolves your problem. I suspect many
> people will see the same problem.
>
The patch works nicely and removes all memory and io regions for the PCI
bridge but for the range 0xcf8-0xcff.
Thanks
Pierre
next prev parent reply other threads:[~2006-07-05 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 6:47 ACPIPNP and too large IO resources Pierre Ossman
2006-07-05 16:47 ` Bjorn Helgaas
2006-07-05 20:53 ` Pierre Ossman [this message]
2006-07-05 21:36 ` Bjorn Helgaas
2006-07-05 22:18 ` Andrew Morton
2006-07-06 15:29 ` Bjorn Helgaas
2006-07-07 1:03 ` Shaohua Li
2006-08-05 0:19 ` Pierre Ossman
2006-08-05 1:07 ` Andrew Morton
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=44AC26DA.1010901@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox