** Description changed: * introduction Found a regression on 5.15.0-1053, which worked OK on 5.15.0-1050 At DPU, when using the 5.15.0-1053-bluefield kernel, when the user-space process uses the OFED driver to create 2000 of SF devices in a batch mode. At host side, the ubuntu kernel will prevent the user-space process from being scheduled for a long time, causing the user-space process to be stuck for a period of time. * log at host side + After ~ 1300 VFs was opened successfully, this Call Trace appearing on host side (the 2K VFs opened successfully at the end, but this trace is appearing some times): - INFO: task fwupd:7067 blocked for more than 368 seconds. - Tainted: G OE 6.8.0-45-generic #45-Ubuntu - "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. - task:fwupd state:D stack:0 pid:7067 tgid:7067 ppid:1 flags:0×00000006 - Call Trace: - __schedule+0x27c/0×6b0 - schedule+0x33/0×110 - schedule_preempt_disabled+0x15/0×30 - __mutex_lock.constprop.0+0x42f/0×740 - ? __memcg_slab_post_alloc_hook+0x18e/0×230 - __mutex_lock_slowpath+0x13/0×20 - mutex_lock+0x3c/0×50 - uevent_show+0xc4/0×170 - dev_attr_show+0x1a/0×70 - sysfs_kf_seq_show+0xa4/0×120 - kernfs_seq_show+0x24/0×40 - seq_read_iter+0x12f/0×4b0 - kernfs_fop_read_iter+0x34/0×40 - vfs_read+0x255/0×390 - ksys_read+0x73/0×100 - __x64_sys_read+0x19/0×30 - x64_sys_call+0x1ada/0×25c0 - do_syscall_64+0x7f/0×180 - ? handle_pte_fault+0x1cb/0×1d0 - ? __handle_mm_fault+0x653/0×790 - ? __count_memcg_events+0x6b/0×120 - ? count_memcg_events.constprop.0+0x2a/0×50 - ? handle_mm_fault+0xad/0×380 - ? do_user_addr_fault+0x32c/0×670 - ? irqentry_exit_to_user_mode+0x7e/0×260 - ? irqentry_exit+0x43/0×50 - ? clear_bhb_loop+0x15/0×70 - ? clear_bhb_loop+0x15/0×70 - ? clear_bhb_loop+0x15/0×70 - entry_SYSCALL_64_after_hwframe+0x78/0×80 - RIP: 0033:0×78c3f511ba9a - RSP: 002b:00007ffd44147480 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 - RAX: ffffffffffffffda RBX: 00005cb70c378cc0 RCX: 000078c3f511ba9a - RDX: 0000000000001008 RSI: 00005cb70c378cc0 RDI: 000000000000000e - RBP: 00007ffd441474a0 R08: 0000000000000000 R09: 0000000000000000 - R10: 0000000000000001 R11: 0000000000000246 R12: 000000000000000e - R13: 0000000000001008 R14: 0000000000001008 R15: 0000000000001007 + [ 1669.234267] virtio_net virtio1297 ens1f2v1296: renamed from eth0 + [ 1671.113300] pci 0000:0e:02.7: [1af4:1041] type 00 class 0x020000 + [ 1671.113531] pci 0000:0e:02.7: enabling Extended Tags + [ 1671.116667] pci 0000:0e:02.7: Adding to iommu group 1563 + [ 1671.117439] virtio-pci 0000:0e:02.7: enabling device (0000 -> 0002) + [ 1671.853981] pci 0000:0e:03.0: [1af4:1041] type 00 class 0x020000 + [ 1671.854089] pci 0000:0e:03.0: enabling Extended Tags + [ 1671.856793] pci 0000:0e:03.0: Adding to iommu group 1564 + [ 1671.857701] virtio-pci 0000:0e:03.0: enabling device (0000 -> 0002) + [ 1672.877615] pci 0000:0e:03.1: [1af4:1041] type 00 class 0x020000 + [ 1672.877723] pci 0000:0e:03.1: enabling Extended Tags + [ 1672.881917] pci 0000:0e:03.1: Adding to iommu group 1565 + [ 1672.886178] virtio-pci 0000:0e:03.1: enabling device (0000 -> 0002) + [ 1700.318640] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [kworker/0:1:18] + [ 1700.318658] Modules linked in: bridge stp llc tun vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio cuse qrtr binfmt_misc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common i10nm_edac nfit libnvdimm ipmi_ssif x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ghash_clmulni_intel sha512_ssse3 sha512_generic sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd mgag200 ledtrig_audio rapl rfkill mei_me drm_shmem_helper intel_cstate iTCO_wdt video intel_pmc_bxt evdev drm_kms_helper acpi_ipmi iTCO_vendor_support mei watchdog i2c_algo_bit dell_smbios ipmi_si intel_uncore sg dcdbas intel_pch_thermal ipmi_devintf dell_wmi_descriptor intel_vsec isst_if_mmio isst_if_mbox_pci isst_if_common wmi_bmof pcspkr ipmi_msghandler acpi_power_meter button nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_mod knem(OE) fuse drm configfs efi_pstore loop ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic mlx5_ib ib_uverbs ib_core sd_mod + [ 1700.318715] t10_pi crc64_rocksoft crc64 crc_t10dif crct10dif_generic ahci libahci xhci_pci mlx5_core libata xhci_hcd virtio_net megaraid_sas net_failover tg3 failover virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel usbcore scsi_mod libphy mlxfw virtio i2c_i801 psample virtio_ring pci_hyperv_intf i2c_smbus usb_common wmi scsi_common + [ 1700.318736] CPU: 0 PID: 18 Comm: kworker/0:1 Tainted: G OE 6.1.0-18-amd64 #1 Debian 6.1.76-1 + [ 1700.318739] Hardware name: Dell Inc. PowerEdge R750/0PJ80M, BIOS 1.11.2 08/10/2023 + [ 1700.318741] Workqueue: events work_for_cpu_fn + [ 1700.318746] RIP: 0010:virtqueue_get_buf_ctx_split+0x1c/0xd0 [virtio_ring] + [ 1700.318755] Code: cc 0f 0b 0f 0b 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 53 80 7f 4b 00 0f 85 a1 00 00 00 48 8b 47 78 48 89 fb 0f b7 40 02 <66> 39 47 58 0f 84 8a 00 00 00 0f b7 43 60 48 8b 7f 78 83 e8 01 66 + [ 1700.318757] RSP: 0018:ff54fb62803d7af0 EFLAGS: 00000246 + [ 1700.318759] RAX: 0000000000000000 RBX: ff4f99cde4b42500 RCX: 0000000000000001 + [ 1700.318760] RDX: 0000000000000000 RSI: ff54fb62803d7b0c RDI: ff4f99cde4b42500 + [ 1700.318761] RBP: ff54fb62803d7b30 R08: 0000000000000001 R09: ff4f99ce260ae980 + [ 1700.318763] R10: 0000000000000003 R11: 0000000000000009 R12: 0000000000000002 + [ 1700.318764] R13: 0000000000000004 R14: 0000000000000000 R15: ff4f99ce2609a000 + [ 1700.318765] FS: 0000000000000000(0000) GS:ff4f99eaff600000(0000) knlGS:0000000000000000 + [ 1700.318766] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 + [ 1700.318767] CR2: 00007f6e4b099b38 CR3: 00000002ae55a006 CR4: 0000000000773ef0 + [ 1700.318768] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 + [ 1700.318769] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 + [ 1700.318770] PKRU: 55555554 + [ 1700.318771] Call Trace: + [ 1700.318773] <IRQ> + [ 1700.318775] ? watchdog_timer_fn+0x1a4/0x200 + [ 1700.318778] ? lockup_detector_update_enable+0x50/0x50 + [ 1700.318780] ? __hrtimer_run_queues+0x10f/0x2b0 + [ 1700.318784] ? hrtimer_interrupt+0xf4/0x210 + [ 1700.318786] ? __sysvec_apic_timer_interrupt+0x5a/0x110 + [ 1700.318790] ? sysvec_apic_timer_interrupt+0x69/0x90 + [ 1700.318794] </IRQ> + [ 1700.318795] <TASK> + [ 1700.318795] ? asm_sysvec_apic_timer_interrupt+0x16/0x20 + [ 1700.318799] ? virtqueue_get_buf_ctx_split+0x1c/0xd0 [virtio_ring] + [ 1700.318805] virtnet_send_command+0x18e/0x1e0 [virtio_net] + [ 1700.318811] _virtnet_set_queues+0xc6/0x110 [virtio_net] + [ 1700.318816] virtnet_probe+0x96c/0xce0 [virtio_net] + [ 1700.318822] ? pci_find_next_ext_capability+0x82/0xe0 + [ 1700.318826] virtio_dev_probe+0x1ac/0x25f [virtio] + [ 1700.318831] really_probe+0xdb/0x380 + [ 1700.318834] ? pm_runtime_barrier+0x50/0x90 + [ 1700.318837] __driver_probe_device+0x78/0x120 + [ 1700.318841] driver_probe_device+0x1f/0x90 + [ 1700.318843] __device_attach_driver+0x85/0x110 + [ 1700.318846] ? driver_allows_async_probing+0x70/0x70 + [ 1700.318848] bus_for_each_drv+0x88/0xd0 + [ 1700.318851] __device_attach+0xb2/0x1e0 + [ 1700.318854] bus_probe_device+0x8e/0xb0 + [ 1700.318856] device_add+0x40f/0x8b0 + [ 1700.318859] ? vp_get_features+0x20/0x20 [virtio_pci] + [ 1700.318864] register_virtio_device+0xce/0x120 [virtio] + [ 1700.318869] virtio_pci_probe+0xc0/0x150 [virtio_pci] + [ 1700.318874] local_pci_probe+0x3e/0x80 + [ 1700.318878] work_for_cpu_fn+0x13/0x20 + [ 1700.318881] process_one_work+0x1c4/0x380 + [ 1700.318884] worker_thread+0x1ab/0x380 + [ 1700.318887] ? rescuer_thread+0x3a0/0x3a0 + [ 1700.318890] kthread+0xd7/0x100 + [ 1700.318893] ? kthread_complete_and_exit+0x20/0x20 + [ 1700.318895] ret_from_fork+0x1f/0x30 + [ 1700.318899] </TASK> + [ 1718.220097] pci 0000:0e:03.2: [1af4:1041] type 00 class 0x020000 + [ 1718.220339] pci 0000:0e:03.2: enabling Extended Tags + [ 1718.231222] pci 0000:0e:03.2: Adding to iommu group 1566 + [ 1718.233040] virtio-pci 0000:0e:03.2: enabling device (0000 -> 0002) + [ 1744.318072] watchdog: BUG: soft lockup - CPU#0 stuck for 24s! [kworker/0:1:18] + * possible solution check between the two tags (1053 and 1050), doesn't find anything interesting. checking the changelog, I guess the introduction of 1052 causes the regression. linux-bluefield (5.15.0-1052.54) jammy; urgency=medium - * jammy/linux-bluefield: 5.15.0-1052.54 -proposed tracker (LP: + * jammy/linux-bluefield: 5.15.0-1052.54 -proposed tracker (LP: #2075859) - * Jammy update: v5.15.163 upstream stable release (LP: #2075170) - - SAUCE: wireguard: allowedips: include <asm/unaligned.h> to fix build error + * Jammy update: v5.15.163 upstream stable release (LP: #2075170) + - SAUCE: wireguard: allowedips: include <asm/unaligned.h> to fix build error - [ Ubuntu: 5.15.0-121.131 ] + [ Ubuntu: 5.15.0-121.131 ] - * jammy/linux: 5.15.0-121.131 -proposed tracker (LP: #2076347) - * jammy:linux bpf selftest do not build (LP: #2076334) - - SAUCE: Revert "bpf: Allow reads from uninit stack" + * jammy/linux: 5.15.0-121.131 -proposed tracker (LP: #2076347) + * jammy:linux bpf selftest do not build (LP: #2076334) + - SAUCE: Revert "bpf: Allow reads from uninit stack" - [ Ubuntu: 5.15.0-120.130 ] + [ Ubuntu: 5.15.0-120.130 ] - * jammy/linux: 5.15.0-120.130 -proposed tracker (LP: #2075903) - * Packaging resync (LP: #1786013) - - [Packaging] debian.master/dkms-versions -- update from kernel-versions - (main/2024.08.05) - * Jammy update: v5.15.163 upstream stable release (LP: #2075170) - - Compiler Attributes: Add __uninitialized macro - - locking/mutex: Introduce devm_mutex_init() - - drm/lima: fix shared irq handling on driver remove - - media: dvb: as102-fe: Fix as10x_register_addr packing - - media: dvb-usb: dib0700_devices: Add missing release_firmware() - - IB/core: Implement a limit on UMAD receive List - - scsi: qedf: Make qedf_execute_tmf() non-preemptible - - crypto: aead,cipher - zeroize key buffer after use - - drm/amdgpu: Initialize timestamp for some legacy SOCs - - drm/amd/display: Check index msg_id before read or write - - drm/amd/display: Check pipe offset before setting vblank - - drm/amd/display: Skip finding free audio for unknown engine_id - - media: dw2102: Don't translate i2c read into write + * jammy/linux: 5.15.0-120.130 -proposed tracker (LP: #2075903) + * Packaging resync (LP: #1786013) + - [Packaging] debian.master/dkms-versions -- update from kernel-versions + (main/2024.08.05) + * Jammy update: v5.15.163 upstream stable release (LP: #2075170) + - Compiler Attributes: Add __uninitialized macro + - locking/mutex: Introduce devm_mutex_init() + - drm/lima: fix shared irq handling on driver remove + - media: dvb: as102-fe: Fix as10x_register_addr packing + - media: dvb-usb: dib0700_devices: Add missing release_firmware() + - IB/core: Implement a limit on UMAD receive List + - scsi: qedf: Make qedf_execute_tmf() non-preemptible + - crypto: aead,cipher - zeroize key buffer after use + - drm/amdgpu: Initialize timestamp for some legacy SOCs + - drm/amd/display: Check index msg_id before read or write + - drm/amd/display: Check pipe offset before setting vblank + - drm/amd/display: Skip finding free audio for unknown engine_id + - media: dw2102: Don't translate i2c read into write ... about 800 commits. one way is to try bisect between them.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2084479 Title: Create 2K VNET VFs cause call trace on host side Status in linux-bluefield package in Ubuntu: New Bug description: * introduction Found a regression on 5.15.0-1053, which worked OK on 5.15.0-1050 At DPU, when using the 5.15.0-1053-bluefield kernel, when the user-space process uses the OFED driver to create 2000 of SF devices in a batch mode. At host side, the ubuntu kernel will prevent the user-space process from being scheduled for a long time, causing the user-space process to be stuck for a period of time. * log at host side After ~ 1300 VFs was opened successfully, this Call Trace appearing on host side (the 2K VFs opened successfully at the end, but this trace is appearing some times): [ 1669.234267] virtio_net virtio1297 ens1f2v1296: renamed from eth0 [ 1671.113300] pci 0000:0e:02.7: [1af4:1041] type 00 class 0x020000 [ 1671.113531] pci 0000:0e:02.7: enabling Extended Tags [ 1671.116667] pci 0000:0e:02.7: Adding to iommu group 1563 [ 1671.117439] virtio-pci 0000:0e:02.7: enabling device (0000 -> 0002) [ 1671.853981] pci 0000:0e:03.0: [1af4:1041] type 00 class 0x020000 [ 1671.854089] pci 0000:0e:03.0: enabling Extended Tags [ 1671.856793] pci 0000:0e:03.0: Adding to iommu group 1564 [ 1671.857701] virtio-pci 0000:0e:03.0: enabling device (0000 -> 0002) [ 1672.877615] pci 0000:0e:03.1: [1af4:1041] type 00 class 0x020000 [ 1672.877723] pci 0000:0e:03.1: enabling Extended Tags [ 1672.881917] pci 0000:0e:03.1: Adding to iommu group 1565 [ 1672.886178] virtio-pci 0000:0e:03.1: enabling device (0000 -> 0002) [ 1700.318640] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [kworker/0:1:18] [ 1700.318658] Modules linked in: bridge stp llc tun vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio cuse qrtr binfmt_misc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common i10nm_edac nfit libnvdimm ipmi_ssif x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ghash_clmulni_intel sha512_ssse3 sha512_generic sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd mgag200 ledtrig_audio rapl rfkill mei_me drm_shmem_helper intel_cstate iTCO_wdt video intel_pmc_bxt evdev drm_kms_helper acpi_ipmi iTCO_vendor_support mei watchdog i2c_algo_bit dell_smbios ipmi_si intel_uncore sg dcdbas intel_pch_thermal ipmi_devintf dell_wmi_descriptor intel_vsec isst_if_mmio isst_if_mbox_pci isst_if_common wmi_bmof pcspkr ipmi_msghandler acpi_power_meter button nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_mod knem(OE) fuse drm configfs efi_pstore loop ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic mlx5_ib ib_uverbs ib_core sd_mod [ 1700.318715] t10_pi crc64_rocksoft crc64 crc_t10dif crct10dif_generic ahci libahci xhci_pci mlx5_core libata xhci_hcd virtio_net megaraid_sas net_failover tg3 failover virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel usbcore scsi_mod libphy mlxfw virtio i2c_i801 psample virtio_ring pci_hyperv_intf i2c_smbus usb_common wmi scsi_common [ 1700.318736] CPU: 0 PID: 18 Comm: kworker/0:1 Tainted: G OE 6.1.0-18-amd64 #1 Debian 6.1.76-1 [ 1700.318739] Hardware name: Dell Inc. PowerEdge R750/0PJ80M, BIOS 1.11.2 08/10/2023 [ 1700.318741] Workqueue: events work_for_cpu_fn [ 1700.318746] RIP: 0010:virtqueue_get_buf_ctx_split+0x1c/0xd0 [virtio_ring] [ 1700.318755] Code: cc 0f 0b 0f 0b 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 53 80 7f 4b 00 0f 85 a1 00 00 00 48 8b 47 78 48 89 fb 0f b7 40 02 <66> 39 47 58 0f 84 8a 00 00 00 0f b7 43 60 48 8b 7f 78 83 e8 01 66 [ 1700.318757] RSP: 0018:ff54fb62803d7af0 EFLAGS: 00000246 [ 1700.318759] RAX: 0000000000000000 RBX: ff4f99cde4b42500 RCX: 0000000000000001 [ 1700.318760] RDX: 0000000000000000 RSI: ff54fb62803d7b0c RDI: ff4f99cde4b42500 [ 1700.318761] RBP: ff54fb62803d7b30 R08: 0000000000000001 R09: ff4f99ce260ae980 [ 1700.318763] R10: 0000000000000003 R11: 0000000000000009 R12: 0000000000000002 [ 1700.318764] R13: 0000000000000004 R14: 0000000000000000 R15: ff4f99ce2609a000 [ 1700.318765] FS: 0000000000000000(0000) GS:ff4f99eaff600000(0000) knlGS:0000000000000000 [ 1700.318766] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1700.318767] CR2: 00007f6e4b099b38 CR3: 00000002ae55a006 CR4: 0000000000773ef0 [ 1700.318768] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1700.318769] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1700.318770] PKRU: 55555554 [ 1700.318771] Call Trace: [ 1700.318773] <IRQ> [ 1700.318775] ? watchdog_timer_fn+0x1a4/0x200 [ 1700.318778] ? lockup_detector_update_enable+0x50/0x50 [ 1700.318780] ? __hrtimer_run_queues+0x10f/0x2b0 [ 1700.318784] ? hrtimer_interrupt+0xf4/0x210 [ 1700.318786] ? __sysvec_apic_timer_interrupt+0x5a/0x110 [ 1700.318790] ? sysvec_apic_timer_interrupt+0x69/0x90 [ 1700.318794] </IRQ> [ 1700.318795] <TASK> [ 1700.318795] ? asm_sysvec_apic_timer_interrupt+0x16/0x20 [ 1700.318799] ? virtqueue_get_buf_ctx_split+0x1c/0xd0 [virtio_ring] [ 1700.318805] virtnet_send_command+0x18e/0x1e0 [virtio_net] [ 1700.318811] _virtnet_set_queues+0xc6/0x110 [virtio_net] [ 1700.318816] virtnet_probe+0x96c/0xce0 [virtio_net] [ 1700.318822] ? pci_find_next_ext_capability+0x82/0xe0 [ 1700.318826] virtio_dev_probe+0x1ac/0x25f [virtio] [ 1700.318831] really_probe+0xdb/0x380 [ 1700.318834] ? pm_runtime_barrier+0x50/0x90 [ 1700.318837] __driver_probe_device+0x78/0x120 [ 1700.318841] driver_probe_device+0x1f/0x90 [ 1700.318843] __device_attach_driver+0x85/0x110 [ 1700.318846] ? driver_allows_async_probing+0x70/0x70 [ 1700.318848] bus_for_each_drv+0x88/0xd0 [ 1700.318851] __device_attach+0xb2/0x1e0 [ 1700.318854] bus_probe_device+0x8e/0xb0 [ 1700.318856] device_add+0x40f/0x8b0 [ 1700.318859] ? vp_get_features+0x20/0x20 [virtio_pci] [ 1700.318864] register_virtio_device+0xce/0x120 [virtio] [ 1700.318869] virtio_pci_probe+0xc0/0x150 [virtio_pci] [ 1700.318874] local_pci_probe+0x3e/0x80 [ 1700.318878] work_for_cpu_fn+0x13/0x20 [ 1700.318881] process_one_work+0x1c4/0x380 [ 1700.318884] worker_thread+0x1ab/0x380 [ 1700.318887] ? rescuer_thread+0x3a0/0x3a0 [ 1700.318890] kthread+0xd7/0x100 [ 1700.318893] ? kthread_complete_and_exit+0x20/0x20 [ 1700.318895] ret_from_fork+0x1f/0x30 [ 1700.318899] </TASK> [ 1718.220097] pci 0000:0e:03.2: [1af4:1041] type 00 class 0x020000 [ 1718.220339] pci 0000:0e:03.2: enabling Extended Tags [ 1718.231222] pci 0000:0e:03.2: Adding to iommu group 1566 [ 1718.233040] virtio-pci 0000:0e:03.2: enabling device (0000 -> 0002) [ 1744.318072] watchdog: BUG: soft lockup - CPU#0 stuck for 24s! [kworker/0:1:18] * possible solution check between the two tags (1053 and 1050), doesn't find anything interesting. checking the changelog, I guess the introduction of 1052 causes the regression. linux-bluefield (5.15.0-1052.54) jammy; urgency=medium * jammy/linux-bluefield: 5.15.0-1052.54 -proposed tracker (LP: #2075859) * Jammy update: v5.15.163 upstream stable release (LP: #2075170) - SAUCE: wireguard: allowedips: include <asm/unaligned.h> to fix build error [ Ubuntu: 5.15.0-121.131 ] * jammy/linux: 5.15.0-121.131 -proposed tracker (LP: #2076347) * jammy:linux bpf selftest do not build (LP: #2076334) - SAUCE: Revert "bpf: Allow reads from uninit stack" [ Ubuntu: 5.15.0-120.130 ] * jammy/linux: 5.15.0-120.130 -proposed tracker (LP: #2075903) * Packaging resync (LP: #1786013) - [Packaging] debian.master/dkms-versions -- update from kernel-versions (main/2024.08.05) * Jammy update: v5.15.163 upstream stable release (LP: #2075170) - Compiler Attributes: Add __uninitialized macro - locking/mutex: Introduce devm_mutex_init() - drm/lima: fix shared irq handling on driver remove - media: dvb: as102-fe: Fix as10x_register_addr packing - media: dvb-usb: dib0700_devices: Add missing release_firmware() - IB/core: Implement a limit on UMAD receive List - scsi: qedf: Make qedf_execute_tmf() non-preemptible - crypto: aead,cipher - zeroize key buffer after use - drm/amdgpu: Initialize timestamp for some legacy SOCs - drm/amd/display: Check index msg_id before read or write - drm/amd/display: Check pipe offset before setting vblank - drm/amd/display: Skip finding free audio for unknown engine_id - media: dw2102: Don't translate i2c read into write ... about 800 commits. one way is to try bisect between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2084479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
