nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Floating point exception with > 180.29 (http://www.nvnews.net/vbulletin/showthread.php?t=130070)

twistedfall 03-15-09 05:15 AM

Floating point exception with > 180.29
 
1 Attachment(s)
I'm running Gentoo on x86 and with recent NVIDIA driver versions I started to experience SIGFPE with some apps. For example:

$ mplayer
Floating point exception
$ amarok
Floating point exception
$ firefox
Floating point exception

This bug started in 180.35 and still present in 180.37 and 185.13. Downgrading to 180.29 resolves this problem. The culprit is libGL.so. Replacing it with version 180.29 also solves this problem.

Switching to xorg-x11 opengl implementation removes the problem too (as NVIDIA libGL.so is no longer used in this case)

I tried rebuilding all apps that have opengl use-flag, but that didn't help.

twisted_fall 03-22-09 03:32 AM

Re: Floating point exception with > 180.29
 
It's still the case for 180.41

kernelOfTruth 03-22-09 10:19 AM

Re: Floating point exception with > 180.29
 
*subscribes*


I have a 7600 GT and experience something related

I get segmentation fault for all apps using gtk+ (from what I can tell) and every apps/process that tries to use libGL.so

180.29 works fine

everything above generates general protection faults (in syslog) and segmentation faults (output in console when launching the app)

180.35, 180.37, 180.41, 185.13 all show this behavior

I believe if your problem is solved mine should be too


seeing you're running a toolchain with enhanced security (pie) I'm wondering whether that might be the cause :headexplode:

the strange thing is that this worked perfectly fine with previous kernel-versions and drivers releases

nvidia-drivers in general are pretty tolerant towards new slab allocators, schedulers, and exotic kernel settings - I don't hope that this changes for the bad (see ati/amd's drivers)

NVIDIA, please, give input in this case if there's any more info you need

twisted_fall 03-30-09 03:40 PM

Re: Floating point exception with > 180.29
 
Argh, still happens with 180.44.

kernelOfTruth, yes, I read your report and it does sound very similar. Alas, I don't see a solution to this.

twisted_fall 03-30-09 03:53 PM

Re: Floating point exception with > 180.29
 
I see that 180.35 brought support for OpenGL 3.0 floating point depth buffers. Maybe they have something to do with this problem

kernelOfTruth 03-30-09 04:12 PM

Re: Floating point exception with > 180.29
 
so if that should turn out to be the case:

is there an option to disable opengl 3.0 or 3.1 ?

even though it's not supported on my 7600GT ? (it doesn't support opengl 3.0 or 3.1, right ?)

@twistedfall:

so you say compiling e.g. the 180.44 kernel and replacing its libGL.so by the libGL.so from 180.29 works ?

interesting :)

twisted_fall 03-30-09 04:17 PM

Re: Floating point exception with > 180.29
 
Well, I didn't check 180.44 specifically, but it did the trick for 180.35. At least mplayer stopped crashing. I didn't run any tests on the stability of such combination.

kernelOfTruth 03-30-09 04:25 PM

Re: Floating point exception with > 180.29
 
the strange thing is that your hardware should support openGL 3.0/3.1:

Quote:

GeForce 8600M GS rev 161
but still is affected

Quote:

You need one of the following graphics cards to get access to the OpenGL 3.1 and GLSL 1.40 functionality:
Desktop

* Quadro FX 370, 570, 1700, 3700, 4600, 4700x2, 4800, 5600, 5800, Quadro VX200, Quadro CX
* GeForce 8000 series or higher; Geforce G100, GT120, 130, GTS 150, Geforce GTS 250, GeForce GTX 260, 280, 285 and 295, any ION based products.

Notebook

* Quadro FX 360M, 370M, 570M, 770M, 1600M, 1700M, 2700M, 3600M, 3700M
* GeForce 8000 series or higher
so something doesn't seem to work properly with the drivers >180.29


my next graphics card most probably will be an nvidia again but first I'd like to use my 7600GT a little longer (for the next 2-3 kernel releases) and not being forced to buy a newer one just because the current driver releases deprecates it in an strange way :angel2:

