Due to commit #ddf0b98 nvidia-mig-manager.service wants to start after systemd-resolved, but before sysinit.
systemd-resolved hower wants to run before sysinit -> break.
Please remove this commit.
Jul 25 10:03:28 hqc4020-sn5 systemd[1]: sysinit.target: Found ordering cycle on systemd-resolved.service/start
Jul 25 10:03:28 hqc4020-sn5 systemd[1]: sysinit.target: Found dependency on nvidia-mig-manager.service/start
Jul 25 10:03:28 hqc4020-sn5 systemd[1]: sysinit.target: Found dependency on sysinit.target/start
Jul 25 10:03:28 hqc4020-sn5 systemd[1]: sysinit.target: Job systemd-resolved.service/start deleted to break ordering cycle starting with sysinit.target/start
sudo systemctl cat systemd-resolved.service
[Unit]
After=systemd-sysctl.service systemd-sysusers.service
Before=sysinit.target network.target nss-lookup.target shutdown.target initrd-switch-root.target
-> means run after sysinit
sudo systemctl cat nvidia-mig-manager.service
[Unit]
After=sysinit.target local-fs.target
Before=basic.target nvidia-persistenced.service systemd-resolved.service
-> means run after systemd-resolved (which should run after sysinit), but before sysinit -> break
klueska
commented
2 months ago
Due to commit #ddf0b98 nvidia-mig-manager.service wants to start after systemd-resolved, but before sysinit. systemd-resolved hower wants to run before sysinit -> break.
Please remove this commit.