At least, nobody can blame Microsoft for that. It's not their product.

It VT switching. For some reason the program you have is using it. Xterm GTerminal… lot of other terminal don't do it.

Even turning AIGLX off only reduces the risk of the race condition. Two applications trying to interface with video card at the same time. Sorry true stability will come with DRI2 drivers for X11 that uses a shared kernel based memory manager gem to stop applications stepping on each other.

This is the X11/posix Video nightmare reason why freebsd and other posix are also taking up the DRI2 and kernel based memory manager for video cards.

[console] own video card memory manager.
[vt] each application with there own video card manager.
X11 is on a vt so it has it own.
And that application is using a vt so it has it own. So X11 and that application has to do pass overs of video card control. Problem is when it gets out of order splat. Basically the applications hand back of control of that section of memory is defective or X11 user-space take back control is defective so leaving you with splat.

Most terminal programs using pty pseudo-terminal interfaces so avoiding these mothers of stuff-ups.

AIGLX is not independent to GLX. Its a segment of the GLX spec. Option "AIGLX" "off" is just tell server not to use segment of GLX spec. There are other options to turn it off.

Option "AIGLX" "off" works on all video cards with GLX support including Nvidia that don't use any redhat code.

“GLX was created by Silicon Graphics and is currently at version 1.4. GLX, with both DRI and Mesa, is included in the X.Org Foundation’s version of the X Window System since X11R6.7.0, and in The XFree86 Project’s version since version 4.0.”

So it’s old like hell and heaven. I had DRI and Mesa support since ages!

Now, for the Red Hat project that was “required for OpenGL compositing window managers (such as Compiz Fusion) to function with hardware acceleration”:

“The AIGLX project has been merged into X.Org and is available as of X.Org 7.1.”

The assume is your problem. xgl existed before glx. xgl is the deprecated interface for providing opengl support.

So, I assume they *do* exist. They were this way long before AIGLX was invented.

And, needless to say, Xfree86 and X.Org never crashed on that laptop before — at least, not this way.

I'm not interested in the various ways of 2-D, 3-D, 1*E^6-D acceleration, I just want that fucking video card to work! When an application uses a certain API call, it must work, regardless of the place where most of the computation is made (hardware, software).

Just added urxvt to my list of applications not to install due to doing switching of virtual terminals.

Why should I disable something I have never enabled? Because the pieces of shit at the X.Org thought so?

I have had for years these options in xorg.conf:
Load "glx"
Load "dbe"
Load "dri"
but they did *not* mean anything like AIGLX or other modern shit until in recent times!

Now, what do I need to do?
Section "ServerFlags"
Option "AIGLX" "off"
EndSection

Why do I *have* to set OFF something I have never set ON?

—

@oiaohm:

> Sure you did not hit ctrl+alt+f1 at some point. Or that application is doing equal for some reason.

No. Just launch urxvt, and click on its close button. This is all you have to do to crash X on a "savage" card.

—

@ g.ray:

> I tried once a Centos netinstall

In the meantime I clarified that it was not a netinstall in the meaning of "minimal boot disk", but a FTP install using CD1 and its Anaconda with "askmethod" to be able to specify a FTP server as the install media.

Everything was just fine otherwise. Same RPMs, but from a server, not the CD-set.

Sooner DRI2 gets here the better. I am 100 percent sick of it.

That is the dicey as hell memory swap between Virtual terminals. Sure you did not hit ctrl+alt+f1 at some point. Or that application is doing equal for some reason.

Nvidia drivers are more resistant to it. I guess you had Nvidia when it used to work.

Due to lack of in kernel memory management of video cards before DRI2+GEM+KMS was invented. What happens is programs loss track of who video card memory is whos leading to these problems.

If you had SAK enabled in kernel that still would have worked to restore access. Ok lossing work but restored access.

I don't say faults don't exist in Linux.

http://lmgtfy.com/?q=disable+aiglx+xorg

Otherwise, there are the same RPMs, installed by the same code.

No idea. I deleted my Linux partition last week, and since then I'm "rootnoverify (hd0,0); chainloader +1; boot" because I'm too lazy to "fixmbr", but even so I'm glad I got rid of it. It's not worth wasting time with all the bugs and annoyances.

Because it beats writing about anti-virus?

Linux is great for bloggers and journos because you can find stuff to complain about for free