195.36.15: Use of hardware accelerated OpenGL kills X forcing power cycle

chickenandbeans · 03-27-10, 07:55 AM

Tried everything here: http://www.nvnews.net/vbulletin/showthread.php?t=46678

Just thought i'd report this:

o.s: opensuse 11.2
arch: x86_64
kernel: 2.6.31.12-22-default also tested with kernel: 2.6.31.12-22-desktop
nvidia driver: NVIDIA-Linux-x86_64-195.36.15-pkg2.run
card: Nvidia 8400 GS
X.Org X Server 1.6.5

motherboard:Intel TOM COVE DH55TC H55 Socket 1156 VGA DVI HDMI Out 8
Intel G6950 2.80GHz 3MB Cache Retail Box Processor
Bios: TCIBX10H.86A.0028.2009.1201.1520 (as far as i'm aware the latest)

Use of hardware accelerated OpenGL functions (xbmc, video, compiz) kills X-server forcing cold power cycle

Reproducable steps:
Test/Crash 1. log in and play a video using mplayer -ao alsa -vo x11 myvideo.org
Works but not ideal due to inability to full screen
Test/Crash 2. log in and play a video using mplayer -ao alsa -vo xv myvideo.org

Problem caused:
X is spikes at 99% cpu
Cause crash after 5secs play. Cannot ssh in remotely. Cannot change tty (alt+F1 etc). Needs a power restart

Log files are as follows:

Code:

(WW) Mar 22 21:00:41 NVIDIA(0): WAIT (2, 6, 0x8000, 0x0000f360, 0x000000d0)
(WW) Mar 22 21:00:48 NVIDIA(0): WAIT (1, 6, 0x8000, 0x0000f360, 0x000000d0)

==> /var/log/messages <==
Mar 22 21:00:51 goat kernel: [118045.247264] NVRM: Xid (0001:00): 8, Channel 00000001

==> /var/log/Xorg.0.log <==
(WW) Mar 22 21:00:51 NVIDIA(0): WAIT (2, 6, 0x8000, 0x0000f360, 0x000010b4)

195.36.15

Crash number 2 can be reproduced with following programs:
log in with compiz enabled. Dies after 30 secs or so (moving windows,resizing etc)
log in with compiz disabled. Dies after 120secs or so (no movement of windows, just an active remote ssh session)
log in and use xbmc. Dies on around 10 secs

Error occurs with these drivers too:

NVIDIA-Linux-x86_64-173.08-pkg2.run
NVIDIA-Linux-x86_64-173.14.05-pkg2.run
NVIDIA-Linux-x86_64-173.14.25-pkg2.run
NVIDIA-Linux-x86_64-177.80-pkg2.run
NVIDIA-Linux-x86_64-180.29-pkg2.run
NVIDIA-Linux-x86_64-185.18.14-pkg2.run
NVIDIA-Linux-x86_64-190.53-pkg2.run
NVIDIA-Linux-x86_64-190.53-pkg2.run.1
NVIDIA-Linux-x86_64-195.30-pkg2.run
NVIDIA-Linux-x86_64-195.36.15-pkg2.run

Tested with the following kernel too:
2.6.31.12-22-desktop
Error message for this kernel:

Code:

==> /var/log/Xorg.0.log <==
GetModeLine - scrn: 0 clock: 106500
GetModeLine - hdsp: 1440 hbeg: 1520 hend: 1672 httl: 1904
              vdsp: 900 vbeg: 903 vend: 909 vttl: 934 flags: 6
(WW) Mar 22 22:01:25 NVIDIA(0): WAIT (2, 6, 0x8000, 0x0000e974, 0x0000e984)



==> /var/log/messages <==
Mar 22 22:01:35 goat kernel: [  962.131257] NVRM: Xid (0001:00): 8, Channel 00000001

==> /var/log/Xorg.0.log <==
(II) Mar 22 22:01:35 NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to
(II) Mar 22 22:01:35 NVIDIA(0):     recover...

Tried the following:

* acpi=off - no effect on the crash

* In the 'devices' section of Xorg.conf I *added* and set Option "UseEvents" "true":

Crash was not immediate 15 secs instead of <10secs

Code:

==> /var/log/Xorg.0.log <==
(WW) Mar 27 10:38:16 NVIDIA(0): WAIT (2, 6, 0x8000, 0x00002508, 0x00002518)

==> /var/log/messages <==
Mar 27 10:38:27 goat kernel: [  569.951403] NVRM: Xid (0001:00): 8, Channel 00000001

* In the 'devices' section of Xorg.conf I set Option "UseEvents" "false":

Same result as previous.

* Setting the option in Xorg.conf (devices section) to:

Option "NvAGP" "0"

Test 2

---same result, although this time the nvidia driver did attempt to recover (which failed)

* Logged in and did a mount -o remount,sync on /

Crash occurred after 5 mins

barbara · 03-27-10, 11:03 AM

I suspect that you will not get any answer...
Good luck anyway.

**AaronP** · 03-27-10, 11:25 AM

This looks a lot like a problem I've seen reported a few times lately where the driver simply loses communications with the GPU, and never gets a response to its queries. We haven't been able to reproduce the problem yet, but it's something we're looking at. I apologize for the inconvenience.

Arup · 03-27-10, 09:15 PM

Just a wild hint and apologize in advance for sounding goofy but could this be an issue of security, I know that SE Linux has to be disabled in Fedora for nvidia driver install so was just wondering.

mooninite · 03-28-10, 12:02 AM

Quote:

Originally Posted by Arup

Just a wild hint and apologize in advance for sounding goofy but could this be an issue of security, I know that SE Linux has to be disabled in Fedora for nvidia driver install so was just wondering.

You should be using the RPM Fusion RPM if you are on Fedora. Or, if you don't like kmod packages like myself, you can just perform execstack on the nVidia libraries and you will be able to run SELinux in enforcing mode again.

Arup · 03-28-10, 02:25 AM

Quote:

Originally Posted by mooninite

You should be using the RPM Fusion RPM if you are on Fedora. Or, if you don't like kmod packages like myself, you can just perform execstack on the nVidia libraries and you will be able to run SELinux in enforcing mode again.

I use RPM fusion on Fedora or easylife, both work out well.

chickenandbeans · 03-29-10, 05:01 AM

AaronP:

Good to know the problem is being looked at. With my hardware set up, the use of the nvidia driver is currently impossible. I'll try and get some gdb output at some point this week, but it's proving quite difficult because the machine freezes.

selinux:

Secure because nothing works with it

No this is disabled on my set up.

If I find a work around i'll post it here

03-27-10, 11:03 AM	#2
barbara Registered User Join Date: Oct 2007 Location: Rome, Italy Posts: 27	Re: 195.36.15: Use of hardware accelerated OpenGL kills X forcing power cycle I suspect that you will not get any answer... Good luck anyway.

03-27-10, 11:25 AM	#3
AaronP NVIDIA Corporation Join Date: Mar 2005 Posts: 2,487	Re: 195.36.15: Use of hardware accelerated OpenGL kills X forcing power cycle This looks a lot like a problem I've seen reported a few times lately where the driver simply loses communications with the GPU, and never gets a response to its queries. We haven't been able to reproduce the problem yet, but it's something we're looking at. I apologize for the inconvenience.

03-27-10, 09:15 PM	#4
Arup Registered User Join Date: May 2009 Posts: 122	Re: 195.36.15: Use of hardware accelerated OpenGL kills X forcing power cycle Just a wild hint and apologize in advance for sounding goofy but could this be an issue of security, I know that SE Linux has to be disabled in Fedora for nvidia driver install so was just wondering.

03-29-10, 05:01 AM	#7
chickenandbeans Registered User Join Date: Mar 2010 Posts: 2	Re: 195.36.15: Use of hardware accelerated OpenGL kills X forcing power cycle AaronP: Good to know the problem is being looked at. With my hardware set up, the use of the nvidia driver is currently impossible. I'll try and get some gdb output at some point this week, but it's proving quite difficult because the machine freezes. selinux: Secure because nothing works with it No this is disabled on my set up. If I find a work around i'll post it here