From: Matthias Hentges <oe@hentges.net>
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: Mon, 02 Oct 2006 19:00:47 +0200 [thread overview]
Message-ID: <1159808447.4652.6.camel@mhcln03> (raw)
In-Reply-To: <45206777.7020405@saville.com>
[-- Attachment #1.1: Type: text/plain, Size: 1152 bytes --]
Hello Wink,
Am Sonntag, den 01.10.2006, 18:12 -0700 schrieb Wink Saville:
> 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
>
> The first two appear to be from lines 215 & 217 of mmconfig.c (x86_64)
> and the other is from line 313 of intel-rng.c.
>
> Attached is my config file, I've tried both Generic-X86-64 and Intel
> EM64T for the Processor family.
>
I'm using the exact same motherboard and CPU and saw some hangs w/
enabled nvidia FB driver.
I'm using 2.6.18-mm1 currently w/o any major problems.
FWIW, I'm seeing identical error messages / warning , but they appear to
be harmless.
My .config for 2.6.18-mm1 is attached
HTH
--
Matthias 'CoreDump' Hentges
You can reach me in #openzaurus on Freenode.
My OS: Debian SID. Geek by Nature, Linux by Choice
[-- Attachment #1.2: config.gz --]
[-- Type: application/x-gzip, Size: 16050 bytes --]
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-02 17:01 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
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 [this message]
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=1159808447.4652.6.camel@mhcln03 \
--to=oe@hentges.net \
--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