Bug 681234 - [abrt] crash in kernel: general protection fault: 0000 [#1] SMP in radeon_read_ring_rptr
Summary: [abrt] crash in kernel: general protection fault: 0000 [#1] SMP in radeon_rea...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard: abrt_hash:1843067170
Depends On: 574377
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-01 14:06 UTC by Red Hat Case Diagnostics
Modified: 2018-11-14 14:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-05 21:35:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
File: backtrace (3.45 KB, text/plain)
2011-03-01 14:07 UTC, Red Hat Case Diagnostics 		no flags Details
File: backtrace (3.45 KB, text/plain)
2011-03-01 14:28 UTC, Red Hat Case Diagnostics 		no flags Details
File: backtrace (3.45 KB, text/plain)
2011-03-01 17:45 UTC, Red Hat Case Diagnostics 		no flags Details
File: backtrace (3.45 KB, text/plain)
2011-03-11 23:46 UTC, Red Hat Case Diagnostics 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.