Nvidia prime intel profile segfaults on login

Bug #1632035 reported by Peter Lopen
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
nvidia-prime (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

when using nvidia profile, everything works fine.
After switching to intel profile, with:
peter@dell:~$ sudo prime-select intel
Info: the current GL alternatives in use are: ['nvidia-370', 'nvidia-370']
Info: the current EGL alternatives in use are: ['nvidia-370', 'nvidia-370']
Info: selecting nvidia-370-prime for the intel profile
update-alternatives: using /usr/lib/nvidia-370-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-370-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-370-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in manual mode
update-alternatives: using /usr/lib/nvidia-370-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in manual mode

system crashes on next login, with following message in X logs:
42977.276] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55812efd1ade]
[ 42977.276] (EE) 1: /usr/lib/xorg/Xorg (0x55812ee1f000+0x1b6e69) [0x55812efd5e69]
[ 42977.277] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fa62d7c3000+0x354a0) [0x7fa62d7f84a0]
[ 42977.277] (EE) 3: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fa628778000+0xadcbe) [0x7fa628825cbe]
[ 42977.277] (EE) 4: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fa628778000+0x4e25d) [0x7fa6287c625d]
[ 42977.277] (EE) 5: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fa628778000+0x84735) [0x7fa6287fc735]
[ 42977.277] (EE) 6: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fa628778000+0x5a73ae) [0x7fa628d1f3ae]
[ 42977.277] (EE)
[ 42977.277] (EE) Segmentation fault at address 0x28

peter@dell:~$ lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04

thank you

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nvidia-prime 0.8.2
Uname: Linux 4.7.2-040702-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Oct 10 19:28:33 2016
InstallationDate: Installed on 2016-04-22 (171 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Peter Lopen (peter-lopen) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-prime (Ubuntu):
status: New → Confirmed
Changed in nvidia-prime (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Reed Love (thedesertsong) wrote :

Hi there.

I'm also having the exact same issue on a Dell Inspiron 15 7559 running Ubuntu 17.04 beta 2, and had the same issue with 16.04 and 16.10.

As long as you just leave it in NVIDIA mode, the laptop runs beautifully... Once "prime-select intel" is invoked and you log out, the system hard locks when trying to load X.

Booting in to rescue mode "mount -o rw,remount /" and running "prime-select nvidia" seems to fix it.

I just now took a look at the "prime-select" script and am happy to see that it's written in Python since it's a language I'm familiar with.

I'll start fartin' around with it and see if I can make some sense of what's going on, otherwise I hope that we can get some traction on fixing this. XD

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.