| 2019-06-05 18:05:22 |
Jeroen Bobbeldijk |
bug |
|
|
added bug |
| 2019-06-05 18:06:40 |
Jeroen Bobbeldijk |
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 |
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 (#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 |
|
| 2019-06-05 18:07:17 |
Jeroen Bobbeldijk |
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 (#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 |
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 |
|
| 2019-06-05 18:09:35 |
Jeroen Bobbeldijk |
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 |
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 (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 |
|
| 2019-06-05 18:09:43 |
Jeroen Bobbeldijk |
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 (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 |
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 ( 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 |
|
| 2019-06-05 18:09:49 |
Jeroen Bobbeldijk |
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 ( 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 |
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 |
|
| 2019-06-05 18:49:33 |
Tyler Hicks |
bug |
|
|
added subscriber Tyler Hicks |
| 2019-06-05 18:49:45 |
Tyler Hicks |
bug |
|
|
added subscriber Steve Beattie |
| 2019-06-05 18:50:05 |
Tyler Hicks |
grub2 (Ubuntu): status |
New |
Triaged |
|
| 2019-06-05 18:50:47 |
Tyler Hicks |
grub2 (Ubuntu): importance |
Undecided |
High |
|
| 2019-06-07 00:07:44 |
Tyler Hicks |
grub2 (Ubuntu): assignee |
|
Tyler Hicks (tyhicks) |
|
| 2019-06-25 19:54:33 |
Tom Reynolds |
bug |
|
|
added subscriber Tom Reynolds |
| 2020-01-20 09:59:17 |
Rafał Niewiński |
bug |
|
|
added subscriber Rafał Niewiński |
| 2020-06-11 01:32:10 |
Dimitri John Ledkov |
grub2 (Ubuntu): assignee |
Tyler Hicks (tyhicks) |
|
|
| 2020-06-11 01:32:17 |
Dimitri John Ledkov |
tags |
|
rls-gg-incoming |
|
| 2020-06-11 10:14:50 |
Kai Kasurinen |
bug |
|
|
added subscriber Kai Kasurinen |
| 2020-06-11 15:17:08 |
Brian Murray |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-06-11 15:17:08 |
Brian Murray |
bug task added |
|
grub2 (Ubuntu Groovy) |
|
| 2020-06-11 15:17:19 |
Brian Murray |
tags |
rls-gg-incoming |
|
|
| 2020-06-11 15:17:34 |
Brian Murray |
nominated for series |
|
Ubuntu Focal |
|
| 2020-06-11 15:17:34 |
Brian Murray |
bug task added |
|
grub2 (Ubuntu Focal) |
|
| 2020-06-12 08:34:21 |
Launchpad Janitor |
grub2 (Ubuntu Focal): status |
New |
Confirmed |
|
| 2020-06-12 12:32:37 |
Francis Ginther |
tags |
|
id-5ee24b2690d5d64dee0494d9 |
|
| 2020-06-19 10:57:51 |
Julian Andres Klode |
grub2 (Ubuntu Groovy): status |
Triaged |
In Progress |
|
| 2020-06-22 11:44:39 |
Julian Andres Klode |
grub2 (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2020-06-22 11:45:48 |
Julian Andres Klode |
grub2 (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2020-06-22 11:45:53 |
Julian Andres Klode |
grub2 (Ubuntu Groovy): status |
Fix Committed |
In Progress |
|
| 2020-06-22 11:48:13 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-06-22 11:48:13 |
Julian Andres Klode |
bug task added |
|
grub2 (Ubuntu Bionic) |
|
| 2020-06-22 11:48:13 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Xenial |
|
| 2020-06-22 11:48:13 |
Julian Andres Klode |
bug task added |
|
grub2 (Ubuntu Xenial) |
|
| 2020-07-30 14:14:47 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388381 |
|
| 2020-08-06 08:17:55 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~juliank/grub/+git/ubuntu/+merge/388791 |
|
| 2020-08-12 16:16:07 |
Launchpad Janitor |
grub2 (Ubuntu Groovy): status |
In Progress |
Fix Released |
|
| 2020-08-17 14:24:09 |
Julian Andres Klode |
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 |
[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
[Regression potential]
If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. |
|
| 2020-08-18 13:55:43 |
Łukasz Zemczak |
grub2 (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-08-18 13:55:45 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-08-18 13:55:47 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2020-08-18 13:55:51 |
Łukasz Zemczak |
tags |
id-5ee24b2690d5d64dee0494d9 |
id-5ee24b2690d5d64dee0494d9 verification-needed verification-needed-focal |
|
| 2020-08-24 08:56:45 |
Julian Andres Klode |
grub2 (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2020-08-24 08:56:48 |
Julian Andres Klode |
grub2 (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2020-08-24 09:02:06 |
Julian Andres Klode |
grub2 (Ubuntu Xenial): status |
Fix Committed |
In Progress |
|
| 2020-08-24 09:02:07 |
Julian Andres Klode |
grub2 (Ubuntu Bionic): status |
Fix Committed |
In Progress |
|
| 2020-08-24 17:31:27 |
Łukasz Zemczak |
grub2 (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-08-24 17:31:34 |
Łukasz Zemczak |
tags |
id-5ee24b2690d5d64dee0494d9 verification-needed verification-needed-focal |
id-5ee24b2690d5d64dee0494d9 verification-needed verification-needed-bionic verification-needed-focal |
|
| 2020-08-25 07:59:08 |
Łukasz Zemczak |
grub2 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2020-08-25 07:59:13 |
Łukasz Zemczak |
tags |
id-5ee24b2690d5d64dee0494d9 verification-needed verification-needed-bionic verification-needed-focal |
id-5ee24b2690d5d64dee0494d9 verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial |
|
| 2020-08-25 09:40:18 |
Julian Andres Klode |
bug task added |
|
grubzfs-testsuite (Ubuntu) |
|
| 2020-08-25 09:40:34 |
Julian Andres Klode |
grubzfs-testsuite (Ubuntu Groovy): status |
New |
Fix Released |
|
| 2020-08-25 09:40:41 |
Julian Andres Klode |
bug task deleted |
grubzfs-testsuite (Ubuntu Xenial) |
|
|
| 2020-08-25 09:40:47 |
Julian Andres Klode |
bug task deleted |
grubzfs-testsuite (Ubuntu Bionic) |
|
|
| 2020-08-25 09:43:06 |
Julian Andres Klode |
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
[Regression potential]
If you actually require microcode updates to get into userspace, your recovery option won't work anymore. Does this happen? Seems unlikely. |
[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. |
|
| 2020-08-25 09:43:10 |
Julian Andres Klode |
grubzfs-testsuite (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-08-27 09:59:50 |
Julian Andres Klode |
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. |
[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. |
|
| 2020-08-27 10:08:06 |
Julian Andres Klode |
tags |
id-5ee24b2690d5d64dee0494d9 verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial |
id-5ee24b2690d5d64dee0494d9 verification-done-focal verification-needed verification-needed-bionic verification-needed-xenial |
|
| 2020-08-27 10:27:41 |
Julian Andres Klode |
tags |
id-5ee24b2690d5d64dee0494d9 verification-done-focal verification-needed verification-needed-bionic verification-needed-xenial |
id-5ee24b2690d5d64dee0494d9 verification-done-bionic verification-done-focal verification-needed verification-needed-xenial |
|
| 2020-08-27 10:58:02 |
Julian Andres Klode |
tags |
id-5ee24b2690d5d64dee0494d9 verification-done-bionic verification-done-focal verification-needed verification-needed-xenial |
id-5ee24b2690d5d64dee0494d9 verification-done-bionic verification-done-focal verification-done-xenial verification-needed |
|
| 2020-08-27 12:56:53 |
Łukasz Zemczak |
grubzfs-testsuite (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-08-27 12:56:59 |
Łukasz Zemczak |
tags |
id-5ee24b2690d5d64dee0494d9 verification-done-bionic verification-done-focal verification-done-xenial verification-needed |
id-5ee24b2690d5d64dee0494d9 verification-done-bionic verification-done-xenial verification-needed verification-needed-focal |
|
| 2020-08-28 09:04:33 |
Julian Andres Klode |
tags |
id-5ee24b2690d5d64dee0494d9 verification-done-bionic verification-done-xenial verification-needed verification-needed-focal |
id-5ee24b2690d5d64dee0494d9 verification-done verification-done-bionic verification-done-focal verification-done-xenial |
|
| 2020-08-31 12:55:06 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-08-31 13:05:13 |
Launchpad Janitor |
grub2 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-08-31 13:18:44 |
Launchpad Janitor |
grub2 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-08-31 13:41:50 |
Launchpad Janitor |
grub2 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2020-09-10 04:09:39 |
Launchpad Janitor |
grubzfs-testsuite (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-10-14 15:48:18 |
Matthieu Clemenceau |
tags |
id-5ee24b2690d5d64dee0494d9 verification-done verification-done-bionic verification-done-focal verification-done-xenial |
fr-166 id-5ee24b2690d5d64dee0494d9 verification-done verification-done-bionic verification-done-focal verification-done-xenial |
|
| 2021-10-08 10:44:12 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/409918 |
|
