[Bug 2148718] Re: intel-ipu7 / intel-ipu7-isys modules are shipped unsigned in latest Resolute kernels, breaking Secure Boot systems

This bug is awaiting verification that the linux-oracle/7.0.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-resolute-linux-oracle' to 'verification-done- resolute-linux-oracle'. If the problem still exists, change the tag 'verification-needed-resolute-linux-oracle' to 'verification-failed- resolute-linux-oracle'. 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-resolute-linux-oracle-v2 verification-needed-resolute-linux-oracle -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148718 Title: intel-ipu7 / intel-ipu7-isys modules are shipped unsigned in latest Resolute kernels, breaking Secure Boot systems Status in linux package in Ubuntu: In Progress 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 Released Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: Affects: Ubuntu 26.04 (Resolute Raccoon) --- Description: On kernel 7.0.0-13 and 7.0.0-14, the webcam stopped working on my XPS 13 9350 Lunar Lake laptop (sensor: OV02C10) with Secure Boot enabled. The intel-ipu7 and intel-ipu7-isys modules are shipped unsigned, so the kernel refuses to load them under Secure Boot. --- Expected: Staging modules are signed by the Ubuntu kernel build and should load successfully with Secure Boot enabled. Actual: Webcam is non-functional on Secure Boot systems unless modules are manually MOK-signed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148718/+subscriptions

[Bug 2148538] Re: Kernel lockup on 6.17.0-1017-oem Lenovo P14s gen 6 AMD Ryzen AI 7 pro 350

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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: Confirmed Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress 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 2153962] Re: net/rds: reset op_nents when zerocopy page pin fails

This bug is awaiting verification that the linux/7.0.0-19.19 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-resolute-linux' to 'verification-done-resolute- linux'. If the problem still exists, change the tag 'verification- needed-resolute-linux' to 'verification-failed-resolute-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-resolute-linux-v2 verification-needed-resolute-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153962 Title: net/rds: reset op_nents when zerocopy page pin fails Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Questing: In Progress Status in linux source package in Resolute: In Progress Bug description: From https://lore.kernel.org/netdev/20260505234336.2132721-1-achender@kernel.org/ When iov_iter_get_pages2() fails in rds_message_zcopy_from_user(), the pinned pages are released with put_page(), and rm->data.op_mmp_znotifier is cleared. But we fail to properly clear rm->data.op_nents. Later when rds_message_purge() is called from rds_sendmsg() the cleanup loop iterates over the incorrectly non zero number of op_nents and frees them again. Fix this by properly resetting op_nents when it should be in rds_message_zcopy_from_user(). Fixes: 0cebaccef3ac ("rds: zerocopy Tx support.") Signed-off-by: Allison Henderson <achender@kernel.org> --- net/rds/message.c | 1 + 1 file changed, 1 insertion(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153962/+subscriptions

