touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Yes, it's certainly a race condition of some sort. Unfortunately quite
impossible to debug remotely as there are no available logs/kernel
traces :-(  SysRQ missing is also a bit unhelpful there (yes, it's
usually Alt+PrintScr); does that work if boot works normally? If it just
doesn't work with that hang, then the kernel is so thoroughly locked up
that not even SysRQ helps. Maybe try with a different keyboard?

> And why systemd 208 was always successful, but 215 not?

Well, that's exactly the $10,000 question that this report is about :-)
It has slightly different udev rules and does different things at
bootup, but there's been a lot of changes between those versions.

Do you get the hang if you boot without "quiet" and also without
"splash"? That's text-mode only and might be a bit faster again.

-- 
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