[TAG] OpenGL hangs my system
ben at callahans.org
Fri Jun 11 18:31:12 MSD 2004
Hi, um, Dylan the Hippy Wabbit. :)
On Fri, Jun 11, 2004 at 02:54:32PM +0100, Dylan the Hippy Wabbit wrote:
> Hi All,
> You complained about not getting many problems sent you. Should have been
> careful what you wished for!
> My problem is that OpenGL programs often freeze the whole system, after an
> unpredicable time running. I'm not a hardcore gamer, as you'll see from
> the hardware spec, but I like to have *some*.
Oddly enough, that's what I've been wrestling with for the past day or
so; similar scenario. However, for me, it's complicated by an
additional factor: the problems appear when I've got OpenGL enabled
_and_ try to suspend the system (it's a laptop.)
> Late Debian Sarge snapshot, running XFree86 4.3.
Yep, that's where I am too - but with an ATI ATI Radeon M9+.
> XFree86.log says:
> XFree86 Version 220.127.116.11 (Debian 4.3.0-7 20040318043201
> root at cyberhq.internal.cyberhqz.com)
> Kernel 2.4.24 compiled for the Duron from source.
At this point, we're up to 2.6.7-rc3. I would suggest at least trying
2.6.6 before deciding that a Linux problem (as contrasted against your
individual version of one) exists.
> There may be some link with how much of main RAM is occupied. I can
> pretty much get away with running anything immediately after logging in.
> If I've been editing photos, or using that F*t B*st*rd Mozilla (I remember
> when web browsers ran in 1MB, not 20!), I'm guaranteed trouble. I don't
> seem to be able to put more than about two extra courses in
> /usr/share/games/tuxracer/courses/contrib and still get to run any of
Interesting. That implies memory leaks, or at least some sort of
persistent memory state.
> If I avoid OpenGL progs the system runs for months on end with the
> expected absence of trouble.
/*runsforever*/ Marking this for later comment...
> Once I've hit trouble I can't quit X with Ctrl-Alt-Backspace, nor can I
> switch to a virtual console to reboot.
Ditto. However, with this current setup, my Alt-Ctrl-BkSp combo just
plain doesn't work at all (and no, I do not have "DontZap" set to true;
in fact, I've explicitly set it to false. Didn't help. I suspect the
> I don't have another system to try SSHing from, and I haven't yet compiled
> in the magic SysRq key. I may have to, if nothing else works.
If your system crashes at all on any kind of a repeateable basis, you
should definitely have it compiled in. At least you'll be able to "clean
up" and exit in a somewhat graceful manner rather than crashing out with
the power switch.
> After restarting the hard way (Ouch!) there appears to be nothing in the
> logs to indicate the problem.
The end of my previous X log contains a clue:
(WW) Open APM failed (/dev/apm_bios) (No such device)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x00000001 [Card 0x1002/0x5c61]
(EE) RADEON(0): [agp] AGP not enabled
This is from my last freeze-up after waking the 'top from hibernation.
Interestingly enough, the mouse still works, indicating that a fair part
of the system is still awake.
> When I was running Debian Woody r0 with XFree86 4.0 there were no
> problems. When I upgraded to 3.0 r1 +backports, with XFree86 4.1, the
> trouble started. Significantly the DRI module format changed between
> these versions of X, forcing me to compile a new module.
Ah - I hadn't realized that it changed.
> Hours spent searching the web have turned up nothing that remotely matched
> my symptoms, so I guess it's not a known common problem. Or maybe I just
> didn't think of the right search terms.
Most likely the latter. I've found way too much stuff on DRI/GL
problems, but it can be hard to sift.
> In case it helps, I've attached my XF86Config.
I just checked it over, and don't see anything obviously wrong (do "dbe"
and "pex5" actually load for you? I gave up on those for ATI a while
back.) In fact, I'm actually going to copy your XkbVariant into mine. :)
The only curious part is
Option "UseFBDev" "false"
Is there a reason for that? Does your card try to run X in FB mode by
default, or what?
You might also want to try changing your driver from "r128" to "ati",
and see if that helps any.
> Any ideas? Apart from the obvious inconvenience, I can't recommend Linux
> to disillusioned Windows sufferers in good faith can I? ;-)
[rolling eyes] Oh, *please*. The days when _that_ sort of blackmail was
effective are long gone - if they ever existed at all. The best
indicator of that is the fact that I was willing to help you in spite of
your trying it.
(You have a specific problem when you want to play *games* - outside of
which everything works great (see the "runsforever" marker) - with *one*
specific server on *one* specific type of hardware, and this is a reason
not to recommend Linux? Give it up.)
* Ben Okopnik * okopnik.freeshell.org * Editor-in-Chief, Linux Gazette *
-*- See the Linux Gazette in its new home: <http://linuxgazette.net> -*-
More information about the TAG