[Bug 2154305] Re: BUG: unable to handle page fault for address: ffff8d47fd39d5e5

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154305 Title: BUG: unable to handle page fault for address: ffff8d47fd39d5e5 Status in linux package in Ubuntu: New Bug description: "ubuntu-bug linux" failed with "HTTP Error 504: Gateway Time-out" for me. So here you get the bug report manually: When I try to build lintian with sbuild unshare backend, the kernel becomes unhappy: ``` [ 755.351303] BUG: unable to handle page fault for address: ffff8d47fd39d5e5 [ 755.351318] #PF: supervisor read access in kernel mode [ 755.351324] #PF: error_code(0x0000) - not-present page [ 755.351329] PGD 0 P4D 0 [ 755.351337] Oops: Oops: 0000 [#1] SMP NOPTI [ 755.351346] CPU: 3 UID: 100999 PID: 43703 Comm: Lintian prepare Not tainted 7.0.0-15-generic #15-Ubuntu PREEMPT(lazy) [ 755.351353] Hardware name: Framework Laptop 12 (13th Gen Intel Core)/FRAPMACP05, BIOS 03.07 02/10/2026 [ 755.351358] RIP: 0010:dup_mmap+0x184/0x870 [ 755.351370] Code: fd 89 43 04 48 c7 c6 ff ff ff ff 48 8d bd 70 ff ff ff e8 bf 3f ee 00 48 89 c3 48 85 c0 0f 84 fc 05 00 00 48 8b 43 10 8b 53 28 <48> 8b 88 90 01 00 00 83 e1 01 0f 84 a3 05 00 00 3b 90 d0 01 00 00 [ 755.351376] RSP: 0018:ffffd086e249bb68 EFLAGS: 00010282 [ 755.351383] RAX: ffff8d47fd39d455 RBX: ffff8de6e6eb4240 RCX: 0000000000000000 [ 755.351387] RDX: 0000000000000139 RSI: 0000000000000000 RDI: 0000000000000000 [ 755.351391] RBP: ffffd086e249bc70 R08: 0000000000000000 R09: 0000000000000000 [ 755.351395] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8de5801c4d00 [ 755.351399] R13: ffff8de5fd39d400 R14: 0000000000000000 R15: ffff8de8ad0829c0 [ 755.351403] FS: 00007f399ea20bc0(0000) GS:ffff8df53c980000(0000) knlGS:0000000000000000 [ 755.351408] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 755.351412] CR2: ffff8d47fd39d5e5 CR3: 000000041c9f2004 CR4: 0000000000f72ef0 [ 755.351417] PKRU: 55555554 [ 755.351421] Call Trace: [ 755.351425] <TASK> [ 755.351433] dup_mm.constprop.0+0x6f/0x170 [ 755.351443] copy_process+0x162d/0x17c0 [ 755.351453] kernel_clone+0xb6/0x4c0 [ 755.351460] ? handle_pte_fault+0x1d8/0x1f0 [ 755.351466] __do_sys_clone+0x68/0xa0 [ 755.351475] __x64_sys_clone+0x25/0x40 [ 755.351482] x64_sys_call+0x139b/0x2390 [ 755.351489] do_syscall_64+0x115/0x5a0 [ 755.351499] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 [ 755.351507] ? irqentry_exit+0x97/0x5a0 [ 755.351515] ? exc_page_fault+0x94/0x1e0 [ 755.351522] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 755.351528] RIP: 0033:0x7f399eb563e8 [ 755.351535] Code: 7d e0 e8 bb f9 f4 ff 45 31 c0 31 d2 31 f6 64 48 8b 04 25 10 00 00 00 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 68 41 89 c4 85 c0 74 29 48 8d 7d e0 e8 e0 f9 [ 755.351540] RSP: 002b:00007ffd78ea0760 EFLAGS: 00000246 ORIG_RAX: 0000000000000038 [ 755.351546] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f399eb563e8 [ 755.351550] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011 [ 755.351554] RBP: 00007ffd78ea0780 R08: 0000000000000000 R09: 0000000000000000 [ 755.351558] R10: 00007f399ea20e90 R11: 0000000000000246 R12: 0000610f18d10010 [ 755.351562] R13: 0000000000000000 R14: 0000000000000000 R15: 0000610f1cd3e6f0 [ 755.351569] </TASK> [ 755.351571] Modules linked in: overlay snd_seq_dummy rfcomm snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat x_tables nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables bridge stp llc ccm snd_hda_codec_intelhdmi snd_hda_codec_hdmi uhid cmac algif_hash algif_skcipher af_alg qrtr snd_hda_codec_alc269 snd_hda_codec_realtek_lib snd_hda_scodec_component snd_hda_codec_generic snd_hda_intel snd_sof_pci_intel_tgl snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common bnep snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda soundwire_cadence cros_ec_lid_angle cros_ec_sensors snd_sof_pci cros_ec_sensors_core snd_sof_xtensa_dsp industrialio_triggered_buffer snd_sof kfifo_buf snd_sof_utils industrialio xe snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_sdw_utils snd_soc_acpi soundwire_bus drm_gpusvm_helper snd_soc_sdca gpu_sched crc8 drm_gpuvm [ 755.351681] drm_ttm_helper snd_soc_avs drm_exec intel_uncore_frequency snd_soc_hda_codec drm_suballoc_helper intel_uncore_frequency_common binfmt_misc snd_hda_ext_core snd_hda_codec x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_intel_dspcfg coretemp snd_intel_sdw_acpi snd_hwdep snd_soc_core kvm_intel snd_compress nls_iso8859_1 ac97_bus snd_pcm_dmaengine snd_pcm kvm cmdlinepart leds_cros_ec snd_seq_midi spi_nor gpio_cros_ec led_class_multicolor cros_ec_chardev cros_ec_sysfs cros_charge_control cros_ec_sensorhub cros_ec_hwmon cros_ec_debugfs mei_pxp mei_hdcp mtd intel_rapl_msr iwlmvm snd_seq_midi_event irqbypass uvcvideo snd_rawmidi processor_thermal_device_pci cros_ec_dev i915 rapl videobuf2_vmalloc btusb mac80211 uvc processor_thermal_device snd_seq videobuf2_memops btmtk processor_thermal_wt_hint platform_temperature_control btrtl snd_seq_device videobuf2_v4l2 intel_cstate processor_thermal_soc_slider btbcm drm_buddy snd_timer libarc4 videobuf2_common processor_thermal_rfim btintel ttm [ 755.351804] processor_thermal_rapl drm_display_helper bluetooth intel_rapl_common snd i2c_i801 iwlwifi mei_me processor_thermal_wt_req cec i2c_smbus spi_intel_pci processor_thermal_power_floor wmi_bmof mei soundcore i2c_mux spi_intel rc_core cfg80211 processor_thermal_mbox i2c_algo_bit platform_profile igen6_edac ov13858 v4l2_fwnode intel_pmc_core int3403_thermal v4l2_async int340x_thermal_zone pmt_telemetry videodev pmt_discovery pmt_class mc cros_ec_lpcs intel_pmc_ssram_telemetry cros_ec int3400_thermal intel_vsec cros_ec_proto acpi_pad acpi_thermal_rel input_leds joydev mac_hid sch_fq_codel nvme_fabrics efi_pstore nfnetlink dm_crypt typec_displayport hid_multitouch hid_generic nvme ucsi_acpi nvme_core typec_ucsi nvme_keyring gpio_keys typec nvme_auth intel_lpss_pci ghash_clmulni_intel psmouse video i2c_hid_acpi intel_lpss hkdf thunderbolt i2c_hid idma64 hid wmi soc_button_array pinctrl_tigerlake serio_raw dm_mirror dm_region_hash dm_log parport_pc ppdev lp msr parport dmi_sysfs autofs4 aesni_intel [ 755.351954] CR2: ffff8d47fd39d5e5 [ 755.351960] ---[ end trace 0000000000000000 ]--- [ 756.089980] RIP: 0010:dup_mmap+0x184/0x870 [ 756.089993] Code: fd 89 43 04 48 c7 c6 ff ff ff ff 48 8d bd 70 ff ff ff e8 bf 3f ee 00 48 89 c3 48 85 c0 0f 84 fc 05 00 00 48 8b 43 10 8b 53 28 <48> 8b 88 90 01 00 00 83 e1 01 0f 84 a3 05 00 00 3b 90 d0 01 00 00 [ 756.089996] RSP: 0018:ffffd086e249bb68 EFLAGS: 00010282 [ 756.090000] RAX: ffff8d47fd39d455 RBX: ffff8de6e6eb4240 RCX: 0000000000000000 [ 756.090002] RDX: 0000000000000139 RSI: 0000000000000000 RDI: 0000000000000000 [ 756.090003] RBP: ffffd086e249bc70 R08: 0000000000000000 R09: 0000000000000000 [ 756.090005] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8de5801c4d00 [ 756.090006] R13: ffff8de5fd39d400 R14: 0000000000000000 R15: ffff8de8ad0829c0 [ 756.090008] FS: 00007f399ea20bc0(0000) GS:ffff8df53c980000(0000) knlGS:0000000000000000 [ 756.090010] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 756.090011] CR2: ffff8d47fd39d5e5 CR3: 000000041c9f2004 CR4: 0000000000f72ef0 [ 756.090013] PKRU: 55555554 [ 756.090015] note: Lintian prepare[43703] exited with irqs disabled ``` This problem is reproducible. Note: I had other problems with this laptop: https://community.frame.work/t/spontaneous-poweroffs-on-framework- laptop-12/82660 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154305/+subscriptions

[Bug 2154307] Re: DKMS modules installed as .ko.zst; are not included in initramfs

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154307 Title: DKMS modules installed as .ko.zst; are not included in initramfs Status in linux package in Ubuntu: New Bug description: DKMS-built kernel modules are installed as .ko.zst (zstd-compressed) rather than uncompressed .ko files. The initramfs-tools module inclusion code does not handle .ko.zst files — it finds and includes only uncompressed .ko files. As a result, DKMS-managed modules are absent from the initramfs, and drivers depending on them fail to load at early boot. The current workaround are manual steps to run unzstd --rm on the modules, depmod -a, and update-initramfs to include them. Affected kernels (confirmed on this system): 6.8.0-50-generic: broken (first occurrence) 6.11.0-24-generic: broken 6.11.0-25-generic: broken 6.11.0-26-generic: working (uncompressed .ko files present after upgrade) 6.11.0-28-generic: broken (regression) All subsequent kernels through 6.17.0-29-generic: broken Cause: July 2023, a patch series by Dimitri John Ledkov was applied to Ubuntu's kernel packaging to enable zstd-compressed modules: https://lists.ubuntu.com/archives/kernel-team/2023-July/141412.html The patch series description makes clear the intent was for DKMS-built modules to remain uncompressed. It explicitly states: "the makefile is patched to not attempt installing random modules compressed — this is to ensure that any dkms / lrm / modules builds." However, in practice, DKMS reads CONFIG_MODULE_COMPRESS_ZSTD from the kernel configuration and compresses its output accordingly, regardless of that intent. The result is that DKMS modules are installed as .ko.zst rather than as .ko. Investigation shows initramfs-tools does have .zst handling, but only in the add_firmware() function (searching /lib/firmware/ paths). There is no corresponding .zst handling in the module inclusion code path. Confirmed by: $ grep -A 10 -B 10 "zst" /usr/share/initramfs- tools/hook-functions This leaves a conflict between the actions of the components: - Ubuntu kernel packaging compresses modules and intends to exclude DKMS — but does not fully achieve that exclusion - DKMS follows CONFIG_MODULE_COMPRESS_ZSTD from the kernel config and compresses its output - initramfs-tools has no .zst handling in its module inclusion path, only in its firmware path Environment: Distribution: Linux Mint 22.3 (Ubuntu Noble/24.04 base) Kernel: Affects 6.8.0-50-generic and all subsequent kernels tested through 6.17.0-29-generic, with one exception noted above GPU: NVIDIA GeForce GTX 1660 Super NVIDIA driver: 580.159.03 (nvidia-dkms-580) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154307/+subscriptions

