Bug 7556

Summary:	nvclock clashes with a segmentation fault if not invoked as root
Product:	Mageia	Reporter:	Vladimir Gurevich <mageia>
Component:	RPM Packages	Assignee:	José Jorge <lists.jjorge>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	nvclock-0.8-0.b4.5.mga2	CVE:
Status comment:

Description Vladimir Gurevich 2012-09-23 20:10:20 CEST

Invoking nvclock or nvclock_gtk with any meaningful parameters results in a segmentation fault. 

I think it started after upgrading to NVIDIA drivers version 304.43.

Here are some examples:

[vag@umka ~]$ nvclock -i
Segmentation fault
[vag@umka ~]$ nvclock -l
Segmentation fault
[vag@umka ~]$ nvclock_gtk 
Segmentation fault

Running as root is mostly OK:

[root@umka vag]# nvclock -i
-- General info --
Card:           nVidia Quadro NVS 135M
Architecture:   G86 A2
PCI id:         0x42b
GPU clock:      182.248 MHz
Bustype:        PCI-Express

-- Shader info --
Clock: 594.000 MHz
Stream units: 16 (1b)
ROP units: 4 (1b)
-- Memory info --
Amount:         128 MB
Type:           128 bit DDR2
Clock:          799.200 MHz

-- PCI-Express info --
Current Rate:   16X
Maximum rate:   16X

-- Sensor info --
Sensor: GPU Internal Sensor
GPU temperature: 70C
Fanspeed: 100.0%

-- VideoBios information --
Version: 60.86.47.00.01
Signon message: G86MV G3-64 Dawson sku0 VGA BIOS
Performance level 0: gpu 275MHz/shader 550MHz/memory 200MHz/1.15V/100%
Performance level 1: gpu 400MHz/shader 800MHz/memory 400MHz/1.15V/100%
VID mask: 3
Voltage level 0: 1.00V, VID: 4
Voltage level 1: 1.15V, VID: 0
Voltage level 2: 1.18V, VID: 2
Voltage level 3: 1.20V, VID: 3

[root@umka vag]# nvclock -l 
Available OpenGL options:
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  156 (NV-CONTROL)
  Minor opcode of failed request:  2 ()
  Serial number of failed request:  29
  Current serial number in output stream:  29
 fsaa aniso quality vsync flipping texsharpen texclamping

This is strange since NV-CONTROL extension is there, but maybe something changed in the driver...

nvclock_gtk also seems to work.

Not sure, whether root privileges are really required for these programs to work, but in any case they shouldn't segfault. Before, I used to invoke nvclock_gtk right from the application menu, though.

Comment 1 Vladimir Gurevich 2012-09-23 20:13:18 CEST

Just in case, here is a GDB trace:

[vag@umka ~]$ gdb nvclock
GNU gdb (GDB) 7.5-1.mga3 (Mageia release 3)
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-mageia-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/nvclock...Reading symbols from /usr/lib/debug/usr/bin/nvclock.debug...done.
done.
(gdb) run -i
Starting program: /usr/bin/nvclock -i

Program received signal SIGSEGV, Segmentation fault.
0x0000000000414290 in load_bios_pramin ()
(gdb) bt
#0  0x0000000000414290 in load_bios_pramin ()
#1  0x0000000000414099 in dump_bios ()
#2  0x0000000000406d56 in create_config ()
#3  0x000000000040652c in open_config ()
#4  0x00000000004113aa in init_nvclock ()
#5  0x0000000000402805 in main ()
(gdb)

Manuel Hiebel 2012-09-23 20:55:39 CEST

Assignee: bugsquad => lists.jjorge

Comment 2 José Jorge 2012-11-21 17:13:45 CET

I cannot reproduce in i586. Still, I have rebuilt nvclock against new libs.
Please re-open if the bug is still there.

[jose@localhost nvclock]$ nvclock -i
Error: You don't have enough permissions to run NVClock! Retry as root or install the Nvidia drivers.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME

Comment 3 Vladimir Gurevich 2012-12-20 18:20:30 CET

Still fails on x86_64

Status: RESOLVED => REOPENED
Resolution: WORKSFORME => (none)

Comment 4 José Jorge 2013-01-05 21:35:51 CET

(In reply to comment #3)
> Still fails on x86_64

I could get my hands on a 9500GS (NV96) and I got this crash if not root, while with a 6200 it does not crash.

But, as upstream devel is stuck for 3 years, I think this project is dead. As nouveau kernel driver is now managing power management, this project will end being useless.

For now, I keep it in the distro for old hardware where it might still be handfull.

If someone really wants this to be fixed, wake up the upstream project!

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX