Bug 251100

Summary: Backtrace in radeon_drv.so on starting X
Product: [Fedora] Fedora Reporter: David Nielsen <gnomeuser>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://www.redhat.com/archives/fedora-test-list/2007-August/msg00087.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-08-07 08:37:47 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:
Attachments:
Description Flags
Xorg.0.log none

Description David Nielsen 2007-08-07 04:41:29 UTC 
Description of problem:
As of Rawhide on the 6th of August 2007 I can no longer start X using the radeon
driver. However the bt can be worked around by using the vesa driver.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x47febd]
1: /lib64/libc.so.6 [0x2aaaab611870]
2:
/usr/lib64/xorg/modules/drivers//radeon_drv.so(RADEONSetSyncRangeFromEdid+0x18)
[0x2aaaacf663f8]
3: /usr/lib64/xorg/modules/drivers//radeon_drv.so [0x2aaaacf58385]
4: /usr/lib64/xorg/modules/drivers//radeon_drv.so(RADEONPreInit+0xac6)
[0x2aaaacf5b586]
5: /usr/bin/X(InitOutput+0x9ad) [0x463a8d]
6: /usr/bin/X(main+0x275) [0x4346e5]
7: /lib64/libc.so.6(__libc_start_main+0xf4) [0x2aaaab5fecc4]
8: /usr/bin/X(FontFileCompleteXLFD+0x239) [0x433b99]

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.6.193-1.fc8

How reproducible:
100%

Steps to Reproduce:
1. start x
  
Actual results:
backtrace

Expected results:
Glorious X

Additional info:
Comment 1 David Nielsen 2007-08-07 04:41:30 UTC 
Created attachment 160797 [details]
Xorg.0.log
Comment 2 Michael Schwendt 2007-08-07 08:37:47 UTC 

*** This bug has been marked as a duplicate of 251051 ***