Bug 681234

Summary: [abrt] crash in kernel: general protection fault: 0000 [#1] SMP in radeon_read_ring_rptr
Product: Red Hat Enterprise Linux 6 Reporter: Red Hat Case Diagnostics <case-diagnostics>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: airlied, jwest
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1843067170
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-05 21:35:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 574377    
Bug Blocks:    
Attachments:
Description Flags
File: backtrace
none
File: backtrace
none
File: backtrace
none
File: backtrace none

Description Red Hat Case Diagnostics 2011-03-01 14:06:52 UTC 
+++ This bug was initially created as a clone of Bug 574377 +++

abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-0.51.rc7.git2.fc13.x86_64
package: kernel
reason: general protection fault: 0000 [#1] SMP
release: Fedora release 11 (Leonidas)

--- Additional comment from dvlasenk onWed Mar 17 12:21:01 EDT 2010 ---
Created attachment 400730 [details]
File: backtrace

--- Additional comment from dvlasenk onWed Mar 17 12:22:24 EDT 2010 ---
This bz was created for testing only
Comment 1 Red Hat Case Diagnostics 2011-03-01 14:07:13 UTC 
Created attachment 481629 [details]
File: backtrace
Comment 4 Red Hat Case Diagnostics 2011-03-01 14:28:20 UTC 
Created attachment 481649 [details]
File: backtrace
Comment 6 Red Hat Case Diagnostics 2011-03-01 17:45:51 UTC 
Created attachment 481692 [details]
File: backtrace
Comment 8 Red Hat Case Diagnostics 2011-03-11 23:46:40 UTC 
Created attachment 483850 [details]
File: backtrace
Comment 11 Dave Airlie 2011-04-14 21:00:24 UTC 
for this to happen the machine needs to be running with nomodeset, which is a workaround configuration, but we could probably track this down if we had hw profiles etc.

We would need at least dmesg + /var/log/Xorg.0.log
Comment 14 Jeremy West 2011-10-05 21:35:53 UTC 
As per comment 11, I'm closing this bug and recommending that any future cases that get associated with this, focus on the real problem of fixing the display such that nomodeset isn't needed. Unless, of course the proper information in comment #11 can be provided and a good solution for this crash is found.