ordering cycle on nvidia-persistenced.service/stop - unable to shutdown

Bug #1964352 reported by Eero Aaltonen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-510 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Shutdown from Gnome and `sudo shutdown -h now` stopped working in Ubuntu 20.04.4 LTS.
I have xserver-xorg-video-nvidia-510 installed.

journalctl bottom shows
```
march 09 15:45:13 myhost systemd[1]: basic.target: Found ordering cycle on nvidia-persistenced.service/stop
march 09 15:45:13 myhost systemd[1]: basic.target: Found dependency on systemd-backlight@backlight:nvidia_0.service/stop
march 09 15:45:13 myhost systemd[1]: basic.target: Found dependency on sysinit.target/stop
march 09 15:45:13 myhost systemd[1]: basic.target: Found dependency on acpid.path/stop
march 09 15:45:13 myhost systemd[1]: basic.target: Found dependency on paths.target/stop
march 09 15:45:13 myhost systemd[1]: basic.target: Found dependency on basic.target/stop
march 09 15:45:13 myhost systemd[1]: basic.target: Job nvidia-persistenced.service/stop deleted to break ordering cycle starting with basic.target/stop
march 09 15:45:13 myhost systemd[1]: Requested transaction contradicts existing jobs: Transaction for poweroff.target/start is destructive (nvidia-suspend.service has 'start' job queued, but 'stop>
march 09 15:45:13 myhost systemd-initctl[201461]: Failed to change runlevel: Transaction for poweroff.target/start is destructive (nvidia-suspend.service has 'start' job queued, but 'stop' is incl>
```

Tags: focal nvidia
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

  apport-collect 1964352

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: xorg (Ubuntu) → nvidia-graphics-drivers-510 (Ubuntu)
tags: added: focal nvidia
Changed in nvidia-graphics-drivers-510 (Ubuntu):
status: New → Incomplete
Revision history for this message
Eero Aaltonen (ejn) wrote :

apport-bug for xserver-xorg-video-nvidia-510

Revision history for this message
Eero Aaltonen (ejn) wrote :

apport-bug for nvidia-kernel-common-510

Revision history for this message
Eero Aaltonen (ejn) wrote :

The most relevant hardware in the system consists of:
1. Lenovo ThinkPad P1 Gen 3, https://ubuntu.com/certified/202009-28225
2. USB-C cable with Thunderbolt 3
3. Lenovo ThinkPad Thunderbolt 3 Workstation Dock Gen 2
4. External monitor connected to dock witg DisplayPort cable

Recent changes include:
1. package updates with
2. Enabling external display during boot

I enabled the external display from UEFI settings under
Config→Display→Boot Display Device→External Display

So the most recent boots have been with the laptop lid closed for the entire time.

Today, when I started investigating I learned that my system has not in fact booted up

$ systemd-analyze plot >bootup.svg
Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
eja@hel-falcon:~$ systemctl list-jobs
JOB UNIT TYPE STATE
1512 systemd-suspend.service start waiting
1511 suspend.target start waiting
1605 nvidia-resume.service start waiting
1604 nvidia-suspend.service start running

4 jobs listed.

$ systemctl status nvidia-suspend.service

verifies that the service is still
     Active: activating (start) since Thu 2022-03-10 10:17:22 EET; 2h 53min ago

Revision history for this message
Eero Aaltonen (ejn) wrote (last edit ):

Test case 2:
booted with laptop lid open.
Results:
$ systemd-analyze plot >bootup.svg
created an image → Boot has completed normally.

Test case 2b:
After open lid boot, closed laptop lid
Results:
$ systemctl status nvidia-suspend.service
● nvidia-suspend.service - NVIDIA system suspend actions
     Loaded: loaded (/lib/systemd/system/nvidia-suspend.service; enabled; vendor preset: enabled)
     Active: inactive (dead)

which is fine, I think.

Changed in nvidia-graphics-drivers-510 (Ubuntu):
status: Incomplete → New
Revision history for this message
Eero Aaltonen (ejn) wrote :

The problem is reproducible. Boot up just now with lid closed resulted in:

$ systemctl status nvidia-suspend.service
● nvidia-suspend.service - NVIDIA system suspend actions
     Loaded: loaded (/lib/systemd/system/nvidia-suspend.service; enabled; vendor preset: enabled)
     Active: activating (start) since Fri 2022-03-11 12:35:15 EET; 3min 14s ago

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.