Savage/MX: all OpenGL apps receive SIGKILL upon start

[Michal K. <lor...@po...>]

Hello there all DRI hackers,

I own a Savage/MX in my laptop and for some time, I've been using it
successfully with the savage DRI driver. However, some time ago things got
messed up. I've been always using the latest CVS versions of X.org, Mesa and
DRM. I usually update them when I update my kernel. Ok, so here's the story. A
couple of months ago (that's an estimation actually, I don't remember the
precise date) I've updated the DRM kernel module and, as always, tested its
functionality by starting glxgears. A black window blinked once and I got the
message "Terminated". I thought it may be the question of incompatibility
between current DRM and old X.org or Mesa, so I recompiled them all from CVS.
Same result. So I started Quake III - "Terminated". Because I use OpenGL apps 
only from time to time, I thought it's probably some minor bug that would soon
be fixed, I forgot about the matter and hoped for the best. Yet, it's been some
time and still all apps become terminated by SIGKILL upon OpenGL initialization.
Today, I recompiled the current CVS version of X.org, Mesa and DRM and it still
did no good. The only message I get is "VM: killing process glxgears" in
/var/log/syslog. I've been trying to produce a backtrace, yet I'm unable to do
it (but I'm a newbie and that may explain it ;-)) X.org says "DRI is enabled"
and produces no errors at all. That's about everything I can tell about the
matter, if you need any more info, just ask and I'll answer ASAP.

My box: Toshiba Satellite 4270 - Celeron 500, 192 MB RAM, Savage/MX 8 MB VRAM,
Slackware 10.0 + current, custom 2.6.14.5 kernel, current CVS versions of X.org,
Mesa and DRM.

One more thing, previously DRI worked *perfectly* (performance way better than
on Windows) for quite a time (about a year I believe).

Thanks in advance for any help,
Michal Kepien