| 2024-04-11 16:23:44 |
Philip Cox |
bug |
|
|
added bug |
| 2024-04-11 18:04:11 |
Philip Cox |
description |
SRU Justification:
[Impact]
The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation.
On hardware reduced platforms[0] this field may exist but it is not exposed currently.
[Fix]
Expose this field even on hardware reduced platforms.
https://lore.kernel.org/lkml/20240312134148.727454-1-dwmw2@infradead.org
[Test Plan]
AWS test.
[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes.
[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html |
SRU Justification:
[Impact]
The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation.
On hardware reduced platforms[0] this field may exist but it is not exposed currently.
[Fix]
Expose this field even on hardware reduced platforms.
https://lore.kernel.org/lkml/20240312134148.727454-1-dwmw2@infradead.org
[Test Plan]
AWS test.
[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes.
[Other info]
SF# 00383181
[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html |
|
| 2024-04-19 14:38:24 |
Philip Cox |
nominated for series |
|
Ubuntu Noble |
|
| 2024-04-19 14:38:24 |
Philip Cox |
bug task added |
|
linux-aws (Ubuntu Noble) |
|
| 2024-04-19 14:38:24 |
Philip Cox |
nominated for series |
|
Ubuntu Mantic |
|
| 2024-04-19 14:38:24 |
Philip Cox |
bug task added |
|
linux-aws (Ubuntu Mantic) |
|
| 2024-04-19 14:38:44 |
Philip Cox |
linux-aws (Ubuntu Mantic): assignee |
|
Philip Cox (philcox) |
|
| 2024-04-19 14:38:51 |
Philip Cox |
linux-aws (Ubuntu Mantic): status |
New |
In Progress |
|
| 2024-04-19 14:38:56 |
Philip Cox |
linux-aws (Ubuntu Noble): status |
New |
In Progress |
|
| 2024-05-07 19:27:22 |
Philip Cox |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-05-07 19:27:22 |
Philip Cox |
bug task added |
|
linux-aws (Ubuntu Jammy) |
|
| 2024-05-07 19:27:29 |
Philip Cox |
linux-aws (Ubuntu Jammy): status |
New |
In Progress |
|
| 2024-05-08 15:15:22 |
Philip Cox |
summary |
aws: Guest kernel support for clean boot on demand |
aws: Support hibernation on Graviton |
|
| 2024-05-08 15:21:38 |
Philip Cox |
description |
SRU Justification:
[Impact]
The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation.
On hardware reduced platforms[0] this field may exist but it is not exposed currently.
[Fix]
Expose this field even on hardware reduced platforms.
https://lore.kernel.org/lkml/20240312134148.727454-1-dwmw2@infradead.org
[Test Plan]
AWS test.
[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes.
[Other info]
SF# 00383181
[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html |
SRU Justification:
[Impact]
This change contains two parts, the first is adding support for
- KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call
And the second part is:
- Guest kernel support for clean boot on demand
For KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call:
PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 state.
This will allow hosting environments to determine that a guest is hibernated rather than just powered off, and ensure that they preserve the virtual environment appropriately to allow the guest to resume safely (or bump the hardware_signature in the FACS to trigger a clean reboot instead).
For Guest kernel support for clean boot on demand:
The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation.
On hardware reduced platforms[0] this field may exist but it is not exposed currently.
[Fix]
The changes for KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call come from:
https://lore.kernel.org/lkml/20240312135958.727765-1-dwmw2@infradead.org
The changes for Guest kernel support for clean boot on demand come from:
https://lore.kernel.org/lkml/20240312134148.727454-1-dwmw2@infradead.org
[Test Plan]
AWS test.
[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes.
[Other info]
SF# 00383181
[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html |
|
| 2024-05-08 15:21:41 |
Philip Cox |
linux-aws (Ubuntu Jammy): assignee |
|
Philip Cox (philcox) |
|
| 2024-05-08 16:29:50 |
Philip Cox |
description |
SRU Justification:
[Impact]
This change contains two parts, the first is adding support for
- KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call
And the second part is:
- Guest kernel support for clean boot on demand
For KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call:
PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 state.
This will allow hosting environments to determine that a guest is hibernated rather than just powered off, and ensure that they preserve the virtual environment appropriately to allow the guest to resume safely (or bump the hardware_signature in the FACS to trigger a clean reboot instead).
For Guest kernel support for clean boot on demand:
The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation.
On hardware reduced platforms[0] this field may exist but it is not exposed currently.
[Fix]
The changes for KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call come from:
https://lore.kernel.org/lkml/20240312135958.727765-1-dwmw2@infradead.org
The changes for Guest kernel support for clean boot on demand come from:
https://lore.kernel.org/lkml/20240312134148.727454-1-dwmw2@infradead.org
[Test Plan]
AWS test.
[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes.
[Other info]
SF# 00383181
[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html |
SRU Justification:
[Impact]
This change contains two parts, the first is adding support for
- KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call
And the second part is:
- Guest kernel support for clean boot on demand
For KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call:
PSCI v1.3 adds support for SYSTEM_OFF2 which is analogous to ACPI S4 state.
This will allow hosting environments to determine that a guest is hibernated rather than just powered off, and ensure that they preserve the virtual environment appropriately to allow the guest to resume safely (or bump the hardware_signature in the FACS to trigger a clean reboot instead).
For Guest kernel support for clean boot on demand:
The FACS field in the ACPI table is optional, but can be used communicate the hardware_signature field. If this field changes on resuming from a hibernation a clean reboot should happen rather than the resume from hibernation.
On hardware reduced platforms[0] this field may exist but it is not exposed currently.
[Fix]
The changes for KVM and guest support for the PSCI SYSTEM_OFF2 (hibernate) call come from:
https://lore.kernel.org/lkml/20240312135958.727765-1-dwmw2@infradead.org
The changes for Guest kernel support for clean boot on demand come from:
https://lore.kernel.org/lkml/20240312134148.727454-1-dwmw2@infradead.org
Latest patches have been picked from:
- noble/mantic: https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/psci-hibernate-6.8
- jammy: https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/psci-hibernate-5.15
[Test Plan]
AWS test.
[Where problems could occur]
If on hardware reduced platforms that incorrectly support/advertise the FACS field, hibernation may break if it returns a hardware signature that changes.
[Other info]
SF# 00383181
[0]: See Section 4.1 of the ACPI spec for info on hardware-reduced platforms.
https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/04_ACPI_Hardware_Specification/ACPI_Hardware_Specification.html |
|
| 2024-05-09 19:00:14 |
Philip Cox |
linux-aws (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2024-05-09 19:02:10 |
Philip Cox |
linux-aws (Ubuntu Mantic): status |
In Progress |
Fix Committed |
|
| 2024-05-09 19:02:13 |
Philip Cox |
linux-aws (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2024-05-10 00:13:08 |
Ali Saidi |
bug |
|
|
added subscriber Ali Saidi |
| 2024-05-16 19:11:58 |
Ubuntu Kernel Bot |
tags |
|
kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws |
|
| 2024-05-20 11:52:39 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-mantic-linux-aws-v2 verification-needed-mantic-linux-aws |
kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 verification-needed-jammy-linux-aws verification-needed-mantic-linux-aws |
|
| 2024-05-22 17:40:15 |
Seth Carolan |
tags |
kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 verification-needed-jammy-linux-aws verification-needed-mantic-linux-aws |
kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 verification-done-jammy-linux-aws verification-needed-mantic-linux-aws |
|
| 2024-05-25 02:22:50 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 verification-done-jammy-linux-aws verification-needed-mantic-linux-aws |
kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 kernel-spammed-noble-linux-aws-v2 verification-done-jammy-linux-aws verification-needed-mantic-linux-aws verification-needed-noble-linux-aws |
|
| 2024-06-04 22:12:33 |
Launchpad Janitor |
linux-aws (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
linux-aws (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2023-47233 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2023-52447 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2023-52530 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26583 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26584 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26585 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26622 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26733 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26735 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26736 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26748 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26782 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26792 |
|
| 2024-06-10 16:29:04 |
Launchpad Janitor |
cve linked |
|
2024-26809 |
|
| 2024-06-10 16:31:27 |
Launchpad Janitor |
linux-aws (Ubuntu Mantic): status |
Fix Committed |
Fix Released |
|
| 2024-06-10 16:31:27 |
Launchpad Janitor |
cve linked |
|
2024-26582 |
|
| 2024-06-10 16:40:27 |
Ubuntu Kernel Bot |
tags |
kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 kernel-spammed-noble-linux-aws-v2 verification-done-jammy-linux-aws verification-needed-mantic-linux-aws verification-needed-noble-linux-aws |
kernel-spammed-jammy-linux-aws-6.5-v2 kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 kernel-spammed-noble-linux-aws-v2 verification-done-jammy-linux-aws verification-needed-jammy-linux-aws-6.5 verification-needed-mantic-linux-aws verification-needed-noble-linux-aws |
|
| 2024-06-11 21:02:57 |
Seth Carolan |
tags |
kernel-spammed-jammy-linux-aws-6.5-v2 kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 kernel-spammed-noble-linux-aws-v2 verification-done-jammy-linux-aws verification-needed-jammy-linux-aws-6.5 verification-needed-mantic-linux-aws verification-needed-noble-linux-aws |
kernel-spammed-jammy-linux-aws-6.5-v2 kernel-spammed-jammy-linux-aws-v2 kernel-spammed-mantic-linux-aws-v2 kernel-spammed-noble-linux-aws-v2 verification-done-jammy-linux-aws verification-done-jammy-linux-aws-6.5 verification-needed-mantic-linux-aws verification-needed-noble-linux-aws |
|
