AWS: Hibernate resume crashes when platform changes

Bug #1965002 reported by Tim Gardner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-aws (Ubuntu)
Fix Released
Medium
Tim Gardner
Focal
Fix Released
Medium
Tim Gardner
Impish
Won't Fix
Medium
Tim Gardner
Jammy
Fix Released
Medium
Tim Gardner

Bug Description

SRU Justification

[Impact]

At present, if a virt instance is hibernated and restarted in a different environment, the instance will crash. We have seen situations where customers have to enable support cases to recover an instance. The proposed patch is supposed to enable the kernel to detect the change and reboot the instance instead of crashing. In the ACPI specification; there is a 'hardware signature' field in the ACPI tables, and the OS can reboot cleanly if/when that signature changes, instead of attempting the resume and crashing.

[Fix]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=74d95555
https://lore<email address hidden>/T/#u

[Test Case]

Hibernate an AWS instance, resume on a different platform. Positive test results from Amazon engineers.

[Where things could go wrong]

Resume currently crashes when a hibernated instance is migrated to a new machine. It can't get much worse, unless the initial hibernate fails.

[Other Info]

SF: #00330794

Tim Gardner (timg-tpi)
Changed in linux-aws (Ubuntu Focal):
assignee: nobody → Tim Gardner (timg-tpi)
importance: Undecided → Medium
status: New → In Progress
Changed in linux-aws (Ubuntu Impish):
assignee: nobody → Tim Gardner (timg-tpi)
importance: Undecided → Medium
status: New → In Progress
Changed in linux-aws (Ubuntu Jammy):
assignee: nobody → Tim Gardner (timg-tpi)
importance: Undecided → Medium
status: New → In Progress
Tim Gardner (timg-tpi)
description: updated
Revision history for this message
Tim Gardner (timg-tpi) wrote :
Changed in linux-aws (Ubuntu Jammy):
status: In Progress → Fix Committed
Tim Gardner (timg-tpi)
Changed in linux-aws (Ubuntu Focal):
status: In Progress → Fix Committed
Changed in linux-aws (Ubuntu Impish):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.4.0-1070.74 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-focal
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/5.13.0-1020.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-impish
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Amazon tested.

tags: added: verification-done-focal verification-done-impish
removed: verification-needed-focal verification-needed-impish
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-aws - 5.4.0-1071.76

---------------
linux-aws (5.4.0-1071.76) focal; urgency=medium

  * focal/linux-aws: 5.4.0-1071.76 -proposed tracker (LP: #1966242)

  * AWS: Hibernate resume crashes when platform changes (LP: #1965002)
    - PM: hibernate: Allow ACPI hardware signature to be honoured
    - PM: hibernate: Honour ACPI hardware signature by default for virtual guests

  [ Ubuntu: 5.4.0-107.121 ]

  * focal/linux: 5.4.0-107.121 -proposed tracker (LP: #1966275)
  * CVE-2022-27666
    - esp: Fix possible buffer overflow in ESP transformation
  * CVE-2022-1055
    - net: sched: fix use-after-free in tc_new_tfilter()
  * Pick fixup from v5.4.176 upstream stable release to address cert
    failure with clock jitter test in NUC7i3DNHE (LP: #1964204)
    - Bluetooth: refactor malicious adv data check

 -- Tim Gardner <email address hidden> Mon, 28 Mar 2022 08:40:36 -0600

Changed in linux-aws (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (68.2 KiB)

This bug was fixed in the package linux-aws - 5.15.0-1003.5

---------------
linux-aws (5.15.0-1003.5) jammy; urgency=medium

  * jammy/linux-aws: 5.15.0-1003.5 -proposed tracker (LP: #1965768)

  * AWS: Hibernate resume crashes when platform changes (LP: #1965002)
    - PM: hibernate: Allow ACPI hardware signature to be honoured
    - PM: hibernate: Honour ACPI hardware signature by default for virtual guests

  * dependency on crda obsolete according to Debian (LP: #1958918)
    - [Packaging] switch dependency from crda to wireless-regdb

  * tcm_loop requires '-extras' for EKS optimised AMIs (LP: #1959593)
    - [Packaging] aws: Include tcm_loop.ko

  * Miscellaneous Ubuntu changes
    - [Config] aws: Sync configs with master

  [ Ubuntu: 5.15.0-23.23 ]

  * jammy/linux: 5.15.0-23.23 -proposed tracker (LP: #1964573)
  * Packaging resync (LP: #1786013)
    - [Packaging] resync dkms-build{,--nvidia-N} from LRMv5
    - debian/dkms-versions -- update from kernel-versions (main/master)
  * [22.04 FEAT] KVM: Enable GISA support for Secure Execution guests
    (LP: #1959977)
    - KVM: s390: pv: make use of ultravisor AIV support
  * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16
    (LP: #1958004)
    - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs
  * CVE-2022-23960
    - ARM: report Spectre v2 status through sysfs
    - ARM: early traps initialisation
    - ARM: use LOADADDR() to get load address of sections
    - ARM: Spectre-BHB workaround
    - ARM: include unprivileged BPF status in Spectre V2 reporting
    - arm64: Add Neoverse-N2, Cortex-A710 CPU part definition
    - arm64: Add HWCAP for self-synchronising virtual counter
    - arm64: Add Cortex-X2 CPU part definition
    - arm64: add ID_AA64ISAR2_EL1 sys register
    - arm64: cpufeature: add HWCAP for FEAT_AFP
    - arm64: cpufeature: add HWCAP for FEAT_RPRES
    - arm64: entry.S: Add ventry overflow sanity checks
    - arm64: spectre: Rename spectre_v4_patch_fw_mitigation_conduit
    - KVM: arm64: Allow indirect vectors to be used without SPECTRE_V3A
    - arm64: entry: Make the trampoline cleanup optional
    - arm64: entry: Free up another register on kpti's tramp_exit path
    - arm64: entry: Move the trampoline data page before the text page
    - arm64: entry: Allow tramp_alias to access symbols after the 4K boundary
    - arm64: entry: Don't assume tramp_vectors is the start of the vectors
    - arm64: entry: Move trampoline macros out of ifdef'd section
    - arm64: entry: Make the kpti trampoline's kpti sequence optional
    - arm64: entry: Allow the trampoline text to occupy multiple pages
    - arm64: entry: Add non-kpti __bp_harden_el1_vectors for mitigations
    - arm64: entry: Add vectors that have the bhb mitigation sequences
    - arm64: entry: Add macro for reading symbol addresses from the trampoline
    - arm64: Add percpu vectors for EL1
    - arm64: proton-pack: Report Spectre-BHB vulnerabilities as part of Spectre-v2
    - arm64: Mitigate spectre style branch history side channels
    - KVM: arm64: Allow SMCCC_ARCH_WORKAROUND_3 to be discovered and migrated
    - arm64: Use the clearbhb instruction in mitigations
    - a...

Changed in linux-aws (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Fabio Augusto Miranda Martins (fabio.martins) wrote :

Is this going to be released to Impish (5.13)?

Revision history for this message
Brian Murray (brian-murray) wrote :

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release.

Changed in linux-aws (Ubuntu Impish):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.