From: Yinghai Lu <yinghai@kernel.org>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.29_rc8] BIOS Bug: CPU MTRRs don't cover all of memory, losing 0MB of RAM.
Date: Mon, 16 Mar 2009 11:21:09 -0700 [thread overview]
Message-ID: <86802c440903161121s3ba18abaiaa3ccf6847e0eafe@mail.gmail.com> (raw)
In-Reply-To: <49BE58BA.1000907@pardus.org.tr>
On Mon, Mar 16, 2009 at 6:48 AM, Ozan Çağlayan <ozan@pardus.org.tr> wrote:
> Hi,
>
> Just compiled and tried to boot it on an HP ProLiant DL580 G5. Here's the
> interesting part:
>
> ..
> -- last_pfn = 0x82ffff max_arch_pfn = 0x1000000
> x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 0MB of RAM.
> ------------[ cut here ]------------
> WARNING: at arch/x86/kernel/cpu/mtrr/main.c:1655 mtrr_trim_uncached_memory+0x2a9/0x2cd()
> Hardware name: ProLiant DL580 G5
> Modules linked in:
> Pid: 0, comm: swapper Not tainted 2.6.29_rc8-115 #1
> Call Trace:
> [<c013134d>] warn_slowpath+0x71/0xa8
> [<c039971c>] ? _spin_unlock_irqrestore+0x19/0x1f
> [<c039971c>] ? _spin_unlock_irqrestore+0x19/0x1f
> [<c01319c4>] ? release_console_sem+0x185/0x1b2
> [<c0131e49>] ? vprintk+0x280/0x2a5
> [<c03973da>] ? printk+0xf/0x15
> [<c053423f>] mtrr_trim_uncached_memory+0x2a9/0x2cd
> [<c052f4bd>] setup_arch+0x439/0x99e
> [<c01319c4>] ? release_console_sem+0x185/0x1b2
> [<c0131e49>] ? vprintk+0x280/0x2a5
> [<c0531b37>] ? __reserve_early+0xe4/0xf8
> [<c03973da>] ? printk+0xf/0x15
> [<c052b5b6>] start_kernel+0x7b/0x345
> [<c052b085>] __init_begin+0x85/0x8d
> ---[ end trace 4eaa2a86a8e2da22 ]---
> update e820 for mtrr
> ..
>
> This is a quite generic x86 desktop kernel with only the
> following differences for the server:
>
> CONFIG_X86_GENERICARCH=y
> CONFIG_X86_BIGSMP=y
> CONFIG_MCORE2=y
> CONFIG_HIGHMEM64G=y
> # CONFIG_X86_GENERIC is not set
>
> I didn't want to add full dmesg and config for not flooding the e-mail but
> if you need them or other output/information, i can send them.
>
can you check tip/master?
http://people.redhat.com/mingo/tip.git/readme.txt
and post boot log.
YH
next prev parent reply other threads:[~2009-03-16 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 13:48 Ozan Çağlayan
2009-03-16 18:21 ` Yinghai Lu [this message]
2009-03-16 20:17 ` Ozan Çağlayan
2009-03-16 22:00 ` Yinghai Lu
2009-03-16 22:42 ` Ozan Çağlayan
2009-03-16 22:52 ` Yinghai Lu
2009-03-17 9:43 ` Ingo Molnar
2009-03-16 23:33 ` [PATCH] x86: workaround system with stange var MTRR -v2 Yinghai Lu
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=86802c440903161121s3ba18abaiaa3ccf6847e0eafe@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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®