nvidia driver stops on setting color profile

Bug #1639557 reported by Wolf Rogner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-367 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Every other time the boot process is halted by the NVIDIA card

Log entries:

Nov 6 11:49:09 mbpr15 systemd-resolved[1109]: Processing query...
Nov 6 11:49:14 mbpr15 systemd[1]: Stopping NVIDIA Persistence Daemon...
Nov 6 11:49:14 mbpr15 nvidia-persistenced: Received signal 15
Nov 6 11:49:14 mbpr15 systemd[1]: Stopping Manage, Install and Generate Color Profiles...
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

Reboot required

Normal behaviour would be:

Nov 6 11:49:42 mbpr15 nvidia-persistenced: Received signal 15
Nov 6 11:49:42 mbpr15 systemd[1]: Stopping NVIDIA Persistence Daemon...
Nov 6 11:49:42 mbpr15 whoopsie[1034]: [11:49:42] Using lock path: /var/lock/whoopsie/lock
Nov 6 11:49:42 mbpr15 nvidia-persistenced: Socket closed.
Nov 6 11:49:42 mbpr15 nvidia-persistenced: PID file unlocked.
Nov 6 11:49:42 mbpr15 nvidia-persistenced: PID file closed.
Nov 6 11:49:42 mbpr15 nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced
Nov 6 11:49:42 mbpr15 nvidia-persistenced: Shutdown (1036)
Nov 6 11:49:42 mbpr15 whoopsie[1034]: [11:49:42] Could not get the Network Manager state:
Nov 6 11:49:42 mbpr15 whoopsie[1034]: [11:49:42] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
...

There is no guarantee that the boot process works the next time (so I have to try several times).

A workaround is to boot into recovery mode and continue from there (works always).

I have tested the videocard with macOS and the card is reported to work fine (several times).

This behaviour is new to 16.10 (nvidia-367, proprietary, tested). It does not occur using the X.Org Nouveau driver (this one is just dead slow and does not work well with presentation equipment).

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nvidia-367 367.57-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 6 11:53:31 2016
InstallationDate: Installed on 2016-10-22 (15 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nvidia-graphics-drivers-367
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Wolf Rogner (war-rsb) wrote :
Revision history for this message
Wolf Rogner (war-rsb) wrote :
Revision history for this message
Wolf Rogner (war-rsb) wrote :

Maybe these two logs help

the old one is the one where the boot process stopped

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.