FS#51495 - [nvidia-304xx] 132-1 crashes all GLX applications

Attached to Project: Arch Linux
Opened by Johnny Nielsen (Johnny.Nielsen) - Saturday, 22 October 2016, 10:26 GMT
Last edited by Laurent Carlier (lordheavy) - Tuesday, 21 February 2017, 13:45 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:
All GLX applications crash.

This is known in other distributions, and seems to be a serious upstream bug with 304.132
https://devtalk.nvidia.com/default/topic/972001/serious-regression-in-legacy-304xx-304-132-drivers/
https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/

Additional info:

* package version(s)
132-1-x86_64

* config and/or log files etc.
Output of glxinfo:
[me@mycomp ~]$ glxinfo
name of display: :0
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 87
Current serial number in output stream: 88
[me@mycomp ~]$

Hardware: GeForce 7300LE
Kernel: 4.8.3-1
X11 server: 1.18.4.

Downgrading the 304xx packages to their previous version makes the problem go away.
Tested successful downgrade:
nvidia-304xx (304.132-1 -> 304.131-17)
nvidia-304xx-libgl (304.132-1 -> 304.131-2)
nvidia-304xx-utils (304.131-2 -> 304.132-1)

Steps to reproduce:
Run any application using GLX.
For example try glxgears (from the mesa-demos package)
For example run nvidia-settings and try to enter the section "OpenGL/GLX information"

Would it be possible for Arch Linux to go back to version 131 until 132 has been fixed?
It breaks entire desktop environments (KDE/Plasma won't start) and makes many applications useless.
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Tuesday, 21 February 2017, 13:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  nvidia-304xx-304.134
Comment by Johnny Nielsen (Johnny.Nielsen) - Saturday, 22 October 2016, 10:27 GMT
Would it be possible for Arch Linux to go back to version 131 until 132 has been fixed?
It breaks entire desktop environments (KDE/Plasma won't start) and makes many applications useless.

Best regards
Johnny :o)
Comment by Johnny Nielsen (Johnny.Nielsen) - Saturday, 22 October 2016, 10:31 GMT
Woops, that successful downgrade should be:
nvidia-304xx (304.132-1 -> 304.131-17)
nvidia-304xx-libgl (304.132-1 -> 304.131-2)
nvidia-304xx-utils (304.132-1 -> 304.131-2)

Best regards
Johnny :o)
Comment by Allan (4llan) - Friday, 28 October 2016, 03:25 GMT
In my case, the downgrade of:
nvidia-304xx-lts (304.132-1 -> 304.131-11) [11 was the last that I had]
nvidia-304xx-libgl (304.132-1 -> 304.131-2)
nvidia-304xx-utils (304.132-1 -> 304.131-2)
just give me blank screen. X doesn't start.

Downgrading the linux-lts (4.4.27-1 -> 4.4.22-1) and voila.
Comment by Christos Nouskas (nous) - Sunday, 30 October 2016, 10:16 GMT
Confirmed on my side too, with the observation that glxinfo as root works. Downgrading to 304.131 fixes; didn't try downgrading the kernel.
Comment by Alex (Alexx) - Saturday, 05 November 2016, 09:11 GMT
I have the same problem, I'm using a gnome 3.22 and yesterday I upgraded to the new nvidia driver and my system does not load the login screen. It shows "ho not something has gone wrong", I'm using a gtx960 with all updated.

Comment by Ralph Corderoy (RalphCorderoy) - Friday, 30 December 2016, 15:13 GMT
Recent activity on one of the threads mentioned when this bug was opened suggests the problem has been fixed by nVidia, under their bug number 1835736, in the last few days with the release of 304.134.
https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/post/5043959/#5043959
Comment by Allan (4llan) - Thursday, 12 January 2017, 16:25 GMT
I'll test nvidia-304xx later, but in my old computer with nvidia-304xx-lts (304.134) the issue isn't fixed.
Comment by Ralph Corderoy (RalphCorderoy) - Thursday, 12 January 2017, 16:40 GMT
Just to be sure I'm talking about the same problem as my bug was closed
as a duplicate of this one, the fault shows itself when trying to play
videos, e.g.

$ mpv foo.mp4
Playing: foo.mp4
(+) Video --vid=1 (*) (h264)
(+) Audio --aid=1 --alang=eng (*) (aac)
[vo/opengl/x11] X11 error: BadValue (integer parameter out of range for operation)
[vo/opengl/x11] Type: 0, display: 0x7f2a6021ddc0, resourceid: 0, serial: 5d
[vo/opengl/x11] Error code: 2, request code: 9a, minor code: 3
[vo/opengl] Could not create GLX context!
libEGL warning: DRI2: failed to authenticate
[vo/opengl] Suspected software renderer or indirect context.
[vo/opengl/x11] X11 error: BadValue (integer parameter out of range for operation)
[vo/opengl/x11] Type: 0, display: 0x7f2a603b92c0, resourceid: 0, serial: 5d
[vo/opengl/x11] Error code: 2, request code: 9a, minor code: 3
[vo/opengl] Could not create GLX context!
[vo/vdpau] Error when calling vdp_device_create_x11: 1
[vo/xv] Warning: this legacy VO has bad quality and performance, and will in particular result in blurry OSD and subtitles. You should fix your graphics drivers, or not force the xv VO.
AO: [alsa] 48000Hz stereo 2ch float
VO: [xv] 640x360 yuv420p
AV: 00:00:04 / 00:31:14 (0%) A-V: -0.000
Comment by Ralph Corderoy (RalphCorderoy) - Friday, 13 January 2017, 13:19 GMT
vo/opengl is now used to play video once again with 304.134-1, thanks.
Just once slight error left.

$ grep `ymd`'.*nvidia' /var/log/pacman.log
[2017-01-13 12:38] [ALPM] upgraded nvidia-304xx-libgl (304.132-2 -> 304.134-1)
[2017-01-13 12:38] [ALPM] upgraded nvidia-304xx-utils (304.132-2 -> 304.134-1)
[2017-01-13 12:38] [ALPM] upgraded lib32-nvidia-304xx-utils (304.132-3 -> 304.134-1)
[2017-01-13 12:38] [ALPM] upgraded lib32-nvidia-304xx-libgl (304.132-3 -> 304.134-1)
[2017-01-13 12:38] [ALPM] upgraded nvidia-304xx (304.132-2 -> 304.134-1)
[2017-01-13 12:38] [ALPM-SCRIPTLET] In order to use nvidia module, reboot the system.
$
$ mpv foo.mp4
Playing: foo.mp4
(+) Video --vid=1 (*) (h264)
(+) Audio --aid=1 --alang=und (*) (aac)
[vo/opengl] retrieving framebuffer depth: OpenGL error INVALID_ENUM.
AO: [alsa] 48000Hz stereo 2ch float
VO: [opengl] 1280x720 yuv420p
AV: 00:00:10 / 00:58:32 (0%) A-V: 0.000
Comment by Darek (blablo) - Tuesday, 14 February 2017, 15:04 GMT Comment by Johnny Nielsen (Johnny.Nielsen) - Wednesday, 15 February 2017, 14:43 GMT
Fixed on my systems by upgrading to:

nvidia-304xx version 304.134
nvidia-304xx-libgl version 304.134
nvidia-304xx-utils version 304.134

Thanks for the good work :o) Keep it up :o)

Cheers :o)
Johnny :o)

Loading...