[Bug 1823391] Re: /lib/systemd/system/grub-initrd-fallback.service may be sequenced too early

Mathieu Trudel-Lapierre mathieu.tl at gmail.com
Wed Jun 5 19:50:06 UTC 2019


I'm currently working on this. It's unclear, after brief testing on AWS,
what the impact of grub-initrd-fallback.service is (even when re-
ordering it's start); but the changes are done and I'll include them
with the grub2 merge.

** Changed in: grub2 (Ubuntu)
       Status: New => In Progress

** Changed in: grub2 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: grub2 (Ubuntu)
     Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  /lib/systemd/system/grub-initrd-fallback.service may be sequenced too
  early

Status in grub2 package in Ubuntu:
  In Progress

Bug description:
  The new /lib/systemd/system/grub-initrd-fallback.service introduced in
  disco and related to initramfsless fallback handling declares itself a
  dependency of the sysinit.target, which is quite early in boot.  This
  shows up in boot charts of various cloud guest instances, implying
  that it does have an impact on boot speed.

  We should evaluate if this can be made a dependency of multi-
  user.target + rescue.target + emergency.target instead (which, per
  bootup(7), I believe covers all of the relevant targets we might be
  booting to).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1823391/+subscriptions



More information about the foundations-bugs mailing list