nvidia-persistenced journalctl errors

Bug #1414417 reported by dino99
80
This bug affects 19 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Confirmed
High
Unassigned

Bug Description

vivid i386 booted with systemd 218-5ubuntu2, nvidia 346.35 & vivid genuine xorg/xserver

346.35 dependencies are set to conflict with nvidia-persistenced

/usr/share/doc/nvidia-346/html/nvidia-persistenced.html tell how to install it, but it fails into a terminal:
oem@u32:~$ % nvidia-persistenced
bash: fg: %: no such job
http://us.download.nvidia.com/XFree86/Linux-x86/346.35/README/nvidia-persistenced.html

and journalctl log:
janv. 25 08:04:31 u32 kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 346.35 Sat Jan 10 20:33:56 PST 2015
janv. 25 08:04:32 u32 nvidia-persistenced[424]: Started (424)
janv. 25 08:04:32 u32 nvidia-persistenced[427]: Failed to open PID file: File exists
janv. 25 08:04:32 u32 nvidia-persistenced[427]: Shutdown (427)
janv. 25 08:04:32 u32 nvidia-persistenced[424]: Failed to unlink socket: No such file or directory
janv. 25 08:04:32 u32 nvidia-persistenced[424]: Failed to unlink PID file: No such file or directory
janv. 25 08:04:32 u32 nvidia-persistenced[424]: Shutdown (424)

So some package(s) seems needing update; maybe needs to open xorg, xserver and/or systemd affected package(s) too.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-2.2-generic 3.19.0-rc4
Uname: Linux 3.19.0-2-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module 346.35 Sat Jan 10 20:33:56 PST 2015
 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu2)
ApportVersion: 2.15.1-0ubuntu2
Architecture: i386
BootDmesg: (Nothing has been logged yet.)
BootLog:

CurrentDesktop: GNOME
Date: Sun Jan 25 11:02:14 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 nvidia-346, 346.35, 3.18.0-9-generic, i686: installed
 nvidia-346, 346.35, 3.19.0-2-generic, i686: installed
 vboxhost, 4.3.20, 3.18.0-9-generic, i686: installed
 vboxhost, 4.3.20, 3.19.0-2-generic, i686: installed
GraphicsCard:
 NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:362e]
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-2-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro init=/lib/systemd/systemd
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC
version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1
version.libdrm2: libdrm2 2.4.58-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Sun Jan 25 08:04:54 2015
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Logitech USB RECEIVER MOUSE, id 8
 input AT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.16.2.901-1ubuntu3

Revision history for this message
dino99 (9d9) wrote :
description: updated
affects: xorg (Ubuntu) → nvidia-graphics-drivers (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Confirmed
Changed in nvidia-graphics-drivers (Ubuntu):
importance: Undecided → High
Revision history for this message
dino99 (9d9) wrote :

Get more details from journalctl when "debug" is added to the boot process:

(systemd 219-4ubuntu1 used)

systemd[1]: Received SIGCHLD from PID 503 (nvidia-persiste).
systemd[1]: Child 503 (nvidia-persiste) died (code=exited, status=1/FAILURE)
nvidia-persistenced[503]: Failed to open PID file: File exists
nvidia-persistenced[503]: Shutdown (503)
nvidia-persistenced[500]: Failed to unlink socket: No such file or directory
nvidia-persistenced[500]: Failed to unlink PID file: No such file or directory
nvidia-persistenced[500]: Shutdown (500)
systemd[1]: Received SIGCHLD from PID 500 (nvidia-persiste).
systemd[1]: Child 500 (nvidia-persiste) died (code=exited, status=0/SUCCESS)
systemd[1]: Received SIGCHLD from PID 331 (udevadm).
systemd[1]: Child 331 (udevadm) died (code=exited, status=0/SUCCESS)
systemd[1]: Child 331 belongs to systemd-udev-settle.service
systemd[1]: systemd-udev-settle.service: main process exited, code=exited, status=0/SUCCESS
systemd[1]: systemd-udev-settle.service changed start -> exited
systemd[1]: Job systemd-udev-settle.service/start finished, result=done
systemd[1]: Started udev Wait for Complete Device Initialization.
systemd[1]: systemd-udev-settle.service: cgroup is empty

Revision history for this message
dino99 (9d9) wrote : Re: [346.47] nvidia-persistenced journalctl errors

That issue is still logged with the latest ubuntu archive nvidia 346.47 and systemd 219-4ubuntu8

summary: - [xorg-edgers] [346.35] nvidia-persistenced journalctl errors
+ [346.47] nvidia-persistenced journalctl errors
Revision history for this message
dino99 (9d9) wrote :

kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 346.59 Tue Mar 31 13:19:00 PDT 2015
avril 10 03:12:55 u32 nvidia-persistenced[489]: Started (489)
avril 10 03:12:55 u32 nvidia-persistenced[492]: Failed to open PID file: File exists
avril 10 03:12:55 u32 nvidia-persistenced[492]: Shutdown (492)
avril 10 03:12:55 u32 nvidia-persistenced[489]: Failed to unlink socket: No such file or directory
avril 10 03:12:55 u32 nvidia-persistenced[489]: Failed to unlink PID file: No such file or directory
avril 10 03:12:55 u32 nvidia-persistenced[489]: Shutdown (489)

running systemd 219.6ubuntu3

summary: - [346.47] nvidia-persistenced journalctl errors
+ [346.59] nvidia-persistenced journalctl errors
Revision history for this message
dino99 (9d9) wrote : Re: [346.59] nvidia-persistenced journalctl errors

Well i've diggen around to understand that issue but fail to even catch the nvidia doc spirit: what is already deprecated or not ?
http://docs.nvidia.com/deploy/driver-persistence/index.html

their main comments:

NVIDIA will support both solutions for the near future (likely through Cuda 6.0), but will focus all future development and bug fixes on the daemon.

The daemon is installed in /usr/bin, while sample installation and init scripts are included with the driver in the documentation directory. The scripts are provided as a guide for installing the daemon to run on system startup for some common init systems; they may require some changes for certain distributions, due to the wide variety of init system configurations.

NVIDIA encourages customers to shift to this daemon approach at their earliest availability.

So is our kernel is using the 'legacy or 'daemon' nowadays ?

Revision history for this message
dino99 (9d9) wrote :

New test feedback:

- have ran: sudo apt-get purge nvidia* and then sudo apt-get install nvidia-346
- and now the journalctl error

 kernel: NVRM: loading NVIDIA UNIX x86 Kernel Module 346.72 Tue May 5 21:12:30 PDT 2015
 nvidia-persistenced[497]: Started (497)
 nvidia-persistenced[497]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 117 has read and write
 nvidia-persistenced[497]: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced
 nvidia-persistenced[497]: Shutdown (497)

*************** note: there is no /dev/nvidia* created ********

Revision history for this message
Hassan El Jacifi (waver) wrote :

Affect also 352:

juin 14 18:25:28 Jupiter nvidia-persistenced[2048]: Unable to access /var/run/nvidia-persistenced: No such file or directory

nvidia-352 352.09-0ubuntu0~xedgers15.04.2
nvidia-settings 352.09-0ubuntu0~xedgers15.04.1graphics driver

dino99 (9d9)
summary: - [346.59] nvidia-persistenced journalctl errors
+ nvidia-persistenced journalctl errors
tags: added: wily
dino99 (9d9)
tags: added: xenial
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.