[Bug 1720131] Re: logind holds open file descriptor to DRI nodes, preventing nvidia suspend
Ard van Breemen
ard at kwaak.net
Fri Apr 26 16:27:21 UTC 2019
The bug prevents use of systems "blessed" with nvidia optimus.
It has been fixed however.
https://github.com/systemd/systemd/issues/6908
I hope the fix can be incorporated into bionic, because it would be sad to have an LTS release that can not turn of the nvidia GPU without rebooting the system.
Of course the fix is to upgrade to systemd 238, and the new bugs in 238 are fixed in 238+10.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1720131
Title:
logind holds open file descriptor to DRI nodes, preventing nvidia
suspend
Status in systemd:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Bug description:
The nvidia binary kernel driver now creates /dev/dri/card? nodes.
When switching between the nvidia and intel drivers on a hybrid
system, all holders of the DRI node need to relinquished so that the
nvidia driver can be unloaded so that bbswitch can turn the card off.
In order for switching hybrid graphics to not require a reboot, logind
needs to close its file descriptor to the nvidia DRI node.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu10
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 28 08:36:13 2017
InstallationDate: Installed on 2017-09-20 (8 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System76 Oryx Pro
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=ZFS=rpool/system ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.02dRSA1 02/20/2017
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76
dmi.board.version: oryp3-ess
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.version: oryp3-ess
dmi.sys.vendor: System76
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1720131/+subscriptions
More information about the foundations-bugs
mailing list