From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Dmitry Nezhevenko <dion@inhex.net>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Yinghai Lu <yinghai@kernel.org>,
Venki Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: 2.6.28 git: WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:404 generic_get_mtrr+0xea/0x120()
Date: Sat, 22 Nov 2008 21:44:31 +0100 [thread overview]
Message-ID: <200811222144.31812.rjw@sisk.pl> (raw)
In-Reply-To: <20081120092239.GA16613@laptop.local>
On Thursday, 20 of November 2008, Dmitry Nezhevenko wrote:
> 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?
Hm, not sure (added some CCs).
next prev parent reply other threads:[~2008-11-22 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 9:22 Dmitry Nezhevenko
2008-11-22 20:44 ` Rafael J. Wysocki [this message]
2008-11-22 21:43 ` Yinghai Lu
2008-11-23 9:57 ` Dmitry Nezhevenko
2008-11-23 23:41 ` Yinghai Lu
2008-11-23 23:42 ` Ingo Molnar
2008-11-24 5:59 ` Dmitry Nezhevenko
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=200811222144.31812.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=dion@inhex.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=venkatesh.pallipadi@intel.com \
--cc=yinghai@kernel.org \
/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®