** 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
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1110.117)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1110.117) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (amd64, armhf, i386) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-470-server/unknown (amd64) nvidia-graphics-drivers-525/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 Aaron, Do we have progress on the investigation? Thanks. -- 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 2126938] Re: network daemon cannot change link-offloading settings
Based on the analysis, it does not sound like there is anything to do in systemd. ** Changed in: systemd (Ubuntu) Status: Incomplete => 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: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Questing: New 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 2150640] Re: Installer fails internally with a RSync error due to page fault
Hello @acelankao, I have not done any work. I am just trying to figure how we're going to test this from an installer's standpoint. Please let me know if I can help. Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150640 Title: Installer fails internally with a RSync error due to page fault Status in subiquity: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: New Bug description: During install, subiquity calls RSync. But sometimes, at random, RSync fails with a kernel page error: Apr 28 14:22:11 ubuntu subiquity_log.3304[7458]: Running command ['rsync', '-aXHAS', '--one-file-system', '/tmp/tmpmfrhpjlr/mount/', '.'] with allowed return codes [0] (capture=False) Apr 28 14:22:11 ubuntu kernel: BUG: unable to handle page fault for address: ffffffff825c9290 Apr 28 14:22:11 ubuntu kernel: #PF: supervisor read access in kernel mode Apr 28 14:22:11 ubuntu kernel: #PF: error_code(0x0000) - not-present page Apr 28 14:22:11 ubuntu kernel: PGD 1cfe47067 P4D 1cfe47067 PUD 1cfe48063 PMD 0 Apr 28 14:22:11 ubuntu kernel: Oops: Oops: 0000 [#2] SMP NOPTI Apr 28 14:22:11 ubuntu kernel: CPU: 8 UID: 0 PID: 7495 Comm: rsync Tainted: P D O 7.0.0-14-generic #14-Ubuntu PREEMPT(lazy) Apr 28 14:22:11 ubuntu kernel: Tainted: [P]=PROPRIETARY_MODULE, [D]=DIE, [O]=OOT_MODULE Apr 28 14:22:11 ubuntu kernel: Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Apr 28 14:22:11 ubuntu kernel: RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] Apr 28 14:22:11 ubuntu kernel: Code: 41 08 48 89 ce e8 28 49 ff ff 48 8b 4d d0 41 89 ce 48 81 f9 00 f0 ff ff 0f 87 f5 fe ff ff 48 89 4b 08 49 8b 55 08 48 83 c1 10 <4c> 8b 39 48 85 d2 7e 21 49 39 cf 74 1c 31 c0 eb 0c 0f 1f 80 00 00 Apr 28 14:22:11 ubuntu kernel: RSP: 0018:ffffd4ec8278bca8 EFLAGS: 00010286 Apr 28 14:22:11 ubuntu kernel: RAX: 0000000000000000 RBX: ffff8de0a4a7a780 RCX: ffffffff825c9290 Apr 28 14:22:11 ubuntu kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Apr 28 14:22:11 ubuntu kernel: RBP: ffffd4ec8278bce8 R08: 0000000000000000 R09: 0000000000000000 Apr 28 14:22:11 ubuntu kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8de110301ec0 Apr 28 14:22:11 ubuntu kernel: R13: ffffd4ec8278bdc0 R14: 00000000825c9280 R15: ffff8de0821af238 Apr 28 14:22:11 ubuntu kernel: FS: 00007fe1b1fd9100(0000) GS:ffff8de224a00000(0000) knlGS:0000000000000000 Apr 28 14:22:11 ubuntu kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 28 14:22:11 ubuntu kernel: CR2: ffffffff825c9290 CR3: 00000001cb64f000 CR4: 0000000000750ef0 Apr 28 14:22:11 ubuntu kernel: PKRU: 55555554 Apr 28 14:22:11 ubuntu kernel: Call Trace: Apr 28 14:22:11 ubuntu kernel: <TASK> Apr 28 14:22:11 ubuntu kernel: ovl_iterate+0xd3/0x120 [overlay] Apr 28 14:22:11 ubuntu kernel: ? __pfx_ovl_iterate+0x10/0x10 [overlay] Apr 28 14:22:11 ubuntu kernel: wrap_directory_iterator+0x4f/0x80 Apr 28 14:22:11 ubuntu kernel: shared_ovl_iterate+0x15/0x30 [overlay] Apr 28 14:22:11 ubuntu kernel: iterate_dir+0xc1/0x2a0 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: __x64_sys_getdents64+0x76/0x140 Apr 28 14:22:11 ubuntu kernel: ? __pfx_filldir64+0x10/0x10 Apr 28 14:22:11 ubuntu kernel: x64_sys_call+0x100b/0x2390 Apr 28 14:22:11 ubuntu kernel: do_syscall_64+0x115/0x5a0 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? handle_mm_fault+0x1c0/0x2e0 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100 Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? irqentry_exit+0x97/0x5a0 Apr 28 14:22:11 ubuntu subiquity_log.3304[7458]: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] Apr 28 14:22:11 ubuntu kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Apr 28 14:22:11 ubuntu kernel: ? exc_page_fault+0x94/0x1e0 Apr 28 14:22:11 ubuntu kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e Apr 28 14:22:11 ubuntu kernel: RIP: 0033:0x7fe1b20d07d7 Apr 28 14:22:11 ubuntu kernel: Code: 11 00 64 c7 00 16 00 00 00 31 c0 eb 9f e8 61 ec 04 00 90 f3 0f 1e fa b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 01 b6 11 00 f7 d8 64 89 02 48 Apr 28 14:22:11 ubuntu kernel: RSP: 002b:00007ffc5f3161c8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9 Apr 28 14:22:11 ubuntu kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe1b20d07d7 Apr 28 14:22:11 ubuntu kernel: RDX: 0000000000008000 RSI: 00005d8aff7c8d80 RDI: 0000000000000003 Apr 28 14:22:11 ubuntu kernel: RBP: 00007ffc5f316200 R08: 00005d8aff7c8d54 R09: 00007fe1b21ecac8 Apr 28 14:22:11 ubuntu kernel: R10: 0000000000008040 R11: 0000000000000293 R12: 0000000000000001 Apr 28 14:22:11 ubuntu kernel: R13: 00005d8aff7c8d50 R14: 00007ffc5f316300 R15: 00007fe1b1fd90b0 Apr 28 14:22:11 ubuntu kernel: </TASK> Apr 28 14:22:11 ubuntu kernel: Modules linked in: bcache btrfs libblake2b ufs qnx4 hfsplus hfs minix msdos jfs nls_ucs2_utils xfs snd_seq_dummy snd_hrtimer qrtr binfmt_misc zfs(PO) spl(O) snd_hda_codec_generic intel_rapl_msr snd_hda_intel intel_rapl_common snd_hda_codec snd_hda_core snd_intel_dspcfg snd_intel_sdw_acpi snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_amd ccp snd_seq snd_seq_device kvm snd_timer irqbypass snd soundcore i2c_piix4 qxl i2c_smbus drm_ttm_helper ttm input_leds joydev drm_exec mac_hid sch_fq_codel lp ppdev parport_pc parport msr efi_pstore nfnetlink dmi_sysfs qemu_fw_cfg virtiofs vmw_vsock_virtio_transport vmw_vsock_virtio_transport_common vsock autofs4 overlay isofs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 linear 8139too psmouse floppy ghash_clmulni_intel vga16fb serio_raw 8139cp vgastate mii pata_acpi aesni_intel Apr 28 14:22:11 ubuntu kernel: CR2: ffffffff825c9290 Apr 28 14:22:11 ubuntu kernel: ---[ end trace 0000000000000000 ]--- Apr 28 14:22:11 ubuntu kernel: RIP: 0010:ovl_iterate_merged+0x1d8/0x2b0 [overlay] Apr 28 14:22:11 ubuntu kernel: Code: 41 08 48 89 ce e8 28 49 ff ff 48 8b 4d d0 41 89 ce 48 81 f9 00 f0 ff ff 0f 87 f5 fe ff ff 48 89 4b 08 49 8b 55 08 48 83 c1 10 <4c> 8b 39 48 85 d2 7e 21 49 39 cf 74 1c 31 c0 eb 0c 0f 1f 80 00 00 Apr 28 14:22:11 ubuntu kernel: RSP: 0018:ffffd4ec88763b88 EFLAGS: 00010286 Apr 28 14:22:11 ubuntu kernel: RAX: 0000000000000000 RBX: ffff8de082540940 RCX: ffffffff825c9290 Apr 28 14:22:11 ubuntu kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Apr 28 14:22:11 ubuntu kernel: RBP: ffffd4ec88763bc8 R08: 0000000000000000 R09: 0000000000000000 Apr 28 14:22:11 ubuntu kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8de13c0df080 Apr 28 14:22:11 ubuntu kernel: R13: ffffd4ec88763ca0 R14: 00000000825c9280 R15: ffff8de0821af0f8 Apr 28 14:22:11 ubuntu kernel: FS: 00007fe1b1fd9100(0000) GS:ffff8de224a00000(0000) knlGS:0000000000000000 Apr 28 14:22:11 ubuntu kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Apr 28 14:22:11 ubuntu kernel: CR2: ffffffff825c9290 CR3: 00000001cb64f000 CR4: 0000000000750ef0 Apr 28 14:22:11 ubuntu kernel: PKRU: 55555554 Apr 28 14:22:11 ubuntu kernel: note: rsync[7495] exited with irqs disabled Apr 28 14:22:11 ubuntu subiquity_log.3304[7458]: rsync error: error in rsync protocol data stream (code 12) at io.c(232) [Receiver=3.4.1] To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2150640/+subscriptions
[Bug 2150196] Update Released
The verification of the Stable Release Update for alsa-ucm-conf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150196 Title: [SRU] ASoC: enable rt1320 speaker amp and DMIC on PTL SoundWire platforms Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.17 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Noble: Fix Released Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Released Status in alsa-ucm-conf source package in Questing: Fix Released Status in linux source package in Questing: Won't Fix Status in linux-oem-6.17 source package in Questing: Invalid Status in alsa-ucm-conf source package in Resolute: Fix Released Status in linux source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: Invalid Status in alsa-ucm-conf source package in Stonking: Fix Released Status in linux source package in Stonking: Fix Committed Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: SRU Justification: [ Impact ] Lenovo PTL systems with rt722 headset codec + rt1320 speaker amp over SoundWire have no speaker audio and no DMIC. The kernel's PTL match table lacks the rt722_l0_rt1320_l23 topology, the rt1320 codec_info_list is missing its DMIC dai, and the is_amp flag is absent -- so the machine driver never matches and the wrong name prefix is assigned. [ Fix ] Seven upstream commits from Linus's mainline, applied in topological order: 1. 38ecd1384079 (v6.19) -- add ptl_rt722_l0_rt1320_l23 match table entry 2. 4fbd3b2ec04d (v7.0) -- use aggregated endpoints for rt722 in that entry 3. 403a0591be68 (v6.19) -- fix name_prefix of second rt1320 (rt1320-2) 4. 754b3dade5dd (v7.0) -- drop rt721 monolithic match tables (prerequisite for 5) 5. 9033f7b7f27d (linux/master, not yet tagged) -- drop rt722 monolithic match tables 6. dd4a1963ddf0 (linux/master, not yet tagged) -- add is_amp flag to fix wrong name prefix 7. ae2cb3384337 (linux/master, not yet tagged) -- add rt1320/rt1321 DMIC dai in codec_info_list All cherry-pick cleanly with zero conflicts. Diffs are byte-identical to upstream (only hunk offsets and context lines differ due to different base tree). [ Test Plan ] On a Lenovo PTL system with spk:rt1320 + hs:rt722: 1. Boot without patches: no speaker sound card components, no DMIC 2. Boot with patches: - Speaker playback: aplay -D hw:0,2 tone.wav - DMIC loopback: play 1kHz tone through speaker, record from DMIC, FFT confirms peak at 1000 Hz - WirePlumber sees all devices - Mute LEDs functional (speaker and mic) - Suspend/resume: full status diff pre vs post identical, loopback and LEDs work after resume [ Where problems could occur ] Patches touch PTL match tables, SoundWire codec_info_list, and SOF HDA codec matching. A wrong match table entry could cause a different PTL topology to break (wrong codec matched). The is_amp flag override in find_acpi_adr_device() runs for all SoundWire codecs on Intel SOF platforms -- if the flag logic is wrong, non-amp codecs could get misidentified, breaking name prefixes and DAI routing. Commits 4-5 remove rt721/rt722 monolithic match tables; any PTL machine still relying on monolithic matching (rather than function topologies) would lose its match entry. [ Other Info ] Commits 5-7 are merged on linux/master but not yet in a tagged release. Tested on two Lenovo PTL machines -- full audio pass including loopback and suspend/resume. Target: oem-6.17 and resolute only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2150196/+subscriptions
понедельник
[Bug 2126938] Re: network daemon cannot change link-offloading settings
@Christian I have fixed this issue as part of the PR - https://github.com/canonical/netplan/pull/591 The test passes now. In the next release, the patch shall not be required. Thanks! -- 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: Confirmed Status in systemd package in Ubuntu: Incomplete Status in linux source package in Questing: New 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