thanks nvidia !

twisted_fall 03-30-09 04:27 PM

Re: Floating point exception with > 180.29
 
It seems that GL_NV_depth_buffer_float is to blame. 180.29 doesn't have it. We only need someone from Nvidia to take a look.

kernelOfTruth 03-31-09 08:36 AM

Re: Floating point exception with > 180.29
 
twisted_fall, could you please post the output of

ls -l /usr/lib32/opengl/nvidia/lib/

and

ls -l /usr/lib64/opengl/nvidia/lib/

after you have replaced the libGL.so file ?


if I've understood it correct only the following stuff is changed / altered compared to the "original" installation:

Quote:

lrwxrwxrwx 1 root root 15 2009-03-30 20:03 libGL.so -> libGL.so.180.29
lrwxrwxrwx 1 root root 15 2009-03-30 20:03 libGL.so.1 -> libGL.so.180.29
-rwxr-xr-x 1 root root 701784 2009-03-30 20:03 libGL.so.180.29
in /usr/lib32/opengl/nvidia/lib/


and

Quote:

lrwxrwxrwx 1 root root 15 2009-03-30 20:03 libGL.so -> libGL.so.180.29
lrwxrwxrwx 1 root root 15 2009-03-30 20:03 libGL.so.1 -> libGL.so.180.29
-rwxr-xr-x 1 root root 900376 2009-03-30 20:03 libGL.so.180.29
in /usr/lib64/opengl/nvidia/lib/


that way I can take the new driver for a test-ride (now the question is whether anything of the BUGS/problems from earlier kernel-releases gets fixed at all in that way or only vdpau)

thanks

@nVidia:

(bump)

kernelOfTruth 03-31-09 01:34 PM

Re: Floating point exception with > 180.29
 
so the libGL.so* and libGLcore.so* stuff needs to be replaced

and this really somehow "fixes" it (of course if you leave the non-working direct rendering aside)

twisted_fall 03-31-09 02:06 PM

Re: Floating point exception with > 180.29
 
As I have 32bit system I don't have separate lib32 and lib64.

Here is ls -l /usr/lib/opengl/nvidia/lib/
Code:

total 16220
lrwxrwxrwx 1 root root      19 Мар 30 23:23 libGLcore.so -> libGLcore.so.180.29
lrwxrwxrwx 1 root root      19 Мар 30 23:23 libGLcore.so.1 -> libGLcore.so.180.29
-rwxr-xr-x 1 root root 15782884 Мар 30 23:23 libGLcore.so.180.29
-rw-r--r-- 1 root root      706 Мар 30 23:23 libGL.la
lrwxrwxrwx 1 root root      15 Мар 30 23:23 libGL.so -> libGL.so.180.29
lrwxrwxrwx 1 root root      15 Мар 30 23:23 libGL.so.1 -> libGL.so.180.29
-rwxr-xr-x 1 root root  701784 Мар 30 23:23 libGL.so.180.29
lrwxrwxrwx 1 root root      23 Мар 30 23:23 libnvidia-cfg.so -> libnvidia-cfg.so.180.29
lrwxrwxrwx 1 root root      23 Мар 30 23:23 libnvidia-cfg.so.1 -> libnvidia-cfg.so.180.29
-rwxr-xr-x 1 root root  114600 Мар 30 23:23 libnvidia-cfg.so.180.29
lrwxrwxrwx 1 root root      23 Мар 30 23:23 libnvidia-tls.so -> ../tls/libnvidia-tls.so
lrwxrwxrwx 1 root root      25 Мар 30 23:23 libnvidia-tls.so.1 -> ../tls/libnvidia-tls.so.1
lrwxrwxrwx 1 root root      30 Мар 30 23:23 libnvidia-tls.so.180.29 -> ../tls/libnvidia-tls.so.180.29

Quote:

if I've understood it correct only the following stuff is changed / altered compared to the "original" installation:
Yes, you are right. But actually I never really gave this config a test drive.


All times are GMT -5. The time now is 10:51 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.