From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: You are fussing about bug reports, here is one. Seems like a shrug, but...
Date: Mon, 29 Dec 2008 14:37:21 -0600 [thread overview]
Message-ID: <49593501.1060705@shaw.ca> (raw)
In-Reply-To: <200812290952.54095.gene.heskett@gmail.com>
Gene Heskett wrote:
> 2.6.28.final, has existed most of the way through the 28-rc series. This ASUS
> mobo is a $250+ mobo, latest (working bios, the beta does work at all) and
> has a quad core Phenom with 4GB of dram on it.
>
> [ 0.000000] ------------[ cut here ]------------
> [ 0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:404
> generic_get_mtrr+0x11c/0x130()
> [ 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 #1
> [ 0.000000] Call Trace:
> [ 0.000000] [<c04267b6>] warn_slowpath+0x76/0x90
> [ 0.000000] [<c050dd97>] vsnprintf+0x2e7/0x680
> [ 0.000000] [<c042750b>] printk+0x1b/0x20
> [ 0.000000] [<c0419e7c>] pat_init+0x7c/0xa0
> [ 0.000000] [<c040e43c>] post_set+0x1c/0x50
> [ 0.000000] [<c0426f5d>] release_console_sem+0x18d/0x1c0
> [ 0.000000] [<c040ea8c>] generic_get_mtrr+0x11c/0x130
> [ 0.000000] [<c0712eda>] mtrr_trim_uncached_memory+0x7a/0x330
> [ 0.000000] [<c042750b>] printk+0x1b/0x20
> [ 0.000000] [<c070fd45>] e820_end_pfn+0xc5/0xf0
> [ 0.000000] [<c070e120>] setup_arch+0x420/0xb60
> [ 0.000000] [<c071126b>] reserve_early_overlap_ok+0x4b/0x60
> [ 0.000000] [<c07079c8>] start_kernel+0x58/0x2e0
> [ 0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
>
> What it seems to be is useless noise, and only ASUS knows if it will be fixed.
> As for reporting this to ASUS, has anyone a contact address?, their website
> has none that works.
Well, as it says it's a BIOS bug.. and potentially a rather serious one,
since bad MTRR settings can slow your system to a crawl by preventing
proper caching or prevent all RAM from being used properly. The code
that produces the warning fixes up the damage for you.
prev parent reply other threads:[~2008-12-29 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 14:52 You are fussing about bug reports, here is one. Seems like a shrug, but Gene Heskett
2008-12-29 17:03 ` Brad Campbell
2008-12-29 20:37 ` Robert Hancock [this message]
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=49593501.1060705@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.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