[Bug 1459475] Re: friendly-recovery slows down boot time

[Martin Pitt]

Phillip Susi [2015-05-28 12:48 -0000]:
> While we're at it, do you have any idea how to trace why it takes 6
> seconds for udev to settle?

That's mostly "don't shoot the messenger". Usually it's kernel drivers
taking long to initialize (check dmesg for what comes online at what
point); occasionally it's also a bug in some udev callout.

You can boot with "debug" to get events, drivers, udev rules etc.
shown in dmesg verbosely, perhaps that reveals something?

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/1459475

Title:
  friendly-recovery slows down boot time

Status in friendly-recovery package in Ubuntu:
  In Progress

Bug description:
  I noticed that systemd-fsck-root.service runs very late in my boot,
  which slows it down.  This turns out to be due to friendly-
  recovery.service being After=udev settle, and Before=systemd-fsck-
  root.service.  This causes fsck-root to wait until after udev settle,
  which takes quite some time ( which is probably another issue ), even
  though during normal boots, friendly-recovery is not run at all due to
  its Condition depending on the kernel command line recovery argument.

  Is there a way to reorganize the relationships so that the transitive
  ordering is not triggered when friendly-recovery is not run at all?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1459475/+subscriptions