Description of problem: The cpuspeed service isn't running after booting. The only relevant lines in /var/log/messages are: Sep 8 17:00:54 Mobile-PC cpuspeed: Enabling ondemand cpu frequency scaling governor Sep 8 17:05:44 Mobile-PC cpuspeed: Disabling ondemand cpu frequency scaling governor Sep 8 17:06:46 Mobile-PC kernel: init[1]: Walked on cycle path to cpuspeed.service/start The service can be started by "sudo systemctl start cpuspeed.service". This problem didn't exist on version 8. Oddly, my system controlled wifi successfully starts at boot, unlike bruno who commented in bodhi. Version-Release number of selected component (if applicable): 9-3.fc14 How reproducible: Easily. Steps to Reproduce: 1. Update to systemd-9-3.fc14. 2. Reboot. 3. Actual results: The cpuspeed service isn't running. Expected results: It should be running. Additional info:
> Sep 8 17:06:46 Mobile-PC kernel: init[1]: Walked on cycle path to > cpuspeed.service/start Please attach the full log. We need to see what the full cycle is about.
Created attachment 446346 [details] Contents of /var/log/messages for most recent boot with systemd-9-3.fc14
The log shows ondemand frequency scaling was enabled. But there are dep cycles indeed. init[1]: Found ordering cycle on haldaemon.service/start init[1]: Walked on cycle path to irqbalance.service/start init[1]: Walked on cycle path to restorecond.service/start init[1]: Walked on cycle path to jexec.service/start init[1]: Walked on cycle path to haldaemon.service/start init[1]: Breaking ordering cycle by deleting job haldaemon.service/start init[1]: Found ordering cycle on haldaemon.service/start init[1]: Walked on cycle path to cpuspeed.service/start init[1]: Walked on cycle path to restorecond.service/start init[1]: Walked on cycle path to jexec.service/start init[1]: Walked on cycle path to haldaemon.service/start init[1]: Breaking ordering cycle by deleting job haldaemon.service/start init[1]: Found ordering cycle on haldaemon.service/start init[1]: Walked on cycle path to restorecond.service/start init[1]: Walked on cycle path to jexec.service/start init[1]: Walked on cycle path to haldaemon.service/start init[1]: Breaking ordering cycle by deleting job haldaemon.service/start init[1]: Found ordering cycle on haldaemon.service/start init[1]: Walked on cycle path to jexec.service/start init[1]: Walked on cycle path to haldaemon.service/start init[1]: Breaking ordering cycle by deleting job haldaemon.service/start Looks related to bug 631620.
Yes, it was enabled, but that start was my manual systemctl after logging in. Gene
Hm, I see. That makes the symptoms even more similar to bug 631620 - a dependency loop (involving haldaemon) is detected, the cycle is claimed to be broken by removing a service and a different service from the loop is removed. *** This bug has been marked as a duplicate of bug 631620 ***