From: Robert Hancock <hancockr@shaw.ca>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Andi Kleen <andi@firstfloor.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 17:31:58 -0600 [thread overview]
Message-ID: <4782B66E.8050400@shaw.ca> (raw)
In-Reply-To: <200801071452.15045.jbarnes@virtuousgeek.org>
Jesse Barnes wrote:
> On Monday, January 07, 2008 2:47 Andi Kleen wrote:
>> This patch
>>
>> commit c5182babd1d0706f1294af7b8dbf64e378b066bb
>> Author: Robert Hancock <hancockr@shaw.ca>
>> Date: Sat Jan 5 13:26:32 2008 +0100
>>
>> x86: validate against ACPI motherboard resources
>>
>> ...
>>
>> recently added to git-x86 causes one of my Intel test systems to not
>> boot unless I specify pci=conf1.
>>
>> ...
>> ACPI: EC: Look up EC in DSDT
>> ACPI: Interpreter enabled
>> ACPI: (supports S0 S3 S4 S5)
>> ACPI: Using IOAPIC for interrupt routing
>> 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
>> ACPI: PCI Root Bridge [PCI0] (0000:00)
>> <hang>
>>
>> The system is a SDV, but I believe production level.
>> DSDT is available at http://firstfloor.org/~andi/dsdt.dsl
>>
>> On previous kernels the MCFG was rejected because it wasn't e820
>> reserved:
>
> Yep, this patch (as was stated many times) requires other fixes to PCI
> probing--either disabling decode, not using mmconfig unless absolutely
> required, or one of the other discussed changes. I'm not sure why it
> was pushed before one of those changes went in.
I believe that such a change is in Greg KH's tree. So -mm (with both
trees) would probably work.
next prev parent reply other threads:[~2008-01-07 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 22:47 Andi Kleen
[not found] ` <200801071452.15045.jbarnes@virtuousgeek.org>
2008-01-07 23:31 ` Robert Hancock [this message]
2008-01-08 1:01 ` Andi Kleen
2008-01-08 1:03 ` Robert Hancock
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=4782B66E.8050400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome