I recall that on one of my machines I had exactly the same situation as
reported in #20 and #21 up to the timings (5.3.0-26-generic in Ubuntu
19.10 with EFI Secure Boot and dual boot with Windows 10,
fastboot/hibernation disabled, LZ4 image by default, booting failed
often, booting succeeded upon reinstall with EFI secure boot).
Unfortunately, I don't have this machine any longer. @mario-gleirscher
would probably be of help if they provide us with some debugging when
asked by the Ubuntu maintainers.

On another machine, I still have this annoying printf in dmesg (and
journalctl -b):

[    0.215092] NET: Registered protocol family 1
[    0.215096] NET: Registered protocol family 44
[    0.215105] pci 0000:00:02.0: Video device with shadowed ROM at [mem 
[    0.215670] PCI: CLS 64 bytes, default 64
[    0.215696] Trying to unpack rootfs image as initramfs...
[    0.303126] Initramfs unpacking failed: Decoding failed
[    0.306614] Freeing initrd memory: 48364K

I run 5.4.0-42-generic in Ubuntu 20.04.1 LTS focal.

As for me, this issue seems to simply uselessly burn processor cycles
(and, as every such issue, indirectly generate superfluous carbon
dioxide); there is a potential for optimization here.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
Status in linux package in Ubuntu:

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

  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:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to