[Bug 2154318] Re: Sata SCSI Controller Problems

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154318 Title: Sata SCSI Controller Problems Status in linux package in Ubuntu: New Bug description: On ubuntu 7.0.0-15-Generic Sata6gbps drives when attempting to mount on Ubuntu 26.04 LTS on Asrock B850M Riptide motherboard results in link speed issues starting at sata6gbps and degrading down to sata3gbps then sata1.5gbps. Random drive disconnects, and eventual kernel panics making using sata HDD drives unstable. Tested Drives, WD Red WDC WD30EFRX-68EUZN0 and Seagate IronWolf NAS ST12000VN0007-2GS116. Both drives exhibit identical behavior regardless of sata cable or ata port on board. Attempting to manually mount causes immediate system crash. Sata drives being connected also significantly increase boot times and shutdown times aswell. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue May 26 14:23:40 2026 InstallationDate: Installed on 2026-05-02 (25 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) MachineType: ASRock B850M Riptide WiFi ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=11c0ad51-6b08-4854-af33-02a8ddfc254c ro quiet splash 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: 02/09/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.10 dmi.board.asset.tag: Default string dmi.board.name: B850M Riptide WiFi dmi.board.vendor: ASRock dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr4.10:bd02/09/2026:br5.41:svnASRock:pnB850MRiptideWiFi:pvrDefaultstring:rvnASRock:rnB850MRiptideWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B850M Riptide WiFi dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: ASRock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154318/+subscriptions

[Bug 2154322] Re: [UCSI regression] Dell Precision 5570: UCSI_GET_PDOS failed (-5) and USB-C Audio Accessory broken since 7.0.0-15

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154322 Title: [UCSI regression] Dell Precision 5570: UCSI_GET_PDOS failed (-5) and USB-C Audio Accessory broken since 7.0.0-15 Status in linux package in Ubuntu: New Bug description: # UCSI / USB-C Audio Accessory regression on kernel 7.0.0-15-generic ## Summary Since first boot of kernel **7.0.0-15-generic**, the UCSI ACPI driver reports persistent errors and `/sys/class/typec/port*/supported_accessory_modes` is `none` on all USB-C ports. As a result, USB-C analog headsets (USB-C Audio Accessory mode) that previously worked under kernel **7.0.0-14-generic** are no longer detected at all: the typec partner is registered, but no USB enumeration and no analog accessory routing occurs. Devices implementing the USB-C standard with a built-in USB DAC (e.g. JBL Tune 310C USB-C, USB ID `0ecb:20f6`) still work normally, confirming the regression is specific to the Audio Accessory mode path / UCSI capability reporting. ## System - Machine: Dell Precision 5570 (Alder Lake-P) - BIOS: 1.40.0 (2026-03-31) - Distro: Ubuntu 26.04 (Resolute Raccoon) - Audio stack: PipeWire 1.6.2 + WirePlumber 0.5.13 (not relevant — issue is below the audio stack) - USB-C controllers: Intel Alder Lake-P Thunderbolt 4 USB Controller `8086:461e`, PCH xHCI `8086:51ed` ## Affected kernel - Working: `7.0.0-14-generic` (`linux-image-7.0.0-14-generic` 7.0.0-14.14) - Broken: `7.0.0-15-generic` (`linux-image-7.0.0-15-generic` 7.0.0-15.15) ## Timeline (correlates exactly with kernel upgrade) | Date / time (UTC) | Event | |---|---| | Before 2026-05-17 | Running kernel 7.0.0-14, zero UCSI errors in kern.log, USB-C analog earphones work | | 2026-05-17 17:34 (CEST 19:34) | dpkg installs/upgrades GRUB 2.14, shim-signed, dracut, lvm2, cryptsetup, presumably pulls in `linux-image-7.0.0-15-generic` | | **2026-05-17 19:49 UTC (21:49 CEST)** | **First boot on 7.0.0-15. First UCSI errors appear immediately in kern.log:** | ``` ucsi_acpi USBC000:00: unknown error 0 ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5) ``` These errors then repeat on every boot since. ## Symptoms 1. `UCSI_GET_PDOS failed (-5)` — the kernel cannot query Power Data Objects from the UCSI controller. 2. `/sys/class/typec/port{0,1,2}/supported_accessory_modes` = `none` on all three USB-C ports. 3. USB-C analog headsets (no built-in DAC) plugged into any port: the typec partner is created (`/sys/class/typec/portN-partner` appears) with no advertised alt modes, but no USB enumeration occurs and no audio routing. 4. USB-C devices with their own DAC (USB Audio Class) enumerate and work normally. ## Reproducer 1. Boot kernel 7.0.0-15-generic on a Dell Precision 5570. 2. Plug a USB-C analog headset (no DAC) into any USB-C port (e.g. Wefix HP-2201A "kit piéton USB-C", or any cheap analog USB-C earbud). 3. Observe: - `/sys/class/typec/portN-partner` is created. - No new USB device in `lsusb`. - No new card in `aplay -l` or `/proc/asound/cards`. - `/sys/class/typec/portN/supported_accessory_modes` = `none`. ## Expected behaviour On kernel 7.0.0-14, the same setup detects the headset (or at least properly reports `supported_accessory_modes` so the analog audio routing can happen). ## Workaround Downgrade to `linux-image-7.0.0-14-generic` (still in the `resolute` archive). ## Files to attach - `/var/log/kern.log` (or excerpt from the first boot on 7.0.0-15) - Output of `dmesg | grep -iE 'ucsi|typec'` - Output of `for p in /sys/class/typec/port*; do echo "$p:"; cat $p/supported_accessory_modes 2>/dev/null; done` ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 26 23:51:26 2026 InstallationDate: Installed on 2026-05-17 (9 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Precision 5570 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-15-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 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2026 dmi.bios.release: 1.40 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.40.0 dmi.board.name: 02JH00 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnDellInc.:bvr1.40.0:bd03/31/2026:br1.40:efr1.19:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn02JH00:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154322/+subscriptions

[Bug 2154305] Re: BUG: unable to handle page fault for address: ffff8d47fd39d5e5

