From: Andi Kleen <ak@suse.de>
To: Wink Saville <wink@saville.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved with 2.6.18 kernel
Date: 02 Oct 2006 11:54:02 +0200 [thread overview]
Message-ID: <p733ba7hwlh.fsf@verdi.suse.de> (raw)
In-Reply-To: <45206777.7020405@saville.com>
Wink Saville <wink@saville.com> writes:
> I'm trying to build the 2.6.18 kernel for a Intel Core 2 Duo 2.4GHZ in
> a Asus P5W DH Deluxe Motherboard which has a 975 chip set. It does
> work when booting from a 2.6.15-27 kernel installed from Ubuntu 2.06
> LTS.
>
> When failing I get three messages on the screen:
>
> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> PCI: Not using MMCONFIG
> Intel-rng: FWH not detected
Can you boot with initcall_debug and report the complete output?
-Andi
next prev parent reply other threads:[~2006-10-02 9:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 1:12 PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved with 2.6.18 kernel Wink Saville
2006-10-02 9:54 ` Andi Kleen [this message]
2006-10-02 15:10 ` Wink Saville
2006-10-02 15:22 ` Andi Kleen
2006-10-02 16:08 ` Wink Saville
2006-10-02 17:00 ` Matthias Hentges
2006-10-03 4:12 ` Wink Saville
2006-10-03 12:23 ` Matthias Hentges
2006-10-03 16:33 ` Wink Saville
2006-10-03 13:30 ` Arjan van de Ven
2006-10-03 16:37 ` Wink Saville
2006-10-04 16:26 ` Hang in fb_notifier_call_chain with nvidia framebuffer Wink Saville
2006-10-08 6:01 ` Andrew Morton
2006-10-08 8:14 ` Wink Saville
2006-10-08 9:07 ` Andrew Morton
2006-10-08 18:06 ` Wink Saville
2006-10-05 6:28 ` 2.6.18 Hang in fb_notifier_call_chain while booting " Wink Saville
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=p733ba7hwlh.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wink@saville.com \
/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