linux-meta-aws patch is submitted at https://lists.ubuntu.com/archives
/kernel-team/2020-November/114920.html
** Also affects: linux-meta-aws (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ Now that micorocode-initrd is in focal, linux-meta-aws should start
+ depending on it in focal too.
+
+ --
+
[Impact]
- * New package to provide micorocode-only initrd for application of
+ * New package to provide micorocode-only initrd for application of
microcode on boot, when otherwise no initrd is in use.
[Test Case]
- * install microcode-initrd in AWS cloud x86 metal instance
- * reboot, observe that microcode has been applied, and yet the boot was
without initrd (observe journalctl -b -k to see that initrd was not used for
boot)
+ * install microcode-initrd in AWS cloud x86 metal instance
+ * reboot, observe that microcode has been applied, and yet the boot was
without initrd (observe journalctl -b -k to see that initrd was not used for
boot)
[Regression Potential]
- * This is a brand new package, that will be used by AWS images.
+ * This is a brand new package, that will be used by AWS images.
Otherwise this package will not be automatically installed anywhere. Re
spinning & promoting AWS images are tested and gated by the CPC team.
[Other Info]
-
- * Original bug report for groovy:
+
+ * Original bug report for groovy:
Normally Ubuntu boots using initrd that has three archives: early amd64
microcode, early intel microcode, and compressed main initrd.
When booting without initrd, simply kernel is loaded without any initrd
and thus without microcode.
However, grub supports booting with multiple initrds and one can specify
a standalone early initrd which contains microcode only, and separate
main initrd.
As an added bonus one can also specify just eary microcode initrd
without a main one, to allow kernel to load microcode early, but
otherwise boot without an initrd.
To achieve that I need to introduce a microcode-initrd package will will
only provide early initrd which only has microcode.
The intention is to seed microcode-initrd to targets that boot on
baremental without initrd.
** Changed in: linux-meta-aws (Ubuntu)
Status: New => Fix Released
** Changed in: linux-meta-aws (Ubuntu Focal)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1890612
Title:
[Source NEW SRU FOCAL] ITP: Please support loading microcode early,
whilst otherwise booting without initrd
Status in cloud-images:
Fix Committed
Status in linux-meta-aws package in Ubuntu:
Fix Released
Status in microcode-initrd package in Ubuntu:
Fix Released
Status in linux-meta-aws source package in Focal:
Triaged
Status in microcode-initrd source package in Focal:
Fix Released
Bug description:
Now that micorocode-initrd is in focal, linux-meta-aws should start
depending on it in focal too.
--
[Impact]
* New package to provide micorocode-only initrd for application of
microcode on boot, when otherwise no initrd is in use.
[Test Case]
* install microcode-initrd in AWS cloud x86 metal instance
* reboot, observe that microcode has been applied, and yet the boot was
without initrd (observe journalctl -b -k to see that initrd was not used for
boot)
[Regression Potential]
* This is a brand new package, that will be used by AWS images.
Otherwise this package will not be automatically installed anywhere.
Re spinning & promoting AWS images are tested and gated by the CPC
team.
[Other Info]
* Original bug report for groovy:
Normally Ubuntu boots using initrd that has three archives: early
amd64 microcode, early intel microcode, and compressed main initrd.
When booting without initrd, simply kernel is loaded without any
initrd and thus without microcode.
However, grub supports booting with multiple initrds and one can
specify a standalone early initrd which contains microcode only, and
separate main initrd.
As an added bonus one can also specify just eary microcode initrd
without a main one, to allow kernel to load microcode early, but
otherwise boot without an initrd.
To achieve that I need to introduce a microcode-initrd package will
will only provide early initrd which only has microcode.
The intention is to seed microcode-initrd to targets that boot on
baremental without initrd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1890612/+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
