Hi Brian! Am 19.05.2011 03:05, schrieb brian m. carlson: > 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.
Could you please attach the complete microcode.ctl sysv init script (or even better a tarball of /etc/init.d) so we can have a look what causes the cycle. 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*. At least it should be logged. But yeah, not having dbus is kind of a showstopper for a desktop system. That said, which version did you use? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
