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 protected] # 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 ...

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Oracular)
   Importance: High
     Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
       Status: New

** 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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2075575

Title:
  kexec fails in LPAR when some cpus are disabled

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Triaged
Status in linux source package in Noble:
  Triaged
Status in linux source package in Oracular:
  In Progress

Bug description:
  == Comment: #0 - SEETEENA THOUFEEK <[email protected]> - 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 protected] 
   
  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://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=21a741eb75f80397e5f7d3739e24d7d75e619011

  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 protected]: 
  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2075575/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to