X Lockup caused by ATITD2 client?

[Draskuul]

I'm running the current ATITD2 client as of my last login (around 1900CST 8/26). I'm running Gentoo, using:

XFree86 4.3.0
glibc 2.3.3
kde 3.2.3
nvidia kernel/glx 4496

Twice now, when the system is fairly stressed, I've had X freeze on me. Applications appear to still be running normall, but nothing it appears that either X or KDE have lost all input control.

The last lines of the egenesis.bug file:


mem marked as Statics:Char: 1 KB
mem marked as Statics:Handle: 4 KB
mem marked as Statics:Ident: 516 KB
mem marked as Unclassified: 24 KB
Patches using 495562 bytes in 1614 blocks (est 521386 real bytes)
Timer Unclassified : 0 calls, 30089058.00 usec, 30089058.00 usec/call
Flushing effect bonfireflame
X I/O error
Textures leaked: sprite-bump sprite
Freed font tahoma at $09553E08
Freed font tahoma at $08538B64
bad font: -adobe-helvetica-medium-r-normal--14-140-75-75-p-77-iso8859-1


Let me know any other details you need. I saved all the .bug files from the time of the last crash. This has happened twice now, forcing me to ssh into the system remotely and kill X.

Edit: I've been running these versions for about 3 weeks now, completely stable, and also under just as much stress as what was placed on it while running ATITD2. It has never become unstable nor locked up here.

[Pluribus]

You dont say what video card you are running or what the status of the Advanced Terrain setting is if you have a capable card :-) As for X locking up, that is 100% a driver lockup... Have you tried ANY of the newer Nvidia drivers?

[Draskuul]

You dont say what video card you are running or what the status of the Advanced Terrain setting is if you have a capable card :-) As for X locking up, that is 100% a driver lockup... Have you tried ANY of the newer Nvidia drivers?

Sorry about that...it's a GF FX5900XT-based card. All video options, including advanced terrain, are enabled or set to max.

It's somewhat more of an input lockup. Applications running on screen still run, and the mouse still moves--but nothing registers. No keyboard input works at all. I've tried killing and restarting the window manager directly, but that's not very doable when you're using KDM to begin with.

Newer drivers are highly problematic, with a number of kernel issues (using v2.6 series here, not 2.4).

I will see this weekend if I can beat the 6xxx series drivers into submission and get it working.

This current setup (exact combination of software/driver/kernel versions) has no problem with many, many countless hours of RTCW:Enemy Territory. I think my ET guild is pretty unhappy by now, now that they've lost me to ATITD :D

[ArmEagle]

If you read the Nvidia boards you'll see that this is a quite usualy problem which Nvidia doesn't seem to bother.
I have the problem a few times each week too on the latest (till 6106) drivers.
I'm using 6111 now and didn't have a problem yet, but I'm sure it will happen.

I hope though that the 6111 drivers won't show the ATITD-graphics-hang bug anymore. I stil lfound that very weird..

[Pluribus]

Newer drivers problematic with 2.6???? Nvidia drivers have supported 2.6 natively for at LEAST the last two driver revs... (Part of me wants to say 3, but I dont remember)

/me hopes they work :-) been running them with 2.6.7 for a while :-)

My understanding is that the 44.96 drivers are not supported by nvidia under the 2.6 kernel. Under that basis, it is hard for me to offer ANY support at all with that configuration. (If the vendor wont support thier product under 2.6, I cant either)

Just checked... the 53.36 driver (Released January 26, 2004) added support for 2.6 kernels...
since then 61.06 and 61.11 have been released.