I captured another case, but with a different kernel error: ``` [ 153.264475] Oops: general protection fault, probably for non-canonical address 0xb231b2318eb98ec9: 0000 [#1] SMP NOPTI [ 153.264494] CPU: 10 UID: 100999 PID: 28947 Comm: Lintian prepare Not tainted 7.0.0-15-generic #15-Ubuntu PREEMPT(lazy) [ 153.264502] Hardware name: Framework Laptop 12 (13th Gen Intel Core)/FRAPMACP05, BIOS 03.07 02/10/2026 [ 153.264505] RIP: 0010:folio_mark_dirty+0x2c/0x60 [ 153.264519] Code: 44 00 00 55 48 89 e5 53 48 89 fb e8 7e 14 03 00 48 8b 13 48 85 c0 74 32 f7 c2 00 00 01 00 75 23 48 8b 50 68 48 89 de 48 89 c7 <48> 8b 52 10 2e 2e 2e ff d2 48 8b 5d f8 c9 31 d2 31 f6 31 ff c3 cc [ 153.264524] RSP: 0018:ffffd24fe0907790 EFLAGS: 00010246 [ 153.264530] RAX: ffff8d2eb073c440 RBX: fffff30289c54f80 RCX: 0000000000000000 [ 153.264535] RDX: b231b2318eb98eb9 RSI: fffff30289c54f80 RDI: ffff8d2eb073c440 [ 153.264538] RBP: ffffd24fe0907798 R08: 0000000000000000 R09: 0000000000000000 [ 153.264541] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001 [ 153.264544] R13: 0000000000000001 R14: fffff30289c54f80 R15: fffff30289c54f80 [ 153.264548] FS: 0000000000000000(0000) GS:ffff8d3430b00000(0000) knlGS:0000000000000000 [ 153.264552] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 153.264556] CR2: 000079dc62700520 CR3: 00000002e88d7003 CR4: 0000000000f72ef0 [ 153.264560] PKRU: 55555554 [ 153.264563] Call Trace: [ 153.264567] <TASK> [ 153.264571] zap_present_ptes.constprop.0+0x6f7/0x750 [ 153.264581] zap_pte_range+0x1f5/0x780 [ 153.264589] zap_pmd_range.isra.0+0xce/0x250 [ 153.264596] unmap_page_range+0x23a/0x3d0 [ 153.264603] unmap_single_vma+0x96/0x110 [ 153.264609] ? mas_find+0x5b/0x1d0 [ 153.264616] unmap_vmas+0xa5/0x180 [ 153.264625] exit_mmap+0x13b/0x400 [ 153.264636] __mmput+0x45/0x170 [ 153.264643] mmput+0x31/0x40 [ 153.264648] exec_mmap+0x183/0x210 [ 153.264654] begin_new_exec+0x114/0x470 [ 153.264659] load_elf_binary+0x315/0xfa0 [ 153.264668] ? ima_bprm_check+0x7c/0xb0 [ 153.264674] exec_binprm+0x13c/0x330 [ 153.264680] bprm_execve.part.0+0x160/0x230 [ 153.264685] bprm_execve+0x4a/0x80 [ 153.264689] do_execveat_common.isra.0+0x18b/0x1a0 [ 153.264694] __x64_sys_execve+0x3e/0x70 [ 153.264700] x64_sys_call+0xc63/0x2390 [ 153.264706] do_syscall_64+0x115/0x5a0 [ 153.264713] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 [ 153.264720] ? irqentry_exit+0x97/0x5a0 [ 153.264727] ? exc_page_fault+0x94/0x1e0 [ 153.264734] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 153.264739] RIP: 0033:0x79dc6265c20b [ 153.264747] Code: Unable to access opcode bytes at 0x79dc6265c1e1. [ 153.264750] RSP: 002b:00007ffc9f4ea098 EFLAGS: 00000202 ORIG_RAX: 000000000000003b [ 153.264756] RAX: ffffffffffffffda RBX: 000062f30533ea40 RCX: 000079dc6265c20b [ 153.264760] RDX: 000062f302506130 RSI: 000062f30533ea40 RDI: 00007ffc9f4ea0a0 [ 153.264763] RBP: 00007ffc9f4ea1c0 R08: 0000000000000fff R09: 0000000000000001 [ 153.264766] R10: 0000000000000008 R11: 0000000000000202 R12: 000062f30478a780 [ 153.264769] R13: 000062f30478a778 R14: 00007ffc9f4ea0a0 R15: 000062f302506130 [ 153.264774] </TASK> [ 153.264777] Modules linked in: overlay snd_seq_dummy rfcomm snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat x_tables nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables bridge stp llc ccm snd_hda_codec_intelhdmi snd_hda_codec_hdmi uhid cmac algif_hash algif_skcipher af_alg snd_hda_codec_alc269 snd_hda_codec_realtek_lib snd_hda_scodec_component qrtr bnep snd_hda_codec_generic snd_hda_intel snd_sof_pci_intel_tgl cros_ec_sensors cros_ec_lid_angle snd_sof_pci_intel_cnl cros_ec_sensors_core xe snd_sof_intel_hda_generic industrialio_triggered_buffer soundwire_intel kfifo_buf snd_sof_intel_hda_sdw_bpt industrialio snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda soundwire_cadence snd_sof_pci snd_sof_xtensa_dsp drm_gpusvm_helper snd_sof gpu_sched snd_sof_utils drm_gpuvm snd_soc_acpi_intel_match drm_ttm_helper snd_soc_acpi_intel_sdca_quirks drm_exec soundwire_generic_allocation drm_suballoc_helper snd_soc_sdw_utils [ 153.264863] snd_soc_acpi soundwire_bus snd_soc_sdca crc8 snd_soc_avs snd_soc_hda_codec snd_hda_ext_core snd_hda_codec snd_hda_core snd_intel_dspcfg snd_intel_sdw_acpi snd_hwdep intel_uncore_frequency intel_uncore_frequency_common snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine binfmt_misc x86_pkg_temp_thermal intel_powerclamp leds_cros_ec snd_pcm cros_ec_debugfs cros_charge_control cros_ec_sensorhub cros_ec_sysfs cros_ec_hwmon cros_ec_chardev gpio_cros_ec led_class_multicolor cmdlinepart coretemp spi_nor snd_seq_midi iwlmvm kvm_intel nls_iso8859_1 mei_pxp mei_hdcp mtd intel_rapl_msr cros_ec_dev mac80211 snd_seq_midi_event i915 uvcvideo kvm btusb libarc4 snd_rawmidi btmtk videobuf2_vmalloc irqbypass processor_thermal_device_pci uvc snd_seq btrtl rapl processor_thermal_device btbcm videobuf2_memops processor_thermal_wt_hint btintel snd_seq_device videobuf2_v4l2 platform_temperature_control processor_thermal_soc_slider drm_buddy intel_cstate videobuf2_common snd_timer bluetooth ttm processor_thermal_rfim iwlwifi [ 153.264957] i2c_i801 mei_me snd drm_display_helper processor_thermal_rapl i2c_smbus spi_intel_pci wmi_bmof intel_rapl_common soundcore i2c_mux spi_intel mei cec processor_thermal_wt_req cfg80211 processor_thermal_power_floor rc_core processor_thermal_mbox i2c_algo_bit igen6_edac platform_profile intel_pmc_core ov13858 int3403_thermal v4l2_fwnode pmt_telemetry int340x_thermal_zone v4l2_async pmt_discovery videodev pmt_class intel_pmc_ssram_telemetry cros_ec_lpcs mc int3400_thermal cros_ec acpi_thermal_rel intel_vsec cros_ec_proto acpi_pad joydev input_leds mac_hid sch_fq_codel nvme_fabrics efi_pstore nfnetlink dm_crypt typec_displayport hid_multitouch hid_generic nvme ucsi_acpi nvme_core typec_ucsi nvme_keyring typec intel_lpss_pci i2c_hid_acpi ghash_clmulni_intel psmouse nvme_auth intel_lpss video i2c_hid hkdf thunderbolt idma64 hid wmi soc_button_array pinctrl_tigerlake serio_raw dm_mirror dm_region_hash dm_log parport_pc lp ppdev msr parport dmi_sysfs autofs4 aesni_intel [ 153.265105] ---[ end trace 0000000000000000 ]--- [ 153.824667] RIP: 0010:folio_mark_dirty+0x2c/0x60 [ 153.824683] Code: 44 00 00 55 48 89 e5 53 48 89 fb e8 7e 14 03 00 48 8b 13 48 85 c0 74 32 f7 c2 00 00 01 00 75 23 48 8b 50 68 48 89 de 48 89 c7 <48> 8b 52 10 2e 2e 2e ff d2 48 8b 5d f8 c9 31 d2 31 f6 31 ff c3 cc [ 153.824688] RSP: 0018:ffffd24fe0907790 EFLAGS: 00010246 [ 153.824692] RAX: ffff8d2eb073c440 RBX: fffff30289c54f80 RCX: 0000000000000000 [ 153.824695] RDX: b231b2318eb98eb9 RSI: fffff30289c54f80 RDI: ffff8d2eb073c440 [ 153.824697] RBP: ffffd24fe0907798 R08: 0000000000000000 R09: 0000000000000000 [ 153.824700] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001 [ 153.824702] R13: 0000000000000001 R14: fffff30289c54f80 R15: fffff30289c54f80 [ 153.824704] FS: 0000000000000000(0000) GS:ffff8d3430b00000(0000) knlGS:0000000000000000 [ 153.824708] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 153.824711] CR2: 000079dc6265c1e1 CR3: 00000002e88d7003 CR4: 0000000000f72ef0 [ 153.824713] PKRU: 55555554 [ 153.824716] note: Lintian prepare[28947] exited with preempt_count 1 ``` -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154305 Title: BUG: unable to handle page fault for address: ffff8d47fd39d5e5 Status in linux package in Ubuntu: New Bug description: "ubuntu-bug linux" failed with "HTTP Error 504: Gateway Time-out" for me. So here you get the bug report manually: When I try to build lintian with sbuild unshare backend, the kernel becomes unhappy: ``` [ 755.351303] BUG: unable to handle page fault for address: ffff8d47fd39d5e5 [ 755.351318] #PF: supervisor read access in kernel mode [ 755.351324] #PF: error_code(0x0000) - not-present page [ 755.351329] PGD 0 P4D 0 [ 755.351337] Oops: Oops: 0000 [#1] SMP NOPTI [ 755.351346] CPU: 3 UID: 100999 PID: 43703 Comm: Lintian prepare Not tainted 7.0.0-15-generic #15-Ubuntu PREEMPT(lazy) [ 755.351353] Hardware name: Framework Laptop 12 (13th Gen Intel Core)/FRAPMACP05, BIOS 03.07 02/10/2026 [ 755.351358] RIP: 0010:dup_mmap+0x184/0x870 [ 755.351370] Code: fd 89 43 04 48 c7 c6 ff ff ff ff 48 8d bd 70 ff ff ff e8 bf 3f ee 00 48 89 c3 48 85 c0 0f 84 fc 05 00 00 48 8b 43 10 8b 53 28 <48> 8b 88 90 01 00 00 83 e1 01 0f 84 a3 05 00 00 3b 90 d0 01 00 00 [ 755.351376] RSP: 0018:ffffd086e249bb68 EFLAGS: 00010282 [ 755.351383] RAX: ffff8d47fd39d455 RBX: ffff8de6e6eb4240 RCX: 0000000000000000 [ 755.351387] RDX: 0000000000000139 RSI: 0000000000000000 RDI: 0000000000000000 [ 755.351391] RBP: ffffd086e249bc70 R08: 0000000000000000 R09: 0000000000000000 [ 755.351395] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8de5801c4d00 [ 755.351399] R13: ffff8de5fd39d400 R14: 0000000000000000 R15: ffff8de8ad0829c0 [ 755.351403] FS: 00007f399ea20bc0(0000) GS:ffff8df53c980000(0000) knlGS:0000000000000000 [ 755.351408] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 755.351412] CR2: ffff8d47fd39d5e5 CR3: 000000041c9f2004 CR4: 0000000000f72ef0 [ 755.351417] PKRU: 55555554 [ 755.351421] Call Trace: [ 755.351425] <TASK> [ 755.351433] dup_mm.constprop.0+0x6f/0x170 [ 755.351443] copy_process+0x162d/0x17c0 [ 755.351453] kernel_clone+0xb6/0x4c0 [ 755.351460] ? handle_pte_fault+0x1d8/0x1f0 [ 755.351466] __do_sys_clone+0x68/0xa0 [ 755.351475] __x64_sys_clone+0x25/0x40 [ 755.351482] x64_sys_call+0x139b/0x2390 [ 755.351489] do_syscall_64+0x115/0x5a0 [ 755.351499] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 [ 755.351507] ? irqentry_exit+0x97/0x5a0 [ 755.351515] ? exc_page_fault+0x94/0x1e0 [ 755.351522] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 755.351528] RIP: 0033:0x7f399eb563e8 [ 755.351535] Code: 7d e0 e8 bb f9 f4 ff 45 31 c0 31 d2 31 f6 64 48 8b 04 25 10 00 00 00 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 68 41 89 c4 85 c0 74 29 48 8d 7d e0 e8 e0 f9 [ 755.351540] RSP: 002b:00007ffd78ea0760 EFLAGS: 00000246 ORIG_RAX: 0000000000000038 [ 755.351546] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f399eb563e8 [ 755.351550] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011 [ 755.351554] RBP: 00007ffd78ea0780 R08: 0000000000000000 R09: 0000000000000000 [ 755.351558] R10: 00007f399ea20e90 R11: 0000000000000246 R12: 0000610f18d10010 [ 755.351562] R13: 0000000000000000 R14: 0000000000000000 R15: 0000610f1cd3e6f0 [ 755.351569] </TASK> [ 755.351571] Modules linked in: overlay snd_seq_dummy rfcomm snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat x_tables nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables bridge stp llc ccm snd_hda_codec_intelhdmi snd_hda_codec_hdmi uhid cmac algif_hash algif_skcipher af_alg qrtr snd_hda_codec_alc269 snd_hda_codec_realtek_lib snd_hda_scodec_component snd_hda_codec_generic snd_hda_intel snd_sof_pci_intel_tgl snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common bnep snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda soundwire_cadence cros_ec_lid_angle cros_ec_sensors snd_sof_pci cros_ec_sensors_core snd_sof_xtensa_dsp industrialio_triggered_buffer snd_sof kfifo_buf snd_sof_utils industrialio xe snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_sdw_utils snd_soc_acpi soundwire_bus drm_gpusvm_helper snd_soc_sdca gpu_sched crc8 drm_gpuvm [ 755.351681] drm_ttm_helper snd_soc_avs drm_exec intel_uncore_frequency snd_soc_hda_codec drm_suballoc_helper intel_uncore_frequency_common binfmt_misc snd_hda_ext_core snd_hda_codec x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_intel_dspcfg coretemp snd_intel_sdw_acpi snd_hwdep snd_soc_core kvm_intel snd_compress nls_iso8859_1 ac97_bus snd_pcm_dmaengine snd_pcm kvm cmdlinepart leds_cros_ec snd_seq_midi spi_nor gpio_cros_ec led_class_multicolor cros_ec_chardev cros_ec_sysfs cros_charge_control cros_ec_sensorhub cros_ec_hwmon cros_ec_debugfs mei_pxp mei_hdcp mtd intel_rapl_msr iwlmvm snd_seq_midi_event irqbypass uvcvideo snd_rawmidi processor_thermal_device_pci cros_ec_dev i915 rapl videobuf2_vmalloc btusb mac80211 uvc processor_thermal_device snd_seq videobuf2_memops btmtk processor_thermal_wt_hint platform_temperature_control btrtl snd_seq_device videobuf2_v4l2 intel_cstate processor_thermal_soc_slider btbcm drm_buddy snd_timer libarc4 videobuf2_common processor_thermal_rfim btintel ttm [ 755.351804] processor_thermal_rapl drm_display_helper bluetooth intel_rapl_common snd i2c_i801 iwlwifi mei_me processor_thermal_wt_req cec i2c_smbus spi_intel_pci processor_thermal_power_floor wmi_bmof mei soundcore i2c_mux spi_intel rc_core cfg80211 processor_thermal_mbox i2c_algo_bit platform_profile igen6_edac ov13858 v4l2_fwnode intel_pmc_core int3403_thermal v4l2_async int340x_thermal_zone pmt_telemetry videodev pmt_discovery pmt_class mc cros_ec_lpcs intel_pmc_ssram_telemetry cros_ec int3400_thermal intel_vsec cros_ec_proto acpi_pad acpi_thermal_rel input_leds joydev mac_hid sch_fq_codel nvme_fabrics efi_pstore nfnetlink dm_crypt typec_displayport hid_multitouch hid_generic nvme ucsi_acpi nvme_core typec_ucsi nvme_keyring gpio_keys typec nvme_auth intel_lpss_pci ghash_clmulni_intel psmouse video i2c_hid_acpi intel_lpss hkdf thunderbolt i2c_hid idma64 hid wmi soc_button_array pinctrl_tigerlake serio_raw dm_mirror dm_region_hash dm_log parport_pc ppdev lp msr parport dmi_sysfs autofs4 aesni_intel [ 755.351954] CR2: ffff8d47fd39d5e5 [ 755.351960] ---[ end trace 0000000000000000 ]--- [ 756.089980] RIP: 0010:dup_mmap+0x184/0x870 [ 756.089993] Code: fd 89 43 04 48 c7 c6 ff ff ff ff 48 8d bd 70 ff ff ff e8 bf 3f ee 00 48 89 c3 48 85 c0 0f 84 fc 05 00 00 48 8b 43 10 8b 53 28 <48> 8b 88 90 01 00 00 83 e1 01 0f 84 a3 05 00 00 3b 90 d0 01 00 00 [ 756.089996] RSP: 0018:ffffd086e249bb68 EFLAGS: 00010282 [ 756.090000] RAX: ffff8d47fd39d455 RBX: ffff8de6e6eb4240 RCX: 0000000000000000 [ 756.090002] RDX: 0000000000000139 RSI: 0000000000000000 RDI: 0000000000000000 [ 756.090003] RBP: ffffd086e249bc70 R08: 0000000000000000 R09: 0000000000000000 [ 756.090005] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8de5801c4d00 [ 756.090006] R13: ffff8de5fd39d400 R14: 0000000000000000 R15: ffff8de8ad0829c0 [ 756.090008] FS: 00007f399ea20bc0(0000) GS:ffff8df53c980000(0000) knlGS:0000000000000000 [ 756.090010] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 756.090011] CR2: ffff8d47fd39d5e5 CR3: 000000041c9f2004 CR4: 0000000000f72ef0 [ 756.090013] PKRU: 55555554 [ 756.090015] note: Lintian prepare[43703] exited with irqs disabled ``` This problem is reproducible. Note: I had other problems with this laptop: https://community.frame.work/t/spontaneous-poweroffs-on-framework- laptop-12/82660 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154305/+subscriptions

