[Bug 1835660] Re: initramfs unpacking failed
TJ
1835660 at bugs.launchpad.net
Sat Jul 25 19:07:16 UTC 2020
Is part of the issue here that some (most) initramfs-tools created
images have an uncompressed early CPU microcode firmware prefixed ?
That is stored as ASCII CPIO which is why Con see's that reported by
'file' since that tool checks the magic signatures at start of a file.
binwalk reveals more detail.
--
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