http://bugzilla.suse.com/show_bug.cgi?id=942940 http://bugzilla.suse.com/show_bug.cgi?id=942940#c22 --- Comment #22 from Thomas Blume --- (In reply to Alexander Nolting from comment #21)

I've played with systemd only for fstrim. But after the issue came up I disabled it. With no change to the issue. The other optimizations made were related to mount /var/log etc... to tmpfs. As you can see this is also disabled as there were a message from rpm after updating once a time systemd saying that the folder /var/log/journal couldn't found in /var/log. But this issue must there for a longer time as my old /var/log folder on the root partition does also not have this subfolder <-- Note, that this laptop is updated to several openSUSE distribution over many years with no complete fresh installation at any time. Also the change from 13.1 to tumbleweed had shown no bigger issue with had forced my to open a bug report. From that perspective I'm quiet happy with stability and the qm by the staff working for openSUSE. :)

Uh, this makes it hard to reproduce. I've tried on a fresh tumbleweed installation, but didn't see the issue. However, after reinvestigation your logs, I've found this: -->-- Oct 05 17:58:42 linux-gwd0 systemd[1]: sysinit.target: Found ordering cycle on sysinit.target/start Oct 05 17:58:42 linux-gwd0 systemd[1]: sysinit.target: Breaking ordering cycle by deleting job cycle.service/start Oct 05 17:58:42 linux-gwd0 systemd[1]: cycle.service: Job cycle.service/start deleted to break ordering cycle starting with sysinit.target/start Oct 05 17:58:44 linux-gwd0 systemd[1]: pcscd.socket: Found ordering cycle on pcscd.socket/start Oct 05 17:58:44 linux-gwd0 systemd[1]: pcscd.socket: Breaking ordering cycle by deleting job cycle.service/start Oct 05 17:58:44 linux-gwd0 systemd[1]: cycle.service: Job cycle.service/start deleted to break ordering cycle starting with pcscd.socket/start Oct 05 17:58:46 linux-gwd0 systemd[1]: sysinit.target: Found ordering cycle on sysinit.target/start Oct 05 17:58:46 linux-gwd0 systemd[1]: sysinit.target: Breaking ordering cycle by deleting job cycle.service/start Oct 05 17:58:46 linux-gwd0 systemd[1]: cycle.service: Job cycle.service/start deleted to break ordering cycle starting with sysinit.target/start --<-- Ordering cycles are always bad, because they can badly affect the start sequence of services. My installation doesn't have any cycle.service, so this might be a relict from an older openSUSE version. Can you please check wheter there is a file: /etc/init.d/boot.cycle and if so, delete it? In addition, you are running systemd-219, which is quite old for tumbleweed. We currently have systemd-224. Would you mind updating your system to the current tumbleweed version? -- You are receiving this mail because: You are on the CC list for the bug.