By always inlining _compound_head(), clone() sees 3%+ performance increase

Bug #2089327 reported by Matthew Ruffell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Noble
Fix Released
Medium
Matthew Ruffell
Oracular
Fix Released
Medium
Matthew Ruffell

Bug Description

BugLink: https://bugs.launchpad.net/bugs/2089327

[Impact]

_compound_head() is called frequently during clone() heavy workloads with
CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP=y set, so much that it is worthwhile
always inlining it for a slight 3%+ performance improvement during clone().

Over the lifecycle of Noble, Oracular it could save significant amounts of
CPU time during clone(), and save a large amount of electricity. We should
always inline _compound_head() and take advantage of the performance boost.

[Fix]

This was fixed in 6.12-rc1 by:

commit ef5f379de302884b9b7ad9b62587a942a9f0bb55
Author: David Hildenbrand <email address hidden>
Date: Tue Aug 20 14:22:10 2024 +0200
Subject: mm: always inline _compound_head() with CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP=y
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ef5f379de302884b9b7ad9b62587a942a9f0bb55

This commit is intended to offset the performance loss caused by:

 c0bff412e67b ("mm: allow anon exclusive check over hugetlb tail pages")

which landed in 6.10-rc1, but the change is generic enough that Noble users
would benefit from the fix as well. They bring both Noble and Oracular +3%.

[Testcase]

clone() heavy workloads are best to show the performance increase.

Originally, the user who requested this is running an Ansible heavy workload,
and finds that clone() bottlenecks during large runs of Ansible against
thousands of containers and hosts.

They benchmarked 6.8.0-49-generic against a patched test kernel of the same
6.8.0-49-generic and found:

Before:
    08:24:23: Rename subiquity netplan config
    08:36:12: hostendpoint_monitoring: Create log directory (10990)
    = 11m49s

    08:37:59: Rename subiquity netplan config
    08:49:49: hostendpoint_monitoring: Create log directory (10991)
    = 11m50s

After:
    08:55:16: Rename subiquity netplan config
    09:06:28: hostendpoint_monitoring: Create log directory (10991)
    = 11m12s

    09:08:59: Rename subiquity netplan config
    09:20:22: hostendpoint_monitoring: Create log directory (10991)
    = 11m23s

Take 11m23s versus 11m49s, for a 3.6%+ performance improvement. This adds up
over thousands of hosts.

I did some basic tests with stress-ng using the clone() stressor.

I ran:

$ sudo apt install stress-ng
$ sudo stress-ng --seq=5 --clone 5 --timeout=60 --metrics

Before:
ubuntu@jammy-test:~$ sudo stress-ng --seq=5 --clone 5 --timeout=60 --metrics
stress-ng: info: [953] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s CPU used per
stress-ng: info: [953] (secs) (secs) (secs) (real time) (usr+sys time) instance (%)
stress-ng: info: [953] clone 19919 61.80 2.19 232.84 322.29 84.75 76.06
stress-ng: info: [55777] clone 19540 61.17 1.75 229.32 319.42 84.56 75.55
stress-ng: info: [107873] clone 19817 62.39 1.92 235.90 317.64 83.33 76.24
stress-ng: info: [177572] clone 19763 60.57 0.89 226.55 326.27 86.89 75.10

After:
ubuntu@jammy-test:~$ sudo stress-ng --seq=5 --clone 5 --timeout=60 --metrics
stress-ng: info: [914] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s CPU used per
stress-ng: info: [914] (secs) (secs) (secs) (real time) (usr+sys time) instance (%)
stress-ng: info: [914] clone 19446 60.67 1.83 229.60 320.50 84.03 76.29
stress-ng: info: [67984] clone 19600 60.63 0.90 226.66 323.26 86.13 75.06
stress-ng: info: [117843] clone 19665 60.64 0.98 226.97 324.27 86.27 75.18
stress-ng: info: [167831] clone 19306 61.22 1.20 227.39 315.38 84.46 74.68

These numbers are a bit more fuzzy, but its about 3% extra bogo ops.

There is a test kernel available in the below ppa:

https://launchpad.net/~mruffell/+archive/ubuntu/sf401086-test

If you install it, you too will get 3%+ performance improvement on clone() heavy
workloads.

