Skip to contentSkip to conversation

2.6.28 git: WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:404 generic_get_mtrr+0xea/0x120()

DISCUSSION Dmitry Nezhevenko 4 participants 7 messages Nov 20, 2008 – Nov 24, 2008

lore
Share & tools
lore
#0 lore raw

Hi folks. This is first time I've tried 2.6.28-git (cloned git a few hours ago). And got this:

[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000007ffd0000 (usable)
[    0.000000]  BIOS-e820: 000000007ffd0000 - 000000007ffde000 (ACPI data)
[    0.000000]  BIOS-e820: 000000007ffde000 - 0000000080000000 (ACPI NVS)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
[    0.000000]  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[    0.000000] DMI present.
[    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working it around.
[    0.000000] last_pfn = 0x7ffd0 max_arch_pfn = 0x100000
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:404 generic_get_mtrr+0xea/0x120()
[    0.000000] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[    0.000000] Modules linked in:
[    0.000000] Pid: 0, comm: swapper Not tainted 2.6.28-rc5 #1
[    0.000000] Call Trace:
[    0.000000]  [<c012b86f>] warn_slowpath+0x6f/0x90
[    0.000000]  [<c0373031>] inet_rtm_newroute+0x21/0x50
[    0.000000]  [<c02593c4>] number+0x2b4/0x2c0
[    0.000000]  [<c0259ff3>] vsnprintf+0x393/0x670
[    0.000000]  [<c0144fd1>] up+0x11/0x40
[    0.000000]  [<c012c069>] release_console_sem+0x189/0x1d0
[    0.000000]  [<c01124da>] generic_get_mtrr+0xea/0x120
[    0.000000]  [<c04db85f>] mtrr_trim_uncached_memory+0x7d/0x374
[    0.000000]  [<c03a569a>] printk+0x17/0x1b
[    0.000000]  [<c011edbc>] pat_init+0x7c/0xa0
[    0.000000]  [<c01129ac>] post_set+0x1c/0x50
[    0.000000]  [<c03a569a>] printk+0x17/0x1b
[    0.000000]  [<c04d7b52>] e820_end_pfn+0xb5/0xd3
[    0.000000]  [<c04d6016>] setup_arch+0x518/0x802
[    0.000000]  [<c04d8cc7>] reserve_early_overlap_ok+0x3f/0x47
[    0.000000]  [<c04cf5dc>] start_kernel+0x58/0x334
[    0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
[    0.000000] kernel direct mapping tables up to 377fe000 @ 10000-16000

Can I just ignore this?

Signature · 1 line
WBR, Dmitry
#1 lore raw
Quoted 42 lines · Dmitry Nezhevenko

Hi folks. This is first time I've tried 2.6.28-git (cloned git a few hours ago). And got this:

[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000007ffd0000 (usable)
[    0.000000]  BIOS-e820: 000000007ffd0000 - 000000007ffde000 (ACPI data)
[    0.000000]  BIOS-e820: 000000007ffde000 - 0000000080000000 (ACPI NVS)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
[    0.000000]  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[    0.000000] DMI present.
[    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working it around.
[    0.000000] last_pfn = 0x7ffd0 max_arch_pfn = 0x100000
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:404 generic_get_mtrr+0xea/0x120()
[    0.000000] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[    0.000000] Modules linked in:
[    0.000000] Pid: 0, comm: swapper Not tainted 2.6.28-rc5 #1
[    0.000000] Call Trace:
[    0.000000]  [<c012b86f>] warn_slowpath+0x6f/0x90
[    0.000000]  [<c0373031>] inet_rtm_newroute+0x21/0x50
[    0.000000]  [<c02593c4>] number+0x2b4/0x2c0
[    0.000000]  [<c0259ff3>] vsnprintf+0x393/0x670
[    0.000000]  [<c0144fd1>] up+0x11/0x40
[    0.000000]  [<c012c069>] release_console_sem+0x189/0x1d0
[    0.000000]  [<c01124da>] generic_get_mtrr+0xea/0x120
[    0.000000]  [<c04db85f>] mtrr_trim_uncached_memory+0x7d/0x374
[    0.000000]  [<c03a569a>] printk+0x17/0x1b
[    0.000000]  [<c011edbc>] pat_init+0x7c/0xa0
[    0.000000]  [<c01129ac>] post_set+0x1c/0x50
[    0.000000]  [<c03a569a>] printk+0x17/0x1b
[    0.000000]  [<c04d7b52>] e820_end_pfn+0xb5/0xd3
[    0.000000]  [<c04d6016>] setup_arch+0x518/0x802
[    0.000000]  [<c04d8cc7>] reserve_early_overlap_ok+0x3f/0x47
[    0.000000]  [<c04cf5dc>] start_kernel+0x58/0x334
[    0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
[    0.000000] kernel direct mapping tables up to 377fe000 @ 10000-16000
Quoted 1 line

Can I just ignore this?

Hm, not sure (added some CCs).

#2 lore raw
Quoted 43 lines · Rafael J. Wysocki
Quoted 42 lines · Dmitry Nezhevenko

Hi folks. This is first time I've tried 2.6.28-git (cloned git a few hours ago). And got this:

[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000007ffd0000 (usable)
[    0.000000]  BIOS-e820: 000000007ffd0000 - 000000007ffde000 (ACPI data)
[    0.000000]  BIOS-e820: 000000007ffde000 - 0000000080000000 (ACPI NVS)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
[    0.000000]  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[    0.000000] DMI present.
[    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working it around.
[    0.000000] last_pfn = 0x7ffd0 max_arch_pfn = 0x100000
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] ------------[ cut here ]------------
[    0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:404 generic_get_mtrr+0xea/0x120()
[    0.000000] mtrr: your BIOS has set up an incorrect mask, fixing it up.
[    0.000000] Modules linked in:
[    0.000000] Pid: 0, comm: swapper Not tainted 2.6.28-rc5 #1
[    0.000000] Call Trace:
[    0.000000]  [<c012b86f>] warn_slowpath+0x6f/0x90
[    0.000000]  [<c0373031>] inet_rtm_newroute+0x21/0x50
[    0.000000]  [<c02593c4>] number+0x2b4/0x2c0
[    0.000000]  [<c0259ff3>] vsnprintf+0x393/0x670
[    0.000000]  [<c0144fd1>] up+0x11/0x40
[    0.000000]  [<c012c069>] release_console_sem+0x189/0x1d0
[    0.000000]  [<c01124da>] generic_get_mtrr+0xea/0x120
[    0.000000]  [<c04db85f>] mtrr_trim_uncached_memory+0x7d/0x374
[    0.000000]  [<c03a569a>] printk+0x17/0x1b
[    0.000000]  [<c011edbc>] pat_init+0x7c/0xa0
[    0.000000]  [<c01129ac>] post_set+0x1c/0x50
[    0.000000]  [<c03a569a>] printk+0x17/0x1b
[    0.000000]  [<c04d7b52>] e820_end_pfn+0xb5/0xd3
[    0.000000]  [<c04d6016>] setup_arch+0x518/0x802
[    0.000000]  [<c04d8cc7>] reserve_early_overlap_ok+0x3f/0x47
[    0.000000]  [<c04cf5dc>] start_kernel+0x58/0x334
[    0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
[    0.000000] kernel direct mapping tables up to 377fe000 @ 10000-16000
Quoted 1 line
Quoted 1 line

Can I just ignore this?

can we get whole boot message? also cat /proc/mtrr

YH

#3 lore raw
Quoted 4 lines · Yinghai Lu

can we get whole boot message? also cat /proc/mtrr

YH

dmesg: http://inhex.net/dion/tmp/dmesg-2.6.28-rc5.txt

/proc/mtrr:
reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg04: base=0x0000f8000 ( 0MB), size= 32KB, count=1: write-protect
reg05: base=0x0000dc000 ( 0MB), size= 8KB, count=1: write-back

Same message exists in 2.6.27 dmesg:
mtrr: your BIOS has set up an incorrect mask, fixing it up.

However it isn't warning.

Signature · 1 line
WBR, Dmitry
#4 lore raw
Quoted 4 lines · Dmitry Nezhevenko
Quoted 3 lines · Yinghai Lu

can we get whole boot message? also cat /proc/mtrr

Quoted 8 lines
Quoted 1 line

YH

dmesg: http://inhex.net/dion/tmp/dmesg-2.6.28-rc5.txt

/proc/mtrr:
reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg04: base=0x0000f8000 ( 0MB), size= 32KB, count=1: write-protect
reg05: base=0x0000dc000 ( 0MB), size= 8KB, count=1: write-back

so that patch workaround your BIOS setup with mtrr mask setting.

YH

#5 lore raw
Quoted 7 lines · Yinghai Lu
Quoted 6 lines · Dmitry Nezhevenko
Quoted 4 lines · Yinghai Lu

can we get whole boot message? also cat /proc/mtrr

YH

Quoted 8 lines
Quoted 6 lines

dmesg: http://inhex.net/dion/tmp/dmesg-2.6.28-rc5.txt

/proc/mtrr:
reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg04: base=0x0000f8000 ( 0MB), size= 32KB, count=1: write-protect
reg05: base=0x0000dc000 ( 0MB), size= 8KB, count=1: write-back

so that patch workaround your BIOS setup with mtrr mask setting.

so the kernel was right to issue a warning.

Ingo

#6 lore raw
Quoted 9 lines · Ingo Molnar
Quoted 7 lines
Quoted 5 lines

/proc/mtrr:
reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg04: base=0x0000f8000 ( 0MB), size= 32KB, count=1: write-protect
reg05: base=0x0000dc000 ( 0MB), size= 8KB, count=1: write-back

so that patch workaround your BIOS setup with mtrr mask setting.

so the kernel was right to issue a warning.

Ok. Thanks.

Btw.. Should it really be a warning, that taints kernel? As I said, 2.6.27 has same message, however it's just printk().

Signature · 1 line
WBR, Dmitry