[Bug 2081281] Re: gnome terminal and other apps freezes for about 30 seconds
** Description changed: - After I did a release upgrade from 22.04 LTS to 24.04.1 LTS some GUI operations lead to a freezing app. I first observed it in gnome-terminal when clicking the plus sign to open another tab. Another example is gnome-control-center. If klick to open the control center help page, the control center freezes. And here is another example. In firefox if I want to fill out a html form, opening a drop down item lets freeze firefox for a while. + After I did a release upgrade from 22.04 LTS to 24.04.1 LTS some GUI operations lead to a freezing app. I first observed it in gnome-terminal when clicking the plus sign to open another tab. Another example is gnome-control-center. If klick to open the control center help page, the control center freezes. And here is another example. In firefox if I want to fill out a html form, opening a drop down item lets freeze firefox for a while. All examples highlight a infobox asking, if I want to wait for the app to respond or kill it. I tried it using X11 or Wayland. Both show the same beavior. I also switched to another desktop manger (from gdm to sddm) but the behavior is the same. I created a new user but also the behavior is the same. I downloaded a live image of Ubuntu Studio and started it from a usb stick, so all was fine. I guess the problem is in the deep of the system, maybe the kernel, but I do not have the knowledge to investigate it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081281 Title: gnome terminal and other apps freezes for about 30 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2081281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081281] [NEW] gnome terminal and other apps freezes for about 30 seconds
Public bug reported: After I did a release upgrade from 22.04 LTS to 24.04.1 LTS some GUI operations lead to a freezing app. I first observed it in gnome-terminal when clicking the plus sign to open another tab. Another example is gnome-control-center. If klick to open the control center help page, the control center freezes. And here is another example. In firefox if I want to fill out a html form, opening a drop down item lets freeze firefox for a while. All examples highlight a infobox asking, if I want to wait for the app to respond or kill it. I tried it using X11 or Wayland. Both show the same beavior. I also switched to another desktop manger (from gdm to sddm) but the behavior is the same. I created a new user but also the behavior is the same. I downloaded a live image of Ubuntu Studio and started it from a usb stick, so all was fine. I guess the problem is in the deep of the system, maybe the kernel, but I do not have the knowledge to investigate it. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "LSHW" https://bugs.launchpad.net/bugs/2081281/+attachment/5819709/+files/lshw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081281 Title: gnome terminal and other apps freezes for about 30 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2081281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080973] Re: [FFe] Update lpmd to version 0.0.6
** Changed in: intel-lpmd (Ubuntu) Assignee: Ubuntu Release Team (ubuntu-release) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080973 Title: [FFe] Update lpmd to version 0.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-lpmd/+bug/2080973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080973] Re: [FFe] Update lpmd to version 0.0.6
** Changed in: intel-lpmd (Ubuntu) Assignee: (unassigned) => Ubuntu Release Team (ubuntu-release) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080973 Title: [FFe] Update lpmd to version 0.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-lpmd/+bug/2080973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067383] Re: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff!
*** This bug is a duplicate of bug 2076587 *** https://bugs.launchpad.net/bugs/2076587 ** This bug has been marked a duplicate of bug 2076587 cpu hotplug crashes the guest! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067383 Title: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2067383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075575] Re: kexec fails in LPAR when some cpus are disabled
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075575 Title: kexec fails in LPAR when some cpus are disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2075575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067355] Re: [24.10 FEAT] Update s390-tools to (currently latest) v2.33.1 in oracular
** Summary changed: - [FEAT 24.10] Update s390-tools to (currently latest) v2.33.1 in oracular + [24.10 FEAT] Update s390-tools to (currently latest) v2.33.1 in oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067355 Title: [24.10 FEAT] Update s390-tools to (currently latest) v2.33.1 in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062118] Re: autopkgtests fail on s390x (segfault)
** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: libtracefs (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062118 Title: autopkgtests fail on s390x (segfault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2062118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062119] Re: libtracefs autopkgtests fail on ppc64el
** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: libtracefs (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062119 Title: libtracefs autopkgtests fail on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062119] Re: libtracefs autopkgtests fail on ppc64el
** Summary changed: - autopkgtests fail on ppc64el + libtracefs autopkgtests fail on ppc64el -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062119 Title: libtracefs autopkgtests fail on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062119] Re: autopkgtests fail on ppc64el
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => bugproxy (bugproxy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062119 Title: autopkgtests fail on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2062119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071471] Re: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071471 Title: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2071471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072661] Re: [24.10 FEAT] [KRN1905] Kernel image in vmalloc space (V!=R)
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072661 Title: [24.10 FEAT] [KRN1905] Kernel image in vmalloc space (V!=R) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2072661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072760] Re: [24.10 FEAT] [KRN1911] Vertical CPU Polarization Support Stage 2
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072760 Title: [24.10 FEAT] [KRN1911] Vertical CPU Polarization Support Stage 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2072760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074376] Re: Disable PCI_DYNAMIC_OF_NODES in Ubuntu
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074376 Title: Disable PCI_DYNAMIC_OF_NODES in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2074376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064530] Re: Include support for .NET 8 for Ubuntu on Power
Fantastic - thank you ! (Closing this ticket now as Fix Released) ** Changed in: ubuntu-power-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064530 Title: Include support for .NET 8 for Ubuntu on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060039] Re: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang
** Changed in: ubuntu-power-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060039 Title: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076587] Re: cpu hotplug crashes the guest!
** Description changed:
SRU Justification:
[ Impact ]
- * While running a (nested) KVM guest on Power 10 (with PowerVM)
-and performing a CPU hotplug, trying to set to 68 vCPUs,
-the KVM guest crashes.
+ * While running a (nested) KVM guest on Power 10 (with PowerVM)
+ and performing a CPU hotplug, trying to set to 68 vCPUs,
+ the KVM guest crashes.
- * In the failure case the KVM guest has maxvcpus 128,
-and it starts fine with an initial value of 4 vCPUs,
-but fails after a larger increase (here to 68 vCPUs).
+ * In the failure case the KVM guest has maxvcpus 128,
+ and it starts fine with an initial value of 4 vCPUs,
+ but fails after a larger increase (here to 68 vCPUs).
- * The error reported is:
-[ 662.102542] KVM: Create Guest vcpu hcall failed, rc=-44
-error: Unable to read from monitor: Connection reset by peer
+ * The error reported is:
+ [ 662.102542] KVM: Create Guest vcpu hcall failed, rc=-44
+ error: Unable to read from monitor: Connection reset by peer
- * This especially seems to happen in memory constraint systems.
+ * This especially seems to happen in memory constraint systems.
- * This can be avoided by pre-creating and parking vCPUs on success
-or return error otherwise, which then leads to a graceful error
-in case of a vCPU hotplug failure, while the guest keeps running.
+ * This can be avoided by pre-creating and parking vCPUs on success
+ or return error otherwise, which then leads to a graceful error
+ in case of a vCPU hotplug failure, while the guest keeps running.
[ Fix ]
- * 08c3286822 ("accel/kvm: Extract common KVM vCPU {creation,parking}
+ * 08c3286822 ("accel/kvm: Extract common KVM vCPU {creation,parking}
code") [pre-req]
- * c6a3d7bc9e ("accel/kvm: Introduce kvm_create_and_park_vcpu() helper")
+ * c6a3d7bc9e ("accel/kvm: Introduce kvm_create_and_park_vcpu() helper")
- * 18530e7c57 ("cpu-common.c: export cpu_get_free_index to be reused
+ * 18530e7c57 ("cpu-common.c: export cpu_get_free_index to be reused
later")
- * cfb52d07f5 ("target/ppc: handle vcpu hotplug failure gracefully")
+ * cfb52d07f5 ("target/ppc: handle vcpu hotplug failure gracefully")
[ Test Plan ]
- * Setup an IBM Power10 system (with firmware FW1060 or newer,
-that comes with nested KVM support), running Ubuntu Server 24.04.
+ * Setup an IBM Power10 system (with firmware FW1060 or newer,
+ that comes with nested KVM support), running Ubuntu Server 24.04.
- * Install and configure KVM on this system with a (higher)
-maxvcpus value of 128, but have a (smaller) initial value of 4 vCPUs.
-$ virsh define ubu2404.xml
+ * Install and configure KVM on this system with a (higher)
+ maxvcpus value of 128, but have a (smaller) initial value of 4 vCPUs.
+ $ virsh define ubu2404.xml
+(https://launchpadlibrarian.net/748483993/check.xml)
- * Now after successful definition, start the VM:
-$ virsh start ubu2404 --console
+ * Now after successful definition, start the VM:
+ $ virsh start ubu2404 --console
- * If the VM is up and running increase the vCPUs to a larger value
-here 68:
-$ virsh setvcpus ubu2404 68
+ * If the VM is up and running increase the vCPUs to a larger value
+ here 68:
+ $ virsh setvcpus ubu2404 68
- * A system with an unpatched qemu will crash, showing:
-[ 662.102542] KVM: Create Guest vcpu hcall failed, rc=-44
-error: Unable to read from monitor: Connection reset by peer
+ * A system with an unpatched qemu will crash, showing:
+ [ 662.102542] KVM: Create Guest vcpu hcall failed, rc=-44
+ error: Unable to read from monitor: Connection reset by peer
- * A patches environment will:
-- either just successfully hotplug the new amount (68) of vCPUs
- without further messages
-- or (in case very memory constraint) print a (graceful) error
- message that hotplug couldn't be performed,
- but stays up and running:
- error: internal error: unable to execute QEMU command 'device_add': \
- kvmppc_cpu_realize: vcpu hotplug failed with -12
+ * A patches environment will:
+ - either just successfully hotplug the new amount (68) of vCPUs
+ without further messages
+ - or (in case very memory constraint) print a (graceful) error
+ message that hotplug couldn't be performed,
+ but stays up and running:
+ error: internal error: unable to execute QEMU command 'device_add': \
+ kvmppc_cpu_realize: vcpu hotplug failed with -12
- * Since certain firmware is required, IBM is doing the test and validation
-(and already successfully verified based on the PPA test builds).
+ * Since certain firmware is required, IBM is doing the test and validation
+ (and already successfully verified based on the PPA test builds).
[ Where problems could occur ]
- * All modification were done in target/ppc/kvm.c
-and are with that limited to the
[Bug 2080474] Re: ubuntu installation failing for systems having SAN disk
** Also affects: subiquity Importance: Undecided Status: New ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: ubuntu-power-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080474 Title: ubuntu installation failing for systems having SAN disk To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2080474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044104] Re: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set
** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044104 Title: [UBUNTU 20.04] chzdev -e is rebuilding initramfs even with zdev:early=0 set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2044104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075721] Re: [Ubuntu24.04] virsh detach-interface is crashing the guest
*** This bug is a duplicate of bug 2074376 *** https://bugs.launchpad.net/bugs/2074376 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075721 Title: [Ubuntu24.04] virsh detach-interface is crashing the guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2075721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076587] Re: cpu hotplug crashes the guest!
And Anushree, would you also agree that bug LP: 2067383 / Bugzilla: 206641 -
https://bugs.launchpad.net/bugs/2067383)
can be considered as a duplicate bug of this one (LP: 2076587 / Bugzilla:
208538) ?
They seem to be suspiciously similar ...
** Description changed:
+ SRU Justification:
+
+ [ Impact ]
+
+ * While running a (nested) KVM guest on Power 10 (with PowerVM)
+and performing a CPU hotplug, trying to set to 68 vCPUs,
+the KVM guest crashes.
+
+ * In the failure case the KVM guest has maxvcpus 128,
+and it starts fine with an initial value of 4 vCPUs,
+but fails after a larger increase (here to 68 vCPUs).
+
+ * The error reported is:
+[ 662.102542] KVM: Create Guest vcpu hcall failed, rc=-44
+error: Unable to read from monitor: Connection reset by peer
+
+ * This especially seems to happen in memory constraint systems.
+
+ * This can be avoided by pre-creating and parking vCPUs on success
+or return error otherwise, which then leads to a graceful error
+in case of a vCPU hotplug failure, while the guest keeps running.
+
+ [ Fix ]
+
+ * 08c3286822 ("accel/kvm: Extract common KVM vCPU {creation,parking}
+ code") [pre-req]
+
+ * c6a3d7bc9e ("accel/kvm: Introduce kvm_create_and_park_vcpu() helper")
+
+ * 18530e7c57 ("cpu-common.c: export cpu_get_free_index to be reused
+ later")
+
+ * cfb52d07f5 ("target/ppc: handle vcpu hotplug failure gracefully")
+
+ [ Test Plan ]
+
+ * Setup an IBM Power10 system (with firmware FW1060 or newer,
+that comes with nested KVM support), running Ubuntu Server 24.04.
+
+ * Install and configure KVM on this system with a (higher)
+maxvcpus value of 128, but have a (smaller) initial value of 4 vCPUs.
+$ virsh define ubu2404.xml
+
+ * Now after successful definition, start the VM:
+$ virsh start ubu2404 --console
+
+ * If the VM is up and running increase the vCPUs to a larger value
+here 68:
+$ virsh setvcpus ubu2404 68
+
+ * A system with an unpatched qemu will crash, showing:
+[ 662.102542] KVM: Create Guest vcpu hcall failed, rc=-44
+error: Unable to read from monitor: Connection reset by peer
+
+ * A patches environment will:
+- either just successfully hotplug the new amount (68) of vCPUs
+ without further messages
+- or (in case very memory constraint) print a (graceful) error
+ message that hotplug couldn't be performed,
+ but stays up and running:
+ error: internal error: unable to execute QEMU command 'device_add': \
+ kvmppc_cpu_realize: vcpu hotplug failed with -12
+
+ * Since certain firmware is required, IBM is doing the test and validation
+(and already successfully verified based on the PPA test builds).
+
+ [ Where problems could occur ]
+
+ * All modification were done in target/ppc/kvm.c
+and are with that limited to the IBM Power platform,
+and will not affect other architectures.
+
+ * The implementation of the pre-creation of vCPUs (init cpu_target_realize)
+may lead to early failures when a user doesn't expect to have such an
+amount of vCPUs yet.
+
+ * And the pre-creation and especially parking (kvm_create_and_park_vcpu)
+will probably consume more resources than before.
+
+ * Hence a patched system might run with a reduced max amount of vCPUs,
+but instead will not crash hard, but gracefully fail on lack of resources.
+
+ * This case and the patch(es) are also discussed in more detail here:
+
https://lore.kernel.org/qemu-devel/20240516053211.145504-1-hars...@linux.ibm.com/T/#t
+and here:
+https://bugzilla.redhat.com/show_bug.cgi?id=2304078
+
+ [ Other Info ]
+
+ * The code is upstream accepted with qemu v9.1.0(-rc0),
+and the upload to oracular was done,
+and now only noble is affected.
+
+ * Ubuntu releases older than noble are not affected,
+since (nested) KVM virtualization on P10
+was introduced starting with noble.
+ __
+
== Comment: #0 - SEETEENA THOUFEEK - 2024-08-12
03:47:06 ==
+++ This bug was initially created as a clone of Bug #205620 +++
---Problem Description---
cpu hotplug crashes the guest!cpu hotplug crashes the guest!
-
+
---Steps to Reproduce---
- I have been trying for the CPU hotplugging to the guest with maxvcpus as 128
and current value I am giving as 4! but when I try to hotplug 68 vcpus to the
guest, it crahses and we get error message as:
+ I have been trying for the CPU hotplugging to the guest with maxvcpus as 128
and current value I am giving as 4! but when I try to hotplug 68 vcpus to the
guest, it crahses and we get error message as:
[ 303.808494] KVM: Create Guest vcpu hcall failed, rc=-44
error: Unable to read from monitor: Connection reset by peer
-
Steps to reproduce:
1) virsh define bug.xml
2) virsh start Fedora39 --console
3) virsh setvcpus Fedora39 68
- Output :
+ Output :
[ 662.102542] KVM: Create Guest vcpu hcall failed, rc=-44
error: Un
[Bug 2076587] Re: cpu hotplug crashes the guest!
Hello Anushree, would you mind sharing the bug.xml file that you mentioned and that you use for testing, for further reference (for us knowing how the VM was defined)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076587 Title: cpu hotplug crashes the guest! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072760] Re: [24.10 FEAT] [KRN1911] Vertical CPU Polarization Support Stage 2
patch set was applied to oracular 6.11 master-next tree updating ticket to Fix Committed ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072760 Title: [24.10 FEAT] [KRN1911] Vertical CPU Polarization Support Stage 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2072760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072641] Re: [UBUNTU 22.04] KVM: s390: unhandled guest LPSWEY instruction
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072641 Title: [UBUNTU 22.04] KVM: s390: unhandled guest LPSWEY instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2072641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076866] Re: Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0
Pull request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2024-September/thread.html#153390 changing status to 'In Progress'. ** Changed in: linux (Ubuntu Noble) Status: Triaged => In Progress ** Changed in: ubuntu-power-systems Status: Triaged => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076866 Title: Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076866] Re: Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0
** Description changed:
SRU Justification:
[ Impact ]
* A KVM guest (VM) that got live migrated between two Power 10 systems
(using nested virtualization, means KVM on top of PowerVM) will
highly likely crash after about an hour.
* At that point it looked like the live migration itself was already
successful, but it wasn't, and the crash is caused due to it.
[ Test Plan ]
* Setting up two Power 10 systems (with firmware level FW1060 or newer,
that supports nested KVM) with Ubuntu Server 24.04 for ppc64el.
* Setup a qemu/KVM environment that allows to live migrate a KVM
guest from one P10 system to the other.
* (The disk type does not seem to matter, hence NFS based disk storage
can be used for example).
* After about an hour the live migrated guest is likely to crash.
Hence wait for 2 hours (which increases the likeliness) and
a crash due to:
"migrate_misplaced_folio+0x540/0x5d0"
occurs.
[ Where problems could occur ]
* The 'fix' to avoid calling folio_likely_mapped_shared for cases where
folio might have already been unmapped and the move of the checks
might have an impact on page table locks if done wrong,
which may lead to wrong locks, blocked memory and finally crashes.
* The direct folio calls in mm/huge_memory.c and mm/memory.c got now
'in-directed', which may lead to a different behaviour and side-effects.
However, isolation is still done, just slightly different and
instead of using numamigrate_isolate_folio, now in (the renamed)
migrate_misplaced_folio_prepare.
* Further upstream conversations:
https://lkml.kernel.org/r/8f85c31a-e603-4578-bf49-136dae0d4...@redhat.com
https://lkml.kernel.org/r/20240626191129.658cfc32...@smtp.kernel.org
https://lkml.kernel.org/r/20240620212935.656243-3-da...@redhat.com
* Fixing a confusing return code, now to just return 0, on success is
clarifying the return code handling and usage, and was mainly done in
preparation of further changes,
but can have bad side effects if the return code was used in other
code places already as is.
* Further upstream conversations:
https://lkml.kernel.org/r/20240620212935.656243-1-da...@redhat.com
https://lkml.kernel.org/r/20240620212935.656243-2-da...@redhat.com
* Fixing the fact that NUMA balancing prohibits mTHP
(multi-size Transparent Hugepage Support) seems to be unreasonable
since its an exclusive mapping.
Allowing this seems to bring significant performance improvements
see commit message d2136d749d76), but introduced significant changes
PTE mapping and modifications and even relies on further commits:
859d4adc3415 ("mm: numa: do not trap faults on shared data section pages")
80d47f5de5e3 ("mm: don't try to NUMA-migrate COW pages that have other
uses")
This case cause issues on systems configured for THP,
may confuse the ordering, which may even lead to memory corruption.
And this may especially hit (NUMA) systems with high core numbers,
where balancing is more often needed.
* Further upstream conversations:
https://lore.kernel.org/all/20231117100745.fnpijbk4xgmal...@techsingularity.net/
https://lkml.kernel.org/r/c33a5c0b0a0323b1f8ed53772f50501f4b196e25.1712132950.git.baolin.w...@linux.alibaba.com
https://lkml.kernel.org/r/d28d276d599c26df7f38c9de8446f60e22dd1950.1711683069.git.baolin.w...@linux.alibaba.com
* The refactoring of the code for NUMA mapping rebuilding and moving
it into a new helper, seems to be straight forward, since the active code
stays unchanged, however the new function needs to be callable, but this
is the case since its all in mm/memory.c.
* Further upstream conversations:
https://lkml.kernel.org/r/cover.1712132950.git.baolin.w...@linux.alibaba.com
https://lkml.kernel.org/r/cover.1711683069.git.baolin.w...@linux.alibaba.com
https://lkml.kernel.org/r/8bc2586bdd8dbbe6d83c09b77b360ec8fcac3736.1711683069.git.baolin.w...@linux.alibaba.com
* The refactoring of folio_estimated_sharers to folio_likely_mapped_shared
is more significant, since the logic changed from
(folio_estimated_sharers) 'estimate the number of sharers of a folio' to
(folio_likely_mapped_shared) 'estimate if the folio is mapped into the page
tables of more than one MM'.
* Since this is an estimation, the results may be unpredictable
(especially for bigger folios), and not like expected or assumed
(there are quite some side-notes in the code comments of bb34f78d72c2,
that mention potential fuzzy results), hence this
may lead to unforeseen behavior.
* The condition statements became clearer since it's now based on
(more or less obvious) number counts, but can still be erroneous in
case folio_estimated_sharers does incorrect calculations.
[Bug 2072641] Re: [UBUNTU 22.04] KVM: s390: unhandled guest LPSWEY instruction
Commit landed in Ubuntu-5.15.0-120.130 (and newer) and we have 5.15.0.121.121 in proposed. Hence updating status to Fix Committed. ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Medium Status: Triaged ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Oracular) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072641 Title: [UBUNTU 22.04] KVM: s390: unhandled guest LPSWEY instruction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2072641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076866] Re: Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0
** Summary changed: - Guest crahses post migration with migrate_misplaced_folio+0x4cc/0x5d0 + Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076866 Title: Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072661] Re: [24.10 FEAT] [KRN1905] Kernel image in vmalloc space (V!=R)
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072661 Title: [24.10 FEAT] [KRN1905] Kernel image in vmalloc space (V!=R) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2072661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076147] Re: Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test
Pull request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2024-September/thread.html#153383 changing status to 'In Progress', assigning kernel team. ** Changed in: linux (Ubuntu Noble) Status: Triaged => In Progress ** Changed in: ubuntu-power-systems Status: Triaged => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076147 Title: Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076147] Re: Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test
** Description changed: SRU Justification: [ Impact ] * KVM 2nd level guest (means KVM VM that runs nested on top of a Power 10 PowerVM hypervisor) hangs during LTP (Linux Test Projects) test suite. * It hangs with: "Back trace of paca->saved_r1 (0xc00c1bc8bb00) (possibly stale) @ new_slab" * Diagnosing the issues points this this fix/upstream-commit: [commit message, by Barry Song ] Within try_to_unmap_one(), page_vma_mapped_walk() races with other PTE modifications preceded by pte clear. While iterating over PTEs of a large folio, it only starts acquiring PTL from the first valid (present) PTE. PTE modifications can temporarily set PTEs to pte_none. Consequently, the initial PTEs of a large folio might be skipped in try_to_unmap_one(). For example, for an anon folio, if we skip PTE0, we may have PTE0 which is still present, while PTE1 ~ PTE(nr_pages - 1) are swap entries after try_to_unmap_one(). So folio will be still mapped, the folio fails to be reclaimed and is put back to LRU in this round. This also breaks up PTEs optimization such as CONT-PTE on this large folio and may lead to accident folio_split() afterwards. And since a part of PTEs are now swap entries, accessing those parts will introduce overhead - do_swap_page. Although the kernel can withstand all of the above issues, the situation still seems quite awkward and warrants making it more ideal. The same race also occurs with small folios, but they have only one PTE, thus, it won't be possible for them to be partially unmapped. This patch [see below] holds PTL from PTE0, allowing us to avoid reading PTE values that are in the process of being transformed. With stable PTE values, we can ensure that this large folio is either completely reclaimed or that all PTEs remain untouched in this round. A corner case is that if we hold PTL from PTE0 and most initial PTEs have been really unmapped before that, we may increase the duration of holding PTL. Thus we only apply this optimization to folios which are still entirely mapped (not in deferred_split list). [ Fix ] * 73bc32875ee9 73bc32875ee9b1881dd780308c6793fe463fe803 "mm: hold PTL from the first PTE while reclaiming a large folio" [ Test Plan ] * An IBM Power 10 system (where PowerVM is mandatory) running Ubuntu Server 24.04 (kernel 6.8) or later with (nested) KVM setup (so KVM on top of PowerVM). * Run LTP test suite Tests running: SLS(io,base) * Without the patch the above test will hang with Back trace of paca->saved_r1 (0xc00c1bc8bb00) (possibly stale) @ new_slab [ Where problems could occur ] * This is a common code change in the memory management sub-system, hence great care needs to be taken, even if it was discussed upfront at the https://lore.kernel.org/ mailing list and the upstream commit provenance shows that many eyes had a look at this. * The modification is relatively small with just one if statement (across two lines) in mm/vmscan.c. * This change is to assist 'try_to_unmap' to acquire page table locks (PTL) from the first page table entry (PTE) and to eliminate the influence of temporary and volatile PTE values. * If done wrong it can especially have a negative impact in case of large folios. and wrong hints might be given to try_to_unmap which may lead to bad page swapping. * In case of an issue with this patch the result can also be decreased performance and efficiency in the page table handling - the opposite of what the patch is supposed to address. * Fortunately several developers had their eyes on this commit, - as the provenance of the patch and the discussion at lkml shows. + as the provenance of the patch and the discussion at LKML shows. + + * Further upstream conversation: +Link: https://lkml.kernel.org/r/20240306095219.71086-1-21cn...@gmail.com [ Other Info ] * The commit is upstream since v6.10(-rc1), hence it will be included - in oracular with the planned target kernel. + in oracular with the planned target kernel of 6.11. + + * And since (nested) KVM virtualization on ppc64el was (re-)introduced +just with noble, no older Ubuntu releases older than noble are affected. __ == Comment: #0 - SEETEENA THOUFEEK - 2024-08-06 00:20:57 == +++ This bug was initially created as a clone of Bug #206372 +++ ---Problem Description--- L2 Guest hung during LTP Tests. Back trace of paca->saved_r1 (0xc00c1bc8bb00) (possibly stale) @ new_slab (edit) ---uname output--- NA ---Additional Hardware Info--- NA Contact Information = na ---Debugger Data--- NA ---Patches Installed--- NA ---Steps to Reproduce--- Tests running: SLS(io,base) LPAR Confi
[Bug 2076866] Re: Guest crahses post migration with migrate_misplaced_folio+0x4cc/0x5d0
** Description changed:
SRU Justification:
[ Impact ]
- * A KVM guest (VM) that got live migrated between two Power 10 systems
-(using nested virtualization, means KVM on top of PowerVM) will
-highly likely crash after about an hour.
-
- * At that point it looked like the live migration itself was already
-successful, but it wasn't, and the crash is caused due to it.
+ * A KVM guest (VM) that got live migrated between two Power 10 systems
+ (using nested virtualization, means KVM on top of PowerVM) will
+ highly likely crash after about an hour.
+
+ * At that point it looked like the live migration itself was already
+ successful, but it wasn't, and the crash is caused due to it.
[ Test Plan ]
- * Setting up two Power 10 systems (with firmware level FW1060 or newer,
-that supports nested KVM) with Ubuntu Server 24.04 for ppc64el.
-
- * Setup a qemu/KVM environment that allows to live migrate a KVM
-guest from one P10 system to the other.
-
- * (The disk type does not seem to matter, hence NFS based disk storage
- can be used for example).
-
- * After about an hour the live migrated guest is likely to crash.
-Hence wait for 2 hours (which increases the likeliness) and
-a crash due to:
-"migrate_misplaced_folio+0x540/0x5d0"
-occurs.
+ * Setting up two Power 10 systems (with firmware level FW1060 or newer,
+ that supports nested KVM) with Ubuntu Server 24.04 for ppc64el.
+
+ * Setup a qemu/KVM environment that allows to live migrate a KVM
+ guest from one P10 system to the other.
+
+ * (The disk type does not seem to matter, hence NFS based disk storage
+ can be used for example).
+
+ * After about an hour the live migrated guest is likely to crash.
+ Hence wait for 2 hours (which increases the likeliness) and
+ a crash due to:
+ "migrate_misplaced_folio+0x540/0x5d0"
+ occurs.
[ Where problems could occur ]
- * The 'fix' to avoid calling folio_likely_mapped_shared for cases where
-folio might have already been unmapped and the move of the checks
-might have an impact on page table locks if done wrong,
-which may lead to wrong locks, blocked memory and finally crashes.
-
- * The direct folio calls in mm/huge_memory.c and mm/memory.c got now
-'in-directed', which may lead to a different behaviour and side-effects.
-However, isolation is still done, just slightly different and
-instead of using numamigrate_isolate_folio, now in (the renamed)
-migrate_misplaced_folio_prepare.
-
- * Further upstream conversations:
-https://lkml.kernel.org/r/8f85c31a-e603-4578-bf49-136dae0d4...@redhat.com
-https://lkml.kernel.org/r/20240626191129.658cfc32...@smtp.kernel.org
-https://lkml.kernel.org/r/20240620212935.656243-3-da...@redhat.com
-
- * Fixing a confusing return code, now to just return 0, on success is
-clarifying the return code handling and usage, and was mainly done in
-preparation of further changes,
-but can have bad side effects if the return code was used in other
-code places already as is.
-
- * Further upstream conversations:
-https://lkml.kernel.org/r/20240620212935.656243-1-da...@redhat.com
-https://lkml.kernel.org/r/20240620212935.656243-2-da...@redhat.com
-
- * Fixing the fact that NUMA balancing prohibits mTHP
-(multi-size Transparent Hugepage Support) seems to be unreasonable
-since its an exclusive mapping.
-Allowing this seems to bring significant performance improvements
-see commit message d2136d749d76), but introduced significant changes
-PTE mapping and modifications and even relies on further commits:
-859d4adc3415 ("mm: numa: do not trap faults on shared data section pages")
-80d47f5de5e3 ("mm: don't try to NUMA-migrate COW pages that have other
uses")
-This case cause issues on systems configured for THP,
-may confuse the ordering, which may even lead to memory corruption.
-And this may especially hit (NUMA) systems with high core numbers,
-where balancing is more often needed.
-
- * Further upstream conversations:
-
https://lore.kernel.org/all/20231117100745.fnpijbk4xgmal...@techsingularity.net/
-
https://lkml.kernel.org/r/c33a5c0b0a0323b1f8ed53772f50501f4b196e25.1712132950.git.baolin.w...@linux.alibaba.com
-
https://lkml.kernel.org/r/d28d276d599c26df7f38c9de8446f60e22dd1950.1711683069.git.baolin.w...@linux.alibaba.com
-
- * The refactoring of the code for NUMA mapping rebuilding and moving
-it into a new helper, seems to be straight forward, since the active code
-stays unchanged, however the new function needs to be callable, but this
-is the case since its all in mm/memory.c.
-
- * Further upstream conversations:
-
https://lkml.kernel.org/r/cover.1712132950.git.baolin.w...@linux.alibaba.com
-
https://lkml.kernel.org/r/cover.1711683069.git.baolin.w...@linux.alibaba.com
-
https://lkml.kernel.org/r/8bc2586bdd8dbbe6d83c09
[Bug 2076866] Re: Guest crahses post migration with migrate_misplaced_folio+0x4cc/0x5d0
** Description changed:
+ SRU Justification:
+
+ [ Impact ]
+
+ * A KVM guest (VM) that got live migrated between two Power 10 systems
+(using nested virtualization, means KVM on top of PowerVM) will
+highly likely crash after about an hour.
+
+ * At that point it looked like the live migration itself was already
+successful, but it wasn't, and the crash is caused due to it.
+
+ [ Test Plan ]
+
+ * Setting up two Power 10 systems (with firmware level FW1060 or newer,
+that supports nested KVM) with Ubuntu Server 24.04 for ppc64el.
+
+ * Setup a qemu/KVM environment that allows to live migrate a KVM
+guest from one P10 system to the other.
+
+ * (The disk type does not seem to matter, hence NFS based disk storage
+ can be used for example).
+
+ * After about an hour the live migrated guest is likely to crash.
+Hence wait for 2 hours (which increases the likeliness) and
+a crash due to:
+"migrate_misplaced_folio+0x540/0x5d0"
+occurs.
+
+ [ Where problems could occur ]
+
+ * The 'fix' to avoid calling folio_likely_mapped_shared for cases where
+folio might have already been unmapped and the move of the checks
+might have an impact on page table locks if done wrong,
+which may lead to wrong locks, blocked memory and finally crashes.
+
+ * The direct folio calls in mm/huge_memory.c and mm/memory.c got now
+'in-directed', which may lead to a different behaviour and side-effects.
+However, isolation is still done, just slightly different and
+instead of using numamigrate_isolate_folio, now in (the renamed)
+migrate_misplaced_folio_prepare.
+
+ * Further upstream conversations:
+https://lkml.kernel.org/r/8f85c31a-e603-4578-bf49-136dae0d4...@redhat.com
+https://lkml.kernel.org/r/20240626191129.658cfc32...@smtp.kernel.org
+https://lkml.kernel.org/r/20240620212935.656243-3-da...@redhat.com
+
+ * Fixing a confusing return code, now to just return 0, on success is
+clarifying the return code handling and usage, and was mainly done in
+preparation of further changes,
+but can have bad side effects if the return code was used in other
+code places already as is.
+
+ * Further upstream conversations:
+https://lkml.kernel.org/r/20240620212935.656243-1-da...@redhat.com
+https://lkml.kernel.org/r/20240620212935.656243-2-da...@redhat.com
+
+ * Fixing the fact that NUMA balancing prohibits mTHP
+(multi-size Transparent Hugepage Support) seems to be unreasonable
+since its an exclusive mapping.
+Allowing this seems to bring significant performance improvements
+see commit message d2136d749d76), but introduced significant changes
+PTE mapping and modifications and even relies on further commits:
+859d4adc3415 ("mm: numa: do not trap faults on shared data section pages")
+80d47f5de5e3 ("mm: don't try to NUMA-migrate COW pages that have other
uses")
+This case cause issues on systems configured for THP,
+may confuse the ordering, which may even lead to memory corruption.
+And this may especially hit (NUMA) systems with high core numbers,
+where balancing is more often needed.
+
+ * Further upstream conversations:
+
https://lore.kernel.org/all/20231117100745.fnpijbk4xgmal...@techsingularity.net/
+
https://lkml.kernel.org/r/c33a5c0b0a0323b1f8ed53772f50501f4b196e25.1712132950.git.baolin.w...@linux.alibaba.com
+
https://lkml.kernel.org/r/d28d276d599c26df7f38c9de8446f60e22dd1950.1711683069.git.baolin.w...@linux.alibaba.com
+
+ * The refactoring of the code for NUMA mapping rebuilding and moving
+it into a new helper, seems to be straight forward, since the active code
+stays unchanged, however the new function needs to be callable, but this
+is the case since its all in mm/memory.c.
+
+ * Further upstream conversations:
+
https://lkml.kernel.org/r/cover.1712132950.git.baolin.w...@linux.alibaba.com
+
https://lkml.kernel.org/r/cover.1711683069.git.baolin.w...@linux.alibaba.com
+
https://lkml.kernel.org/r/8bc2586bdd8dbbe6d83c09b77b360ec8fcac3736.1711683069.git.baolin.w...@linux.alibaba.com
+
+ * The refactoring of folio_estimated_sharers to folio_likely_mapped_shared
+is more significant, since the logic changed from
+(folio_estimated_sharers) 'estimate the number of sharers of a folio' to
+(folio_likely_mapped_shared) 'estimate if the folio is mapped into the page
+tables of more than one MM'.
+
+ * Since this is an estimation, the results may be unpredictable
+(especially for bigger folios), and not like expected or assumed
+(there are quite some side-notes in the code comments of bb34f78d72c2,
+that mention potential fuzzy results), hence this
+may lead to unforeseen behavior.
+
+ * The condition statements became clearer since it's now based on
+(more or less obvious) number counts, but can still be erroneous in
+case folio_estimated_sharers does incorrect calculations.
+
+
[Bug 2072760] Re: [24.10 FEAT] [KRN1911] Vertical CPU Polarization Support Stage 2
Pull request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2024-September/thread.html#153380 changing status to 'In Progress', assigning kernel team. ** Changed in: ubuntu-z-systems Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Information type changed from Private to Public ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072760 Title: [24.10 FEAT] [KRN1911] Vertical CPU Polarization Support Stage 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2072760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077722] Re: [Ubuntu 24.04] MultiVM - L2 guest(s) running stress-ng getting stuck at booting after triggering crash
Looks like it is not yet clear if xive is the problem. So isn't it too early to revert the patches? Is it really safe to do so? I see they got introduced with kernel 6.8, but are still in the later kernels. I don't see any upstream revert (ideally as "stable update"), which would be the right approach - I think. ** Changed in: ubuntu-power-systems Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077722 Title: [Ubuntu 24.04] MultiVM - L2 guest(s) running stress-ng getting stuck at booting after triggering crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2077722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060039] Re: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang
** Description changed: SRU Justification: - + [Impact] - * L1 host hangs when triggering FADump with recommended crash - + * L1 host hangs when triggering FADump that results in crash + [Fix] - * 353d7a84c214f184d5a6b62acdec8b4424159b7c 353d7a84c214 "powerpc/64s/radix/kfence: map __kfence_pool at page granularity" - + * 353d7a84c214f184d5a6b62acdec8b4424159b7c 353d7a84c214 "powerpc/64s/radix/kfence: map __kfence_pool at page granularity" + [Test Case] - * Have a Ubuntu Server 24.04 LTS installation on ppc64el. - * Enable FADump with 1GB: fadump=on crashkernel=1024M - * A kernel panic will happen when dump got triggered - + * Have a Ubuntu Server 24.04 LTS installation on ppc64el. + * Enable FADump with 1GB: fadump=on crashkernel=1024M + * A kernel panic will happen when dump got triggered + [Regression Potential] * There is a certain risk of a regression, but it is mapping only the memory - allocated for KFENCE pool at page granularity, reducing memory consumption - when KFENCE is used. - + allocated for KFENCE pool at page granularity, reducing memory consumption + when KFENCE is used. + * On top the commit is already upstream reviewed and accepted. - + * The modifications were done and tested by IBM. - + * The fadump feature is supported only on IBM POWER systems. - + [Other] * The fix/commit got upstream accepted with kernel v6.11-rc4, - hence Oracular (with a planned kernel of 6.11) is not affected. + hence Oracular (with a planned kernel of 6.11) is not affected. ... Problem description : == Triggered FADump with the recommended crash. L1 host got hung. As per the public document https://wiki.ubuntu.com/ppc64el/Recommendations recommended crash kernel size is 1024M for the system. But with 1024M and 2048M, the L1 is getting hanged. with 4096, crash is generated and collected. root@ubuntu2404:~# uname -ar Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu2404:~# free -h totalusedfree shared buff/cache available Mem:48Gi 1.7Gi46Gi13Mi 687Mi 46Gi Swap: 8.0Gi 0B 8.0Gi root@ubuntu2404:~# cat /proc/cmdline BOOT_IMAGE=/vmlinux-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro fadump=on crashkernel=1024M root@ubuntu2404:~# dmesg | grep -i reser [0.00] fadump: Reserved 1024MB of memory at 0x004000 (System RAM: 51200MB) [0.00] fadump: Initialized 0x4000 bytes cma area at 1024MB from 0x4007 bytes of memory reserved for firmware-assisted dump [0.00] Memory: 49316672K/52428800K available (23616K kernel code, 4096K rwdata, 25536K rodata, 8832K init, 2487K bss, 2063552K reserved, 1048576K cma-reserved) [0.396408] ibmvscsi 3066: Client reserve enabled root@ubuntu2404:~# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:ready to fadump IBM is looking to update the crash kernel reservations section of the wiki for Power. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060039 Title: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073786] Re: [24.10 FEAT] [LDP2018] Upgrade s390-tools to latest version (v2.34.0)
** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073786 Title: [24.10 FEAT] [LDP2018] Upgrade s390-tools to latest version (v2.34.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2073786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076866] Re: Guest crahses post migration with migrate_misplaced_folio+0x4cc/0x5d0
** Summary changed: - ISST-LTE:KOP:1060.1:doodlp1g8:Post Migration Non-MDC L1 eralp1 crashed with migrate_misplaced_folio+0x4cc/0x5d0 + Guest crahses post migration with migrate_misplaced_folio+0x4cc/0x5d0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076866 Title: Guest crahses post migration with migrate_misplaced_folio+0x4cc/0x5d0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076406] Re: L2 Guest migration: continuously dumping while running NFS guest migration
Pull request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2024-September/thread.html#153261 changing status to 'In Progress', assigning kernel team. ** Changed in: linux (Ubuntu Noble) Status: Triaged => In Progress ** Changed in: ubuntu-power-systems Status: Triaged => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076406 Title: L2 Guest migration: continuously dumping while running NFS guest migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076406] Re: L2 Guest migration: continuously dumping while running NFS guest migration
A test kernel was build in this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp2076406 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076406 Title: L2 Guest migration: continuously dumping while running NFS guest migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology
Pull request submitted to kernel team's mailing list: https://lists.ubuntu.com/archives/kernel-team/2024-September/thread.html#153260 changing status to 'In Progress', assigning kernel team. ** Changed in: linux (Ubuntu Noble) Status: Confirmed => In Progress ** Changed in: ubuntu-power-systems Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070329 Title: KOP L2 guest fails to boot with 1 core - SMT8 topology To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology
A test kernel is currently being build in this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp2070329 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070329 Title: KOP L2 guest fails to boot with 1 core - SMT8 topology To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076406] Re: L2 Guest migration: continuously dumping while running NFS guest migration
** Description changed: + SRU Justification: + + [ Impact ] + + * While doing ISST testing it turned out that a 2nd level (KVM) +guest (aka VM) continuously dumped when running an NFS +guest migration. + + [ Test Plan ] + + * Setup two IBM Power 10 system (with firmware 1060, that offers +support for KVM) with Ubuntu Server 24.04 for ppc64el. + + * Setup qemu/KVM on both on these system to allow guest migration. + + * Setup a KVM guest and place its disk on an NFS volume. + + * Now initiate a guest migration. + + * Without the two patches the initiator system will start to dump. + + * Since this setup requires a special firmware level, +the verification will be done by the IBM Power team. + + [ Where problems could occur ] + + * Although the patch set looks huge, +the patches themselves are relatively small and less invasive +and I would consider them mainly as fixes. + + * kvmppc_set_one_reg_hv() wrongly get() the value instead of +set() for MMCR3. + + * And The kvmppc_get_one_reg_hv() for SDAR is wrongly getting +the SIAR instead of SDAR - which is quite traceable. + + * Then a one-reg interface for DEXCR register KVM_REG_PPC_DEXCR +is introduced. Here issues can happen if the initialization +is done wrong or in the case statement. +A fix was added to keep nested guest DEXCR in sync. +The guest state element defined for DEXCR was already there, +but not really considered - this is fixed now (DEXCR GSID). +If initialization was done wrong or code in case stmt, +this can harm the guest state. +Guest state may get out of sync. + + * Another one-reg register identifier was introduced +that is used to read and set the virtual HASHKEYR +for the guest during enter/exit with KVM_REG_PPC_HASHKEYR. +Again initialization and the case code are critical. +Code was added to keep nested guest HASHKEYR in sync. +Again the state element defined for HASHKEYR was there, +but not considered, what is fixed now (HASHKEYR GSID) +If initialization was done wrong or code in case stmt, +this can harm the guest state. +This can harm the L2 guest during enter or exit. + + * Again another one-reg identifier was introduced +that is used to read and set the virtual HASHPKEYR +for the guest during enter/exit with KVM_REG_PPC_HASHPKEYR. +And again the guest state element defined for HASHPKEYR +was there but ignored which is now fixed (HASHPKEYR GSID). +If initialization was done wrong or code in case stmt, +this can harm the guest state. +This can harm the L2 guest during enter or exit. + + [ Other Info ] + + * Since (nested) KVM support is new on P10, +this does not affect older Power generation +(P9 is the only other hw generation that is supported by 24.04, +but it only supports native virtualization). + + * Both patches are upstream accepted since v6.11(-rc1), +hence will be in oracular +and are also upstream tagged as stable updates. + + * Since the required firmware FW1060 is relatively new, +we can assume that not many user ran into this issue yet. + __ + == Comment: #0 - SEETEENA THOUFEEK - 2024-08-09 03:50:24 == +++ This bug was initially created as a clone of Bug #206737 +++ ---Problem Description--- L2 Guest migration: evelp2g4[L2]: while running NFS guest migration continuously dumping smp_call_function_many_cond+0x500/0x738 (unreliable) and watchdog: BUG: soft lockup - CPU#14 stuck for 223s! [systemd-homed} - + ---uname output--- NA - - Machine Type = NA - + + Machine Type = NA + Contact Information = NA [79205.163691] Hardware name: IBM pSeries (emulated by qemu) POWER10 (raw) 0x800200 0xf06 of:SLOF,HEAD hv:linux,kvm pSeries [79205.163834] NIP: c02bb7a4 LR: c02bb750 CTR: c00d192c - [79205.163929] REGS: c003871cf1b0 TRAP: 0900 Tainted: G L + [79205.163929] REGS: c003871cf1b0 TRAP: 0900 Tainted: G L [79205.165041] MSR: 8280b033 CR: 4404 XER: 20040004 [79205.165266] CFAR: IRQMASK: 0 -GPR00: c02bbc58 c003871cf450 c20ded00 0009 -GPR04: 0009 0009 0080 0200 -GPR08: 01ff 0001 c00740f57ee0 44048222 -GPR12: c00d192c c00743ddc980 -GPR16: cd86e200 0001 0001 -GPR20: 000c c3d06188 c00ac4d0 ca374e00 -GPR24: c3d06840 c00741193188 c00741193188 -GPR28: c00741193180 c3d06840 0048 0009 + GPR00: c02bbc58 c003871cf450 c20ded0
[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology
** Description changed: + SRU Justification: + + [ Impact ] + + * On a P10 system with SMT-8 configured +a level 2 guest (VM) fails to boot in case +it only has one core assigned. + + [ Test Plan ] + + * Setup an IBM Power 10 system - that support up to SMT-8 +and with firmware 1060, that offers support for KVM - +using Ubuntu Server 24.04 for ppc64el. + + * Setup qemu/KVM on this system. + + * Configure a KVM guest (e.g. using virtinst or +qemu-system-ppc64 directly) now with smt-8, +but only one virtual CPU. + + * Try to boot this specific guest: +qemu-system-ppc64 \ + -drive file=rhel.qcow2,format=qcow2 \ + -m 20G \ + -smp 8,cores=1,threads=8 \ + -cpu host \ + -nographic \ + -machine pseries,ic-mode=xics -accel kvm + + * It will fail to boot with a kernel that does not +have the two patches in place. + + * Since this setup requires a special firmware level, +the verification will be done by the IBM Power team. + + [ Where problems could occur ] + + * Primarily support for using DPDES (register) is required, +since its needed for enabling usage of doorbells in L2 gusts. +This is mainly done by adding DEFINEs, stubs and case. +If the definitions are not correct or if the code executed by +the new case (KVMPPC_GSID_DPDES) is done wrong, +the guest state could be incorrect, harming the L2 guest doorbell. +(DPDES is to provide the means for the hypervisor to save a + [sub-]processor's Directed Privileged Doorbell exception state + when the set of programs running on the [sub-]processor is + swapped out or moved from one [sub-]processor to another.) + + * The missing Doorbell emulation got added by a 4 line if statement +in powerpc/kvm/book3s_hv.c, which is relatively traceable. + + * The main issue I can think of is that kvmppc_set_dpdes is called +with wrong arguments. + + * And kvmppc_set_dpdes will not work (at all) if the above DPDES +support (and commit/patch) is missing. + + [ Other Info ] + + * Since (nested) KVM support is new on P10, +this does not affect older Power generation +(P9 is the only other hw generation that is supported by 24.04, +but it only supports native virtualization). + + * Both patches are upstream accepted since v6.11(-rc1), +hence will be in oracular +and are also upstream tagged as stable updates. + + * Since the required firmware FW1060 is relatively new, +we can assume that not many user ran into this issue yet. + __ + == Comment: #0 - SEETEENA THOUFEEK - 2024-06-25 01:24:11 == +++ This bug was initially created as a clone of Bug #205277 +++ ---Problem Description--- KOP L2 guest fails to boot with 1 core - SMT8 topology - + ---Additional Hardware Info--- - na + na - ---Debugger Data--- - na - + na + ---Steps to Reproduce--- - KOP L2 guest fails to boot when we set the CPU topology as 1 core - SMT 8 + KOP L2 guest fails to boot when we set the CPU topology as 1 core - SMT 8 command line used to verify the issue: #!/bin/sh QEMU="/home/mgautam/qemu" qemu-system-ppc64 -s \ -drive file=/root/debian-12-nocloud-ppc64el.qcow2,format=qcow2 \ -m 20G \ -smp 8,cores=1,sockets=1,threads=8 \ -cpu host \ -nographic \ -machine pseries,ic-mode=xics -accel kvm \ -net nic,model=virtio \ -net user,host=10.0.2.10,hostfwd=tcp:127.0.0.1:10022-:22 - NOTE: L2 boots fine when doorbells are turned off in L1 kernel - - As per the investigation so far, the doorbell exception is not getting fired inside L2 guest. At L1 level, if we set DPDES=1 in the GSB for L2, the guest never receives the doorbell and also it is never cleared from the GSB. We are discussing this behaviour with phyp team. + As per the investigation so far, the doorbell exception is not getting + fired inside L2 guest. At L1 level, if we set DPDES=1 in the GSB for L2, + the guest never receives the doorbell and also it is never cleared from + the GSB. We are discussing this behaviour with phyp team. The root cause of this issue is lack of DPDES support at L1. I've posted the fix upstream - https://lore.kernel.org/linuxppc- dev/20240522084949.123148-1-gau...@linux.ibm.com/T/#u + The fix has been accepted upstream and will be backported for kernels >= + 6.7 - The fix has been accepted upstream and will be backported for kernels >= 6.7 + https://lore.kernel.org/linuxppc- + dev/20240605113913.83715-1-gau...@linux.ibm.com/ - https://lore.kernel.org/linuxppc-dev/20240605113913.83715-1-gau...@linux.ibm.com/ - ---Patches Installed--- na - + ---System Hang--- - na - + na + ---uname output--- na - - Contact Information = na - - Machine Type = na - Userspace rpm: na - - Userspace tool common name: na - - The userspace tool has the following bit modes: na + Contact Information = na - Userspace tool obtained from project website: n
[Bug 2076406] Re: L2 Guest migration: continuously dumping while running NFS guest migration
** Summary changed: - ISST-LTE:KOP:1060FW:evelp2 :L2 Guest migration: evelp2g4[L2]: while running NFS guest migration continuously dumping smp_call_function_many_cond+0x500/0x738 (unreliable) and watchdog: BUG: soft lockup - CPU#14 stuck for 223s! [systemd-homed} (Fedora) + L2 Guest migration: continuously dumping while running NFS guest migration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076406 Title: L2 Guest migration: continuously dumping while running NFS guest migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part
Pull request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2024-August/thread.html#153225
changing status to 'In Progress', assigning kernel team.
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
** Changed in: linux (Ubuntu Jammy)
Assignee: Frank Heimes (fheimes) => Canonical Kernel Team
(canonical-kernel-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959940
Title:
[22.10 FEAT] KVM: Secure Execution guest dump encryption with customer
keys - kernel part
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959940/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part
** Description changed: + SRU Justification: + + [ Impact ] + + * Hypervisor-initiated dumps for Secure Execution +(aka confidential computing) guests are not helpful, +because memory and CPU state is encrypted by a +transient key only available to the Ultravisor (uv). + + * Workload owners can still configure kdump in order to obtain kernel +crash information, but there are situation where kdump doesn't work. + + * In such situations problem determination is severely impeded. + + * This patch set solves this by implementing dumps created in a way +that can only be decrypted by the owner of the guest image +and be used for problem determination. + + [ Test Plan ] + + * The setup of a Secure Execution environment is not trivial +and requires a certain set of hardware (IBM z15 or higher) +with FC 115). + + * On top of the modification of qemu that are handled in this +LP bug, modifications of the Kernel (LP#1959940) and +the s390-tools (LP#1959965) are required on top. + + * So at least a modified kernel and qemu test builds are needed +or both should be in -proposed at the same time (which might +be difficult). +A modified s390-tools is not urgently needed, since for the +verification of the kernel and qemu part a newer version +can be used (but a modified s390-tools is also available in PPA). + + * A detailed description (using Ubuntu as example) on how to setup +secure execution is available here: +Introducing IBM Secure Execution for Linux, April 2024 update +https://www.ibm.com/docs/en/linuxonibm/pdf/lx24se04.pdf + + * And information on 'Working with dumps of KVM guests in +IBM Secure Execution mode' is available here: + https://www.ibm.com/docs/en/linux-on-systems?topic=commands-zgetdump#czgetdump__se_dump_examples + + [ Where problems could occur ] + + * Ultravisor (uv) return codes are introduced, which is +generally appreciated. Just the right return codes need to be set +(and reacted upon). + + * Protected virtual machine dumps are newly introduced on top of +dump of 'normal' KVM VMs. +Since code is shared, it could have an unforeseen impact. + + * The doc renaming could lead to confusion, +if people rely on old doc structure. + + * The new capability case (217) could cause issues, +for example is case of issues during initialization.. + + * CPU dump functionality was added (mainly as new s390x specific code +under s390/kvm), but CPU dump is only one part, +if not working correctly, it may lead to partially useless dump data. + + * Configuration dump functionality was also added +(again mainly as new s390x specific code under s390/kvm), +similar to CPU dump. +And moving from dumping inside of a VM to dumping from outside +(due to potential failures if done inside), might lead to a more +complex flow (now involving the uv), hence could be more error prone. + + * Adding query dump information, requires user space buffers. +Here it's crucial that buffer size is big enough. + + * The newly added constants and structure definitions that are +needed for dump support could become problematic in case wrong +data types were used (applies to all header modifications). + + * IOCTL for PV information retrieval got introduced +(kvm_s390_handle_pv_info, kvm_s390_handle_pv). +There are potential side effect (see man ioctl), +hence all potential failure cases should be covered. + + * New dump feature requires to know how much memory is needed, but if +this call for this is incorrect, it could break the dump process. + + * uv_cb_header struct changed to offset representation, +but using wrong offsets will lead to a wrong struct, +dump issues and potential crashes. + + [ Other Info ] + + * Since 22.04 is a popular LTS release, it is already in use by many +secure execution customers. +But in case of severe crashes or issues in the secure execution +(KVM) guests dumps cannot be used as of today. + + * This enables customers, IBM and Canonical to get support in case of +crashes/dumps on hardware that runs secure execution environments. + + __ + KVM: Secure Execution guest dump encryption with customer keys - kernel part Description: Hypervisor-initiated dumps for Secure Execution guests are not helpful because memory and CPU state is encrypted by a transient key only available to the Ultravisor. Workload owners can still configure kdump in order to obtain kernel crash infomation, but there are situation where kdump doesn't work. In such situations problem determination is severely impeded. This feature will implement dumps created in a way that can only be decrypted by the owner of the guest image and be used for problem determination. Request Type: Kernel - Enhancement from IBM Upstream Acceptance: In Progress Code Contribution: IBM code -- You rec
[Bug 1959966] Re: [23.04 FEAT] KVM: Secure Execution guest dump encryption with customer keys - qemu part
** Description changed: SRU Justification: [ Impact ] - * Hypervisor-initiated dumps for Secure Execution (aka confidential computing) -guests are not helpful because memory and CPU state is encrypted by a -transient key only available to the Ultravisor. + * Hypervisor-initiated dumps for Secure Execution (aka confidential computing) + guests are not helpful because memory and CPU state is encrypted by a + transient key only available to the Ultravisor. - * Workload owners can still configure kdump in order to obtain kernel crash -information, but there are situation where kdump doesn't work. + * Workload owners can still configure kdump in order to obtain kernel crash + information, but there are situation where kdump doesn't work. - * In such situations problem determination is severely impeded. + * In such situations problem determination is severely impeded. - * This patch set solves this by implementing dumps created in a way -that can only be decrypted by the owner of the guest image -and be used for problem determination. + * This patch set solves this by implementing dumps created in a way + that can only be decrypted by the owner of the guest image + and be used for problem determination. [ Test Plan ] - * The setup of a Secure Execution environment is not trivial -and requires a certain set of hardware (IBM Z15 or higher) -with FC 115). + * The setup of a Secure Execution environment is not trivial + and requires a certain set of hardware (IBM Z15 or higher) + with FC 115). - * On top of the modification of qemu that are handled in this -LP bug, modifications of the Kernel (LP#1959940) and -the s390-tools (LP#1959965) are required on top. + * On top of the modification of qemu that are handled in this + LP bug, modifications of the Kernel (LP#1959940) and + the s390-tools (LP#1959965) are required on top. - * So at least a modified kernel and qemu test builds are needed -or both should be in -proposed at the same time (which might -be difficult). -A modified s390-tools is not urgently needed, since for the -verification of the kernel and qemu part a newer version -can be used (but a modified s390-tools is also available in PPA). + * So at least a modified kernel and qemu test builds are needed + or both should be in -proposed at the same time (which might + be difficult). + A modified s390-tools is not urgently needed, since for the + verification of the kernel and qemu part a newer version + can be used (but a modified s390-tools is also available in PPA). - * A detailed description (using Ubuntu as example) on how to setup -secure execution is available here: -Introducing IBM Secure Execution for Linux, April 2024 update -https://www.ibm.com/docs/en/linuxonibm/pdf/lx24se04.pdf + * A detailed description (using Ubuntu as example) on how to setup + secure execution is available here: + Introducing IBM Secure Execution for Linux, April 2024 update + https://www.ibm.com/docs/en/linuxonibm/pdf/lx24se04.pdf - * And information on 'Working with dumps of KVM guests in -IBM Secure Execution mode' is available here: - https://www.ibm.com/docs/en/linux-on-systems?topic=commands-zgetdump#czgetdump__se_dump_examples + * And information on 'Working with dumps of KVM guests in + IBM Secure Execution mode' is available here: + https://www.ibm.com/docs/en/linux-on-systems?topic=commands-zgetdump#czgetdump__se_dump_examples [ Where problems could occur ] - * Mainly dump code (dump/dump.c and include/sysemu/dump.h) is modified, -which may lead to broken or incorrect dumps, -also for non-secure-execution guests. (So testing of both is needed.) + * Mainly dump code (dump/dump.c and include/sysemu/dump.h) is modified, + which may lead to broken or incorrect dumps, + also for non-secure-execution guests. (So testing of both is needed.) - * Modifications in the elf header header handling -as well as wrong hardware address and offset calculation can -(in worst case) lead to unusable files. + * Modifications in the elf header header handling + as well as wrong hardware address and offset calculation can + (in worst case) lead to unusable files. - * Modification in dump state handling may cause issue generating -the dump itself. + * Modification in dump state handling may cause issue generating + the dump itself. - * Modifications need to be endianess-aware, since this secure -execution dump is for s390x - if not dumps become useless. + * Modifications need to be endianess-aware, since this secure + execution dump is for s390x - if not dumps become useless. - * Functions for writing the header got modified (and split), -which may lead to wrong headers (if done erroneously). + * Functions for writing the header got modified (and split), + which may lead
[Bug 1982335] Re: [24.10 FEAT] Valgrind: Support for new IBM Z Hardware (IBM z16)
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1982335 Title: [24.10 FEAT] Valgrind: Support for new IBM Z Hardware (IBM z16) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071774] Re: zfs-dkms FTBFS on Linux 6.10/s390x
Thanks for confirming, Timo! ** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071774 Title: zfs-dkms FTBFS on Linux 6.10/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2071774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part
I think I got it, there are just two backports, for commit e9bf3acb23f0a6e18438c35944d6cb618d16cf05 and commit 437cfd714db9c1d28878a6e2555e9a730f3490c8 . The rest are cherrypicks. With that a test kernel is currently being build in this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp1959940j ** Changed in: linux (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959940 Title: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959966] Re: [23.04 FEAT] KVM: Secure Execution guest dump encryption with customer keys - qemu part
** Changed in: qemu (Ubuntu Jammy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959966 Title: [23.04 FEAT] KVM: Secure Execution guest dump encryption with customer keys - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959966] Re: [23.04 FEAT] KVM: Secure Execution guest dump encryption with customer keys - qemu part
** Description changed: + SRU Justification: + + [ Impact ] + + * Hypervisor-initiated dumps for Secure Execution (aka confidential computing) +guests are not helpful because memory and CPU state is encrypted by a +transient key only available to the Ultravisor. + + * Workload owners can still configure kdump in order to obtain kernel crash +information, but there are situation where kdump doesn't work. + + * In such situations problem determination is severely impeded. + + * This patch set solves this by implementing dumps created in a way +that can only be decrypted by the owner of the guest image +and be used for problem determination. + + [ Test Plan ] + + * The setup of a Secure Execution environment is not trivial +and requires a certain set of hardware (IBM Z15 or higher) +with FC 115). + + * On top of the modification of qemu that are handled in this +LP bug, modifications of the Kernel (LP#1959940) and +the s390-tools (LP#1959965) are required on top. + + * So at least a modified kernel and qemu test builds are needed +or both should be in -proposed at the same time (which might +be difficult). +A modified s390-tools is not urgently needed, since for the +verification of the kernel and qemu part a newer version +can be used (but a modified s390-tools is also available in PPA). + + * A detailed description (using Ubuntu as example) on how to setup +secure execution is available here: +Introducing IBM Secure Execution for Linux, April 2024 update +https://www.ibm.com/docs/en/linuxonibm/pdf/lx24se04.pdf + + * And information on 'Working with dumps of KVM guests in +IBM Secure Execution mode' is available here: + https://www.ibm.com/docs/en/linux-on-systems?topic=commands-zgetdump#czgetdump__se_dump_examples + + [ Where problems could occur ] + + * Mainly dump code (dump/dump.c and include/sysemu/dump.h) is modified, +which may lead to broken or incorrect dumps, +also for non-secure-execution guests. (So testing of both is needed.) + + * Modifications in the elf header header handling +as well as wrong hardware address and offset calculation can +(in worst case) lead to unusable files. + + * Modification in dump state handling may cause issue generating +the dump itself. + + * Modifications need to be endianess-aware, since this secure +execution dump is for s390x - if not dumps become useless. + + * Functions for writing the header got modified (and split), +which may lead to wrong headers (if done erroneously). + + * It's a big patch set in general, which may bring further unforeseen +effects, but it's worth to mention that the code is upstream accepted +since quite a while (qemu 7.2) and already included in Ubuntu +since 23.04 and successfully in use. + + * On top the packages from the PPA test build were tested upfront. + + [ Other Info ] + + * Since 22.04 is a popular LTS release, it is already in use by many +secure execution customers. +But in case of severe crashes or issues in the secure execution +(KVM) guests dumps cannot be used as of today. + + * This enables customers, IBM and Canonical to support in case of +crashes/dumps on hardware that runs secure execution environments. + __ + KVM: Secure Execution guest dump encryption with customer keys - qemu part Description: Hypervisor-initiated dumps for Secure Execution guests are not helpful because memory and CPU state is encrypted by a transient key only available to the Ultravisor. Workload owners can still configure kdump in order to obtain kernel crash infomation, but there are situation where kdump doesn't work. In such situations problem determination is severely impeded. This feature will implement dumps created in a way that can only be decrypted by the owner of the guest image and be used for problem determination. Request Type: Package - Update Version Upstream Acceptance: In Progress Code Contribution: IBM code -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959966 Title: [23.04 FEAT] KVM: Secure Execution guest dump encryption with customer keys - qemu part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077978] Re: [SRU] [agx] eth0 is not a predictable_names
** Description changed: SRU Justification: [ Impact ] * eth0 is not a predictable_names. The Jetson AGX Orin board uses the on-chip ethernet MAC plus an on-board Ethernet PHY. Since it is not a PCIe device, it does not get discovered and named. Considering the case, its name should anyway be defined to eno1. * This upload should statically define it for this platform and this driver in particular. Note that since only jammy images currently exist on this platform, systemd comes with v249, which prevent us from using the DT alias names feature introduced with v252. [ Test Plan ] ubuntu@ubuntu:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1466 qdisc mq state UP group default qlen 1000 link/ether 48:b0:2d:e7:11:5a brd ff:ff:ff:ff:ff:ff inet 10.102.182.159/22 metric 100 brd 10.102.183.255 scope global dynamic eth0 valid_lft 1295712sec preferred_lft 1295712sec inet6 fe80::4ab0:2dff:fee7:115a/64 scope link valid_lft forever preferred_lft forever 3: wlP1p1s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether cc:47:40:3f:0b:a7 brd ff:ff:ff:ff:ff:ff inet6 fe80::ce47:40ff:fe3f:ba7/64 scope link valid_lft forever preferred_lft forever 4: can0: mtu 16 qdisc noop state DOWN group default qlen 10 link/can 5: can1: mtu 16 qdisc noop state DOWN group default qlen 10 link/can [ Where problems could occur ] * nvidia-tegra-default applies default extra configuration for system based on Nvidia Tegra ORIN SoC. Installing it on other ARM64 systems could lead to unexpected behavior. However, as this is an extra package not listed in any image definitions (except the Tegra ones), no problem is expected to occur for current Ubuntu users. [ Other Info ] + * Since device tree alias support got introduced in systemd/networkd v252 + (and newer), noble and oracular are not affected by this, + and the SRU is for jammy only. * This is related to LP #2071428 (Riverside) + __ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-tegra-defaults 1.3~22.04.1 ProcVersionSignature: User Name 5.15.0-1013.13-nvidia-tegra-igx 5.15.148 Uname: Linux 5.15.0-1013-nvidia-tegra-igx aarch64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) Date: Tue Aug 27 15:29:31 2024 Dependencies: SourcePackage: nvidia-tegra-defaults UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077978 Title: [SRU] [agx] eth0 is not a predictable_names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-tegra-defaults/+bug/2077978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077978] Re: [SRU] [agx] eth0 is not a predictable_names
Many thanks Remy for having filled out the SRU template, the updated debdiff and the details. LGTM now I've uploaded the updated package now ... ** Description changed: + SRU Justification: + [ Impact ] * eth0 is not a predictable_names. The Jetson AGX Orin board uses the on-chip ethernet MAC plus an on-board Ethernet PHY. Since it is not a PCIe device, it does not get discovered and named. Considering the case, its name should anyway be defined to eno1. * This upload should statically define it for this platform and this driver in particular. Note that since only jammy images currently exist on this platform, systemd comes with v249, which prevent us from using the DT alias names feature introduced with v252. [ Test Plan ] ubuntu@ubuntu:~$ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1466 qdisc mq state UP group default qlen 1000 link/ether 48:b0:2d:e7:11:5a brd ff:ff:ff:ff:ff:ff inet 10.102.182.159/22 metric 100 brd 10.102.183.255 scope global dynamic eth0 valid_lft 1295712sec preferred_lft 1295712sec inet6 fe80::4ab0:2dff:fee7:115a/64 scope link valid_lft forever preferred_lft forever 3: wlP1p1s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether cc:47:40:3f:0b:a7 brd ff:ff:ff:ff:ff:ff inet6 fe80::ce47:40ff:fe3f:ba7/64 scope link valid_lft forever preferred_lft forever 4: can0: mtu 16 qdisc noop state DOWN group default qlen 10 link/can 5: can1: mtu 16 qdisc noop state DOWN group default qlen 10 link/can [ Where problems could occur ] * nvidia-tegra-default applies default extra configuration for system based on Nvidia Tegra ORIN SoC. Installing it on other ARM64 systems could lead to unexpected behavior. However, as this is an extra package not listed in any image definitions (except the Tegra ones), no problem is expected to occur for current Ubuntu users. [ Other Info ] * This is related to LP #2071428 (Riverside) + __ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-tegra-defaults 1.3~22.04.1 ProcVersionSignature: User Name 5.15.0-1013.13-nvidia-tegra-igx 5.15.148 Uname: Linux 5.15.0-1013-nvidia-tegra-igx aarch64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) Date: Tue Aug 27 15:29:31 2024 Dependencies: SourcePackage: nvidia-tegra-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: nvidia-tegra-defaults (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: nvidia-tegra-defaults (Ubuntu) Status: New => In Progress ** Changed in: nvidia-tegra-defaults (Ubuntu Jammy) Status: New => In Progress ** Changed in: nvidia-tegra-defaults (Ubuntu Jammy) Assignee: (unassigned) => Rémy MARTIN (rmartin013) ** Changed in: nvidia-tegra-defaults (Ubuntu Jammy) Importance: Undecided => High ** Changed in: nvidia-tegra-defaults (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077978 Title: [SRU] [agx] eth0 is not a predictable_names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-tegra-defaults/+bug/2077978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076406] Re: ISST-LTE:KOP:1060FW:evelp2 :L2 Guest migration: evelp2g4[L2]: while running NFS guest migration continuously dumping smp_call_function_many_cond+0x500/0x738 (unreliable) and watchdog
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: ubuntu-power-systems Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Noble) 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: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: linux (Ubuntu Oracular) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => (unassigned) ** Changed in: linux (Ubuntu Oracular) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076406 Title: ISST-LTE:KOP:1060FW:evelp2 :L2 Guest migration: evelp2g4[L2]: while running NFS guest migration continuously dumping smp_call_function_many_cond+0x500/0x738 (unreliable) and watchdog: BUG: soft lockup - CPU#14 stuck for 223s! [systemd-homed} (Fedora) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060039] Re: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed ** Changed in: linux (Ubuntu Noble) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Oracular) Status: Confirmed => Fix Committed ** Changed in: ubuntu-power-systems Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060039 Title: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067383] Re: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff!
Following up on this - looks like the discussion moved to patch set (iianm): [PATCH V16 0/7] Add architecture agnostic code to support vCPU Hotplughttps://lore.kernel.org/qemu-devel/20240716111502.202344-1-salil.me...@huawei.com/ Still in the process of being upstream accepted... ** Changed in: ubuntu-power-systems Status: New => Incomplete ** Changed in: qemu (Ubuntu) Status: New => Incomplete ** Also affects: qemu (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Oracular) Importance: Undecided Status: Incomplete ** Changed in: qemu (Ubuntu Noble) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067383 Title: [Ubuntu 24.04] hotplug of 68 or more cpus is making the guest shutoff! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2067383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070253] Re: KVM on PowerVM: L2 Guest-Aggressively entering CEDE results in low performance. Possible tuning opportunity.
The commit is now included in the 24.04 / noble kernel: Ubuntu-6.8.0-44.44 (and newer) which is currently in -proposed: linux-generic | 6.8.0-44.44| noble-proposed| amd64, arm64, armhf, ppc64el, s390x Hence updating this ticket for noble to Fix Committed. ** Changed in: linux (Ubuntu Noble) Status: Triaged => Fix Committed ** Changed in: ubuntu-power-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070253 Title: KVM on PowerVM: L2 Guest-Aggressively entering CEDE results in low performance. Possible tuning opportunity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070253] Re: KVM on PowerVM: L2 Guest-Aggressively entering CEDE results in low performance. Possible tuning opportunity.
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: High Status: New ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux (Ubuntu Oracular) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070253 Title: KVM on PowerVM: L2 Guest-Aggressively entering CEDE results in low performance. Possible tuning opportunity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076147] Re: Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: High Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: Triaged ** Changed in: linux (Ubuntu Oracular) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Noble) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076147 Title: Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: High Status: Confirmed ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed ** Changed in: linux (Ubuntu Oracular) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070329 Title: KOP L2 guest fails to boot with 1 core - SMT8 topology To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075575] Re: kexec fails in LPAR when some cpus are disabled
** Changed in: linux (Ubuntu Oracular) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075575 Title: kexec fails in LPAR when some cpus are disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2075575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
Thank you Tasmiya and Jamie - I'm updating the tags accordingly ... ** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
One of the two issues that I faced, the rust code that failed to build, was now solved upstream in a different way, by lowering the lint level to warn (rather than adjusting the code, like I did initially). I'm aligning now the package to the upstream fix, hence uploading yet another debdiff here. A new test build was successful and is available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp2077055second ** Attachment added: "debdiffs.tgz" https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+attachment/5809745/+files/debdiffs.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959965] Re: [22.04 FEAT] KVM: Secure Execution guest dump encryption with customer keys - s390-tools part
** Also affects: s390-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: s390-tools (Ubuntu Jammy) Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959965 Title: [22.04 FEAT] KVM: Secure Execution guest dump encryption with customer keys - s390-tools part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
Here's an updated debdiff (patch headers modified, now incl. references to upstream issues and proper patch description). ** Attachment added: "debdiffs.tgz" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/2077055/+attachment/5809485/+files/debdiffs.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)
Did the verification for the kernel (linux-generic) like above and based on representative kernel modules (arch-specific and common): noble: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble $ uname -a Linux P10d-LPAR06 6.8.0-41-generic #41-Ubuntu SMP Fri Aug 2 21:00:36 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux $ sudo unzstd /usr/lib/debug/lib/modules/6.8.0-41-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko.zst /usr/lib/debug/lib/modules/6.8.0-41-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko.zst: 338761 bytes $ readelf -wi /usr/lib/debug/lib/modules/6.8.0-41-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko | grep DW_AT_produce | grep -c mbackchain 0 $ readelf -wi /usr/lib/debug/lib/modules/6.8.0-41-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko | grep DW_AT_produce | grep -c no-omit-frame-pointer 0 $ sudo unzstd /usr/lib/debug/lib/modules/6.8.0-41-generic/kernel/fs//nfs/nfsv4.ko.zst /usr/lib/debug/lib/modules/6.8.0-41-generic/kernel/fs//nfs/nfsv4.ko.zst: 18009201 bytes $ readelf -wi /usr/lib/debug/lib/modules/6.8.0-41-generic/kernel/fs//nfs/nfsv4.ko | grep DW_AT_produce | grep -c mbackchain 0 $ readelf -wi /usr/lib/debug/lib/modules/6.8.0-41-generic/kernel/fs//nfs/nfsv4.ko | grep DW_AT_produce | grep -c no-omit-frame-pointer 0 oracular: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Oracular Oriole (development branch) Release:24.10 Codename: oracular $ uname -a Linux P10d-LPAR06 6.11.0-4-generic #4-Ubuntu SMP Tue Aug 20 14:54:18 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux $ sudo unzstd /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko.zst /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko.zst: 354129 bytes $ readelf -wi /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko | grep DW_AT_produce | grep -c mbackchain 0 $ readelf -wi /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko | grep DW_AT_produce | grep -c no-omit-frame-pointer 0 $ sudo unzstd /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko.zst /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko.zst: 19618441 bytes $ readelf -wi /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko | grep DW_AT_produce | grep -c mbackchain 0 $ readelf -wi /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko | grep DW_AT_produce | grep -c no-omit-frame-pointer 0 (Btw. the negative test for mbackchain was done by intention, since this needs to be set for s390x, but for s390x only. The changes were done at the same time, verifying here, that is was really not set for ppc64el.) Like one can see "-no-omit-frame-pointer" (and 'mbackchain') is not set, hence successful verified. Closing the affected 'linux (Ubuntu)' as 'Fix Released' - and with that the project entry as well. ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux (Ubuntu Oracular) Status: New => Fix Released ** Changed in: ubuntu-power-systems Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064539 Title: Revert back frame pointers for ppc64el (remove -fno-omit-frame- pointer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)
Did the verification for the kernel (linux-generic) like above and based on representative kernel modules (arch-specific and common): noble: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble $ uname -a Linux testlpar1 6.8.0-35-generic #35-Ubuntu SMP Mon May 20 15:36:54 UTC 2024 s390x s390x s390x GNU/Linux $ sudo unzstd /usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/arch/s390/crypto/aes_s390.ko.zst /usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/arch/s390/crypto/aes_s390.ko.zst: 507329 bytes $ readelf -wi /usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce | grep -c mbackchain 2 $ readelf -wi /usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce | grep -c no-omit-frame-pointer 0 $ sudo unzstd /usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/fs/nfs/nfsv4.ko.zst /usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/fs/nfs/nfsv4.ko.zst: 17383593 bytes $ readelf -wi /usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/fs/nfs/nfsv4.ko | grep DW_AT_produce | grep -c mbackchain 24 $ readelf -wi /usr/lib/debug/lib/modules/6.8.0-35-generic/kernel/fs/nfs/nfsv4.ko | grep DW_AT_produce | grep -c no-omit-frame-pointer 0 oracular: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Oracular Oriole (development branch) Release:24.10 Codename: oracular $ uname -a Linux s1lp14 6.11.0-4-generic #4-Ubuntu SMP Tue Aug 20 14:03:40 UTC 2024 s390x s390x s390x GNU/Linux $ sudo unzstd /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/s390/crypto/aes_s390.ko.zst /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/s390/crypto/aes_s390.ko.zst: 529441 bytes $ readelf -wi /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce | grep -c mbackchain 2 $ readelf -wi /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce | grep -c no-omit-frame-pointer 0 $ sudo unzstd /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko.zst [sudo] password for ubuntu: /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko.zst: 18990945 bytes $ readelf -wi /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko | grep DW_AT_produce | grep -c mbackchain 24 $ readelf -wi /usr/lib/debug/lib/modules/6.11.0-4-generic/kernel/fs/nfs/nfsv4.ko | grep DW_AT_produce | grep -c no-omit-frame-pointer 0 Like one can see '-mbackchain' is set, but "-no-omit-frame-pointer" is not set, hence successful verified. Closing the affected 'linux (Ubuntu)' as 'Fix Released' - and with that the project entry as well. ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux (Ubuntu Oracular) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064538 Title: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2064538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)
** Description changed: SRU Justification: [ Impact ] * The preferred way of doing stack unwinding on Linux on Z is via dwarf call frame information. In absence of a dwarf unwinder (as in the Linux kernel) a stack chain can be maintained at runtime in addition to the dwarf unwinding information. * This allows for simple backtrace implementations, but imposes a small runtime overhead. For this to work, all code that might be part of backtrace must be built with the -mbackchain GCC option. * The -fno-omit-framepointer switch is neither necessary nor helpful in this context. Having a (soft/simulated) frame pointer does not improve backtraces at all on IBM Z. * However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. * Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame- pointers should not be used on IBM Z. * So we are facing here a performance penalty without any gain - on this particular platform. * And sometimes (in rare cases like LP#2060108) frame pointers may even lead to failed builds. [ Test Plan ] * Due to the above description of the impact and rationale, this pragmatic approach for testing is given: * Build the affected packages where frame-pointers should be reverted using the updated dpkg package (that incl. the modified build defaults) on (or for) this particular platform. * Now frame-pointer usage be checked in the following different ways: * 1) For the ease of use (and thanks to Julian Klode), there is this python test script available that allows to verify a binary in regard to frame pointers: https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 - https://gist.githubusercontent.com/julian-klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py + https://gist.githubusercontent.com/julian-klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py + requires python3-pyelftools * 2) Another more manual way is to verify based on debug symbols like this: - find and install the ddeb package - maybe extract the file (e.g. unzstd) - use 'readelf -wi' - and grep for 'DW_AT_produce' (build options) - look for entries regarding frame-pointer The output may look similar to this: readelf -wi ./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce <23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 2.42 <129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 -mindirect-branch=thunk-extern -mfunction-return=thunk-extern -mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g -gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common -fno-strict-aliasing -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -fno-allow-store-data-races -fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -fno-inline-functions-called-once -falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow -fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -fPIC * 3) And maybe watching the build messages / log for the build options that were used (but that is probably not sufficient - it's better to inspect the output.) [ Where problems could occur ] * The dpkg modifications could have been done erroneously. A dpkg test build and/or builds of other packages with the modified dpkg version in place would show this. * The settings in dpkg might be overwritten by other settings/packages. Tests like above, would show this. * One may think there could be issues in an environment where some packages have frame-pointer enabled and other don't. This is fine and was confirmed by IBM toolchain team and ours (as well as by a longer running test system, with FP disabled in kernel, that showed no issues - like expected). [ Other Info ] * These changes were implemented during the opening of the oracular series. The very same changes are backported to 24.04 LTS. * These only affect the ppc64el and s390x architectures, for other architectures it's a no-change upload. * We didn't see any fallout for these changes during the development on the oracular series, and therefore don't expect any fallout or regressions in 24.04 LTS either. -- You received this bug not
[Bug 2064539] Re: Revert back frame pointers for ppc64el (remove -fno-omit-frame-pointer)
** Description changed: SRU Justification: [ Impact ] - * Power's Linux ABIs all require an explicit call chain be stored on + * Power's Linux ABIs all require an explicit call chain be stored on the call stack frames which are all accessible via the stack pointer. - * Therefore, having a (soft/simulated) frame pointer does not improve + * Therefore, having a (soft/simulated) frame pointer does not improve backtraces at all on Power. - * However, forcing a frame pointer via the -fno-omit-frame-pointer + * However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. - * Given -fno-omit-frame-pointer does not provide any improvements + * Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame- pointers should not be used on Power. - * So we are facing here a performance penalty without any gain - on + * So we are facing here a performance penalty without any gain - on this particular platform. - * And sometimes (in rare cases like LP#2060108) frame pointers may even + * And sometimes (in rare cases like LP#2060108) frame pointers may even lead to failed builds. [ Test Plan ] - * Due to the above description of the impact and rationale, -this pragmatic approach for testing is given: + * Due to the above description of the impact and rationale, + this pragmatic approach for testing is given: - * Build the affected packages where frame-pointers should be reverted -using the updated dpkg package (that incl. the modified build defaults) -on (or for) this particular platform. + * Build the affected packages where frame-pointers should be reverted + using the updated dpkg package (that incl. the modified build defaults) + on (or for) this particular platform. - * Now frame-pointer usage be checked in the following different ways: + * Now frame-pointer usage be checked in the following different ways: - * 1) For the ease of use (and thanks to Julian Klode), there is this python - test script available that allows to verify a binary in regard to - frame pointers: - https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 + * 1) For the ease of use (and thanks to Julian Klode), there is this python + test script available that allows to verify a binary in regard to + frame pointers: + https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 + https://gist.githubusercontent.com/julian-klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py + requires python3-pyelftools - * 2) Another more manual way is to verify based on debug symbols like this: - - find and install the ddeb package - - maybe extract the file (e.g. unzstd) - - use 'readelf -wi' - - and grep for 'DW_AT_produce' (build options) - - look for entries regarding frame-pointer - The output may look similar to this: - readelf -wi ./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce - <23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 2.42 - <129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 -mindirect-branch=thunk-extern -mfunction-return=thunk-extern -mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g -gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common -fno-strict-aliasing -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -fno-allow-store-data-races -fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -fno-inline-functions-called-once -falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow -fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -fPIC + * 2) Another more manual way is to verify based on debug symbols like this: + - find and install the ddeb package + - maybe extract the file (e.g. unzstd) + - use 'readelf -wi' + - and grep for 'DW_AT_produce' (build options) + - look for entries regarding frame-pointer + The output may look similar to this: + readelf -wi ./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce + <23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 2.42 + <129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 -mindirect-branch=thunk-extern -mfunction-return=thunk-extern -mindirect-branch-t
[Bug 2064538] Re: Revert back frame pointers for s390x (remove -fno-omit-frame-pointer but use -mbackchain)
** Description changed: SRU Justification: [ Impact ] * The preferred way of doing stack unwinding on Linux on Z is via dwarf call frame information. In absence of a dwarf unwinder (as in the Linux kernel) a stack chain can be maintained at runtime in addition to the dwarf unwinding information. * This allows for simple backtrace implementations, but imposes a small runtime overhead. For this to work, all code that might be part of backtrace must be built with the -mbackchain GCC option. * The -fno-omit-framepointer switch is neither necessary nor helpful in this context. Having a (soft/simulated) frame pointer does not improve backtraces at all on IBM Z. * However, forcing a frame pointer via the -fno-omit-frame-pointer option negatively affects performance for multiple reasons: extra prologue/epilogue overhead and fewer shrink-wrapping opportunities. * Given -fno-omit-frame-pointer does not provide any improvements (backtraces or otherwise) and only reduces performance, -fno-omit-frame- pointers should not be used on IBM Z. * So we are facing here a performance penalty without any gain - on this particular platform. * And sometimes (in rare cases like LP#2060108) frame pointers may even lead to failed builds. [ Test Plan ] * Due to the above description of the impact and rationale, this pragmatic approach for testing is given: * Build the affected packages where frame-pointers should be reverted using the updated dpkg package (that incl. the modified build defaults) on (or for) this particular platform. * Now frame-pointer usage be checked in the following different ways: * 1) For the ease of use (and thanks to Julian Klode), there is this python test script available that allows to verify a binary in regard to frame pointers: https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208 + https://gist.githubusercontent.com/julian-klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py * 2) Another more manual way is to verify based on debug symbols like this: - find and install the ddeb package - maybe extract the file (e.g. unzstd) - use 'readelf -wi' - and grep for 'DW_AT_produce' (build options) - look for entries regarding frame-pointer The output may look similar to this: readelf -wi ./usr/lib/debug/lib/modules/6.8.0-38-generic/kernel/arch/s390/crypto/aes_s390.ko | grep DW_AT_produce <23> DW_AT_producer: (indirect string, offset: 0x7d): GNU AS 2.42 <129> DW_AT_producer: (indirect string, offset: 0x3eef): GNU C11 13.2.0 -m64 -mpacked-stack -mbackchain -msoft-float -march=z13 -mtune=z16 -mindirect-branch=thunk-extern -mfunction-return=thunk-extern -mindirect-branch-table -mrecord-mcount -mnop-mcount -mfentry -mzarch -g -gdwarf-5 -O2 -std=gnu11 -p -fshort-wchar -funsigned-char -fno-common -fno-strict-aliasing -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -fno-allow-store-data-races -fno-stack-protector -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -fno-inline-functions-called-once -falign-functions=8 -fstrict-flex-arrays=3 -fno-strict-overflow -fstack-check=no -fconserve-stack -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -fPIC * 3) And maybe watching the build messages / log for the build options that were used (but that is probably not sufficient - it's better to inspect the output.) [ Where problems could occur ] * The dpkg modifications could have been done erroneously. A dpkg test build and/or builds of other packages with the modified dpkg version in place would show this. * The settings in dpkg might be overwritten by other settings/packages. Tests like above, would show this. * One may think there could be issues in an environment where some packages have frame-pointer enabled and other don't. This is fine and was confirmed by IBM toolchain team and ours (as well as by a longer running test system, with FP disabled in kernel, that showed no issues - like expected). [ Other Info ] - * These changes were implemented during the opening of the oracular series. -The very same changes are backported to 24.04 LTS. + * These changes were implemented during the opening of the oracular series. + The very same changes are backported to 24.04 LTS. - * These only affect the ppc64el and s390x architectures, -for other architectures it's a no-change upload. + * These only affect the ppc64el and s390x architectures, + for other architectures it's a no-change upload. - * We didn't see any fallout for these changes during the development -on the oracular series, and therefore don't expect any fallout or
[Bug 2077722] Re: [Ubuntu 24.04] MultiVM - L2 guest(s) running stress-ng getting stuck at booting after triggering crash
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077722 Title: [Ubuntu 24.04] MultiVM - L2 guest(s) running stress-ng getting stuck at booting after triggering crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2077722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part
Hello Janosch, many thanks for the patch set! I'm just back and will work on this soon-ish. But just to clarify, are these all plain cherry-picks from upstream - or did you had to do any real backport work to get some of the commits applied to the jammy kernel (I mean if any real modifications of code or context were needed)? I just need to add this to the PR/provenance - for our kernel team. I could of course also compare the patches you've sent with what exists upstream, but I think you know it right away ... (Of course talking about the kernel patches/commits only.) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Frank Heimes (fheimes) ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959940 Title: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074376] Re: Disable PCI_DYNAMIC_OF_NODES in Ubuntu
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074376 Title: Disable PCI_DYNAMIC_OF_NODES in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2074376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959940] Re: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959940 Title: [22.10 FEAT] KVM: Secure Execution guest dump encryption with customer keys - kernel part To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073372] Re: [UBUNTU 20.04] s390x: z13 wcsncmp implementation segfaults if n=1
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073372 Title: [UBUNTU 20.04] s390x: z13 wcsncmp implementation segfaults if n=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2073372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069040] Re: Compile glibc for Power9
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069040 Title: Compile glibc for Power9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2069040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067350] Re: Removal of 31-bit (s390) glibc packages
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067350 Title: Removal of 31-bit (s390) glibc packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077540] Re: [24.10] Please test secure-boot and lockdown on the 6.11 kernel (s390x) for Oracular
Updating this ticket with a message that I received via mail: Secureboot lockdown was successfully tested by Grgo/IBM. Test completed! With that I'm closing this ticket as Fix Released. ** Changed in: ubuntu-z-systems Assignee: (unassigned) => bugproxy (bugproxy) ** Changed in: ubuntu-z-systems Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-z-systems Importance: Critical => High ** Changed in: ubuntu-z-systems Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077540 Title: [24.10] Please test secure-boot and lockdown on the 6.11 kernel (s390x) for Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
** Tags added: update-excuse-oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067355] Re: [FEAT 24.10] Update s390-tools to (currently latest) v2.33.1 in oracular
** Summary changed: - Update s390-tools to (currently latest) v2.33.1 in oracular + [FEAT 24.10] Update s390-tools to (currently latest) v2.33.1 in oracular ** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067355 Title: [FEAT 24.10] Update s390-tools to (currently latest) v2.33.1 in oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2067355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
I will create a PR with the changes soon (probably two, since the patches that I had to create to get the build fixed are not related to each other)... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
** Attachment added: "debdiffs.tgz" https://bugs.launchpad.net/ubuntu/+source/s390-tools-signed/+bug/2077055/+attachment/5807008/+files/debdiffs.tgz ** Changed in: s390-tools-signed (Ubuntu) Assignee: (unassigned) => Frank Heimes (fheimes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
The test build in PPA was successful - preparing the debdiff(s) ... ** Also affects: s390-tools-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: s390-tools-signed (Ubuntu) Importance: Undecided => High ** Changed in: s390-tools-signed (Ubuntu) Status: New => In Progress ** Changed in: s390-tools (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
After a discussion with Marc Hartmayer, on discarding *(.note.GNU-stack) for the bootloader tools and after fixing another (but unrelated) rust issue, I think I have now a package that should build. It already built locally for me, now trying in PPA (-proposed enabled): https://launchpad.net/~fheimes/+archive/ubuntu/lp2077055 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075567] Re: zlib fails to build on s390x on oracular with gcc 14
** Changed in: ubuntu-z-systems Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075567 Title: zlib fails to build on s390x on oracular with gcc 14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2075567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
The patched gcc 14 build meanwhile completed. Using it solved the zlib issue (LP#2075567), but unfortunately not the s390-tools 2.34.0 issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076569] Re: ISST-LTE:KOP:doodlp1g3:L2 guest hung and Call traces seen with Snapshot tests
*** This bug is a duplicate of bug 2076147 *** https://bugs.launchpad.net/bugs/2076147 This is a duplicate of: LP#2076147 - "Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test" https://bugs.launchpad.net/bugs/2076147 Marking this LP bug as such ... ** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => (unassigned) ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** This bug has been marked a duplicate of bug 2076147 Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076569 Title: ISST-LTE:KOP:doodlp1g3:L2 guest hung and Call traces seen with Snapshot tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2076569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2074376] Re: Disable PCI_DYNAMIC_OF_NODES in Ubuntu
** Changed in: ubuntu-power-systems Importance: Undecided => Medium ** Changed in: ubuntu-power-systems Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2074376 Title: Disable PCI_DYNAMIC_OF_NODES in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2074376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075567] Re: zlib fails to build on s390x on oracular with gcc 14
The fix solves the problem - I tried with a patched gcc-14: https://launchpad.net/~fheimes/+archive/ubuntu/lp2073786/+sourcepub/16401085/+listing-archive-extra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075567 Title: zlib fails to build on s390x on oracular with gcc 14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2075567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
Meanwhile I created an upstream issue on top: https://github.com/ibm-s390-linux/s390-tools/issues/174 asking the maintainers for their opinion as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
Turns out that my gcc 14 rebuild in PPA didn't pulled in my patch, so started another build... (the handling of quilt patches is a bit different in gcc). ** Bug watch added: github.com/ibm-s390-linux/s390-tools/issues #174 https://github.com/ibm-s390-linux/s390-tools/issues/174 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
Update: a few hours ago the above two patches were accepted (upstream): https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git With that the commits can (and will) be picked up for oracular. So it's planned to have a new official gcc-14 build over the weekend (which would solve the zlib issue, and let's see for s390-tools issue). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077055] Re: s390-tools v2.34.0 FTBFS on oracular/s390x
I've now looked a bit closer at the code that is build when things break, and remembered the issues with builtins we have at LP#2075567 (caused by aligning the gcc builtins to the llvm ones). This is meanwhile fixed by IBM: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/2075567/comments/4 Since it's not upstream accepted yet, I'm picking two patches myself: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=e8a7142a697c5d2673adea33ba23af82a89c9559 https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=a247088adaf122116919235f4a40189506139495 and building a patched gcc: https://launchpad.net/~fheimes/+archive/ubuntu/lp2073786/+sourcepub/16399725/+listing-archive-extra (seems to be a bit tricky, since the d/patch handling is different and several rules files exist, but let's see) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077055 Title: s390-tools v2.34.0 FTBFS on oracular/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075567] Re: zlib fails to build on s390x on oracular with gcc 14
Thanks iii, just saw this a few minutes ago. Does it makes sense to also add: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=a247088adaf122116919235f4a40189506139495 (seems to be a bit related ...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2075567 Title: zlib fails to build on s390x on oracular with gcc 14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2075567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