[Where problems could occur]

We are inlining a hotly used function in the clone() syscall callpath. This
should technically increase the performance due to not having to context switch
between calls to _compound_head(), without much of a downside, apart from
slightly increased binary size, and the inability to livepatch the function.

I checked on cscope, and _compound_head is called from:

compound_head()
page_folio()

both in page-flags.h as #defines. This is going to have a minuscule footprint
change.

The risk of regression is well worth the 3%+ performance gain.

CVE References

Changed in linux (Ubuntu):
status: New → Fix Released
Changed in linux (Ubuntu Noble):
status: New → In Progress
Changed in linux (Ubuntu Oracular):
status: New → In Progress
Changed in linux (Ubuntu Noble):
importance: Undecided → Medium
Changed in linux (Ubuntu Oracular):
importance: Undecided → Medium
Changed in linux (Ubuntu Noble):
assignee: nobody → Matthew Ruffell (mruffell)
Changed in linux (Ubuntu Oracular):
assignee: nobody → Matthew Ruffell (mruffell)
tags: added: sts
description: updated
Revision history for this message
Matthew Ruffell (mruffell) wrote :
Changed in linux (Ubuntu Noble):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Oracular):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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

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

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

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

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

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

tags: added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux
Revision history for this message
Matthew Ruffell (mruffell) wrote :

Performing verification for noble.

I deployed a lab system:

24.04 LTS
Sapphire Rapids
Intel(R) Xeon(R) Platinum 8468

with 6.8.0-52-generic from -updates.

Running stress-ng:

$ sudo stress-ng --seq=100 --clone 100 --timeout=60 --metrics

stress-ng: info: [180365] setting to a 1 min, 0 secs run per stressor
stress-ng: info: [180365] dispatching hogs: 100 clone
stress-ng: metrc: [180365] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s CPU used per RSS Max
stress-ng: metrc: [180365] (secs) (secs) (secs) (real time) (usr+sys time) instance (%) (KB)
stress-ng: metrc: [180365] clone 119032 60.25 9.76 6548.93 1975.76 18.15 108.86 160468
stress-ng: metrc: [425951] clone 118137 60.26 9.39 6638.21 1960.35 17.77 110.31 158680
stress-ng: metrc: [653004] clone 118219 60.25 9.50 6563.46 1962.11 17.99 109.09 160768
stress-ng: metrc: [893057] clone 117937 60.27 9.60 6634.14 1956.95 17.75 110.24 159764

I then enabled -proposed and install 6.8.0-53-generic and rebooted.

stress-ng: info: [164395] setting to a 1 min, 0 secs run per stressor
stress-ng: info: [164395] dispatching hogs: 100 clone
stress-ng: metrc: [164395] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s CPU used per RSS Max
stress-ng: metrc: [164395] (secs) (secs) (secs) (real time) (usr+sys time) instance (%) (KB)
stress-ng: metrc: [164395] clone 120568 60.15 9.35 6541.61 2004.34 18.40 108.90 155180
stress-ng: metrc: [352781] clone 120290 60.16 8.02 6515.23 1999.39 18.44 108.43 159156
stress-ng: metrc: [658902] clone 120097 60.17 7.34 6475.08 1996.07 18.53 107.74 158680
stress-ng: metrc: [960574] clone 120291 60.17 8.18 6562.26 1999.08 18.31 109.19 157928

As you can see, there is a very small +3.6%ish performance gain on bogo ops.

The inlining is working as intended. Happy to mark verified for noble.

tags: added: verification-done-noble-linux
removed: verification-needed-noble-linux
Revision history for this message
Matthew Ruffell (mruffell) wrote :

Performing verification for oracular.

I deployed a lab system:

oracular
Sapphire Rapids
Intel(R) Xeon(R) Platinum 8468

with 6.11.0-14-generic from -updates.

Running stress-ng:

$ sudo stress-ng --seq=100 --clone 100 --timeout=60 --metrics

