Bug 3606 - Lock up w/ DRI, glxgears. Radeon 7000 -series.
Summary: Lock up w/ DRI, glxgears. Radeon 7000 -series.
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 6.8.2
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
: 2581 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-23 02:04 UTC by Joe Khoobyar
Modified: 2010-03-27 04:14 UTC (History)
4 users (show)

See Also:
i915 platform:
i915 features:


Attachments
patch to compile it under Fedora Core 5 (987 bytes, patch)
2007-02-28 05:37 UTC, Dmitry Butskoy
no flags Details | Splinter Review
Log from when X was hung (55.44 KB, text/plain)
2007-03-25 00:41 UTC, Timo Jyrinki
no flags Details
X failing to restart (48.21 KB, text/plain)
2007-03-25 00:42 UTC, Timo Jyrinki
no flags Details

Description Joe Khoobyar 2005-06-23 02:04:45 UTC
This desktop is an Athlon XP 1800+, w/ a VIA KT400 chipset on the motherboard. 
The card I've got in there is a Radeon RV100 QY [Radeon 7000/VE] with 64 megs of
DDR sdram.

When I run glxgears w/ DRI enabled, the entire system locks up when the mouse is
moved, unless I set SWcursor on.  By the entire system, I mean everything, not
just X.  The only recourse is to press the Reset switch.

Although I'm glad I thought to try setting SWcursor on, this still is just a
hack to workaround a bug somewhere.  Plus, the cursor disappears when I move it
over the glxgears window.
Comment 1 Dmitry Butskoy 2005-07-11 22:38:53 UTC
  The same for me (with the same card).
  Similar lock up is when I try to watch TV using "xawtv". Disabling dri helps
in this case (as for glxgears too), but using software cursor does not...
Comment 2 T. Hood 2005-09-28 02:10:14 UTC

*** This bug has been marked as a duplicate of 2362 ***
Comment 3 Eric Anholt 2005-09-30 18:40:21 UTC
Reopening bug because it is definitely not clear that this is the same thing
being referred to by the submitter of #2362.
Comment 4 T. Hood 2005-10-04 05:32:40 UTC
See also #2581.
Comment 5 Mike Klemencic 2005-10-24 22:32:57 UTC
I am willing to donate a Radeon 7000/VE card to get this problem resolved,
please contact mikeklem [at] csh.rit.edu
Comment 6 Michel Dänzer 2006-05-09 03:37:51 UTC
Does this still happen with current versions of xf86-video-ati and Mesa?
Comment 7 Erik Andren 2006-05-31 12:27:57 UTC
ping!
Comment 8 Timo Jyrinki 2007-02-22 14:02:03 UTC
This is interesting in that the bug is "null" status/resolution state currently. Trying to change something, sorry for the noise. Meanwhile, you (Joe, Dmitry, Mike) could tell if you are still seeing this with X.org 7.2.
Comment 9 Dmitry Butskoy 2007-02-26 06:02:46 UTC
Unfrotunately, the solution pointed out in bug #5986 (comes from Debian) does not help in my case:

ATI Radeon RV100 QY [Radeon 7000/VE]
xawtv-3.95, xorg-x11-drv-ati-6.5.8.0

Surely I've checked out not the patch itself, but its idea -- to comment out the fragment in src/radeon_accelfuncs.c :
>       a->SubsequentSolidTwoPointLine
>           = FUNC_NAME(RADEONSubsequentSolidTwoPointLine);
It seems it does NOT help...
Comment 10 Dmitry Butskoy 2007-02-26 06:04:37 UTC
BTW,
I'm free enough now to check some further ideas for xorg-x11-drv-ati
(Thanks x.org source is now splitted! ;) )
Comment 11 Daniel Stone 2007-02-27 01:27:05 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 12 Michel Dänzer 2007-02-28 01:01:24 UTC
(In reply to comment #9)
> Unfrotunately, the solution pointed out in bug #5986 (comes from Debian) does
> not help in my case:

Yes, that's just a workaround for a very specific problem (lockups with CP line acceleration on RV280s).

> ATI Radeon RV100 QY [Radeon 7000/VE]
> xawtv-3.95, xorg-x11-drv-ati-6.5.8.0

If your problem only occurs with xawtv, it's probably not the same issue as reported here originally either.

Still waiting for updates on whether the original problem reported here persists with current releases.
Comment 13 Dmitry Butskoy 2007-02-28 05:34:57 UTC
Well,
I've upgraded my xorg-x11-drv-ati (xf86-video-ati) from 6.5.8.0 to 6.6.3 (have compiled it under the old Fedora Core 5 environment, i.e. xorg-x11-server-sdk-1.0.1 , with some little adaptation).

It seems that the issue is gone. Already 15 minutes with hard tests I cannot cause my compurter to freeze ;)

Note, that the issue still was present in version 6.6.1 .

Also note: to compile the 6.6.3 version under old plus "exa < 2.0" servers's environment, I have to apply the patch (attached) and cause 'USE_EXA' macro to be set anyway (because of some inaccuracy in ifdef code usage).
Comment 14 Dmitry Butskoy 2007-02-28 05:37:56 UTC
Created attachment 8904 [details] [review]
patch to compile it under Fedora Core 5

