I also see this breakage with microcode.ctl, which, AFAICT, only starts
in 2345, not in S:

  May 19 00:17:22 lakeview systemd[1]: Found ordering cycle on 
sysinit.target/start
  May 19 00:17:22 lakeview systemd[1]: Walked on cycle path to 
microcode.ctl.service/start
  May 19 00:17:22 lakeview systemd[1]: Walked on cycle path to 
basic.target/start
  May 19 00:17:22 lakeview systemd[1]: Walked on cycle path to 
sockets.target/start
  May 19 00:17:22 lakeview systemd[1]: Walked on cycle path to dbus.socket/start
  May 19 00:17:22 lakeview systemd[1]: Walked on cycle path to 
sysinit.target/start
  May 19 00:17:22 lakeview systemd[1]: Breaking ordering cycle by deleting job 
microcode.ctl.service/start

I'm not sure what service thought that microcode.ctl was in any way
essential.  While uploading fixed microcode can fix some small bugs, one
must assume that whatever microcode the processor has built into it is
functional enough to boot the system.  While it (correctly) picked
microcode.ctl to ignore this time, it previously picked dbus, which led
to a spectacular failure of myriad services to start *with no comment*.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

Attachment: signature.asc
Description: Digital signature

Reply via email to