|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd doesn't start dbus on cycles | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Richard Brown <RBrownCCB> |
| Component: | GNOME | Assignee: | Frederic Crozat <fcrozat> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P1 - Urgent | CC: | coolo, koenig |
| Version: | Factory | Flags: | coolo:
SHIP_STOPPER+
|
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
dmesg output when xdm fails to start
dmesg for broken xdm/gdm startup at boot |
||
|
Description
Richard Brown
2011-10-22 11:46:51 UTC
please check dmesg if you can see any systemd cycles. *** Bug 725656 has been marked as a duplicate of this bug. *** Created attachment 458357 [details]
dmesg output when xdm fails to start
Attached is the dmesg output when xdm fails to start, doesn't appear to be very useful.
No, it's very useful. open-isci init script is problematic - I don't see how though [ 9.335402] systemd[1]: Found ordering cycle on basic.target/start [ 9.335406] systemd[1]: Walked on cycle path to sockets.target/start [ 9.335409] systemd[1]: Walked on cycle path to dbus.socket/start [ 9.335411] systemd[1]: Walked on cycle path to sysinit.target/start [ 9.335413] systemd[1]: Walked on cycle path to open-iscsi.service/start [ 9.335415] systemd[1]: Walked on cycle path to network.target/start [ 9.335418] systemd[1]: Walked on cycle path to NetworkManager-wait-online.service/start [ 9.335420] systemd[1]: Walked on cycle path to NetworkManager.service/verify-active [ 9.335422] systemd[1]: Walked on cycle path to basic.target/start [ 9.335424] systemd[1]: Breaking ordering cycle by deleting job dbus.socket/start I can confirm that uninstalling open-iscsi gets xdm starting up on reboot again..interesting. I don't see how its causing this problem however I don't get it either, open-iscsi looks harmless. possible the co-existance of boot.open-iscsi and open-iscsi confuses systemd. It does confuse me :) (In reply to comment #2) > *** Bug 725656 has been marked as a duplicate of this bug. *** indeed (full dmesg-systemd-1 attached)! how to get rid of this (such) cycle(s) ? $ dmesg | grep systemd [ 5.882291] systemd[1]: systemd 37 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; suse) [ 6.293614] systemd[1]: Set hostname to <linux-fudg.site>. [ 8.826441] systemd[1]: Found ordering cycle on basic.target/start [ 8.826450] systemd[1]: Walked on cycle path to sockets.target/start [ 8.826456] systemd[1]: Walked on cycle path to dbus.socket/start [ 8.826461] systemd[1]: Walked on cycle path to sysinit.target/start [ 8.826466] systemd[1]: Walked on cycle path to open-iscsi.service/start [ 8.826471] systemd[1]: Walked on cycle path to network.target/start [ 8.826476] systemd[1]: Walked on cycle path to NetworkManager-wait-online.service/start [ 8.826482] systemd[1]: Walked on cycle path to NetworkManager.service/verify-active [ 8.826487] systemd[1]: Walked on cycle path to basic.target/start [ 8.826492] systemd[1]: Breaking ordering cycle by deleting job dbus.socket/start [ 8.826507] systemd[1]: Found ordering cycle on basic.target/start [ 8.826512] systemd[1]: Walked on cycle path to sysinit.target/start [ 8.826516] systemd[1]: Walked on cycle path to open-iscsi.service/start [ 8.826521] systemd[1]: Walked on cycle path to network.target/start [ 8.826526] systemd[1]: Walked on cycle path to NetworkManager-wait-online.service/start [ 8.826532] systemd[1]: Walked on cycle path to NetworkManager.service/verify-active [ 8.826537] systemd[1]: Walked on cycle path to basic.target/start [ 8.826542] systemd[1]: Breaking ordering cycle by deleting job open-iscsi.service/start [ 22.031144] systemd-fsck[748]: /dev/sda1: sauber, 265/40000 Dateien, 51194/159744 Bl\xffffffc3\xffffffb6\xffffffb6cke the last line of systemd-fsck with german msg doesn't fit in the all-english syslog msgs, and what happend to the german umlaut-o (UTF8 0xc3 0xb6) ? and why does 0xb6 show up twice ??? (-> bug #725993) back to the systemd cycle: I tried "rpm -e open-iscsi", and now it looks "somewhat" better: # dmesg | grep systemd [ 5.713276] systemd[1]: systemd 37 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP; suse) [ 6.076103] systemd[1]: Set hostname to <linux-fudg.site>. [ 26.867730] systemd-fsck[759]: /dev/sda1: sauber, 265/40000 Dateien, 51194/159744 Bl\xffffffc3\xffffffb6\xffffffb6cke (X11 still does not show up but now the Xserver crashes -- different report #725996 ...) Created attachment 458383 [details]
dmesg for broken xdm/gdm startup at boot
systemd has a hard time to figure dependencies when two initscripts have the same name and one is a "boot" initscript. I'm looking at how to solve the issue. was already filled some time ago, let's handle it there. *** This bug has been marked as a duplicate of bug 661401 *** |