Random Lockups with linux & ATi video card...

by e:n:i:g:m:a on 01/23/2005 01:53, 11 messages, last message: 12/10/2006 10:35, 3917 views, last view: 05/02/2024 23:27

OK, so I'd like to know if anyone else has this problem as it seems that I'm the only one who's mentioned it...

Does anyone else get random hard lockups while running cube on their linux box?

It seems that while running on my computer I get rather random lockups whilst playing. Now what happens when it locks up is that the sound which was playing a sound effect or music starts to stutter, then it just freezed to a buzzy noise. Furthermore, the keyboard is totally locked up too and I can't type quit or ctrl+alt+backspace to kill the X server, and I can't ssh into my machine. The xorg logs don't show any errors either...

Anyway, anyone have any similar problems? I've got an ATi Radeon 9000 running the newest drivers on xorg 6.8.0-r3

   Board Index   

#1: ..

by Grogan on 01/24/2005 02:05

I said once I had never had a lockup playing cube, but since then the last two times I built xorg CVS sources I was having reproducable lockups playing cube. In the same spot, but not only in that one spot. With either of those builds of xorg.

Open source DRI, not ATI drivers.

I had similar symptoms with the audio too when it locked, but that's not really significant. I've seen that happen many times when games lock up a PC. (On Windows too).

I can ssh in, but the machine will not reboot. It hangs on shutdown (or kernel oops, I can't tell) and I have to physically power off.

But I've not had that problem before, and going back to what I got on Dec. 4 2004 it's fine. That's where I'm staying for a while, too. This has been the most stable build of xorg I've had to date. (I tar up my /usr/X11R6 directory when I get a good one like this so I don't get burned when I play russian roulette)

X Window System Version 6.8.1.99
Release Date: 2 October 2004 + cvs
X Protocol Version 11, Revision 0, Release 6.8.1.99
Build Operating System: Linux 2.6.9 i686 [ELF]
Current Operating System: Linux getstuffed 2.6.11-rc2 #1 Fri Jan 21 23:54:01 EST 2005 i686
Build Date: 04 December 2004

I don't think it's specifically cube, because I had Tux Racer do that too in a specific place. (in a very poor addon map, but still that never happened before)

I've had Radeon 9200SE (first time) and Radeon 7500 cards (second time) in this machine at the times it occurred.

In my case I can only blame the drivers in the version of xorg, but perhaps it's those ATI drivers for you. This was happening to you also with your xorg 6.7 on gentoo if I recall correctly.

While never during cube, I have had the PC hard lock a few times when I was playing games with ATI drivers. When that occurred, it was a complete lockup, with no network response either. Not even ping, let alone ssh.

reply to this message

#2: Re: ..

by e:n:i:g:m:a on 01/24/2005 05:47, refers to #1

you did have a hard lock while playing games with the ATi drivers?

Perhaps I should try the opensource drivers?

BTW: when cube locked, were you using the patched binary with the ATi Fix?
And do you see any performance gain when using the DRI drivers versus xorg's?

reply to this message

#3: ..

by Grogan on 01/24/2005 06:45

Yes, on more than one occasion my PC has locked up solid while playing games using the ATI drivers. I hate them.

No, I wasn't running the ati workaround binary when cube locked up, because I was using the open source drivers. I was using my own cube client. But that was caused by the xorg from CVS.

