Bug 585786

Summary:	abrt got the wrong crash message from kernel logs.
Product:	Red Hat Enterprise Linux 6	Reporter:	Eric Sandeen <esandeen>
Component:	abrt	Assignee:	Denys Vlasenko <dvlasenk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michal Nowak <mnowak>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	ahecox, dvlasenk, esandeen, gavin, jmoskovc, jozwicki, kklic, mnowak, npajkovs, ohudlick
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	abrt_hash:1931063738
Fixed In Version:	abrt-1.1.1-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	585596	Environment:
Last Closed:	2010-07-02 18:47:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	585596
Bug Blocks:

Comment 2 RHEL Program Management 2010-04-26 04:11:34 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.

Comment 3 Denys Vlasenko 2010-04-30 11:46:42 UTC

Fixed in newer versions - looks for "WARNING: at" now

Comment 6 Michal Nowak 2010-05-14 10:28:29 UTC

OLD: abrt-1.0.7-2.el6.x86_64  N/A
and text of backtrace starts like this:

EDAC amd64: WARNING: ECC is disabled by BIOS. Module will NOT be loaded.
Either Enable ECC in the BIOS, or set 'ecc_enable_override'.
Also, use of the override can cause unknown side effects.
amd64_edac: probe of 0000:00:18.2 failed with error -22
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
...

NEW: abrt-1.1.0-1.el6.x86_64  BUG: Bad page state in process metacity  pfn:100000

VERIFIED

Comment 7 releng-rhel@redhat.com 2010-07-02 18:47:25 UTC

Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.