RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

abrt version: 1.1.4
architecture: x86_64
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-37.el6.x86_64
package: kernel
reason: WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140() (Not tainted)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
How to reproduce: not sure what events led to the crash

backtrace
-----
WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140() (Not tainted)
Hardware name: 649325U
mtrr: your BIOS has set up an incorrect mask, fixing it up.
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.32-37.el6.x86_64 #1
Call Trace:
[<ffffffff8106a703>] warn_slowpath_common+0x83/0xc0
[<ffffffff8106a7a1>] warn_slowpath_fmt+0x41/0x50
[<ffffffff8102b9ee>] generic_get_mtrr+0x11e/0x140
[<ffffffff818e5bbb>] mtrr_cleanup+0x8c/0x405
[<ffffffff818e49f1>] ? get_mtrr_state+0x2ec/0x2fb
[<ffffffff818e4535>] mtrr_bp_init+0x1ab/0x1d2
[<ffffffff818dfeba>] setup_arch+0x4b8/0xa9e
[<ffffffff814d761d>] ? printk+0x41/0x44
[<ffffffff818dab75>] start_kernel+0xdc/0x40d
[<ffffffff818da33a>] x86_64_start_reservations+0x125/0x129
[<ffffffff818da438>] x86_64_start_kernel+0xfa/0x109

Created attachment 426294 [details]
File: backtrace

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

This warning points to a bad bios which has set up the mtrr values incorrectly.  The kernel was able to detect the bad setting and fix it.

Maybe FW_BUG is appropriate here ... but this is not a bug.

P.

*** Bug 651180 has been marked as a duplicate of this bug. ***

*** Bug 651180 has been marked as a duplicate of this bug. ***

Created attachment 478751 [details]
File: backtrace

Created attachment 492038 [details]
File: backtrace

Created attachment 501972 [details]
File: backtrace

Created attachment 510954 [details]
File: backtrace

Created attachment 522360 [details]
File: backtrace

Created attachment 523923 [details]
File: backtrace

Created attachment 527754 [details]
File: backtrace

Created attachment 528242 [details]
File: backtrace