6600gt vs ut2004

[netllama]

Can you try applying all of these patches and see if it has any impact?
http://www.nvnews.net/vbulletin/showthread.php?t=56150
http://www.nvnews.net/vbulletin/showthread.php?t=57990

Thanks,
Lonni

[djzort]

Originally Posted by netllama

Can you try applying all of these patches and see if it has any impact?
http://www.nvnews.net/vbulletin/showthread.php?t=56150
http://www.nvnews.net/vbulletin/showthread.php?t=57990

Thanks,
Lonni

ok tried with perhaps only slight improvements.

quake3 still runs fine. for kicks i turned up all the antialiasing effects (in nvidia-settings) and that all works very well.

i started playing with stack tracing ut

further, last night after playing a few maps of q3a i fired up ut2004 and it worked. i played a map or two, and tried to change the res and it locked up. i just have it set to 800x600 windowed in the config to simplify things (as q3a had some initial fullscreen problems)

after reboot i tried ut2004 again and it just froze at the same place.

would you like to look at the stack traces? ironically i wasnt running strace when ut worked. doesnt life suck?

however prior to that after my first stack trace, i changed from NvidiaLog.ut2 to NoLogo.ut2 and i got to the menu before tryign to change res and it locking again, after reboot ut continued to crash still with NoLogo.ut2.

so the first trace file is a crash
second gets to teh menu and crashes
third crashes

im also posting on the ut2004 lists, but who knows where the problem is. its very wierd

[netllama]

Actually, if you could provide both of the following, it might shed some light on the problem:
* the address of one of the nvidia symbols appearing in the stack trace. Can be obtained like this:
(gdb) print _nv000043gl
* a dump of the register values at the time of the crash:
(gdb) info registers

Thanks,
Lonni

[djzort]

Originally Posted by netllama

Actually, if you could provide both of the following, it might shed some light on the problem:
* the address of one of the nvidia symbols appearing in the stack trace. Can be obtained like this:
(gdb) print _nv000043gl
* a dump of the register values at the time of the crash:
(gdb) info registers

Thanks,
Lonni

sorry how do i achieve this, youve lost me somewhat in how i use gdb with ut2004 etc. or on the strace files etc

[netllama]

I assumed when you mentioned stack traces, you were obtaining them from gdb. What kind of stack traces did you mean?

-Lonni

[djzort]

Originally Posted by netllama

I assumed when you mentioned stack traces, you were obtaining them from gdb. What kind of stack traces did you mean?

-Lonni

i just used 'strace' which basically just dumps out what the program is going.
i have three dumps (about ~130mb each) that bzip2 down to about 1.5mb if you would like me to post them

if you could give me a quick instruction for GDB i would be more than happy to crash my pc a few more times.

[netllama]

I doubt that strace is going to be helpful for this problem, and I'd be surprised if there were any debugging symbols in UT2004 that would make debugging it valuable in gdb.

However, you can certainly try with gdb. Its fairly simple:
gdb ut2004
and then you type 'run'. When it crashes you type 'bt' which will give you a backtrace to post here.

Thanks,
Lonni

[djzort]

Originally Posted by netllama

I doubt that strace is going to be helpful for this problem, and I'd be surprised if there were any debugging symbols in UT2004 that would make debugging it valuable in gdb.

However, you can certainly try with gdb. Its fairly simple:
gdb ut2004
and then you type 'run'. When it crashes you type 'bt' which will give you a backtrace to post here.

Thanks,
Lonni

will do
strace was usefull just to check that it was getting the right libraries and opening the right files etc.

[djzort]

Originally Posted by netllama

I doubt that strace is going to be helpful for this problem, and I'd be surprised if there were any debugging symbols in UT2004 that would make debugging it valuable in gdb.

However, you can certainly try with gdb. Its fairly simple:
gdb ut2004
and then you type 'run'. When it crashes you type 'bt' which will give you a backtrace to post here.

Thanks,
Lonni

the whole pc just reboot
i cant get back to the gdb console to get the traces!!

[zander]

Does the reboot problem continue to reproduce if you apply the patch below? It works around a known bug in some Linux kernels' implementation of the change_page_attr() interface function with respect to the handling of large pages and the no-execute page protection feature. This bug can lead to system reboots. To apply the patch, please follow these steps:

# sh /path/to/NVIDIA-Linux-x86_64-1.0-7676-pkg2.run --extract-only
# cd NVIDIA-Linux-x86_64-1.0-7676-pkg2
# patch -p0 < /path/to/NVIDIA_kernel-1.0-7676-1321905.diff.txt
# ./nvidia-installer -n

You should also apply the other patches available from http://www.nvnews.net/vbulletin/showthread.php?t=56150.

[djzort]

Originally Posted by zander

Does the reboot problem continue to reproduce if you apply the patch below? It works around a known bug in some Linux kernels' implementation of the change_page_attr() interface function with respect to the handling of large pages and the no-execute page protection feature. This bug can lead to system reboots. To apply the patch, please follow these steps:

# sh /path/to/NVIDIA-Linux-x86_64-1.0-7676-pkg2.run --extract-only
# cd NVIDIA-Linux-x86_64-1.0-7676-pkg2
# patch -p0 < /path/to/NVIDIA_kernel-1.0-7676-1321905.diff.txt
# ./nvidia-installer -n

You should also apply the other patches available from http://www.nvnews.net/vbulletin/showthread.php?t=56150.

applied, built, loaded, played q3a, started ut2004, same crash.

[djzort]

Originally Posted by djzort

applied, built, loaded, played q3a, started ut2004, same crash.

if i set the config file for full screen i get a complete reboot

if i set the config file for windowed, the computer just seezes up (speling)

dont know if that helps.

i hope this is helping you guys with your 6600gtpcie amd64 testing.

Dean