By DRI, I simply meant the DRI included with xorg (and the DRM from whatever 2.6 kernel I'm using) as opposed to the ATI drivers. I don't use the DRI trunk from freedesktop.org, though I have in the past. Last couple of times time I tried that, I couldn't get the kernel modules to work. They'd compile, but fail to load due to missing symbols.

Your radeon is supported, the open source drivers should be ok. Especially for Cube, and you won't have to use the ATI workaround client either.

reply to this message

#4: Debian Sarge with nVidia freezes too

by MeatROme on 11/11/2005 13:29

I'm using the (unfree) nVidia drivers and am experiencing the same random freezes you've described under Gnome in xfree86.

There doesn't seem to be anything I can connect to these issues, wether ingame or on my box.

When it happens I need "kill -9" the cube process.
After that my display in X still responds to keystrokes but not to mouse (though I seem to remember a time it did). I restart gdm and try again.

This is very unsatisfying ... any help would be appreciated. Googling didn't turn up anything pertinent.

reply to this message

#5: Issue might be due to port forwarding

by MeatROme on 11/14/2005 12:01

I talked to shavvn on IRC and we both agreed that these issues seemed to occur in conjuction with missing/erronous port forwarding.

If you are behind a router you should definitely see to it that :
UDP ports 28765 and 28766 get forwarded (maybe even DNATed). I usually also do that for the same TCP ports - to be on the safe side.

For sauerbraten the ports are 28785 and 28786.

See the documentation that came with the game!

HTH

reply to this message

#6: I can't play cube!!

by jsm on 11/17/2005 21:21

..

reply to this message

#7: I can't play cube!!

by jsm on 11/17/2005 21:23

when I try to start cube I can hear the music but my screen goes black.
Can somebody help me?

reply to this message

#8: Cube lockouts

by LancerNZ on 11/27/2005 02:55

The random lock ups are a real downer and did not happen for me until downloading the new improved August 2005 cube. I can fix it as follows...
1. I no longer run cube itself, but found a script called "reset_res". From the command line I issue "reset_res cube" which plays cube from its own special shell. When lock up occurs, I CTRL-ALT-F2 to bring a console, log in, and...
ps -A | grep client
...then...
kill -9 (whatever number the linuxclient shows as)

This stops the game and I can CTRL-ALT-F7 to get back to my ordinary desktop. Everything is very big and my typing may in fact be off screen, but the console I launched cube from is in focus so I can at least type commands even if I can't see what I'm typing.
I then issue a "umouse" command, which brings back the mouse movement.
After this, I run "reset_res cube" again and then exit the game once it starts. After this second run CTRL-ALT-plus/minus now work to resize the screen back to normal.

Unfortunately I will have lost my score from he previous match as quitting and reentering the room does that.

I'm not happy with the newer cube since this crash was introduced to it. My drivers are Nvidia.

reply to this message

#9: Cube 2 starts to run slow and hungs after 1 minute

by Kubunteando on 12/09/2006 09:49

Umm..
Cube 2 2006_12_4_linux_gui binnary files hungs everytime after 1 minute playing. Simply starts running fine, and then slower everytime, until just crashes. I have noticed that the memory is not freed, since starts to use all the mamory including swap, and dies with the error message on kern.log \"Out of memory\".

I can play CUBE 1 with no problems.

I have an ATI Radeon Mobility 9000. I have tried the Xorg drivers and also the ATI drivers, both using the latest that support this ATI: 8.28.8.

I can see these errorr messages in the kern.log comming in huge amounts when I am playing cube 2:

[fglrx:firegl_rmmap] *ERROR* map 0xf1eeb350 still in use (map_count=1)
[fglrx:firegl_free_buffer_queue] *ERROR* buffer queue 0xf1eeb340 still mapped (user_handle = 0x0005a000)

I don\'t mean this is not a bug on the ATI drivers, but I only have these issue with cube 2 and not with other 3D games.

Any one having the same issue?

Is it possible to make a workaround for this? Like using the ATIs in the same way as cube 1?

It happened the same to me with the previous version of Cube 2 from august 2006. So far I have not been able to enjoy Cube 2, sigh...

reply to this message

#10: same here

by stones on 12/10/2006 10:34

I get the occasional lock up, But it seems to only happen in CO-OP edit maps.
Everything will just freeze, when im finally able to get my desktop back i see a memory error \"mem reference at 287598 could not be read at 234798\"
Not the exact message just a quik example.
This is on XP and an Nvdia card

reply to this message

#11: and also

by stones on 12/10/2006 10:35

Overclocking my processor too high will cause instant crashes and freezes in game as well

reply to this message

   Board Index