[Bug 2154322] [NEW] [UCSI regression] Dell Precision 5570: UCSI_GET_PDOS failed (-5) and USB-C Audio Accessory broken since 7.0.0-15

Public bug reported: # UCSI / USB-C Audio Accessory regression on kernel 7.0.0-15-generic ## Summary Since first boot of kernel **7.0.0-15-generic**, the UCSI ACPI driver reports persistent errors and `/sys/class/typec/port*/supported_accessory_modes` is `none` on all USB-C ports. As a result, USB-C analog headsets (USB-C Audio Accessory mode) that previously worked under kernel **7.0.0-14-generic** are no longer detected at all: the typec partner is registered, but no USB enumeration and no analog accessory routing occurs. Devices implementing the USB-C standard with a built-in USB DAC (e.g. JBL Tune 310C USB-C, USB ID `0ecb:20f6`) still work normally, confirming the regression is specific to the Audio Accessory mode path / UCSI capability reporting. ## System - Machine: Dell Precision 5570 (Alder Lake-P) - BIOS: 1.40.0 (2026-03-31) - Distro: Ubuntu 26.04 (Resolute Raccoon) - Audio stack: PipeWire 1.6.2 + WirePlumber 0.5.13 (not relevant — issue is below the audio stack) - USB-C controllers: Intel Alder Lake-P Thunderbolt 4 USB Controller `8086:461e`, PCH xHCI `8086:51ed` ## Affected kernel - Working: `7.0.0-14-generic` (`linux-image-7.0.0-14-generic` 7.0.0-14.14) - Broken: `7.0.0-15-generic` (`linux-image-7.0.0-15-generic` 7.0.0-15.15) ## Timeline (correlates exactly with kernel upgrade) | Date / time (UTC) | Event | |---|---| | Before 2026-05-17 | Running kernel 7.0.0-14, zero UCSI errors in kern.log, USB-C analog earphones work | | 2026-05-17 17:34 (CEST 19:34) | dpkg installs/upgrades GRUB 2.14, shim-signed, dracut, lvm2, cryptsetup, presumably pulls in `linux-image-7.0.0-15-generic` | | **2026-05-17 19:49 UTC (21:49 CEST)** | **First boot on 7.0.0-15. First UCSI errors appear immediately in kern.log:** | ``` ucsi_acpi USBC000:00: unknown error 0 ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5) ``` These errors then repeat on every boot since. ## Symptoms 1. `UCSI_GET_PDOS failed (-5)` — the kernel cannot query Power Data Objects from the UCSI controller. 2. `/sys/class/typec/port{0,1,2}/supported_accessory_modes` = `none` on all three USB-C ports. 3. USB-C analog headsets (no built-in DAC) plugged into any port: the typec partner is created (`/sys/class/typec/portN-partner` appears) with no advertised alt modes, but no USB enumeration occurs and no audio routing. 4. USB-C devices with their own DAC (USB Audio Class) enumerate and work normally. ## Reproducer 1. Boot kernel 7.0.0-15-generic on a Dell Precision 5570. 2. Plug a USB-C analog headset (no DAC) into any USB-C port (e.g. Wefix HP-2201A "kit piéton USB-C", or any cheap analog USB-C earbud). 3. Observe: - `/sys/class/typec/portN-partner` is created. - No new USB device in `lsusb`. - No new card in `aplay -l` or `/proc/asound/cards`. - `/sys/class/typec/portN/supported_accessory_modes` = `none`. ## Expected behaviour On kernel 7.0.0-14, the same setup detects the headset (or at least properly reports `supported_accessory_modes` so the analog audio routing can happen). ## Workaround Downgrade to `linux-image-7.0.0-14-generic` (still in the `resolute` archive). ## Files to attach - `/var/log/kern.log` (or excerpt from the first boot on 7.0.0-15) - Output of `dmesg | grep -iE 'ucsi|typec'` - Output of `for p in /sys/class/typec/port*; do echo "$p:"; cat $p/supported_accessory_modes 2>/dev/null; done` ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 26 23:51:26 2026 InstallationDate: Installed on 2026-05-17 (9 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Precision 5570 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-15-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 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2026 dmi.bios.release: 1.40 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.40.0 dmi.board.name: 02JH00 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnDellInc.:bvr1.40.0:bd03/31/2026:br1.40:efr1.19:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn02JH00:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154322 Title: [UCSI regression] Dell Precision 5570: UCSI_GET_PDOS failed (-5) and USB-C Audio Accessory broken since 7.0.0-15 Status in linux package in Ubuntu: New Bug description: # UCSI / USB-C Audio Accessory regression on kernel 7.0.0-15-generic ## Summary Since first boot of kernel **7.0.0-15-generic**, the UCSI ACPI driver reports persistent errors and `/sys/class/typec/port*/supported_accessory_modes` is `none` on all USB-C ports. As a result, USB-C analog headsets (USB-C Audio Accessory mode) that previously worked under kernel **7.0.0-14-generic** are no longer detected at all: the typec partner is registered, but no USB enumeration and no analog accessory routing occurs. Devices implementing the USB-C standard with a built-in USB DAC (e.g. JBL Tune 310C USB-C, USB ID `0ecb:20f6`) still work normally, confirming the regression is specific to the Audio Accessory mode path / UCSI capability reporting. ## System - Machine: Dell Precision 5570 (Alder Lake-P) - BIOS: 1.40.0 (2026-03-31) - Distro: Ubuntu 26.04 (Resolute Raccoon) - Audio stack: PipeWire 1.6.2 + WirePlumber 0.5.13 (not relevant — issue is below the audio stack) - USB-C controllers: Intel Alder Lake-P Thunderbolt 4 USB Controller `8086:461e`, PCH xHCI `8086:51ed` ## Affected kernel - Working: `7.0.0-14-generic` (`linux-image-7.0.0-14-generic` 7.0.0-14.14) - Broken: `7.0.0-15-generic` (`linux-image-7.0.0-15-generic` 7.0.0-15.15) ## Timeline (correlates exactly with kernel upgrade) | Date / time (UTC) | Event | |---|---| | Before 2026-05-17 | Running kernel 7.0.0-14, zero UCSI errors in kern.log, USB-C analog earphones work | | 2026-05-17 17:34 (CEST 19:34) | dpkg installs/upgrades GRUB 2.14, shim-signed, dracut, lvm2, cryptsetup, presumably pulls in `linux-image-7.0.0-15-generic` | | **2026-05-17 19:49 UTC (21:49 CEST)** | **First boot on 7.0.0-15. First UCSI errors appear immediately in kern.log:** | ``` ucsi_acpi USBC000:00: unknown error 0 ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5) ``` These errors then repeat on every boot since. ## Symptoms 1. `UCSI_GET_PDOS failed (-5)` — the kernel cannot query Power Data Objects from the UCSI controller. 2. `/sys/class/typec/port{0,1,2}/supported_accessory_modes` = `none` on all three USB-C ports. 3. USB-C analog headsets (no built-in DAC) plugged into any port: the typec partner is created (`/sys/class/typec/portN-partner` appears) with no advertised alt modes, but no USB enumeration occurs and no audio routing. 4. USB-C devices with their own DAC (USB Audio Class) enumerate and work normally. ## Reproducer 1. Boot kernel 7.0.0-15-generic on a Dell Precision 5570. 2. Plug a USB-C analog headset (no DAC) into any USB-C port (e.g. Wefix HP-2201A "kit piéton USB-C", or any cheap analog USB-C earbud). 3. Observe: - `/sys/class/typec/portN-partner` is created. - No new USB device in `lsusb`. - No new card in `aplay -l` or `/proc/asound/cards`. - `/sys/class/typec/portN/supported_accessory_modes` = `none`. ## Expected behaviour On kernel 7.0.0-14, the same setup detects the headset (or at least properly reports `supported_accessory_modes` so the analog audio routing can happen). ## Workaround Downgrade to `linux-image-7.0.0-14-generic` (still in the `resolute` archive). ## Files to attach - `/var/log/kern.log` (or excerpt from the first boot on 7.0.0-15) - Output of `dmesg | grep -iE 'ucsi|typec'` - Output of `for p in /sys/class/typec/port*; do echo "$p:"; cat $p/supported_accessory_modes 2>/dev/null; done` ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 26 23:51:26 2026 InstallationDate: Installed on 2026-05-17 (9 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Precision 5570 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-15-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 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2026 dmi.bios.release: 1.40 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.40.0 dmi.board.name: 02JH00 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnDellInc.:bvr1.40.0:bd03/31/2026:br1.40:efr1.19:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn02JH00:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:pfaPrecision: dmi.product.family: Precision dmi.product.name: Precision 5570 dmi.product.sku: 0B1A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154322/+subscriptions