Besides this patch, you have to use "make CC='gcc -DUSE_EXA'" to cause USE_EXA macro to be set, else it is failed to compile.
Comment 15 Michel Dänzer 2007-02-28 06:36:06 UTC
(In reply to comment #13)
> It seems that the issue is gone. Already 15 minutes with hard tests I cannot
> cause my compurter to freeze ;)

You're saying even xawtv survives now? :)

> Note, that the issue still was present in version 6.6.1 .

Yes, the fix for this only went into 6.6.2.

Closing, feel free to reopen if you still get lockups with a current driver on a Radeon 7000.
Comment 16 Dmitry Butskoy 2007-02-28 06:45:16 UTC
> You're saying even xawtv survives now? :)
Yep!

xawtv still works... :)
Comment 17 Timo Jyrinki 2007-03-25 00:40:50 UTC
Reopening because a mobility m6 (ie. 7000-series) crash is still being reported with the 6.6.3 driver at https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/15219. X.org 7.2, Mesa 6.5.2, xserver-xorg-video-ati 6.6.3 (with a few additional patches from git).

Dave Gilbert says there:
---
"In general use on the desktop it has been fine (I even had compiz running).
However, I had left euphoria screensaver running overnight and I've come back to it twice now humg; this time I ssh'd in and found it was a hung X server; killing the X server got me control back.
I've included two Xorg.0.log files; the 'hung' one is the one where it was hung - last thing is a power management command. (To make it clear, it has managed power saving and running this screensaver - so it's not an everytime). In this hung state the X server wouldn't let me attach with a gdb or allow me to strace it to see what it was up to.

I've also included the log from me trying to restart it - it complains of EngineRestore 'Idle timed out'."
Comment 18 Timo Jyrinki 2007-03-25 00:41:51 UTC
Created attachment 9280 [details]
Log from when X was hung

Copied from ubuntu's bug reporting system
Comment 19 Timo Jyrinki 2007-03-25 00:42:40 UTC
Created attachment 9281 [details]
X failing to restart

Also copied.
Comment 20 Dave Gilbert 2007-03-25 06:40:56 UTC
(In reply to comment #17)
> Reopening because a mobility m6 (ie. 7000-series) crash is still being reported

Just to be clear my bug reported there is a Radeon 7200 (R100 QD).

Dave

Comment 21 Dmitry Butskoy 2007-03-26 04:28:30 UTC
> killing the X server got me control back.
It seems to be some another issue, since the entire system is not freezed (it's possible to login remote usung ssh) ...
Comment 22 Rolf Leggewie 2008-02-01 01:27:08 UTC
(In reply to comment #21)
> > killing the X server got me control back.
> It seems to be some another issue, since the entire system is not freezed (it's
> possible to login remote usung ssh) ...

dupe of bug 2581?
Comment 23 Rolf Leggewie 2008-08-08 18:24:53 UTC
*** Bug 2581 has been marked as a duplicate of this bug. ***
Comment 24 Timo Jyrinki 2008-08-20 04:31:46 UTC
Could you by any chance try for example latest Ubuntu 8.10 alpha from http://cdimage.ubuntu.com/releases/8.10/ ? It includes all the latest fixes done with help of AMD releasing documentation, and is known to fix many problems. Dunno if Radeon 7000 series are affected or not.
Comment 25 Dave Gilbert 2008-08-23 15:19:43 UTC
I've tried on Ubuntu Intrepid 8.10 Alpha 4 and haven't had much look;
it's failing to open AGP so disabling DRI.

(It's also giving me a completely white screen if Compiz is on - but I guess that might be separate).

I've added a comment to the Ubuntu tracker of my matching Ubuntu bug; this is on a Tyan S2460/Dual athlon 760MP with Radeon R100QD/7200 - others may have more look.
Comment 26 Alex Deucher 2008-08-23 16:30:52 UTC
(In reply to comment #25)
> I've tried on Ubuntu Intrepid 8.10 Alpha 4 and haven't had much look;
> it's failing to open AGP so disabling DRI.
> 

Can you attach your xorg log?

> (It's also giving me a completely white screen if Compiz is on - but I guess
> that might be separate).
> 

Compiz requires the DRI.  It won't work without it.
Comment 27 Dave Gilbert 2008-08-23 16:44:39 UTC
I've got the X.org logs and a boot messages in the matching ubuntu bug:

https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/15219

X.org log:

http://launchpadlibrarian.net/17039039/Xorg.0.log.intrepid

messages:
http://launchpadlibrarian.net/17039052/messages-gallifrey

I realise compiz needs DRI/3D - but leaving a fully white screen without anyway to get out of it was not what I was expecting.
(the mouse cursor still moved - so the X server was still alive).

(I got KDE4.1 to come up - it offered the choice to switch to Xrender rather than OpenGL - in OpenGL mode it also got white screen).
Comment 28 Corbin Simpson 2010-03-27 04:14:18 UTC
Closing; not sure if FIXED or WONTFIX is more accurate, since the code has changed so much since the last substantial report. If there's still problems with a current stack, please open a new bug.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.