Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 1.0.7 detected a crash.
architecture: x86_64
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-22.el6.x86_64
package: kernel
reason: ------------[ cut here ]------------
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)
comment
-----
After GNOME login, I recieved this error
Running on Intel® Core™2 Quad CPU Q9400 @ 2.66 GHz, 3.7 GiB of memory
kerneloops
-----
------------[ cut here ]------------
WARNING: at drivers/pci/dmar.c:636 check_zero_address+0x158/0x1a4() (Not tainted)
Hardware name: HP xw4600 Workstation
Your BIOS is broken; DMAR reported at address fed90000 returns all ones!
BIOS vendor: Hewlett-Packard; Ver: 786F3 v01.21; Product Version:
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.32-22.el6.x86_64 #1
Call Trace:
[<ffffffff81067d43>] warn_slowpath_common+0x83/0xc0
[<ffffffff81067de1>] warn_slowpath_fmt+0x41/0x50
[<ffffffff818e86f7>] check_zero_address+0x158/0x1a4
[<ffffffff812ca2ab>] ? acpi_get_table_with_size+0x5a/0xb4
[<ffffffff814d08b5>] ? _etext+0x0/0x3
[<ffffffff818e8755>] detect_intel_iommu+0x12/0x91
[<ffffffff818c4363>] pci_iommu_alloc+0x5e/0x6c
[<ffffffff818d4ba7>] mem_init+0x19/0xec
[<ffffffff818bccb7>] start_kernel+0x20c/0x401
[<ffffffff818bc33a>] x86_64_start_reservations+0x125/0x129
[<ffffffff818bc438>] x86_64_start_kernel+0xfa/0x109
Comment 2RHEL Program Management
2010-05-04 08:30:21 UTC
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.
(In reply to comment #3)
> Looks like a hardware error not a bug, so we should probably drop the WARN_ON
> and the dump_stack() so abrt isn't triggered.
Agreed.
P.
Let's actually use this BZ to introduce the world (well ... the RH world) to FW_BUG, FW_INFO, and FW_WARN as well as TAINT_FIRMWARE_WORKAROUND.
P.
Comment 9RHEL Program Management
2010-10-05 01:50:30 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Comment 10Aristeu Rozanski
2010-12-13 15:07:40 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0542.html