stress-ng: info: [143114] setting to a 1 min, 0 secs run per stressor
stress-ng: info: [143114] dispatching hogs: 100 clone
stress-ng: metrc: [143114] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s CPU used per RSS Max
stress-ng: metrc: [143114] (secs) (secs) (secs) (real time) (usr+sys time) instance (%) (KB)
stress-ng: metrc: [143114] clone 119939 60.11 8.21 6512.88 1995.43 18.39 108.49 155476
stress-ng: metrc: [379548] clone 119720 60.15 7.59 6558.45 1990.49 18.23 109.17 157648
stress-ng: metrc: [687474] clone 119502 60.14 7.29 6565.02 1986.98 18.18 109.28 158100
stress-ng: metrc: [990655] clone 119355 60.15 7.16 6566.15 1984.24 18.16 109.28 157164

I then enabled -proposed and installed 6.11.0-17-generic and rebooted.

stress-ng: info: [127695] setting to a 1 min, 0 secs run per stressor
stress-ng: info: [127695] dispatching hogs: 100 clone
stress-ng: metrc: [127695] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s CPU used per RSS Max
stress-ng: metrc: [127695] (secs) (secs) (secs) (real time) (usr+sys time) instance (%) (KB)
stress-ng: metrc: [127695] clone 120142 60.12 8.64 6525.11 1998.47 18.39 108.68 155340
stress-ng: metrc: [288779] clone 119832 60.13 7.76 6564.59 1992.88 18.23 109.30 157108
stress-ng: metrc: [381377] clone 119782 60.14 8.29 6556.41 1991.70 18.25 109.16 156376
stress-ng: metrc: [447458] clone 119489 60.16 7.66 6553.12 1986.35 18.21 109.06 157224

As you can see, there is a very small performance gain on bogo ops.

The inlining is working as intended. Happy to mark verified for oracular.

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

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

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

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

tags: added: kernel-spammed-oracular-linux-intel-v2 verification-needed-oracular-linux-intel
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (73.0 KiB)

This bug was fixed in the package linux - 6.8.0-53.55