[Bug 2154244] Re: My computer will have intermittent black screens, and I don‘t know how to report bugs. I hope you‘ll see what’s said below.

*** This bug is a duplicate of bug 2154246 *** https://bugs.launchpad.net/bugs/2154246 ** This bug has been marked a duplicate of bug 2154246 Intermittent black screen -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154244 Title: My computer will have intermittent black screens, and I don‘t know how to report bugs. I hope you‘ll see what’s said below. Status in linux package in Ubuntu: New Bug description: My computer will have intermittent black screens, and I don‘t know how to report bugs. I hope you‘ll see what’s said below. cat /proc/version_signature > version.log sudo lspci -vnvn > lspci-vnvn.log [sudo: authenticate] 密码： pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: kentrl 6710 F.... wireplumber /dev/snd/controlC0: kentrl 6710 F.... wireplumber /dev/snd/seq: kentrl 6691 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 26 10:31:43 2026 InstallationDate: Installed on 2026-05-15 (11 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: MECHREVO WUJIE Series ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=81689f9c-e406-439a-916f-1a710c9d5612 ro quiet splash 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: 02/28/2026 dmi.bios.release: 1.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.10MRO17 dmi.board.asset.tag: Standard dmi.board.name: WUJIE Series-X4HP4NAL dmi.board.vendor: MECHREVO dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: MECHREVO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.10MRO17:bd02/28/2026:br1.17:efr1.33:svnMECHREVO:pnWUJIESeries:pvrStandard:rvnMECHREVO:rnWUJIESeries-X4HP4NAL:rvrStandard:cvnMECHREVO:ct10:cvrStandard:sku0001:pfaHPT_FP8: dmi.product.family: HPT_FP8 dmi.product.name: WUJIE Series dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: MECHREVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154244/+subscriptions

