Comment 20 for bug 1111470

Revision history for this message
Bob Ball (bob-ball) wrote : Re: Precise kernel not bootable under Xen - alloc_l1_table

Interesting bit of the normal dmesg boot looks to be:

[ 0.000000] mtrr_cleanup: can not find optimal value
[ 0.000000] please specify mtrr_gran_size/mtrr_chunk_size
[ 0.000000] e820: update [mem 0xcf700000-0xffffffff] usable ==> reserved
[ 0.000000] e820: update [mem 0x228000000-0x22bffffff] usable ==> reserved
[ 0.000000] WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 64MB of RAM.
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: at /build/buildd/linux-lts-quantal-3.5.0/arch/x86/kernel/cpu/mtrr/cleanup.c:971 mtrr_trim_uncached_memory+0x299/0x2c0()
[ 0.000000] Hardware name:
[ 0.000000] Modules linked in:
[ 0.000000] Pid: 0, comm: swapper Not tainted 3.5.0-22-generic #34~precise1-Ubuntu
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff81052c9f>] warn_slowpath_common+0x7f/0xc0
[ 0.000000] [<ffffffff81052cfa>] warn_slowpath_null+0x1a/0x20
[ 0.000000] [<ffffffff81d002e7>] mtrr_trim_uncached_memory+0x299/0x2c0
[ 0.000000] [<ffffffff81cfa02b>] setup_arch+0x499/0x821
[ 0.000000] [<ffffffff81685ba6>] ? printk+0x61/0x63
[ 0.000000] [<ffffffff81cf3954>] start_kernel+0xd4/0x3d2
[ 0.000000] [<ffffffff81cf3397>] x86_64_start_reservations+0x131/0x135
[ 0.000000] [<ffffffff81cf3120>] ? early_idt_handlers+0x120/0x120
[ 0.000000] [<ffffffff81cf3468>] x86_64_start_kernel+0xcd/0xdc
[ 0.000000] ---[ end trace 056f32e7b63342ac ]---

I've attached the full dmesg incase there are other things that you want to see.