https://bugzilla.novell.com/show_bug.cgi?id=737636
https://bugzilla.novell.com/show_bug.cgi?id=737636#c15
Marius Tomaschewski
Created an attachment (id=474575) --> (http://bugzilla.novell.com/attachment.cgi?id=474575) [details] dmesg output of failure after updating to test version
Spoke too soon. On the 5th reboot it shows the original (erroneous) behaviour again, attached is the dmesg.
Look at the wrong start order -- systemd also starts most network depending services incl. remote-fs before network: [ 7.024754] systemd[1]: Installed new job remote-fs.target/start as 65 [ 7.024757] systemd[1]: Installed new job syslog.service/start as 66 [ 7.024760] systemd[1]: Installed new job nfs-secure.service/start as 69 [ 7.024764] systemd[1]: Installed new job var-lib-nfs-rpc_pipefs.mount/start as 70 [ 7.024767] systemd[1]: Installed new job rpcbind.service/start as 71 .. [ 7.024833] systemd[1]: Installed new job network.service/start as 88 [ 7.024836] systemd[1]: Installed new job network.target/start as 89 I don't think I can fix (work around) here something in the network script. See also bug 744293 -- does the systemd dependency fix helps in your case? Perhaps network simply gets stopped because of a try to resolve the deps? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.