[Bug 1835660] Re: initramfs unpacking failed
Zakhar
1835660 at bugs.launchpad.net
Thu May 21 09:58:02 UTC 2020
Confirmed also on a clean 20.04, kernel 5.4.0-31-generic
The time difference between gzip and lz4 is not noticeable by the user:
LZ4:
Startup finished in 14.815s (firmware) + 3.483s (loader) + 1.879s (kernel) + 23.176s (userspace) = 43.354s
graphical.target reached after 23.164s in userspace
GZIP:
Startup finished in 14.760s (firmware) + 3.441s (loader) + 2.276s (kernel) + 22.805s (userspace) = 43.283s
graphical.target reached after 22.775s in userspace
Actually, same as one poster above, it's a fraction of second faster
with gzip... but that could be in the limits of the precision of this
kind of measure.
So I'll stick to GZIP until the bug is fixed.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking failed
Status in initramfs-tools package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Confirmed
Bug description:
"initramfs unpacking failed: Decoding failed", message appears on
boot up.
If I "update-initramfs" using gzip instead of lz, then boot up passes
without decoding failed message.
---
However, we currently believe that the decoding error reported in
dmesg is actually harmless and has no impact on usability on the
system.
Switching from lz4 to gzip compression, simply papers over the
warning, without any benefits, and slows down boot.
Kernel should be fixed to correctly parse lz4 compressed initrds, or
at least lower the warning, to not be user visible as an error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions
More information about the foundations-bugs
mailing list