Re: [BUG 2.6.29_rc8] BIOS Bug: CPU MTRRs don't cover all of memory, losing 0MB of RAM.

From: Yinghai Lu
Date: Mon Mar 16 2009 - 14:21:21 EST


On Mon, Mar 16, 2009 at 6:48 AM, Ozan Çağlayan <ozan@xxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/