kexec fails in LPAR when some cpus are disabled
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| The Ubuntu-power-systems project |
Triaged
|
High
|
Ubuntu on IBM Power Systems Bug Triage | |||
| linux (Ubuntu) | Status tracked in Oracular | |||||
| Jammy |
Triaged
|
Undecided
|
Unassigned | |||
| Noble |
Triaged
|
Undecided
|
Unassigned | |||
| Oracular |
Fix Committed
|
High
|
Ubuntu on IBM Power Systems Bug Triage | |||
Bug Description
== Comment: #0 - SEETEENA THOUFEEK <email address hidden> - 2024-08-02 03:11:31 ==
+++ This bug was initially created as a clone of Bug #206083 +++
---Problem Description---
kexec fails in LPAR when some cpus are disabled
Contact Information = <email address hidden>
Machine Type = na
---uname output---
na
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Summary:
At L1 level, kexec fails if some of the cpus in the machine are disabled.
Distros and kernel versions used:
1. Distro versions used
a. L1 LPAR :
b. L2 :
Repro steps:
1. Boot into an L1 lpar
2. Disable some cpus (eg: ppc64_cpu --cores-on=3)
3. Try to kexec.
This bug is reproducible only when we load the target kernel/initrd and use "kexec -e" as follows:
kexec -l --initrd initramfs-$(uname -r).img vmlinuz-$(uname -r) --append="$(cat /proc/cmdline)"
kexec -e
kexec works fine if we do a normal kexec without skipping the shutdown path
kexec --initrd initramfs-$(uname -r).img vmlinuz-$(uname -r) --append="$(cat /proc/cmdline)"
Fix is upstream now:
https:/
Thanks,
Sourabh Jain
please include in Ubuntu
Oops output:
no
Stack trace output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for <email address hidden>:
-Attach sysctl -a output output to the bug.
| tags: | added: architecture-ppc64le bugnameltc-208048 severity-high targetmilestone-inin--- |
| Changed in ubuntu: | |
| assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
| affects: | ubuntu → kernel-package (Ubuntu) |
| affects: | kernel-package (Ubuntu) → linux (Ubuntu) |
| Changed in ubuntu-power-systems: | |
| assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → High |
| Changed in ubuntu-power-systems: | |
| importance: | Undecided → High |
| Frank Heimes (fheimes) wrote | #1 |
| Changed in ubuntu-power-systems: | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Oracular): | |
| status: | New → In Progress |
| Changed in linux (Ubuntu Jammy): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Noble): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Oracular): | |
| status: | In Progress → Fix Committed |
Hello Seeteena, thanks for having this reported.
The referenced commit is upstream accepted in kernel v6.10(-rc7) and v6.11(-rc1), hence it will be included in the planned target kernel for 'oracular' / 24.10.
And I am glad to see that the commit was upstream also tagged as stable update, for kernel v5.9 and newer
(Fixes: 7fa95f9adaee ("powerpc/64s: system call support for scv/rfscv instructions")
Cc: <email address hidden> # v5.9+)
that means it will be automatically picked by the Canonical kernel teams' "<Ubuntu codename> update: v<version> upstream stable release" process and with that will find it's way into noble/24.04 kernel 6.8 and jammy/22.04 kernel 5.15.
We'll use this LP bug for tracking ...