Bug 860901 - [abrt]: WARNING: at arch/x86/kernel/cpu/mtrr/cleanup.c:971 mtrr_trim_uncached_memory+0x28a/0x2b2()
Summary: [abrt]: WARNING: at arch/x86/kernel/cpu/mtrr/cleanup.c:971 mtrr_trim_uncached...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a4664d4beee71ad14923e391bfc...
: 926877 1196482 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-27 04:22 UTC by Pavel Mlčoch
Modified: 2015-02-26 13:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-01 19:40:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pavel Mlčoch 2012-09-27 04:22:12 UTC
Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
cmdline:        BOOT_IMAGE=/vmlinuz-3.6.0-0.rc6.git0.2.fc18.x86_64 root=UUID=444d27ef-70e0-4d44-966f-4b4da485a36a ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 rhgb quiet
kernel:         3.6.0-0.rc6.git0.2.fc18.x86_64

backtrace:
:WARNING: at arch/x86/kernel/cpu/mtrr/cleanup.c:971 mtrr_trim_uncached_memory+0x28a/0x2b2()
:Hardware name: MS-7250
:Modules linked in:
:Pid: 0, comm: swapper Not tainted 3.6.0-0.rc6.git0.2.fc18.x86_64 #1
:Call Trace:
: [<ffffffff8106788f>] warn_slowpath_common+0x7f/0xc0
: [<ffffffff810678ea>] warn_slowpath_null+0x1a/0x20
: [<ffffffff81f15e8f>] mtrr_trim_uncached_memory+0x28a/0x2b2
: [<ffffffff81f0f19d>] setup_arch+0x527/0xb4c
: [<ffffffff816d1047>] ? printk+0x61/0x63
: [<ffffffff81f09956>] start_kernel+0xe3/0x408
: [<ffffffff81f09356>] x86_64_start_reservations+0x131/0x135
: [<ffffffff81f0945a>] x86_64_start_kernel+0x100/0x10f

Comment 1 Josh Boyer 2012-11-13 15:18:19 UTC
This seems to be related to a BIOS bug and is just a warning.  You should see something like this in dmesg:

WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing XXXXMB of RAM.

I don't think there's anything we can really do here.

Comment 2 Josh Boyer 2013-04-03 19:26:22 UTC
*** Bug 926877 has been marked as a duplicate of this bug. ***

Comment 3 Josh Boyer 2015-02-26 13:29:40 UTC
*** Bug 1196482 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.