From: Arjan van de Ven <arjan@linux.intel.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: greg@kroah.com, linux-acpi@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
akpm@osdl.org, mingo@redhat.com,
Reuben Farrelly <reuben-lkml@reub.net>,
"Randy.Dunlap" <rdunlap@xenotime.net>
Subject: RE: 2.6.18-rc1-mm1
Date: Mon, 10 Jul 2006 10:48:49 +0200 [thread overview]
Message-ID: <1152521329.4874.3.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB6ECF9C0@hdsmsx411.amr.corp.intel.com>
On Sun, 2006-07-09 at 13:47 -0400, Brown, Len wrote:
> >> 2. Onto some more minor warnings:
> >>
> >> ACPI: bus type pci registered
> >> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> >> PCI: Not using MMCONFIG.
> >> PCI: Using configuration type 1
> >> ACPI: Interpreter enabled
> >>
> >> Is there any way to verify that there really is a BIOS bug
> >there? If it is, is there anyone within Intel or are there any
> >known contacts
> >who can push and poke > to get this looked at/fixed?
> >(It's a new Intel board, I'd hope they could get it right..).
>
> Arjan should probably comment on that one.
I could.. but please next time if you want to CC me use an email address
I actually read ;)
Greg has a patch to relax this check, and Rajesh has a further patch to
relax it more. However, to a large degree we cannot relax it too much
without breaking the reason this check is there: detect a buggy MCFG
table and not crash and burn later on, but rather just not use it.
next prev parent reply other threads:[~2006-07-10 8:49 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 17:47 2.6.18-rc1-mm1 Brown, Len
2006-07-10 8:48 ` Arjan van de Ven [this message]
2006-07-11 23:00 ` 2.6.18-rc1-mm1 Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 9:43 2.6.18-rc1-mm1 Etienne Lorrain
2006-07-12 18:12 2.6.18-rc1-mm1 Chuck Ebbert
2006-07-11 2:58 2.6.18-rc1-mm1 Chuck Ebbert
2006-07-11 3:15 ` 2.6.18-rc1-mm1 Randy.Dunlap
2006-07-11 6:00 ` 2.6.18-rc1-mm1 Cedric Le Goater
2006-07-12 18:30 ` 2.6.18-rc1-mm1 Badari Pulavarty
2006-07-11 3:26 ` 2.6.18-rc1-mm1 H. Peter Anvin
2006-07-09 9:11 2.6.18-rc1-mm1 Andrew Morton
2006-07-09 10:20 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-09 10:26 ` 2.6.18-rc1-mm1 Fabio Comolli
2006-07-09 10:45 ` 2.6.18-rc1-mm1 Andrew Morton
2006-07-09 12:37 ` 2.6.18-rc1-mm1 Nick Piggin
2006-07-09 12:55 ` 2.6.18-rc1-mm1 Nick Piggin
2006-07-10 8:50 ` 2.6.18-rc1-mm1 Arjan van de Ven
2006-07-09 10:32 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-09 10:33 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-09 10:52 ` 2.6.18-rc1-mm1 Andrew Morton
2006-07-09 21:06 ` 2.6.18-rc1-mm1 Arjan van de Ven
2006-07-10 7:40 ` 2.6.18-rc1-mm1 Ingo Molnar
2006-07-10 9:22 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-10 9:25 ` 2.6.18-rc1-mm1 Ingo Molnar
2006-07-10 10:01 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-10 10:37 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-10 10:37 ` 2.6.18-rc1-mm1 Ingo Molnar
2006-07-10 10:57 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-09 11:02 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-09 11:13 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-09 12:10 ` 2.6.18-rc1-mm1 Andrew Morton
2006-07-09 13:19 ` 2.6.18-rc1-mm1 Michal Piotrowski
2006-07-09 11:22 ` 2.6.18-rc1-mm1 Reuben Farrelly
2006-07-09 12:22 ` 2.6.18-rc1-mm1 Andrew Morton
2006-07-09 12:56 ` 2.6.18-rc1-mm1 Alan Cox
2006-07-09 14:21 ` 2.6.18-rc1-mm1 Reuben Farrelly
2006-07-09 16:29 ` 2.6.18-rc1-mm1 Jeff Garzik
2006-07-09 18:35 ` 2.6.18-rc1-mm1 Andi Kleen
2006-07-11 19:37 ` 2.6.18-rc1-mm1 Greg KH
2006-07-09 21:10 ` 2.6.18-rc1-mm1 john stultz
2006-07-09 17:33 ` 2.6.18-rc1-mm1 Randy.Dunlap
2006-07-09 21:40 ` 2.6.18-rc1-mm1 Andrew Morton
2006-07-10 4:56 ` 2.6.18-rc1-mm1 Randy.Dunlap
2006-07-10 5:01 ` 2.6.18-rc1-mm1 Andrew Morton
2006-07-10 5:35 ` 2.6.18-rc1-mm1 Randy.Dunlap
2006-07-09 17:28 ` 2.6.18-rc1-mm1 Dominik Karall
2006-07-09 20:24 ` 2.6.18-rc1-mm1 Andrew Morton
2006-07-10 7:11 ` 2.6.18-rc1-mm1 Mauro Carvalho Chehab
2006-07-10 22:25 ` 2.6.18-rc1-mm1 Dominik Karall
2006-07-13 22:10 ` 2.6.18-rc1-mm1 Dominik Karall
2006-07-09 19:24 ` 2.6.18-rc1-mm1 Valdis.Kletnieks
2006-07-09 21:11 ` 2.6.18-rc1-mm1 john stultz
2006-07-10 0:33 ` 2.6.18-rc1-mm1 J.A. Magallón
2006-07-10 10:02 ` 2.6.18-rc1-mm1 Alan Cox
2006-07-10 1:10 ` 2.6.18-rc1-mm1 Brice Goglin
2006-07-10 15:22 ` 2.6.18-rc1-mm1 Rafael J. Wysocki
2006-07-10 22:21 ` 2.6.18-rc1-mm1 J.A. Magallón
2006-07-12 20:45 ` 2.6.18-rc1-mm1 Reuben Farrelly
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=1152521329.4874.3.camel@laptopd505.fenrus.org \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=reuben-lkml@reub.net \
/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
all inboxes | Powered by JetHome®