Bug 869163 - [abrt]: WARNING: at arch/x86/kernel/cpu/mtrr/cleanup.c:971 mtrr_trim_uncached_memory+0x285/0x2a3()
[abrt]: WARNING: at arch/x86/kernel/cpu/mtrr/cleanup.c:971 mtrr_trim_uncached...
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
17
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
abrt_hash:ae649d80f9bf4bec0a916551362...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-23 03:43 EDT by Security32
Modified: 2012-10-23 08:40 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-10-23 08:40:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Security32 2012-10-23 03:43:00 EDT
Additional info:
libreport version: 2.0.16
abrt_version:   2.0.13
cmdline:        BOOT_IMAGE=/boot/vmlinuz-3.3.4-5.fc17.i686 root=UUID=1c6de466-feeb-4aca-8c15-5fbfb370ccbb ro LANG=ru_RU.UTF-8 rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=False rd.luks=0 KEYTABLE=ru rhgb quiet
kernel:         3.3.4-5.fc17.i686

backtrace:
:WARNING: at arch/x86/kernel/cpu/mtrr/cleanup.c:971 mtrr_trim_uncached_memory+0x285/0x2a3()
:Hardware name: To Be Filled By O.E.M.
:Modules linked in:
:Pid: 0, comm: swapper Not tainted 3.3.4-5.fc17.i686 #1
:Call Trace:
: [<c0920038>] ? printk+0x2d/0x2f
: [<c04372f2>] warn_slowpath_common+0x72/0xa0
: [<c0bbb535>] ? mtrr_trim_uncached_memory+0x285/0x2a3
: [<c0bbb535>] ? mtrr_trim_uncached_memory+0x285/0x2a3
: [<c0437342>] warn_slowpath_null+0x22/0x30
: [<c0bbb535>] mtrr_trim_uncached_memory+0x285/0x2a3
: [<c0bb4f73>] setup_arch+0x598/0xafd
: [<c0920038>] ? printk+0x2d/0x2f
: [<c0bb24b2>] start_kernel+0xb8/0x35d
: [<c0bb2078>] i386_start_kernel+0x78/0x7d
Comment 1 Josh Boyer 2012-10-23 08:40:16 EDT
3.3 is very stale at this point.  If you can recreate with the 3.6.x updates please reopen.

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