[Kernel-packages] [Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
In case -proposed in Focal's HWE needs also verification: could someone with a 5675C or 5775C test 5.8.0-31.33~20.04.1 with the corresponding patch as well? I've unfortunately no access to my Broadwell machine for the next 5-7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in linux-hwe-5.8 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Bug description: 5.8 kernel hangs on boot on my PC with Intel Core i7-5775C. Bug is already fixed upstream: https://gitlab.freedesktop.org/drm/intel/-/issues/2381 https://bugzilla.kernel.org/show_bug.cgi?id=208737 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1=1664ffee760a5d98952318fdd9b198fae396d660 Please backport the fix. Thanks! [Impact] * Bug causes boot failure on common hardware. [Test Case] * Test kernel validated by submitter (see Comment #6). [Regression Potential] * Low: Simple cherry-pick from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1903397] Re: Groovy 5.8 kernel hangs on boot on CPUs with eLLC
Will this land in Focal's HWE package as well? Just wondering because only Groovy is listed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1903397 Title: Groovy 5.8 kernel hangs on boot on CPUs with eLLC Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Fix Committed Bug description: 5.8 kernel hangs on boot on my PC with Intel Core i7-5775C. Bug is already fixed upstream: https://gitlab.freedesktop.org/drm/intel/-/issues/2381 https://bugzilla.kernel.org/show_bug.cgi?id=208737 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.10-rc1=1664ffee760a5d98952318fdd9b198fae396d660 Please backport the fix. Thanks! [Impact] * Bug causes boot failure on common hardware. [Test Case] * Test kernel validated by submitter (see Comment #6). [Regression Potential] * Low: Simple cherry-pick from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Just installed a new system and the bug is still there, leading me straight back to this bug report for the 'fix'. I was really hoping that this bug would have been addressed in 20.04.1. Not sure why no one from the dev team is picking this up to rectify it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
I'm watching this error since about 10 months hoping that this would be fixed before the 20.04 release. Now we're almost 4 months past the release date and it's still there. Given that the fix is quite easy, I'm wondering why this is still an unresolved issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