---------------
linux (6.8.0-53.55) noble; urgency=medium

  * noble/linux: 6.8.0-53.55 -proposed tracker (LP: #2093677)

  * Packaging resync (LP: #1786013)
    - [Packaging] debian.master/dkms-versions -- update from kernel-versions
      (main/2025.01.13)

  * generate and ship vmlinux.h to allow packages to build BPF CO-RE
    (LP: #2050083)
    - [Packaging] add linux-bpf-dev package
    - [Packaging] do not attempt to generate BTF header on armhf

  * Unable to boot as a guest on VMware ESX (LP: #2091941)
    - ptp/vmware: Use VMware hypercall API
    - input/vmmouse: Use VMware hypercall API
    - drm/vmwgfx: Use VMware hypercall API
    - x86/vmware: Use VMware hypercall API
    - x86/vmware: Correct macro names
    - x86/vmware: Remove legacy VMWARE_HYPERCALL* macros

  * When /dev/vmbus/hv_kvp is not present, disable hv-kvp-daemon (LP: #2091744)
    - [Packaging] disable hv-kvp-daemon if needed

  * Backport "netkit: Add option for scrubbing skb meta data" to 6.8
    (LP: #2091184)
    - netkit: Add option for scrubbing skb meta data

  * KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter and VM-
    Exit (LP: #2093146)
    - KVM: x86: Cache CPUID.0xD XSTATE offsets+sizes during module init

  * [SRU] add support of QCA BT 0489:e0fc (LP: #2085406)
    - Bluetooth: btusb: add Foxconn 0xe0fc for Qualcomm WCN785x

  * ice driver RTNL assertion failed warning on shutdown/reboot (LP: #2091107)
    - ice: Remove and readd netdev during devlink reload

  * vfio_pci soft lockup on VM start while using PCIe passthrough (LP: #2089306)
    - SAUCE: Revert "vfio/pci: Insert full vma on mmap'd MMIO fault"
    - SAUCE: Revert "vfio/pci: Use unmap_mapping_range()"

  * [SRU] Fix error of resume on rtl8168fp (LP: #2087507)
    - r8169: avoid unsolicited interrupts

  * [SRU] power: intel_pstate: HWP interrupt support for maximum ratio changed
    (LP: #2090852)
    - x86/cpufeatures: Add HWP highest perf change feature flag
    - cpufreq: intel_pstate: Support highest performance change interrupt

  * Noble update: upstream stable patchset 2024-11-29 (LP: #2089884)
    - static_call: Handle module init failure correctly in
      static_call_del_module()
    - static_call: Replace pointless WARN_ON() in static_call_module_notify()
    - jump_label: Simplify and clarify static_key_fast_inc_cpus_locked()
    - jump_label: Fix static_key_slow_dec() yet again
    - scsi: st: Fix input/output error on empty drive reset
    - scsi: pm8001: Do not overwrite PCI queue mapping
    - drm/amdgpu: Fix get each xcp macro
    - mailbox: rockchip: fix a typo in module autoloading
    - mailbox: bcm2835: Fix timeout during suspend mode
    - ceph: remove the incorrect Fw reference check when dirtying pages
    - ieee802154: Fix build error
    - net: sparx5: Fix invalid timestamps
    - net/mlx5: Fix error path in multi-packet WQE transmit
    - net/mlx5: Added cond_resched() to crdump collection
    - net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc()
    - net/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice
    - netfilter: uapi: NFTA_FLOWTABLE_HOOK is NLA_NESTED
    - net...

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

This bug was fixed in the package linux - 6.11.0-18.18

---------------
linux (6.11.0-18.18) oracular; urgency=medium

  * CVE-2025-0927
    - SAUCE: fs: hfs/hfsplus: add key_len boundary check to hfs_bnode_read_key

linux (6.11.0-17.17) oracular; urgency=medium

  * oracular/linux: 6.11.0-17.17 -proposed tracker (LP: #2093643)

  * Packaging resync (LP: #1786013)
    - [Packaging] debian.master/dkms-versions -- update from kernel-versions
      (main/2025.01.13)

  * When /dev/vmbus/hv_kvp is not present, disable hv-kvp-daemon (LP: #2091744)
    - [Packaging] disable hv-kvp-daemon if needed

  * Backport "netkit: Add option for scrubbing skb meta data" to 6.8
    (LP: #2091184)
    - netkit: Add option for scrubbing skb meta data

  * KVM: Cache CPUID at KVM.ko module init to reduce latency of VM-Enter and VM-
    Exit (LP: #2093146)
    - KVM: x86: Cache CPUID.0xD XSTATE offsets+sizes during module init

  * [SRU] add support of QCA BT 0489:e0fc (LP: #2085406)
    - Bluetooth: btusb: add Foxconn 0xe0fc for Qualcomm WCN785x

  * oracular: ubuntu_boot lib/dynamic_queue_limits.c:99! (LP: #2089684)
    - virtio_net: correct netdev_tx_reset_queue() invocation point
    - virtio_ring: add a func argument 'recycle_done' to virtqueue_resize()
    - virtio_net: ensure netdev_tx_reset_queue is called on tx ring resize

  * Failed to probe for OVTI02C1: chip id mismatch: 560243!=0 (LP: #2090932)
    - SAUCE: ACPI: scan: Update HID for new platform

  * Bluetooth[8086:a876] crash with "hci0: Failed to read MSFT supported
    features (-110)" (LP: #2085485)
    - Bluetooth: btintel_pcie: Add recovery mechanism

  * Poor bluetooth performance on Lenovo X13s (LP: #2089357)
    - SAUCE: Bluetooth: qca: Support downloading board ID specific NVM for WCN6855

  * vfio_pci soft lockup on VM start while using PCIe passthrough (LP: #2089306)
    - SAUCE: Revert "mm: use rwsem assertion macros for mmap_lock"
    - SAUCE: Revert "vfio/pci: Insert full vma on mmap'd MMIO fault"
    - SAUCE: Revert "vfio/pci: Use unmap_mapping_range()"

  * Oracular update: v6.11.11 upstream stable release (LP: #2091655)
    - wifi: mac80211: Fix setting txpower with emulate_chanctx
    - wifi: cfg80211: Add wiphy_delayed_work_pending()
    - wifi: mac80211: Convert color collision detection to wiphy work
    - wifi: radiotap: Avoid -Wflex-array-member-not-at-end warnings
    - spi: stm32: fix missing device mode capability in stm32mp25
    - ASoC: codecs: rt5640: Always disable IRQs from rt5640_cancel_work()
    - ASoC: Intel: bytcr_rt5640: Add support for non ACPI instantiated codec
    - ASoC: Intel: bytcr_rt5640: Add DMI quirk for Vexia Edu Atla 10 tablet
    - ASoC: Intel: sst: Support LPE0F28 ACPI HID
    - wifi: iwlwifi: mvm: Use the sync timepoint API in suspend
    - wifi: iwlwifi: mvm: SAR table alignment
    - mac80211: fix user-power when emulating chanctx
    - usb: add support for new USB device ID 0x17EF:0x3098 for the r8152 driver
    - usb: typec: use cleanup facility for 'altmodes_node'
    - selftests/watchdog-test: Fix system accidentally reset after watchdog-test
    - ALSA: hda/realtek: Add subwoofer quirk for Infinix ZERO BOOK 13
    - ASoC: codecs: wcd937x: ...

Changed in linux (Ubuntu Oracular):
status: Fix Committed → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Update Released

The verification of the Stable Release Update for linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra/6.8.0-1003.3 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-done-noble-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-failed-noble-linux-nvidia-tegra'.

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

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

tags: added: kernel-spammed-noble-linux-nvidia-tegra-v2 verification-needed-noble-linux-nvidia-tegra
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra-pvw/6.8.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia-tegra-pvw' to 'verification-done-noble-linux-nvidia-tegra-pvw'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-tegra-pvw' to 'verification-failed-noble-linux-nvidia-tegra-pvw'.

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

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

tags: added: kernel-spammed-noble-linux-nvidia-tegra-pvw-v2 verification-needed-noble-linux-nvidia-tegra-pvw
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-6.11/6.11.0-1011.11~24.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-gcp-6.11' to 'verification-done-noble-linux-gcp-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-gcp-6.11' to 'verification-failed-noble-linux-gcp-6.11'.

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

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

tags: added: kernel-spammed-noble-linux-gcp-6.11-v2 verification-needed-noble-linux-gcp-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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

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

tags: added: kernel-spammed-noble-linux-azure-v2 verification-needed-noble-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-6.11/6.11.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia-6.11' to 'verification-done-noble-linux-nvidia-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-6.11' to 'verification-failed-noble-linux-nvidia-6.11'.

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

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

tags: added: kernel-spammed-noble-linux-nvidia-6.11-v2 verification-needed-noble-linux-nvidia-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-6.11/6.11.0-1012.12~24.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-6.11' to 'verification-done-noble-linux-azure-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-6.11' to 'verification-failed-noble-linux-azure-6.11'.

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

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

tags: added: kernel-spammed-noble-linux-azure-6.11-v2 verification-needed-noble-linux-azure-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-nvidia/6.8.0-1014.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-done-noble-linux-azure-nvidia'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-nvidia' to 'verification-failed-noble-linux-azure-nvidia'.

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

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

tags: added: kernel-spammed-noble-linux-azure-nvidia-v2 verification-needed-noble-linux-azure-nvidia
Juerg Haefliger (juergh)
tags: added: kernel-daily-bug
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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

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

tags: added: kernel-spammed-noble-linux-aws-6.11-v2 verification-needed-noble-linux-aws-6.11
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-fips/6.8.0-72.72+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-linux-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-fips' to 'verification-failed-noble-linux-fips'.

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

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

tags: added: kernel-spammed-noble-linux-fips-v2 verification-needed-noble-linux-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-fips/6.8.0-1035.37+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-gcp-fips' to 'verification-done-noble-linux-gcp-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-gcp-fips' to 'verification-failed-noble-linux-gcp-fips'.

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

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

tags: added: kernel-spammed-noble-linux-gcp-fips-v2 verification-needed-noble-linux-gcp-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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

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

tags: added: kernel-spammed-noble-linux-aws-fips-v2 verification-needed-noble-linux-aws-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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

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

tags: added: kernel-spammed-noble-linux-xilinx-v2 verification-needed-noble-linux-xilinx
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-fips/6.8.0-1034.39+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-fips' to 'verification-done-noble-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-fips' to 'verification-failed-noble-linux-azure-fips'.

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

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

tags: added: kernel-spammed-noble-linux-azure-fips-v2 verification-needed-noble-linux-azure-fips
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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