Set verification-done due to positive test result from user. ** Tags removed: verification-needed-noble-linux-oem-6.17 ** Tags added: verification-done-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148538 Title: Kernel lockup on 6.17.0-1017-oem Lenovo P14s gen 6 AMD Ryzen AI 7 pro 350 Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: I have a Lenovo ThinkPad P14s Gen 6 AMD Ryzen AI 7 pro 350 I have installed - 24.04 LTS - 6.17.0-1017-oem - linux-image-6.17.0-1017-oem 6.17.0-1017.17 Regularly (at this point, seems to happen once per day), the kernel locks up (actually, let me amend that; I just noticed that the key combination I thought would go into terminal mode doesn't do that, so I don't know if the kernel has locked up or gnome has frozen). I haven't been able to identify particular workloads that are causing this behavior. At any given instance, I am running firefox, brave, mattermost, vs code, multiple terminal sessions, obsidian, perhaps some qemu vms (no GUI). Looking at the journal, after one recent lockup, I saw the following: amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. workqueue: amdgpu_tlb_fence_work [amdgpu] hogged CPU for >13333us 35 times, consider switching to WQ_UNBOUND amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. INFO: task kworker/7:0:37823 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/7:0 state:D stack:0 pid:37823 tgid:37823 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/15:0:39916 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/15:0 state:D stack:0 pid:39916 tgid:39916 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/12:4:40454 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/12:4 state:D stack:0 pid:40454 tgid:40454 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/5:4:40750 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/5:4 state:D stack:0 pid:40750 tgid:40750 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/15:3:40825 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/15:3 state:D stack:0 pid:40825 tgid:40825 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:8:40844 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:8 state:D stack:0 pid:40844 tgid:40844 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:9:40845 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:9 state:D stack:0 pid:40845 tgid:40845 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/4:2:41419 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/4:2 state:D stack:0 pid:41419 tgid:41419 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:0:41524 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:0 state:D stack:0 pid:41524 tgid:41524 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? _raw_spin_lock_irqsave+0xe/0x20 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/4:0:42116 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/4:0 state:D stack:0 pid:42116 tgid:42116 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. Supervising 9 threads of 6 processes of 1 users. Supervising 9 threads of 6 processes of 1 users. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. kauditd_printk_skb: 4 callbacks suppressed SRU Justification: [ Impact ] On Lenovo ThinkPad P14s Gen 6 systems with AMD Ryzen AI 7 PRO 350, the system can lock up under graphical workloads. Kernel logs show the AMDGPU MES ring buffer becoming full and hung task reports involving amdgpu_tlb_fence_work. The issue is caused by commit f3854e04b708 ("drm/amdgpu: attach tlb fence to the PTs update") which attaches TLB fences too broadly and can flood KIQ/MES TLB invalidation work. [ Fix ] Backport upstream fixes: - d967509651601 ("drm/amdgpu: make sure userqs are enabled in userq IOCTLs") - 9163fe4d790f (Revert "drm/amdgpu: don't attach the tlb fence for SI") - e9f58ff991dd ("drm/amdgpu: rework how we handle TLB fences") [ Test Plan ] 1. Boot the affected Lenovo P14s Gen 6 AMD Ryzen AI 7 PRO 350 system. 2. Exercise the graphical workload that previously reproduced the lockup. 3. Verify the system remains responsive and dmesg does not show MES ring buffer full or amdgpu_tlb_fence_work hung task messages. A test kernel with this fix series ran for 12 hours on the affected system without reproducing the lockup (LP #2148538 comment #29). [ Where problems could occur ] Regressions could appear as GPU hangs, failed VM updates, TLB flush failures, or user queue/KFD workload failures on AMD GPUs. [ Other Info ] Noble linux is not affected (offending commit absent). Resolute linux is not affected (fixes already present). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148538/+subscriptions
среда
[Bug 2156421] [NEW] bug on keyboard keys kernel 7
Public bug reported: i have bug on my legion 5 irx9, i use linux mint distibution, if i press prtsc keys, which is screenshot, it is not respond on system. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156421 Title: bug on keyboard keys kernel 7 Status in linux package in Ubuntu: New Bug description: i have bug on my legion 5 irx9, i use linux mint distibution, if i press prtsc keys, which is screenshot, it is not respond on system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156421/+subscriptions
[Bug 2148638] Re: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized.
Hi Shieh, I will analyze the log soon, a little busy now. And I suggest you keep the current setup to reproduce the issue in case there will more test. Thank you very much. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148638 Title: ubuntu 26.04 - When the NVME hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: When the CD8P NVMe hard drives were hot-swapped, the OS reported an error and some of the drives were not recognized. This issue happens on CD8P NVMe disk and does not happens on bm1743 NVMe disk. CD8P drives are Kaoxia drives The BM1743 drives that work are Samsung devices. Nvme disk detail: CD8P https://lenovopress.lenovo.com/lp1904-thinksystem-cd8p-read-intensive-nvme-pcie-50-ssd bm1743 https://lenovopress.lenovo.com/lp2156-thinksystem-bm1743-read-intensive-nvme-pcie-50-x4-ssd Steps to reproduce: 1.In the UEFI, enable VMD without created RAID disk. 2.Install ubuntu26.04 on M.2 sata disk. 3.use command lsblk to check all NVMEe disk 4.Unplug all NVMe device, then check NVMe device information again via lsblk. 5.plug all NVMe SSD 6.OS reported an error and some of the drives were not recognized. Compare with Ubuntu 24.04: There is no errors messages and all NVMe disks can be recognized after re-plug all NVMe SSD Info: The issue also happens on latest daily build: 0415 This issue only happens on VMD enabled, there is no this issue when vmd feature disable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148638/+subscriptions
[Bug 2155195] Re: [Panther Lake/xe] DisplayPort-over-Thunderbolt external monitor not detected at cold boot (regression in linux 7.0.0-22)
expecting to be fixed on 7.0.0-26. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155195 Title: [Panther Lake/xe] DisplayPort-over-Thunderbolt external monitor not detected at cold boot (regression in linux 7.0.0-22) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu release: Ubuntu 26.04 LTS (resolute) [lsb_release -rd] Kernel package: linux-image-7.0.0-22-generic 7.0.0-22.22 version_signature: Ubuntu 7.0.0-22.22-generic 7.0.0 What I expected: On boot, an external monitor connected via a Dell Thunderbolt 4 dock (DisplayPort output) should be detected and lit, as it was on kernel 7.0.0-15-generic. What happened instead: After updating to 7.0.0-22-generic, the external monitor is not detected on a cold boot. All other dock functions work normally (USB keyboard/mouse, YubiKey, Gigabit Ethernet), and the same dock + cable + monitor work in Windows on the same machine. The internal panel (eDP-1) works. All /sys/class/drm/card1-DP-*/status read "disconnected"; only eDP-1 is connected. Root cause (boot-time ordering race in DisplayPort-over-Thunderbolt tunneling): The Thunderbolt connection manager sets up and tears down the DP tunnel ~83s BEFORE the xe display driver finishes loading, so the tunnel is destroyed and never recreated. Kernel log (monotonic boot offsets): [ 4.97s] thunderbolt 0-1: new device found ... Dell Thunderbolt 4 Dock [ 17.72s] thunderbolt 0000:00:0d.2: 0:5 <-> 1:14 (DP): not active, tearing down [101.11s] xe 0000:00:02.0: [drm] Found pantherlake (device ID b080) integrated display [102.46s] [drm] Initialized xe 1.1.0 for 0000:00:02.0 The late xe load correlates with a stalled udev coldplug: `systemd- analyze blame` shows a cluster of device units (dev-rfkill, tpm0, ttyS0-3, ...) all settling at ~1min 39s, i.e. udev is wedged ~99s and only modprobes xe afterward. This ~99s stall does not occur on 7.0.0-15-generic. Recovery (confirms HW is fine): unplugging/replugging the single Thunderbolt cable AFTER boot (xe now loaded) immediately re- establishes the DP tunnel and DP-7 goes "connected" and the monitor lights up. The failure is purely the cold-boot ordering race. Hardware: - Dell XPS 16 (product_name "XPS 16 DA16260", board 0TVXV7), BIOS 1.5.1 (2026-04-01) - GPU: Intel Panther Lake [Arc B390] [8086:b080] (rev 04), driver: xe - Dock: Dell Thunderbolt 4 Dock (USB4, links at 40 Gb/s) -> DisplayPort -> external monitor - Session: Wayland (GNOME/mutter) Workarounds: replug the Thunderbolt cable after boot; or boot 7.0.0-15-generic. See also (same teardown signature, different distro/HW): https://github.com/basecamp/omarchy/issues/3906 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: kgapos 6304 F.... pipewire kgapos 6325 F.... wireplumber /dev/snd/seq: kgapos 6304 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 20:48:43 2026 InstallationDate: Installed on 2026-05-28 (6 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. XPS 16 DA16260 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux StagingDrivers: intel_ipu7_isys intel_ipu7 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2026 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0TVXV7 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd04/01/2026:br1.5:efr1.2:svnDellInc.:pnXPS16DA16260:pvr:rvnDellInc.:rn0TVXV7:rvrA02:cvnDellInc.:ct10:cvr:sku0DBA:pfaDellLaptops: dmi.product.family: Dell Laptops dmi.product.name: XPS 16 DA16260 dmi.product.sku: 0DBA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155195/+subscriptions
[Bug 2155161] Re: Jabra Evolve 2 85 headset keeps reconnecting via usb
Hi Alexander Thank you for your information. BR An -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155161 Title: Jabra Evolve 2 85 headset keeps reconnecting via usb Status in linux package in Ubuntu: New Bug description: As soon as i want to use any kind of usb connection with the headset the usb connects and reconnects over and over again. I made sure its not an issue of cable used or the usb hub in the docking station. by connecting it directly to the laptop. Although i could use usb with this headset on ubuntu lts 24 without any issues since i reinstalled with kubuntu 26 this occurs (guess it would happen in ubuntu 26 too) I gladly provide more info if needed. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jun 3 16:10:16 2026 InstallationDate: Installed on 2026-05-12 (22 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp0s20f3Link: Not connected. MachineType: Dell Inc. Precision 3581 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=UUID=e1d7f812-2942-4efe-80f9-510636bb0378 ro quiet cryptdevice=UUID=24e90ca6-128d-41d3-be29-328e50acf97d:luks-24e90ca6-128d-41d3-be29-328e50acf97d root=/dev/mapper/luks-24e90ca6-128d-41d3-be29-328e50acf97d splash nvidia-drm.modeset=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2025 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.1 dmi.board.name: 0V8YXF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnDellInc.:bvr1.27.1:bd12/12/2025:br1.27:efr1.25:svnDellInc.:pnPrecision3581:pvr:rvnDellInc.:rn0V8YXF:rvrA00:cvnDellInc.:ct10:cvr:sku0C07:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 3581 dmi.product.sku: 0C07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155161/+subscriptions
[Bug 2156328] Re: HP Envy x360 16-ac0xxx (Meteor Lake, Intel Core Ultra 7 155U) — xe driver HPD interrupt storm on HDMI-A-1 at boot
Additional note: Bug affects both i915 and xe drivers. With xe.force_probe=7d45 i915.force_probe=!7d45 in GRUB, the xe driver is active and shows the same HPD storm. With default GRUB (no force_probe), i915 takes over and also hits the storm. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156328 Title: HP Envy x360 16-ac0xxx (Meteor Lake, Intel Core Ultra 7 155U) — xe driver HPD interrupt storm on HDMI-A-1 at boot Status in linux package in Ubuntu: New Bug description: HP Envy x360 16-ac0xxx (Meteor Lake, Intel Core Ultra 7 155U) — xe driver HPD interrupt storm on HDMI-A-1 at boot On kernel 7.0.0-22-generic and 7.0.0-1005-oem, the xe DRM driver detects an HPD interrupt storm on HDMI-A-1 within ~12 seconds of boot even with no monitor connected, falling back to polling mode. This causes HDMI monitors to take 30+ minutes to be detected and causes repeated connect/disconnect cycling when a monitor is plugged in. Key dmesg line: xe 0000:00:02.0: [drm] HPD interrupt storm detected on connector HDMI-A-1: switching from hotplug detection to polling Parameters xe.hpd_storm_ctl and xe.enable_guc are silently ignored (unknown parameter). Firmware is fully up to date per fwupdmgr. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: edwardrem 6222 F.... pipewire edwardrem 6244 F.... wireplumber /dev/snd/seq: edwardrem 6222 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 08:58:01 2026 InstallationDate: Installed on 2026-05-13 (28 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: HP HP Envy x360 2-in-1 Laptop 16-ac0xxx ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=12e4f41c-ffc3-4b6f-a529-9c3a95b5e45a ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2025 dmi.bios.release: 15.5 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8C66 dmi.board.vendor: HP dmi.board.version: 01.30 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnInsyde:bvrF.05:bd07/24/2025:br15.5:efr1.30:svnHP:pnHPEnvyx3602-in-1Laptop16-ac0xxx:pvrType1ProductConfigId:rvnHP:rn8C66:rvr01.30:cvnHP:ct31:cvrChassisVersion:sku9S1R6UA#ABA:pfa103C_5335M8HPENVY: dmi.product.family: 103C_5335M8 HP ENVY dmi.product.name: HP Envy x360 2-in-1 Laptop 16-ac0xxx dmi.product.sku: 9S1R6UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156328/+subscriptions
вторник
[Bug 2148538] Re: Kernel lockup on 6.17.0-1017-oem Lenovo P14s gen 6 AMD Ryzen AI 7 pro 350
** Changed in: linux-oem-6.17 (Ubuntu Noble) Assignee: (unassigned) => AaronMa (mapengyu) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148538 Title: Kernel lockup on 6.17.0-1017-oem Lenovo P14s gen 6 AMD Ryzen AI 7 pro 350 Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Questing: In Progress Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: I have a Lenovo ThinkPad P14s Gen 6 AMD Ryzen AI 7 pro 350 I have installed - 24.04 LTS - 6.17.0-1017-oem - linux-image-6.17.0-1017-oem 6.17.0-1017.17 Regularly (at this point, seems to happen once per day), the kernel locks up (actually, let me amend that; I just noticed that the key combination I thought would go into terminal mode doesn't do that, so I don't know if the kernel has locked up or gnome has frozen). I haven't been able to identify particular workloads that are causing this behavior. At any given instance, I am running firefox, brave, mattermost, vs code, multiple terminal sessions, obsidian, perhaps some qemu vms (no GUI). Looking at the journal, after one recent lockup, I saw the following: amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. workqueue: amdgpu_tlb_fence_work [amdgpu] hogged CPU for >13333us 35 times, consider switching to WQ_UNBOUND amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. INFO: task kworker/7:0:37823 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/7:0 state:D stack:0 pid:37823 tgid:37823 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/15:0:39916 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/15:0 state:D stack:0 pid:39916 tgid:39916 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/12:4:40454 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/12:4 state:D stack:0 pid:40454 tgid:40454 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/5:4:40750 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/5:4 state:D stack:0 pid:40750 tgid:40750 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/15:3:40825 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/15:3 state:D stack:0 pid:40825 tgid:40825 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:8:40844 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:8 state:D stack:0 pid:40844 tgid:40844 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:9:40845 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:9 state:D stack:0 pid:40845 tgid:40845 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/4:2:41419 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/4:2 state:D stack:0 pid:41419 tgid:41419 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/10:0:41524 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/10:0 state:D stack:0 pid:41524 tgid:41524 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? _raw_spin_lock_irqsave+0xe/0x20 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> INFO: task kworker/4:0:42116 blocked for more than 122 seconds. Tainted: P O 6.17.0-1017-oem #17-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/4:0 state:D stack:0 pid:42116 tgid:42116 ppid:2 task_flags:0x4208060 flags:0x00004000 Workqueue: events amdgpu_tlb_fence_work [amdgpu] Call Trace: <TASK> __schedule+0x30d/0x7a0 schedule+0x27/0x90 schedule_timeout+0x104/0x110 dma_fence_default_wait+0x1f0/0x250 ? __pfx_dma_fence_default_wait_cb+0x10/0x10 dma_fence_wait_timeout+0x13a/0x170 amdgpu_tlb_fence_work+0x29/0x140 [amdgpu] process_one_work+0x18e/0x3e0 worker_thread+0x2e3/0x420 ? __pfx_worker_thread+0x10/0x10 kthread+0x10a/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x121/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. Supervising 9 threads of 6 processes of 1 users. Supervising 9 threads of 6 processes of 1 users. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. amdgpu 0000:c4:00.0: amdgpu: MES ring buffer is full. kauditd_printk_skb: 4 callbacks suppressed SRU Justification: [ Impact ] On Lenovo ThinkPad P14s Gen 6 systems with AMD Ryzen AI 7 PRO 350, the system can lock up under graphical workloads. Kernel logs show the AMDGPU MES ring buffer becoming full and hung task reports involving amdgpu_tlb_fence_work. The issue is caused by commit f3854e04b708 ("drm/amdgpu: attach tlb fence to the PTs update") which attaches TLB fences too broadly and can flood KIQ/MES TLB invalidation work. [ Fix ] Backport upstream fixes: - d967509651601 ("drm/amdgpu: make sure userqs are enabled in userq IOCTLs") - 9163fe4d790f (Revert "drm/amdgpu: don't attach the tlb fence for SI") - e9f58ff991dd ("drm/amdgpu: rework how we handle TLB fences") [ Test Plan ] 1. Boot the affected Lenovo P14s Gen 6 AMD Ryzen AI 7 PRO 350 system. 2. Exercise the graphical workload that previously reproduced the lockup. 3. Verify the system remains responsive and dmesg does not show MES ring buffer full or amdgpu_tlb_fence_work hung task messages. A test kernel with this fix series ran for 12 hours on the affected system without reproducing the lockup (LP #2148538 comment #29). [ Where problems could occur ] Regressions could appear as GPU hangs, failed VM updates, TLB flush failures, or user queue/KFD workload failures on AMD GPUs. [ Other Info ] Noble linux is not affected (offending commit absent). Resolute linux is not affected (fixes already present). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148538/+subscriptions
[Bug 2126938] Re: network daemon cannot change link-offloading settings
** Changed in: netplan.io (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Questing) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2126938 Title: network daemon cannot change link-offloading settings Status in linux package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Status in linux source package in Questing: Invalid Status in netplan.io source package in Questing: Confirmed Status in systemd source package in Questing: Won't Fix Status in linux source package in Resolute: Invalid Status in netplan.io source package in Resolute: Confirmed Status in systemd source package in Resolute: Won't Fix Bug description: netplan.io is showing new autopkgtest failures in Questing VMs, when testing against Linux kernel 6.17 Interestingly, the same failure happens with both the systemd-networkd and NetworkManager daemons. Also, the issue does NOT happen inside the armhf runners (containers) that are using an old 6.8 container host kernel. Specifically: 942s ====================================================================== 942s FAIL: test_link_offloading (__main__.TestNetworkManager.test_link_offloading) 942s ---------------------------------------------------------------------- 942s Traceback (most recent call last): 942s File "/tmp/autopkgtest.urTG2T/build.w51/src/tests/integration/ethernets.py", line 331, in test_link_offloading 942s self.assertIn(b'tcp-segmentation-offload: off', out) 942s ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 942s AssertionError: b'tcp-segmentation-offload: off' not found in b'Features for eth42:\nrx-checksumming: off\ntx-checksumming: off\n\ttx-checksum-ipv4: off [fixed]\n\ttx-checksum-ip-generic: off\n\ttx-checksum-ipv6: off [fixed]\n\ttx-checksum-fcoe-crc: off [fixed]\n\ttx-checksum-sctp: off\nscatter-gather: on\n\ttx-scatter-gather: on\n\ttx-scatter-gather-fraglist: on\ntcp-segmentation-offload: on\n\ttx-tcp-segmentation: off\n\ttx-tcp-ecn-segmentation: off [requested on]\n\ttx-tcp-mangleid-segmentation: off [requested on]\n\ttx-tcp6-segmentation: off\n\ttx-tcp-accecn-segmentation: on\ngeneric-segmentation-offload: off\ngeneric-receive-offload: off\nlarge-receive-offload: off [fixed]\nrx-vlan-offload: on\ntx-vlan-offload: on\nntuple-filters: off [fixed]\nreceive-hashing: off [fixed]\nhighdma: on\nrx-vlan-filter: off [fixed]\nvlan-challenged: off [fixed]\ntx-gso-robust: off [fixed]\ntx-fcoe-segmentation: off [fixed]\ntx-gre-segmentation: on\ntx-gre-csum-segmentation: on\ntx-ipxip4-segmentation: on\ntx-ipxip6-segmentation: on\ntx-udp_tnl-segmentation: on\ntx-udp_tnl-csum-segmentation: on\ntx-gso-partial: off [fixed]\ntx-tunnel-remcsum-segmentation: off [fixed]\ntx-sctp-segmentation: on\ntx-esp-segmentation: off [fixed]\ntx-udp-segmentation: off [requested on]\ntx-gso-list: on\ntx-nocache-copy: off\nloopback: off [fixed]\nrx-fcs: off [fixed]\nrx-all: off [fixed]\ntx-vlan-stag-hw-insert: on\nrx-vlan-stag-hw-parse: on\nrx-vlan-stag-filter: off [fixed]\nl2-fwd-offload: off [fixed]\nhw-tc-offload: off [fixed]\nesp-hw-offload: off [fixed]\nesp-tx-csum-hw-offload: off [fixed]\nrx-udp_tunnel-port-offload: off [fixed]\ntls-hw-tx-offload: off [fixed]\ntls-hw-rx-offload: off [fixed]\nrx-gro-hw: off [fixed]\ntls-hw-record: off [fixed]\nrx-gro-list: off\nmacsec-hw-offload: off [fixed]\nrx-udp-gro-forwarding: off\nhsr-tag-ins-offload: off [fixed]\nhsr-tag-rm-offload: off [fixed]\nhsr-fwd-offload: off [fixed]\nhsr-dup-offload: off [fixed]\n' 942s 942s ====================================================================== 942s FAIL: test_link_offloading (__main__.TestNetworkd.test_link_offloading) 942s ---------------------------------------------------------------------- 942s Traceback (most recent call last): 942s File "/tmp/autopkgtest.urTG2T/build.w51/src/tests/integration/ethernets.py", line 331, in test_link_offloading 942s self.assertIn(b'tcp-segmentation-offload: off', out) 942s ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 942s AssertionError: b'tcp-segmentation-offload: off' not found in b'Features for eth42:\nrx-checksumming: off\ntx-checksumming: off\n\ttx-checksum-ipv4: off [fixed]\n\ttx-checksum-ip-generic: off\n\ttx-checksum-ipv6: off [fixed]\n\ttx-checksum-fcoe-crc: off [fixed]\n\ttx-checksum-sctp: off\nscatter-gather: on\n\ttx-scatter-gather: on\n\ttx-scatter-gather-fraglist: on\ntcp-segmentation-offload: on\n\ttx-tcp-segmentation: off\n\ttx-tcp-ecn-segmentation: off [requested on]\n\ttx-tcp-mangleid-segmentation: off [requested on]\n\ttx-tcp6-segmentation: off\n\ttx-tcp-accecn-segmentation: on\ngeneric-segmentation-offload: off\ngeneric-receive-offload: off\nlarge-receive-offload: off [fixed]\nrx-vlan-offload: on\ntx-vlan-offload: on\nntuple-filters: off [fixed]\nreceive-hashing: off [fixed]\nhighdma: on\nrx-vlan-filter: off [fixed]\nvlan-challenged: off [fixed]\ntx-gso-robust: off [fixed]\ntx-fcoe-segmentation: off [fixed]\ntx-gre-segmentation: on\ntx-gre-csum-segmentation: on\ntx-ipxip4-segmentation: on\ntx-ipxip6-segmentation: on\ntx-udp_tnl-segmentation: on\ntx-udp_tnl-csum-segmentation: on\ntx-gso-partial: off [fixed]\ntx-tunnel-remcsum-segmentation: off [fixed]\ntx-sctp-segmentation: on\ntx-esp-segmentation: off [fixed]\ntx-udp-segmentation: off [requested on]\ntx-gso-list: on\ntx-nocache-copy: off\nloopback: off [fixed]\nrx-fcs: off [fixed]\nrx-all: off [fixed]\ntx-vlan-stag-hw-insert: on\nrx-vlan-stag-hw-parse: on\nrx-vlan-stag-filter: off [fixed]\nl2-fwd-offload: off [fixed]\nhw-tc-offload: off [fixed]\nesp-hw-offload: off [fixed]\nesp-tx-csum-hw-offload: off [fixed]\nrx-udp_tunnel-port-offload: off [fixed]\ntls-hw-tx-offload: off [fixed]\ntls-hw-rx-offload: off [fixed]\nrx-gro-hw: off [fixed]\ntls-hw-record: off [fixed]\nrx-gro-list: off\nmacsec-hw-offload: off [fixed]\nrx-udp-gro-forwarding: off\nhsr-tag-ins-offload: off [fixed]\nhsr-tag-rm-offload: off [fixed]\nhsr-fwd-offload: off [fixed]\nhsr-dup-offload: off [fixed]\n' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2126938/+subscriptions
[Bug 2156312] [NEW] Internal display black screen on Intel Lunar Lake with eDP panel
Public bug reported: [Impact] Internal display goes black after login on Intel Lunar Lake systems with an eDP panel. The external monitor works. The internal display shows as disabled in display settings and cannot be enabled. Hits 100% on affected hardware (3 units, 15/15 attempts). The bug is caused by LOBF (Link Off Between Frames) being enabled on platforms that use the legacy VRR timing generator. Those platforms do not meet the bspec requirement for LOBF (Always-on VRR TG with fixed refresh rate mode). Enabling LOBF incorrectly causes the display to go dark. [Fix] Replace the raw vmin/vmax/flipline comparison with the proper bspec checks: - intel_vrr_always_use_vrr_tg() to gate LOBF on platforms with Always-on VRR TG - intel_vrr_is_fixed_rr() to confirm fixed refresh rate mode Backported from upstream commit 8a517b1e6d8b, merged in v7.1-rc1. [Test Plan] Boot on affected Intel Lunar Lake hardware with an eDP panel. Without patch: internal display is black after login; shows as disabled in display settings. With patch: internal display works normally after login. [Where problems could occur] Could affect intel_alpm.c LOBF configuration logic in the i915 driver. If intel_vrr_always_use_vrr_tg() or intel_vrr_is_fixed_rr() return wrong results on a platform, LOBF would be incorrectly blocked, and Panel Replay power savings would be lost on those machines. The display would still work — it would just not enter LOBF mode. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Questing) Importance: Undecided Status: New ** Affects: linux-oem-6.17 (Ubuntu Questing) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: Invalid ** Tags: cpl jira-cpl-301 jira-somerville-4895 oem-priority somerville ** Also affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Questing) Importance: Undecided Status: New ** Tags added: cpl jira-cpl-301 oem-priority ** Tags added: jira-somerville-4895 somerville ** Changed in: linux-oem-6.17 (Ubuntu Questing) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Resolute) Status: New => Invalid ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.17 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156312 Title: Internal display black screen on Intel Lunar Lake with eDP panel Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: New Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Internal display goes black after login on Intel Lunar Lake systems with an eDP panel. The external monitor works. The internal display shows as disabled in display settings and cannot be enabled. Hits 100% on affected hardware (3 units, 15/15 attempts). The bug is caused by LOBF (Link Off Between Frames) being enabled on platforms that use the legacy VRR timing generator. Those platforms do not meet the bspec requirement for LOBF (Always-on VRR TG with fixed refresh rate mode). Enabling LOBF incorrectly causes the display to go dark. [Fix] Replace the raw vmin/vmax/flipline comparison with the proper bspec checks: - intel_vrr_always_use_vrr_tg() to gate LOBF on platforms with Always-on VRR TG - intel_vrr_is_fixed_rr() to confirm fixed refresh rate mode Backported from upstream commit 8a517b1e6d8b, merged in v7.1-rc1. [Test Plan] Boot on affected Intel Lunar Lake hardware with an eDP panel. Without patch: internal display is black after login; shows as disabled in display settings. With patch: internal display works normally after login. [Where problems could occur] Could affect intel_alpm.c LOBF configuration logic in the i915 driver. If intel_vrr_always_use_vrr_tg() or intel_vrr_is_fixed_rr() return wrong results on a platform, LOBF would be incorrectly blocked, and Panel Replay power savings would be lost on those machines. The display would still work — it would just not enter LOBF mode. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156312/+subscriptions
[Bug 2155235] Re: Intel i915 eDP-1 "Failed to enable link training" after suspend on Alder Lake
Hi, Could you run this command and provide the result? sudo cat /sys/class/drm/card1-eDP-1/edid | od -A x -t x1z | head -3 BR An -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2155235 Title: Intel i915 eDP-1 "Failed to enable link training" after suspend on Alder Lake Status in linux package in Ubuntu: New Bug description: After resume from suspend, the internal laptop monitor (eDP-1) stays black while the external HDMI monitor turns on. The logs show: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:507:eDP-1][ENCODER:506:DDI A/PHY A][DPRX] Failed to enable link training . Workaround that helps: adding i915.enable_psr=0 i915.enable_dc=0 to kernel parameters. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 14:28:23 2026 InstallationDate: Installed on 2026-04-27 (38 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp4s0Link: Not connected. MachineType: HP Victus by HP Gaming Laptop 15-fa0xxx ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=efc1b9e5-9810-4f5d-b2b3-d4ebbe04d955 ro quiet splash i915.enable_psr=0 i915.enable_dc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2025 dmi.bios.release: 15.31 dmi.bios.vendor: AMI dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8A4F dmi.board.vendor: HP dmi.board.version: 37.56 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 37.56 dmi.modalias: dmi:bvnAMI:bvrF.31:bd04/22/2025:br15.31:efr37.56:svnHP:pnVictusbyHPGamingLaptop15-fa0xxx:pvr:rvnHP:rn8A4F:rvr37.56:cvnHP:ct10:cvrChassisVersion:sku6X7N4EA#UUQ:pfa103C_5335M7HPVictus: dmi.product.family: 103C_5335M7 HP Victus dmi.product.name: Victus by HP Gaming Laptop 15-fa0xxx dmi.product.sku: 6X7N4EA#UUQ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2155235/+subscriptions
[Bug 2156305] Re: OS dmesg log shows 'mpam_msc' errors
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+attachment/5976527/+files/dmesg.txt.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156305 Title: OS dmesg log shows 'mpam_msc' errors Status in linux package in Ubuntu: New Bug description: After installation of Ubuntu 24.04.3 on a Nvidia/ARM64 server, the dmesg showed 'mpam_msc' errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+subscriptions
[Bug 2156305] Re: OS dmesg log shows 'mpam_msc' errors
Additional information: 1. In the Ubuntu 24.04.3, there are at least two types of complaints shown in the OS demsg: a. Line 2283: [ 16.524691] ACPI MPAM: Bad level (4294967294) for cache with id 0 b. Line 2284: [ 16.530958] mpam_msc mpam_msc.183: probe with driver mpam_msc failed with error -22 2. But none of RHEL 9.6 or 10.0 kernel showed the same error messages errors. 3. Ubuntu 24.04.3 may have different code level of mpam_msc driver incompatible with current ACPI MPAM firmware. 4. Nviaida's own tool passed the MPAM table test. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156305 Title: OS dmesg log shows 'mpam_msc' errors Status in linux package in Ubuntu: New Bug description: After installation of Ubuntu 24.04.3 on a Nvidia/ARM64 server, the dmesg showed 'mpam_msc' errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+subscriptions
[Bug 2156305] [NEW] OS dmesg log shows 'mpam_msc' errors
Public bug reported: After installation of Ubuntu 24.04.3 on a Nvidia/ARM64 server, the dmesg showed 'mpam_msc' errors. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156305 Title: OS dmesg log shows 'mpam_msc' errors Status in linux package in Ubuntu: New Bug description: After installation of Ubuntu 24.04.3 on a Nvidia/ARM64 server, the dmesg showed 'mpam_msc' errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156305/+subscriptions