[Bug 2154245] [NEW] My computer will have intermittent black screens

Public bug reported: My computer will have intermittent black screens ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: kentrl 6710 F.... wireplumber /dev/snd/controlC0: kentrl 6710 F.... wireplumber /dev/snd/seq: kentrl 6691 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 26 10:35:38 2026 InstallationDate: Installed on 2026-05-15 (11 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: MECHREVO WUJIE Series ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=81689f9c-e406-439a-916f-1a710c9d5612 ro quiet splash 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: 02/28/2026 dmi.bios.release: 1.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.10MRO17 dmi.board.asset.tag: Standard dmi.board.name: WUJIE Series-X4HP4NAL dmi.board.vendor: MECHREVO dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: MECHREVO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.10MRO17:bd02/28/2026:br1.17:efr1.33:svnMECHREVO:pnWUJIESeries:pvrStandard:rvnMECHREVO:rnWUJIESeries-X4HP4NAL:rvrStandard:cvnMECHREVO:ct10:cvrStandard:sku0001:pfaHPT_FP8: dmi.product.family: HPT_FP8 dmi.product.name: WUJIE Series dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: MECHREVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154245 Title: My computer will have intermittent black screens Status in linux package in Ubuntu: New Bug description: My computer will have intermittent black screens ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: kentrl 6710 F.... wireplumber /dev/snd/controlC0: kentrl 6710 F.... wireplumber /dev/snd/seq: kentrl 6691 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue May 26 10:35:38 2026 InstallationDate: Installed on 2026-05-15 (11 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: MECHREVO WUJIE Series ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=81689f9c-e406-439a-916f-1a710c9d5612 ro quiet splash 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: 02/28/2026 dmi.bios.release: 1.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.10MRO17 dmi.board.asset.tag: Standard dmi.board.name: WUJIE Series-X4HP4NAL dmi.board.vendor: MECHREVO dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: MECHREVO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.10MRO17:bd02/28/2026:br1.17:efr1.33:svnMECHREVO:pnWUJIESeries:pvrStandard:rvnMECHREVO:rnWUJIESeries-X4HP4NAL:rvrStandard:cvnMECHREVO:ct10:cvrStandard:sku0001:pfaHPT_FP8: dmi.product.family: HPT_FP8 dmi.product.name: WUJIE Series dmi.product.sku: 0001 dmi.product.version: Standard dmi.sys.vendor: MECHREVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154245/+subscriptions

[Bug 2153976] Re: Fix graceful fault handling after FPU softirq changes causes hard freeze on EFI runtime calls

** Changed in: linux (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux-oem-6.17 (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153976 Title: Fix graceful fault handling after FPU softirq changes causes hard freeze on EFI runtime calls Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: Confirmed Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Running `sudo fwts uefirttime` on HP systems (CID: 202511-38089, 202511-38088, 02511-38091, 202511-38068, 202511-38069) with 6.17 causes a hardsystem freeze. The machine becomes unreachable by ping/SSH and requires a hardpower cycle. Root cause: commit d02198550423 ("x86/fpu: Improve crypto performance by making kernel-mode FPU reliably usable in softirqs") changed kernel_fpu_begin() to use local_bh_disable() instead of preempt_disable(). This sets SOFTIRQ_OFFSET in preempt_count during EFI runtime calls, making in_interrupt() return true in normal task context. The EFI graceful page fault handler efi_crash_gracefully_on_page_fault() uses in_interrupt() to bail out for faults in real interrupt context. With SOFTIRQ_OFFSET now set, the handler always bails out, leaving firmware page faults unhandled. This escalates to die() which also sees in_interrupt() as true and calls panic("Fatal exception in interrupt"), freezing the system. [Fix] Replace in_interrupt() with !in_task() in efi_crash_gracefully_on_page_fault(). This preserves the original intent of bailing for interrupts or NMI faults, while no longer falsely triggering from the FPU code path's local_bh_disable(). [Test Plan] 1. Boot affected HP machine with the patched 6.17-oem kernel. 2. Run:    $ sudo fwts uefirttime Without patch: system hard-freezes, requires power cycle. With patch: fwts completes (pass or fail), system remains responsive. [Where problems could occur] The change is in the EFI page fault handler (arch/x86/platform/efi/quirks.c). If !in_task() incorrectly identifies a real interrupt-context fault as task context, the handler would try to process it as an EFI firmware fault instead of letting the normal oops path handle it. This could mask real kernel bugs during interrupt-context EFI faults, though such faults are extremely rare. Also, a softirq taken between efi_rts_work.efi_rts_id assignment and the fpregs_lock() call could cause a page fault that gets misidentified. The use of !in_task() (which incorporates in_serving_softirq()) handles this window correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153976/+subscriptions

[Bug 2101816] Re: [amdgpu] Crash with SIGABRT in amdgpu_ctx_set_sw_reset_status() from amdgpu_cs_submit_ib() from util_queue_thread_func() from impl_thrd_routine() from start_thread()

** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Opinion ** Changed in: xwayland (Ubuntu) Status: Triaged => Opinion ** Changed in: mutter (Ubuntu) Status: Triaged => Opinion -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2101816 Title: [amdgpu] Crash with SIGABRT in amdgpu_ctx_set_sw_reset_status() from amdgpu_cs_submit_ib() from util_queue_thread_func() from impl_thrd_routine() from start_thread() Status in Mesa: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Opinion Status in xwayland package in Ubuntu: Opinion Status in gnome-shell package in Fedora: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 48~beta-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/fb85627cf28fc2fa707952f5c3c1a887e8f2b5fb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2101816/+subscriptions