[Group.of.nepali.translators] [Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode
This bug was fixed in the package grubzfs-testsuite - 0.4.10.1 --- grubzfs-testsuite (0.4.10.1) focal; urgency=medium * Update for grub dis_ucode_ldr change (LP: #1831789) -- Julian Andres Klode Wed, 12 Aug 2020 10:40:40 +0200 ** Changed in: grubzfs-testsuite (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831789 Title: Add "dis_ucode_ldr" to linux boot options for Recovery Mode Status in grub2 package in Ubuntu: Fix Released Status in grubzfs-testsuite package in Ubuntu: Fix Released Status in grub2 source package in Xenial: Fix Released Status in grub2 source package in Bionic: Fix Released Status in grub2 source package in Focal: Fix Released Status in grubzfs-testsuite source package in Focal: Fix Released Status in grub2 source package in Groovy: Fix Released Status in grubzfs-testsuite source package in Groovy: Fix Released Bug description: [Impact] Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html [Test case] Check that dis_ucode_ldr is present on Linux entries (zsys support in focal+ is verified by grubzfs-testsuite changes) [Regression potential] If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. For grubzfs-testsuite, given that it is not installed, the only regression could be failing tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode
This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.28 --- grub2 (2.02~beta2-36ubuntu3.28) xenial; urgency=medium * debian/patches/ubuntu-flavour-order.patch: - Add a (hidden) GRUB_FLAVOUR_ORDER setting that can mark certain kernel flavours as preferred, and specify an order between those preferred flavours (LP: #1882663) * debian/patches/ubuntu-recovery-dis_ucode_ldr.patch: - Pass dis_ucode_ldr to kernel for recovery mode (LP: #1831789) -- Julian Andres Klode Mon, 24 Aug 2020 10:54:59 +0200 ** Changed in: grub2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831789 Title: Add "dis_ucode_ldr" to linux boot options for Recovery Mode Status in grub2 package in Ubuntu: Fix Released Status in grubzfs-testsuite package in Ubuntu: Fix Released Status in grub2 source package in Xenial: Fix Released Status in grub2 source package in Bionic: Fix Released Status in grub2 source package in Focal: Fix Released Status in grubzfs-testsuite source package in Focal: Fix Committed Status in grub2 source package in Groovy: Fix Released Status in grubzfs-testsuite source package in Groovy: Fix Released Bug description: [Impact] Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html [Test case] Check that dis_ucode_ldr is present on Linux entries (zsys support in focal+ is verified by grubzfs-testsuite changes) [Regression potential] If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. For grubzfs-testsuite, given that it is not installed, the only regression could be failing tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode
This bug was fixed in the package grub2 - 2.02-2ubuntu8.18 --- grub2 (2.02-2ubuntu8.18) bionic; urgency=medium * debian/patches/ubuntu-flavour-order.patch: - Add a (hidden) GRUB_FLAVOUR_ORDER setting that can mark certain kernel flavours as preferred, and specify an order between those preferred flavours (LP: #1882663) * debian/patches/ubuntu-recovery-dis_ucode_ldr.patch: - Pass dis_ucode_ldr to kernel for recovery mode (LP: #1831789) -- Julian Andres Klode Mon, 24 Aug 2020 10:45:45 +0200 ** Changed in: grub2 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831789 Title: Add "dis_ucode_ldr" to linux boot options for Recovery Mode Status in grub2 package in Ubuntu: Fix Released Status in grubzfs-testsuite package in Ubuntu: Fix Released Status in grub2 source package in Xenial: Fix Committed Status in grub2 source package in Bionic: Fix Released Status in grub2 source package in Focal: Fix Released Status in grubzfs-testsuite source package in Focal: Fix Committed Status in grub2 source package in Groovy: Fix Released Status in grubzfs-testsuite source package in Groovy: Fix Released Bug description: [Impact] Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html [Test case] Check that dis_ucode_ldr is present on Linux entries (zsys support in focal+ is verified by grubzfs-testsuite changes) [Regression potential] If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. For grubzfs-testsuite, given that it is not installed, the only regression could be failing tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode
This bug was fixed in the package grub2 - 2.04-1ubuntu26.3 --- grub2 (2.04-1ubuntu26.3) focal; urgency=medium * 2.04-1ubuntu27 and 2.04-1ubuntu28 folded together for focal * debian/patches/ubuntu-flavour-order.patch: - Add a (hidden) GRUB_FLAVOUR_ORDER setting that can mark certain kernel flavours as preferred, and specify an order between those preferred flavours (LP: #1882663) * debian/patches/ubuntu-zfs-enhance-support.patch: - Use version_find_latest for ordering kernels, so it also supports the GRUB_FLAVOUR_ORDER setting. * debian/patches/ubuntu-dont-verify-loopback-images.patch: - disk/loopback: Don't verify loopback images (LP: #1878541), Thanks to Chris Coulson for the patch * debian/patches/ubuntu-recovery-dis_ucode_ldr.patch - Pass dis_ucode_ldr to kernel for recovery mode (LP: #1831789) * debian/patches/ubuntu-add-initrd-less-boot-fallback.patch: - Merge changes from xnox to fix multiple initrds support (LP: #1878705) * debian/patches/ubuntu-clear-invalid-initrd-spacing.patch: - Remove, no longer needed thanks to xnox's patch * Ensure that grub-multi-install can always find templates (LP: #1879948) -- Julian Andres Klode Mon, 17 Aug 2020 16:04:31 +0200 ** Changed in: grub2 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831789 Title: Add "dis_ucode_ldr" to linux boot options for Recovery Mode Status in grub2 package in Ubuntu: Fix Released Status in grubzfs-testsuite package in Ubuntu: Fix Released Status in grub2 source package in Xenial: Fix Committed Status in grub2 source package in Bionic: Fix Committed Status in grub2 source package in Focal: Fix Released Status in grubzfs-testsuite source package in Focal: Fix Committed Status in grub2 source package in Groovy: Fix Released Status in grubzfs-testsuite source package in Groovy: Fix Released Bug description: [Impact] Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html [Test case] Check that dis_ucode_ldr is present on Linux entries (zsys support in focal+ is verified by grubzfs-testsuite changes) [Regression potential] If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. For grubzfs-testsuite, given that it is not installed, the only regression could be failing tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode
** Also affects: grubzfs-testsuite (Ubuntu) Importance: Undecided Status: New ** Changed in: grubzfs-testsuite (Ubuntu Groovy) Status: New => Fix Released ** No longer affects: grubzfs-testsuite (Ubuntu Xenial) ** No longer affects: grubzfs-testsuite (Ubuntu Bionic) ** Description changed: [Impact] Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html [Test case] - Check that dis_ucode_ldr is present on Linux entries + Check that dis_ucode_ldr is present on Linux entries (zsys support in focal+ is verified by grubzfs-testsuite changes) [Regression potential] If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. ** Changed in: grubzfs-testsuite (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831789 Title: Add "dis_ucode_ldr" to linux boot options for Recovery Mode Status in grub2 package in Ubuntu: Fix Released Status in grubzfs-testsuite package in Ubuntu: Fix Released Status in grub2 source package in Xenial: Fix Committed Status in grub2 source package in Bionic: Fix Committed Status in grub2 source package in Focal: Fix Committed Status in grubzfs-testsuite source package in Focal: In Progress Status in grub2 source package in Groovy: Fix Released Status in grubzfs-testsuite source package in Groovy: Fix Released Bug description: [Impact] Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html [Test case] Check that dis_ucode_ldr is present on Linux entries (zsys support in focal+ is verified by grubzfs-testsuite changes) [Regression potential] If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1831789] Re: Add "dis_ucode_ldr" to linux boot options for Recovery Mode
This bug was fixed in the package grub2 - 2.04-1ubuntu28 --- grub2 (2.04-1ubuntu28) groovy; urgency=medium * Ensure that grub-multi-install can always find templates (LP: #1879948) * Fix changelog entries for security update -- Julian Andres Klode Mon, 10 Aug 2020 15:07:29 +0200 ** Changed in: grub2 (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1831789 Title: Add "dis_ucode_ldr" to linux boot options for Recovery Mode Status in grub2 package in Ubuntu: Fix Released Status in grub2 source package in Xenial: New Status in grub2 source package in Bionic: New Status in grub2 source package in Focal: In Progress Status in grub2 source package in Groovy: Fix Released Bug description: Due to some recent problems with a microcode update which broke booting of some laptops I suggest adding "dis_ucode_ldr" to recovery mode boot options to allow booting after a bad microcode update. See the following topics that describe the problems: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620 - https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 When such problems occur it's very hard to see that the microcode loading is the issue, the booting just hangs at the purple screen, even removing "quiet splash" or using the recovery option will not show the error. We'll need to double check that dis_ucode_ldr works as expected across all architectures. According to the kernel docs (Documentation/admin-guide/kernel-parameters.txt), dis_ucode_ldr is x86 only, so my guess is that it will be ignored for other architectures. According to the kernel code (arch/x86/kernel/cpu/microcode/core.c), dis_ucode_ldr works for both AMD and Intel. I have some time tomorrow on test this on a ARM device. This was also discussed Ubuntu Developer mailing list where it was suggested to post this here, see: https://lists.ubuntu.com/archives /ubuntu-devel/2019-June/040725.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1831789/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
