From: Robert Hancock <hancockr@shaw.ca>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
mingo@elte.hu, tglx@linutronix.de, linux-kernel@vger.kernel.org,
akpm@osdl.org, rajesh.shah@intel.com, greg@kroah.com
Subject: Re: MCFG ACPI patch in git-x86 causes boot regression
Date: Mon, 07 Jan 2008 19:03:46 -0600 [thread overview]
Message-ID: <4782CBF2.6030208@shaw.ca> (raw)
In-Reply-To: <20080108010110.GB16156@one.firstfloor.org>
Andi Kleen wrote:
> On Mon, Jan 07, 2008 at 05:31:58PM -0600, Robert Hancock wrote:
>> Jesse Barnes wrote:
>
> Hmm -- I didn't see Jesse's mail?
>
>> I believe that such a change is in Greg KH's tree. So -mm (with both
>> trees) would probably work.
>
> Yes 2.6.24-rc6-mm1 works, but plain git-x86 does not:
>
> PCI: MCFG configuration 0: base 4026531840 segment 0 buses 0 - 127
> PCI: MCFG area at f0000000 reserved in ACPI motherboard resources
> PCI: Using MMCONFIG at f0000000 - f7ffffff
At least, I thought it was in Greg's tree, not sure now.. This is the
patch in -mm:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc6/2.6.24-rc6-mm1/broken-out/pci-disable-decoding-during-sizing-of-bars.patch
Without this change a bunch of machines fail to boot even without the
MCFG change (since their MCFG was E820 reserved and so the old
validation check passed).
next prev parent reply other threads:[~2008-01-08 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 22:47 MCFG ACPI patch in git-x86 causes boot regression Andi Kleen
[not found] ` <200801071452.15045.jbarnes@virtuousgeek.org>
2008-01-07 23:31 ` Robert Hancock
2008-01-08 1:01 ` Andi Kleen
2008-01-08 1:03 ` Robert Hancock [this message]
2008-01-08 8:15 ` Ingo Molnar
2008-01-08 16:14 ` Andi Kleen
2008-01-08 16:27 ` Ingo Molnar
2008-01-08 19:02 ` Jesse Barnes
2008-01-08 8:13 ` 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=4782CBF2.6030208@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rajesh.shah@intel.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.