** Changed in: nvclock (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039916
Title:
Nvidia driver causing SIGSEGV in nvclock and smartdimmer
To manag
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-updates (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
A ray of hope for the alternative. After fixing a bug in the nvidiabl
kernel module[1] I can use the standard OS brightness controls to
control the backlight. More work needs to be done on that, and it needs
to be brought into Ubuntu, but it is the proper solution and it does
work for many devices.
Discussion with Adam Conrad on IRC #ubuntu-devel:
A recent change to the nvidia DKMS drivers package has broken another
package such that it won't conceivably ever work again. What's the procedure in
such cases?
TJ-: That might need to be slightly less vague.
infinity: bug #1039916 ... look a
Two tests have confirmed that the nvidia driver DKMS package security patches
are the cause of the breakage to nvclock/smartdimmer. The upshot is that maybe
'nvclock' should be removed from the archives since the security patches
appear sane and are important to protect most users.
After reversi
The blacklisted entry was introduced by the latest security patch to the
nvidia drivers.
nvidia-graphics-drivers-updates (295.49-0ubuntu0.2) precise-security;
urgency=low
* SECURITY UPDATE: privilege escalation via kernel memory access
- debian/dkms/patches/blacklist-vga-pmu-registers.patch
After adding debug logging to the nvidia kernel module's source-code -
at every point in nv-map.c::nv_kern_mmap() where it sets an error in the
'status' variable - I have been able to pin-point where the allocation
is being refused.
It is this code:
vma->vm_ops = &nv_vm_ops;
if (IS_REG_O
Further analysis shows the nvidia driver failing to allocate the
requested memory mappings.
Enabling nvidia kernel module's debug output
$ cat /etc/modprobe.d/nvidia-current-updates.conf
options nvidia-current-updates NVreg_ResmanDebugLevel=0
and integrating it into the smartdimmer output:
$ s
More detail, including the process memory map.
$ sudo ./smartdimmer -g
OK: map_mem(): PEXTDEV register 0xd5101000 requested 0x1000 and received
0x1000 after0 attempts at 0x7f709064e000
OK: map_mem(): PFB register 0xd510 requested 0x1000 and received
0x1000 after0
My last comment was messed up by my failing to refactor after a mass cut
and paste operation. Here's a better, clearer view of what is going on:
$ ./smartdimmer -g
OK: map_mem(): PEXTDEV register 0xd5101000 requested 0x1000 and received
0x1000 after0 attempts at 0x7f3a97e76000
OK:
The issue is being caused by calls the system's mmap() function failing
to allocate the requested VMA mappings.
After some further debugging and playing with values I modified
backend/back_linux.c::map_dev_mem() so that when mmap() returns
MAP_FAILED the function adjusts the requested allocation t
A better summary:
(gdb) p /x *nv_card
$13 = {card_name = 0x41332c, number = 0x0, caps = 0x0, device_id = 0x398,
subvendor_id = 0x0, arch = 0x8000,
reg_address = 0xd500, dev_name = 0x61e250, devbusfn = 0x100, irq = 0x10,
base_freq = 0x0, gpu = 0x3, debug = 0x0,
bios = 0x0, have_coolbits
The route of the problem is that the nvidia driver returns invalid
values for PCIO, PDISPLAY and PRAMIN.
Breakpoint 6, map_mem (dev_name=0x61e250 "/dev/nvidia0") at backend.c:34
34 dev_handle_t *fd = open_dev(dev_name);
(gdb) n
36 if(!fd) /* open_dev has already set the e
For those users simply wanting to control the backlight (and currently
using smartdimmer) a better alternative with active development is
Guillaume Zin's "nvidiabl" kernel-module project. This presents a
standard /sys/class/backlight/ node that the system can control using
all existing tools.
http
This bug causes a regression for bug #95444 "No Screen Backlight
Control; Notebooks (Vaio, Macbook, HP/Compaq, Samsung, Zepto et al.)
with Nvidia Geforce8/Geforce9/Quadro series graphics" which was marked
'Fix Released' 2009-03-27.
** Changed in: nvclock (Ubuntu)
Status: Confirmed => In P
** Changed in: nvclock (Ubuntu)
Importance: Undecided => Medium
** Changed in: nvclock (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvclock (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1039916
Title:
Nv
17 matches
Mail list logo
