Bug 195798 - dri causes hard hang
Summary: dri causes hard hang
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-17 21:36 UTC by sean
Modified: 2008-08-02 23:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-05-26 19:09:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
log from first X login - dri enabled (61.76 KB, text/plain)
2006-06-17 21:36 UTC, sean
no flags Details

Description sean 2006-06-17 21:36:36 UTC
Description of problem:
startx causes a hard hang. I hear the monitor click, then a very dark reddish
screen, then a "no signal to monitor".

ctl-alt-backspace doesn't work, neither does ctl-alt-del. 

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.1.0-13

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

I have an amd64 box, with radeon 8500dv on agp.

If I comment out dri from xorg.conf, it works. And, really strange, after it
works, if I logout of X, uncomment dri, it also works!

Always happens after recent ( past month ) of xorg-x11-server yum updates.

I've attached Xorg.0.log from the failed X login. No errors I can see.

Comment 1 sean 2006-06-17 21:36:37 UTC
Created attachment 131114 [details]
log from first X login - dri enabled

Comment 2 sean 2006-08-10 14:41:49 UTC
This is still a problem with fc6t2 updated to August 9.

Anything I can provide to fix this?

sean

Comment 3 Adam Jackson 2007-04-04 19:26:35 UTC
Can you attach the X log from FC6?  Or even better, an FC7 LiveCD.

Comment 4 Adam Jackson 2007-05-26 19:09:50 UTC
Mass closure: This bug has been in NEEDINFO for over six weeks with no
additional information provided, and is therefore being closed.  If this bug is
still an issue for you, please supply the requested information, and reopen the bug.


Note You need to log in before you can comment on or make changes to this bug.