Martin, In addition the previous post #8
I tried again booting without "quiet" in the kernel line: 10/10 boots were successful. Then with "quiet": 3 out of 10 did hang. Hanging (or crash) happens right after the fsck is done. Mostly after sda1 fsck and before sdb1 fsck. Sometimes both sda1 and sdb1 fsck lines are visible after the hang, indicating they both been done. So, if booting always succeeds without "quiet" (slow boot) and hang only occurs with "quiet" (fast boot), can that be an indication of an unsuccessful race condition, followed by a hang or crash? And why systemd 208 was always successful, but 215 not? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1385630 Title: systemd 215 hangs during boot Status in “systemd” package in Ubuntu: Incomplete Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
