linux-kernel - Re: MCFG ACPI patch in git-x86 causes boot regression

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <4782CBF2.6030208@shaw.ca>
Date:	Mon, 07 Jan 2008 19:03:46 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>, mingo@...e.hu,
	tglx@...utronix.de, linux-kernel@...r.kernel.org, akpm@...l.org,
	rajesh.shah@...el.com, greg@...ah.com
Subject: Re: MCFG ACPI patch in git-x86 causes boot regression

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).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/