[РЕШЕНО] Ошибка № ...

воскресенье

[Bug 2153155] Re: Fix bad audio record quality when volume above 50% on Framework PTL

This bug is awaiting verification that the linux-nvidia- bos/7.0.0-2016.16 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-nvidia-bos' to 'verification-done-resolute-linux-nvidia-bos'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia-bos' to 'verification-failed-resolute-linux-nvidia-bos'. 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-nvidia-bos-v2 verification-needed-resolute-linux-nvidia-bos -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153155 Title: Fix bad audio record quality when volume above 50% on Framework PTL Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New 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: [Impact] Framework PTL platform with Realtek ALC295 audio solution will have audio recording quality when the input volume is configure > 50%. [Fix] Fix by backporting the commit: 67c738152207 ("67c738152207") which fix mic boost on particular SSIDs of the Framework machines [Test Case] 1. Boot up the machine of new Framework PTL platforms with Realtek ALC295 audio solution 2. Go to g-s-d and select sound --> input (Internal Microphone) --> Adjust the input volume > 50% 3. Do `arecord` with the internal microphone and play the recorded clips. [Where problems could occur] It only limit the mic boost based on particular SSIDs. The risk of regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2153155/+subscriptions

[Bug 2154174] Re: resolute ubuntu_kernel_selftests:seccomp_build test compilation issue

[Bug 2154343] Re: ubuntu_bpf: FTBFS with clang 23 / gcc 15

This bug is awaiting verification that the linux-nvidia/7.0.0-1016.16 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-nvidia' to 'verification-done- resolute-linux-nvidia'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia' to 'verification-failed- resolute-linux-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-v2 verification-needed-resolute-linux-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154343 Title: ubuntu_bpf: FTBFS with clang 23 / gcc 15 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Released Bug description: [Impact] tools/testing/selftests/bpf/prog_tests/fexit_bpf2bpf.c:117:12: error: assigning to 'char *' from 'const char *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] [Fix] Apply the upstream fix: ``` commit ca0f39a369c5f927c3d004e63a5a778b08a9df94 Author: Varun R Mallya <varunrmallya@gmail.com> Date: Fri Mar 6 03:51:32 2026 +0530 selftests/bpf: Fix const qualifier warning in fexit_bpf2bpf.c Building selftests with clang 23.0.0 (6fae863eba8a72cdd82f37e7111a46a70be525e0) triggers the following error: tools/testing/selftests/bpf/prog_tests/fexit_bpf2bpf.c:117:12: error: assigning to 'char *' from 'const char *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers] The variable `tgt_name` is declared as `char *`, but it stores the result of strstr(prog_name[i], "/"). Since `prog_name[i]` is a `const char *`, the returned pointer should also be treated as const-qualified. Update `tgt_name` to `const char *` to match the type of the underlying string and silence the compiler warning. ``` [How to reproduce] Run test again after applying the patch [Regression potential] Low: clean upstream cherry-pick for a known issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2154343/+subscriptions

[Bug 2156312] Re: Internal display black screen on Intel Lunar Lake with eDP panel

This bug is awaiting verification that the linux-nvidia/7.0.0-1016.16 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-nvidia' to 'verification-done- resolute-linux-nvidia'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia' to 'verification-failed- resolute-linux-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-v2 verification-needed-resolute-linux-nvidia -- 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: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: Fix Released 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 2156556] Re: Fix no audio from right built-in speaker on HP ZBook with TAS2781 amplifier

This bug is awaiting verification that the linux-nvidia/7.0.0-1016.16 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-nvidia' to 'verification-done- resolute-linux-nvidia'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia' to 'verification-failed- resolute-linux-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-v2 verification-needed-resolute-linux-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156556 Title: Fix no audio from right built-in speaker on HP ZBook with TAS2781 amplifier Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: New 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: New Bug description: [Impact] The TI TAS2781 smart amp fails to initialize when connected over SPI on the new HP HP ZBook. The right built-in speaker will fail to output after reboot [Fix] Two changes in one commit: 1. Always run the software reset sequence for the amp, not just in the no-gpio path. This resets device-0 even when its hardware reset pin has no effect. 2. Ignore -EXDEV during block processing when the device is on SPI. The driver keeps iterating through the blocks and adds up the total block size correctly. Upstream commit (in tiwai/sound for-next, not yet in a released tag): 513480da5e9c ALSA: hda/tas2781: Fix device-0 reset issue and handle -EXDEV in block data processing https://patch.msgid.link/20260609105253.19510-1-baojun.xu@ti.com [Test Plan] On HP Zbook with a TAS2781 amp connected over SPI: $ dmesg | grep -i tas2781 Play audio: $ speaker-test -c 2 -t wav Without patch: dmesg shows "dev sw-reset fail" or "process_block: single write error" / "bulk_write error". No sound from the TAS2781 speakers. With patch: no reset or block errors in dmesg. Speakers play sound. [Where problems could occur] The reset change now runs the software reset on every path, including the gpio reset path. If the software reset is wrong for some amp, the device could fail to come up and stay silent. Both changes are amp init only, so a regression would show up as no sound on TAS2781 SPI systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156556/+subscriptions

[Bug 2156559] Re: Fix no sound output device on Dell GhostRider PTL no camera SKU

This bug is awaiting verification that the linux-nvidia/7.0.0-1016.16 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-nvidia' to 'verification-done- resolute-linux-nvidia'. If the problem still exists, change the tag 'verification-needed-resolute-linux-nvidia' to 'verification-failed- resolute-linux-nvidia'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-resolute-linux-nvidia-v2 verification-needed-resolute-linux-nvidia -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156559 Title: Fix no sound output device on Dell GhostRider PTL no camera SKU Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Fix Committed Bug description: [Impact] SoundWire audio can come up with the wrong topology on Intel SOF systems. Playback or capture paths may not work as expected. Intel SoundWire (SDW) audio codecs may load the wrong topology. [Fix] Always append the dai_type to the DAI link and stream name. Upstream commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai link name unconditionally") fix this problem [Test Plan] On the Dell GhostRider PTL no Camera SKU: $ dmesg | grep -i sof $ aplay -l $ arecord -l Play and record audio: $ speaker-test -c 2 -t wav $ arecord -d 5 -f cd /tmp/test.wav && aplay /tmp/test.wav Without patch: wrong or missing topology selection on some configs; playback or capture path does not work as expected. With patch: correct topology loads; playback and capture work. [Where problems could occur] The change makes the dai_type suffix unconditional and drops the old name format. If a topology file still expects the old non-suffixed stream name, partial matching could miss and that topology would fail to bind. The change is limited to DAI link naming in one board driver, so a regression would be no/incorrect audio, not a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156559/+subscriptions

[Bug 2161834] [NEW] asus_wmi: Fn Lock state resets on reboot and cannot be observed from userspace

Public bug reported: Hardware and software --------------------- System: ASUSTeK COMPUTER INC. ZenBook UX325UA/UM325UA, revision 1.0 BIOS: UX325UA.306 (2025-02-19) Ubuntu: Ubuntu 26.04 LTS Kernel on which the issue was reproduced: 7.0.0-28-generic Ubuntu kernel source package: linux-source-7.0.0 7.0.0-28.28 Expected behavior ----------------- Linux should provide a supported way to read and restore the last physical Fn Lock state selected with Fn+Esc, so that userspace can persist that state across boots. Windows on this laptop remembers/restores the selected state. Original behavior with the stock Ubuntu kernel ---------------------------------------------- The stock asus_wmi driver does not expose its current Fn Lock state through a supported userspace interface. At module probe it unconditionally initializes its private fnlock_locked state from the read-only fnlock_default module parameter (true by default) and calls the ASUS WMI device setter. A physical Fn+Esc press changes the state for the running session, but the selected state cannot be learned and restored reliably across the next module probe or boot. The relevant firmware interface is ASUS WMI device 0x00100023. Physical Fn+Esc produces ASUS WMI notification 0x4e. asus_wmi handles and consumes that notification internally: it toggles its private fnlock_locked value and calls the firmware setter, then returns without reporting an input key. Captures from the "Asus WMI hotkeys" evdev device showed ordinary ASUS hotkeys but no Fn+Esc event. Consequently, a normal userspace key watcher cannot solve this. It cannot observe notification 0x4e through evdev, cannot read the driver's private state, and cannot explicitly set that state through a supported runtime interface. The read-only fnlock_default parameter can only choose a fixed probe-time value; it cannot implement "remember the last physical selection." Concise reproduction using the original stock driver ---------------------------------------------------- 1. Boot Ubuntu 26.04 with its stock 7.0.0-28-generic asus_wmi module and no fnlock_default override. 2. Note whether F1-F12 or the alternate media actions are active without Fn. 3. Press physical Fn+Esc and verify that the mode changes for the running session. 4. Monitor the "Asus WMI hotkeys" input device while pressing Fn+Esc; no corresponding evdev key event is produced. 5. Reboot. The driver again applies its fixed fnlock_default value at probe instead of restoring the state selected in step 3. Investigation and proof of concept ---------------------------------- The original problem was reproduced and investigated with the stock Ubuntu driver before any workaround was installed. A local DKMS proof of concept was then built from Ubuntu's matching asus_wmi source. It exposes the driver's current state, accepts explicit 0 or 1 writes, and notifies a userspace watcher after a successful physical Fn+Esc transition. A root-only service can thereby persist the resulting state and restore it later. Testing confirmed that the driver state can be exposed and managed safely without synthesizing key input or accessing undocumented hardware registers. The currently running system does contain that local out-of-tree DKMS replacement and its local persistence services. It will therefore be visible in the Apport data attached to this report. It is evidence and a proof of concept only; it is not a proposed Ubuntu packaging solution, and the original stock-kernel finding predates its installation. No EFI variables, Windows partitions, firmware/BIOS settings, DSDT overrides, or raw embedded-controller registers were changed during the investigation. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 21:32:58 2026 InstallationDate: Installed on 2024-12-18 (584 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX325UA_UM325UA ProcFB: 0 amdgpudrmfb SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-04 (82 days ago) dmi.bios.date: 02/19/2025 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX325UA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX325UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX325UA.306:bd02/19/2025:br5.19:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX325UA_UM325UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX325UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaZenBook: dmi.product.family: ZenBook dmi.product.name: ZenBook UX325UA_UM325UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** 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/2161834 Title: asus_wmi: Fn Lock state resets on reboot and cannot be observed from userspace Status in linux package in Ubuntu: New Bug description: Hardware and software --------------------- System: ASUSTeK COMPUTER INC. ZenBook UX325UA/UM325UA, revision 1.0 BIOS: UX325UA.306 (2025-02-19) Ubuntu: Ubuntu 26.04 LTS Kernel on which the issue was reproduced: 7.0.0-28-generic Ubuntu kernel source package: linux-source-7.0.0 7.0.0-28.28 Expected behavior ----------------- Linux should provide a supported way to read and restore the last physical Fn Lock state selected with Fn+Esc, so that userspace can persist that state across boots. Windows on this laptop remembers/restores the selected state. Original behavior with the stock Ubuntu kernel ---------------------------------------------- The stock asus_wmi driver does not expose its current Fn Lock state through a supported userspace interface. At module probe it unconditionally initializes its private fnlock_locked state from the read-only fnlock_default module parameter (true by default) and calls the ASUS WMI device setter. A physical Fn+Esc press changes the state for the running session, but the selected state cannot be learned and restored reliably across the next module probe or boot. The relevant firmware interface is ASUS WMI device 0x00100023. Physical Fn+Esc produces ASUS WMI notification 0x4e. asus_wmi handles and consumes that notification internally: it toggles its private fnlock_locked value and calls the firmware setter, then returns without reporting an input key. Captures from the "Asus WMI hotkeys" evdev device showed ordinary ASUS hotkeys but no Fn+Esc event. Consequently, a normal userspace key watcher cannot solve this. It cannot observe notification 0x4e through evdev, cannot read the driver's private state, and cannot explicitly set that state through a supported runtime interface. The read-only fnlock_default parameter can only choose a fixed probe-time value; it cannot implement "remember the last physical selection." Concise reproduction using the original stock driver ---------------------------------------------------- 1. Boot Ubuntu 26.04 with its stock 7.0.0-28-generic asus_wmi module and no fnlock_default override. 2. Note whether F1-F12 or the alternate media actions are active without Fn. 3. Press physical Fn+Esc and verify that the mode changes for the running session. 4. Monitor the "Asus WMI hotkeys" input device while pressing Fn+Esc; no corresponding evdev key event is produced. 5. Reboot. The driver again applies its fixed fnlock_default value at probe instead of restoring the state selected in step 3. Investigation and proof of concept ---------------------------------- The original problem was reproduced and investigated with the stock Ubuntu driver before any workaround was installed. A local DKMS proof of concept was then built from Ubuntu's matching asus_wmi source. It exposes the driver's current state, accepts explicit 0 or 1 writes, and notifies a userspace watcher after a successful physical Fn+Esc transition. A root-only service can thereby persist the resulting state and restore it later. Testing confirmed that the driver state can be exposed and managed safely without synthesizing key input or accessing undocumented hardware registers. The currently running system does contain that local out-of-tree DKMS replacement and its local persistence services. It will therefore be visible in the Apport data attached to this report. It is evidence and a proof of concept only; it is not a proposed Ubuntu packaging solution, and the original stock-kernel finding predates its installation. No EFI variables, Windows partitions, firmware/BIOS settings, DSDT overrides, or raw embedded-controller registers were changed during the investigation. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 21:32:58 2026 InstallationDate: Installed on 2024-12-18 (584 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX325UA_UM325UA ProcFB: 0 amdgpudrmfb SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-04 (82 days ago) dmi.bios.date: 02/19/2025 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX325UA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX325UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.6 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX325UA.306:bd02/19/2025:br5.19:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX325UA_UM325UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX325UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaZenBook: dmi.product.family: ZenBook dmi.product.name: ZenBook UX325UA_UM325UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161834/+subscriptions

[Bug 2161821] Re: amdgpu: RX 7900 XTX fans dont poweroff regression in 7.0.0-28, 7.0.0-27 good

** Summary changed: - amdgpu: RX 7900 XTX fans spin up on poweroff regression in 7.0.0-28, 7.0.0-27 good + amdgpu: RX 7900 XTX fans dont poweroff regression in 7.0.0-28, 7.0.0-27 good ** Summary changed: - amdgpu: RX 7900 XTX fans dont poweroff regression in 7.0.0-28, 7.0.0-27 good + amdgpu: RX 7900 XTX fans spin in S5 (soft-off) regression in 7.0.0-28, 7.0.0-27 good -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161821 Title: amdgpu: RX 7900 XTX fans spin in S5 (soft-off) regression in 7.0.0-28, 7.0.0-27 good Status in linux package in Ubuntu: New Bug description: On shutdown, the RX 7900 XTX fans spin up and continue running while the system is in S5 (soft-off). The rest of the machine powers down correctly, confirmed by the fact that switching off the PSU stops the fans, so this is standby-rail behaviour, not a shutdown hang. Regression, bisected between Ubuntu kernel builds: 7.0.0-27-generic — GOOD (fans stop on poweroff) 7.0.0-28-generic — BAD (fans spin in S5) Reproducible both directions, multiple cycles each. Hardware: Ryzen 7 7600X, ASRock B850I Lightning WiFi. Two amdgpu-bound devices present: RX 7900 XTX (03:00.0, DCN 3.2) as the discrete/display GPU, plus the Raphael iGPU (0b:00.0, DCN 3.1.5), which amdgpu still fully initialises. Poweroff teardown covers both. Not yet tested on mainline; willing to test a mainline kernel to confirm whether this is an Ubuntu-delta regression or upstream, if a triager wants that. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jul 26 18:11:16 2026 InstallationDate: Installed on 2025-11-07 (261 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) IwDevWlp7s0Link: Not connected. MachineType: ASRock B850I Lightning WiFi ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=b80b57ad-ad0b-4866-844f-72c840a6557d ro quiet splash maxcpus=12 smt=on nvme_core.io_timeout=4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-02-15 (161 days ago) dmi.bios.date: 12/11/2025 dmi.bios.release: 5.40 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 4.03 dmi.board.asset.tag: Default string dmi.board.name: B850I Lightning 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.03:bd12/11/2025:br5.40:svnASRock:pnB850ILightningWiFi:pvrDefaultstring:rvnASRock:rnB850ILightningWiFi:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: B850I Lightning 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/2161821/+subscriptions

[Bug 2161831] [NEW] iwlwifi (AX101/so-a0-hr-b0/fw 89) NMI_INTERRUPT_UMAC_FATAL firmware assert on 5 GHz DFS channels

Public bug reported: Title: iwlwifi (AX101 / so-a0-hr-b0 / fw 89) — reproducible NMI_INTERRUPT_UMAC_FATAL firmware assert on 5 GHz DFS channels: 293 asserts / 50 boots over 11 months, 84% clustered 20:00–24:00, peak at 21:00 ================================================================================ SUMMARY ================================================================================ The iwlwifi firmware reproducibly asserts (NMI_INTERRUPT_UMAC_FATAL / ADVANCED_SYSASSERT) when associated to an AP on a 5 GHz DFS channel, cascading into a device-reset storm ("Too many device errors - delay next reset") and a full desktop freeze requiring a hard power-cycle. Over 11 months of daily use: 293 asserts across 50 boots (2025-08-15 → 2026-07-26), with 84% occurring between 20:00–24:00 local and 53% at the 21:00 hour alone — consistent with elevated evening DFS radar activity. Zero asserts on non-DFS channels or 2.4 GHz. ================================================================================ HARDWARE ================================================================================ - Laptop: ASUS Vivobook X1504VA - CPU: Intel Core i3-1315U (Raptor Lake-U, 13th Gen) - Wi-Fi: Intel AX101 CNVi, PCI 0000:00:14.3, RF module so-a0-hr-b0 (HR1 B3) ================================================================================ SOFTWARE ================================================================================ - OS: Ubuntu 26.04 (development branch) - Kernel: 7.0.0-28-generic - Driver: iwlwifi / iwlmvm - Firmware: iwlwifi-so-a0-hr-b0-89.ucode, version 89.123cf747.0 (latest available; driver requests API 89 only, no fallback) ================================================================================ ASSERT SIGNATURES ================================================================================ iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL iwlwifi 0000:00:14.3: 0x2010120E | ADVANCED_SYSASSERT iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0 iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE iwlwifi 0000:00:14.3: Too many device errors - delay next reset ================================================================================ STATISTICAL EVIDENCE (persistent journald, 50 affected boots) ================================================================================ - Range: 2025-08-15 21:22 → 2026-07-26 10:51 - Total NMI_INTERRUPT_UMAC_FATAL events: 293 - Hour-of-day distribution: 21:00 -> 154 (53%) 22:00 -> 34 23:00 -> 32 20:00 -> 27 17:00 -> 26 ┐ 10:00 -> 12 ├ daytime remainder = only days spent on-site at the affected location 15:00 -> 8 ┘ - 247/293 (84%) fall in 20:00–24:00. - Signal quality excellent (-44 dBm) — not a weak-signal issue. ================================================================================ TRIGGER / REPRODUCTION ================================================================================ - Occurs only on a 5 GHz DFS channel (confirmed on channel 112 / 5560 MHz). - A radar-related channel switch (CSA) — or a manual 5→2.4 GHz band switch while associated — deterministically triggers the assert; the manual case caused an immediate full desktop freeze + reboot. - The strong evening clustering is consistent with elevated DFS radar activity at that time. ================================================================================ WHEN IT DOES NOT HAPPEN ================================================================================ - Non-DFS 5 GHz channel (36–48 / 149–161): zero asserts over 5+ hours. - 2.4 GHz (channel 11): zero asserts. - AP configured with skip-dfs-channels=all: never occurs. ================================================================================ IMPACT ================================================================================ After the assert cascade the device enters permanent reset failure, Wi-Fi drops, and the GNOME desktop hangs. A warm reboot does NOT recover the CNVi (it is not power-cycled); a full cold poweroff is required to restore Wi-Fi. ================================================================================ RULED OUT (verified via journalctl across affected boots) ================================================================================ - GPU/i915 hang, kernel panic/lockup/RCU stall, MCE/hardware, thermal, OOM — all absent. - The only recurring fault is iwlwifi. - Not mitigated by: bt_coex_active=0, disable_11ax=1, or power-management tweaks (iwlmvm power_scheme=1, wifi.powersave off). - Firmware downgrade is impossible (driver requests API 89 only). ================================================================================ WORKAROUND ================================================================================ Force the client to 2.4 GHz (separate SSID), or pin the AP to a fixed non-DFS 5 GHz channel. The provider (Vodafone) router's 5 GHz channel is locked to "automatic", so channel pinning was not possible on that device. ================================================================================ EXPECTED BEHAVIOR ================================================================================ The firmware should handle a DFS radar event / channel-switch announcement (CSA) gracefully, without a fatal UMAC assert and device-reset storm. ================================================================================ HOW TO FILE ================================================================================ Ubuntu (auto-collects hardware, dmesg, versions): ubuntu-bug linux Upstream (firmware fix): bugzilla.kernel.org -> Product: Drivers, Component: network-wireless (iwlwifi) or linux-wireless@vger.kernel.org Attach: iwlwifi-bug-attachment.txt (per-boot assert summary + full assert log lines) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: taszilo 5120 F.... wireplumber /dev/snd/seq: taszilo 5103 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 11:23:59 2026 InstallationDate: Installed on 2025-06-13 (408 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X1504VA_X1504VA ProcEnviron: LANG=hu_HU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=934c7500-722d-4723-8f37-6f28418723dd ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-13 (43 days ago) dmi.bios.date: 03/13/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X1504VA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X1504VA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX1504VA.304:bd03/13/2024:br5.27:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX1504VA_X1504VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX1504VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivobook: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop X1504VA_X1504VA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "iwlwifi-bug-attachment.txt" https://bugs.launchpad.net/bugs/2161831/+attachment/5986590/+files/iwlwifi-bug-attachment.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161831 Title: iwlwifi (AX101/so-a0-hr-b0/fw 89) NMI_INTERRUPT_UMAC_FATAL firmware assert on 5 GHz DFS channels Status in linux package in Ubuntu: New Bug description: Title: iwlwifi (AX101 / so-a0-hr-b0 / fw 89) — reproducible NMI_INTERRUPT_UMAC_FATAL firmware assert on 5 GHz DFS channels: 293 asserts / 50 boots over 11 months, 84% clustered 20:00–24:00, peak at 21:00 ================================================================================ SUMMARY ================================================================================ The iwlwifi firmware reproducibly asserts (NMI_INTERRUPT_UMAC_FATAL / ADVANCED_SYSASSERT) when associated to an AP on a 5 GHz DFS channel, cascading into a device-reset storm ("Too many device errors - delay next reset") and a full desktop freeze requiring a hard power-cycle. Over 11 months of daily use: 293 asserts across 50 boots (2025-08-15 → 2026-07-26), with 84% occurring between 20:00–24:00 local and 53% at the 21:00 hour alone — consistent with elevated evening DFS radar activity. Zero asserts on non-DFS channels or 2.4 GHz. ================================================================================ HARDWARE ================================================================================ - Laptop: ASUS Vivobook X1504VA - CPU: Intel Core i3-1315U (Raptor Lake-U, 13th Gen) - Wi-Fi: Intel AX101 CNVi, PCI 0000:00:14.3, RF module so-a0-hr-b0 (HR1 B3) ================================================================================ SOFTWARE ================================================================================ - OS: Ubuntu 26.04 (development branch) - Kernel: 7.0.0-28-generic - Driver: iwlwifi / iwlmvm - Firmware: iwlwifi-so-a0-hr-b0-89.ucode, version 89.123cf747.0 (latest available; driver requests API 89 only, no fallback) ================================================================================ ASSERT SIGNATURES ================================================================================ iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0. iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL iwlwifi 0000:00:14.3: 0x2010120E | ADVANCED_SYSASSERT iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0 iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE iwlwifi 0000:00:14.3: Too many device errors - delay next reset ================================================================================ STATISTICAL EVIDENCE (persistent journald, 50 affected boots) ================================================================================ - Range: 2025-08-15 21:22 → 2026-07-26 10:51 - Total NMI_INTERRUPT_UMAC_FATAL events: 293 - Hour-of-day distribution: 21:00 -> 154 (53%) 22:00 -> 34 23:00 -> 32 20:00 -> 27 17:00 -> 26 ┐ 10:00 -> 12 ├ daytime remainder = only days spent on-site at the affected location 15:00 -> 8 ┘ - 247/293 (84%) fall in 20:00–24:00. - Signal quality excellent (-44 dBm) — not a weak-signal issue. ================================================================================ TRIGGER / REPRODUCTION ================================================================================ - Occurs only on a 5 GHz DFS channel (confirmed on channel 112 / 5560 MHz). - A radar-related channel switch (CSA) — or a manual 5→2.4 GHz band switch while associated — deterministically triggers the assert; the manual case caused an immediate full desktop freeze + reboot. - The strong evening clustering is consistent with elevated DFS radar activity at that time. ================================================================================ WHEN IT DOES NOT HAPPEN ================================================================================ - Non-DFS 5 GHz channel (36–48 / 149–161): zero asserts over 5+ hours. - 2.4 GHz (channel 11): zero asserts. - AP configured with skip-dfs-channels=all: never occurs. ================================================================================ IMPACT ================================================================================ After the assert cascade the device enters permanent reset failure, Wi-Fi drops, and the GNOME desktop hangs. A warm reboot does NOT recover the CNVi (it is not power-cycled); a full cold poweroff is required to restore Wi-Fi. ================================================================================ RULED OUT (verified via journalctl across affected boots) ================================================================================ - GPU/i915 hang, kernel panic/lockup/RCU stall, MCE/hardware, thermal, OOM — all absent. - The only recurring fault is iwlwifi. - Not mitigated by: bt_coex_active=0, disable_11ax=1, or power-management tweaks (iwlmvm power_scheme=1, wifi.powersave off). - Firmware downgrade is impossible (driver requests API 89 only). ================================================================================ WORKAROUND ================================================================================ Force the client to 2.4 GHz (separate SSID), or pin the AP to a fixed non-DFS 5 GHz channel. The provider (Vodafone) router's 5 GHz channel is locked to "automatic", so channel pinning was not possible on that device. ================================================================================ EXPECTED BEHAVIOR ================================================================================ The firmware should handle a DFS radar event / channel-switch announcement (CSA) gracefully, without a fatal UMAC assert and device-reset storm. ================================================================================ HOW TO FILE ================================================================================ Ubuntu (auto-collects hardware, dmesg, versions): ubuntu-bug linux Upstream (firmware fix): bugzilla.kernel.org -> Product: Drivers, Component: network-wireless (iwlwifi) or linux-wireless@vger.kernel.org Attach: iwlwifi-bug-attachment.txt (per-boot assert summary + full assert log lines) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: taszilo 5120 F.... wireplumber /dev/snd/seq: taszilo 5103 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 11:23:59 2026 InstallationDate: Installed on 2025-06-13 (408 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop X1504VA_X1504VA ProcEnviron: LANG=hu_HU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=934c7500-722d-4723-8f37-6f28418723dd ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-13 (43 days ago) dmi.bios.date: 03/13/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X1504VA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X1504VA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX1504VA.304:bd03/13/2024:br5.27:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopX1504VA_X1504VA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX1504VA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivobook: dmi.product.family: Vivobook dmi.product.name: Vivobook_ASUSLaptop X1504VA_X1504VA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161831/+subscriptions

суббота

[Bug 2161797] Re: [regression 7.0.0-27 -> 7.0.0-28] i915 derives wrong backlight PWM period on Kaby Lake-R (max_brightness 1023 instead of 7500), panel ignores all brightness changes

** 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/2161797 Title: [regression 7.0.0-27 -> 7.0.0-28] i915 derives wrong backlight PWM period on Kaby Lake-R (max_brightness 1023 instead of 7500), panel ignores all brightness changes Status in linux package in Ubuntu: New Bug description: After upgrading from Ubuntu 25.10 to 26.04, display brightness control stopped having any physical effect on this laptop's internal eDP panel. The entire software chain works correctly. Writes to /sys/class/backlight/intel_backlight/brightness succeed, actual_brightness reads back the value that was written, and GNOME/Mutter's DisplayConfig Backlight property tracks it. The panel simply does not change. The brightness slider and the Fn brightness keys therefore appear to do nothing. The distinguishing symptom is that i915 computes a different backlight PWM period: WORKING kernels intel_backlight max_brightness = 7500 BROKEN kernel intel_backlight max_brightness = 1023 7500 is the BIOS-programmed PWM period for this panel. 1023 (2^10 - 1) looks like a synthetic fallback, which suggests that on 7.0.0-28 i915 is no longer reading the BIOS/VBT-programmed value and instead computes a period the panel cannot follow. I tested every 7.0.0-x kernel available in resolute/main, plus the 25.10 kernel. All were booted on the same machine with the identical stock kernel command line ("quiet splash", no acpi_backlight= or i915.* parameters). Only the kernel differs. 6.17.0-8-generic max_brightness = 7500 GOOD (Ubuntu 25.10 GA kernel) 7.0.0-14-generic max_brightness = 7500 GOOD 7.0.0-22-generic max_brightness = 7500 GOOD 7.0.0-27-generic max_brightness = 7500 GOOD 7.0.0-28-generic max_brightness = 1023 BAD The regression therefore landed in the 7.0.0-27.27 -> 7.0.0-28.28 upload. 7.0.0-28 is the current 26.04 kernel, so all 26.04 users on affected panels are hit. I am currently running 7.0.0-27-generic as a workaround, which has fully working ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4288 F.... wireplumber /dev/snd/seq: ubuntu 4267 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 18:32:06 2026 InstallationDate: Installed on 2025-10-27 (271 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 15-ck0xx ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic root=/dev/mapper/username--vg-username--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-25 (0 days ago) dmi.bios.date: 08/09/2021 dmi.bios.release: 15.15 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 841C dmi.board.vendor: HP dmi.board.version: 64.14 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 64.14 dmi.modalias: dmi:bvnInsyde:bvrF.15:bd08/09/2021:br15.15:efr64.14:svnHP:pnHPPavilionLaptop15-ck0xx:pvrType1ProductConfigId:rvnHP:rn841C:rvr64.14:cvnHP:ct10:cvrChassisVersion:sku3QQ89EA#ABZ:pfa103C_5335KVHPPavilion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-ck0xx dmi.product.sku: 3QQ89EA#ABZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161797/+subscriptions

[Bug 2161289] Re: Kernel 7.0.0-28-generic: system hangs on shutdown/reboot on ThinkPad T14 Gen 2 AMD

Similar issue. System hangs indefinitely during shutdown or reboot, but only when some USB devices are connected (affects gamepads, mounted USB drives, and devices drawing power/charging via USB). So it can be linked to USB subsystem management in kernel 7.0.0-28-generic, like if something blocks USB shutdown or xhci driver. For me the issue is session-dependent: after logging out and shutting down from the login screen (Mint 22.3, Cinnamon 64 bit), shutdown works. Windows 10 on the same hardware shuts down correctly with the same USB devices connected. USB wakeup settings are disabled. Reverting to kernel 6.17.0-40-generic completely resolves the issue. System (after reverting to 6.17.0-40-generic): System: Kernel: 6.17.0-40-generic arch: x86_64 bits: 64 Desktop: Cinnamon v: 6.6.9 Distro: Linux Mint 22.3 Zena Machine: Type: Desktop Mobo: Micro-Star model: MAG B650 TOMAHAWK WIFI (MS-7D75) v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC. v: 1.O0 date: 06/24/2025 CPU: Info: 8-core model: AMD Ryzen 7 7800X3D bits: 64 type: MT MCP cache: L2: 8 MiB Speed (MHz): avg: 3457 min/max: 426/5053 cores: 1: 4405 2: 3585 3: 4405 4: 3728 5: 3665 6: 2983 7: 3671 8: 2983 9: 4400 10: 3598 11: 2983 12: 2983 13: 2983 14: 2983 15: 2983 16: 2983 Graphics: Device-1: AMD driver: amdgpu v: kernel Device-2: AMD Raphael driver: amdgpu v: kernel Device-3: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo type: USB Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X: loaded: amdgpu dri: radeonsi gpu: amdgpu resolution: 1: 1920x1080 2: 1920x1080 API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.8-0ubuntu0.24.04.2 renderer: AMD Radeon RX 9070 (radeonsi gfx1201 LLVM 20.1.2 DRM 3.64 6.17.0-40-generic) API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib Audio: Device-1: AMD driver: snd_hda_intel Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel Device-4: Generalplus GENERAL WEBCAM driver: snd-usb-audio,uvcvideo type: USB Device-5: Micro Star USB Audio driver: hid-generic,snd-usb-audio,usbhid type: USB API: ALSA v: k6.17.0-40-generic status: kernel-api Server-1: PipeWire v: 1.0.5 status: active Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 IF: enp14s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e IF: wlp15s0 state: down mac: <filter> Bluetooth: Device-1: MediaTek Wireless_Device driver: btusb type: USB Report: hciconfig ID: hci0 state: up address: <filter> bt-v: 5.4 Drives: Local Storage: total: 3.64 TiB used: 605.18 GiB (16.2%) ID-1: /dev/nvme0n1 vendor: KIOXIA model: EXCERIA PLUS G4 SSD size: 931.51 GiB ID-2: /dev/sda vendor: Seagate model: ST3000DM001-1ER166 size: 2.73 TiB type: USB -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161289 Title: Kernel 7.0.0-28-generic: system hangs on shutdown/reboot on ThinkPad T14 Gen 2 AMD Status in linux package in Ubuntu: Confirmed Bug description: ## Summary On Ubuntu 26.04 LTS, kernel 7.0.0-28-generic fails to shutdown or reboot properly on ThinkPad T14 Gen 2 (Ryzen 5 Pro). System reaches final.target, black screen, but power LED stays on indefinitely. ## Affected Hardware - ThinkPad T14 Gen 2 (Type 20UF) - AMD Ryzen 5 Pro 5650U - Integrated AMD Vega Graphics (amdgpu) ## Affected Kernel - 7.0.0-28-generic: FAILS - 7.0.0-27-generic: WORKS ## Steps to Reproduce 1. Boot kernel 7.0.0-28 2. Attempt shutdown or reboot via UI or CLI 3. System hangs with black screen, power LED remains on 4. Requires force power-off ## Root Cause systemd successfully reaches shutdown.target and final.target (journalctl confirms all services stopped cleanly). System hangs at kernel ACPI power management stage, likely amdgpu driver regression in 7.0.0-28. ## Workaround Downgrade to kernel 7.0.0-27-generic. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 00:18:57 2026 InstallationDate: Installed on 2026-05-08 (72 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20XLS0T500 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-kitty XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=off pci=noaer acpi=debug 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/16/2026 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET64W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XLS0T500 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrR1MET64W(1.34):bd04/16/2026:br1.34:efr1.34:svnLENOVO:pn20XLS0T500:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XLS0T500:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XL_BU_Think_FM_ThinkPadT14Gen2a:pfaThinkPadT14Gen2a: dmi.product.family: ThinkPad T14 Gen 2a dmi.product.name: 20XLS0T500 dmi.product.sku: LENOVO_MT_20XL_BU_Think_FM_ThinkPad T14 Gen 2a dmi.product.version: ThinkPad T14 Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161289/+subscriptions

[Bug 2161359] Re: linux-modules-7.0.0-28-generic breaks backlight control on some laptops

This bug affects me too on Lenovo ThinkPad T480. The brightnes control panel appears, but it has no effect. Additionally, when I suspend the laptop, then when I continue the screen becomes very dim, it's very hard to see anything, and I can't bring its brightness without restarting the laptop. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161359 Title: linux-modules-7.0.0-28-generic breaks backlight control on some laptops Status in linux package in Ubuntu: Confirmed Bug description: linux-modules-7.0.0-28-generic includes changes to backlight control in i915 module. This was supposed to be addressing LP: #2152570 making backlight work on some older laptops. The changes break backlight control on a Samsung 940X laptop with i5-3317 CPU. - drm/i915/backlight: Remove try_vesa_interface https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=40d2f5820951dee818d05c14677277048bd85f9f The previous version of intel_dp_aux_init_backlight_funcs in drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c had a display->params.enable_dpcd_backlight case of INTEL_DP_AUX_BACKLIGHT_AUTO which would only try VESA interface for a panel->vbt.backlight.type of INTEL_BACKLIGHT_VESA_EDP_AUX_INTERFACE or "if (intel_dp->edp_dpcd[0] >= DP_EDP_15)" The new version of intel_dp_aux_init_backlight_funcs tries a VESA interface for all values of panel->vbt.backlight.type including INTEL_BACKLIGHT_PMIC or INTEL_BACKLIGHT_LPSS or INTEL_BACKLIGHT_DSI_DCS or INTEL_BACKLIGHT_PANEL_DRIVER_INTERFACE or INTEL_BACKLIGHT_DISPLAY_DDI even when "(intel_dp->edp_dpcd[0] < DP_EDP_15)". That is overriding funcs that are set in drivers/gpu/drm/i915/display/intel_backlight.c by intel_backlight_init_funcs before it calls intel_dp_aux_init_backlight_funcs. Looking at the output of drm_dbg_kms() calls in i915 driver using kernel boot parameter drm.debug=0x06 shows that the VESA control is used. I added a call to log vbt.backlight.type from intel_bios.c parse_lfp_backlight(). i915 0000:00:02.0: [drm:parse_lfp_backlight [i915]] vbt.backlight.type: INTEL_BACKLIGHT_DISPLAY_DDI That confirmed that vbt.backlight.type is INTEL_BACKLIGHT_DISPLAY_DDI on this laptop. The dmesg output from intel_edp_init_dpcd shows that intel_dp->edp_dpcd[0] is DP_EDP_13, (0x02). i915 0000:00:02.0: [drm:intel_edp_init_dpcd [i915]] eDP DPCD: 02 b7 f6 00 00 Whatever extra tests added in the new check_if_vesa_backlight_possible() function does not spare this laptop. The VESA control is pushed in replacing the working functions previously set by intel_backlight_init_funcs(). ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: mike 2707 F.... wireplumber /dev/snd/controlC0: mike 2707 F.... wireplumber /dev/snd/seq: mike 2697 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 12:43:48 2026 InstallationDate: Installed on 2025-09-10 (313 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 940X3G/930X3G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=ff2b50fd-2ec0-4e8d-8be8-8d109a2614e9 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M drm.debug=0x06 SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-24 (87 days ago) dmi.bios.date: 08/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ACJ.128.140819.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: NP940X3G-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ACJ.128.140819.dg:bd08/19/2014:br4.6:svnSAMSUNGELECTRONICSCO.,LTD.:pn940X3G/930X3G:pvrP05ACJ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940X3G-K04US:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:skuSAMSUNGSENSSeries:pfaSAMSUNGSENS: dmi.product.family: SAMSUNG SENS dmi.product.name: 940X3G/930X3G dmi.product.sku: SAMSUNG SENS Series dmi.product.version: P05ACJ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161359/+subscriptions

[Bug 2158978] Re: System freeze on startup: nvidia-modeset/DifrPrefetchEventDeferredWork deadlock with KMS thread (driver 595.71.05, kernel 7.0.0-27)

After upgrading to version 595.84, the issue still persists. Specifically: approximately 1–2 hours after the system suspends, the system completely freezes, and the kernel log still shows the "KMS thread blocked" warning. I have attached the full nvidia-bug- report.log.gz report file for your reference. ** Attachment added: "nvidia-bug-report.log.gz" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-595/+bug/2158978/+attachment/5986278/+files/nvidia-bug-report.log.gz -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158978 Title: System freeze on startup: nvidia-modeset/DifrPrefetchEventDeferredWork deadlock with KMS thread (driver 595.71.05, kernel 7.0.0-27) Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-595 package in Ubuntu: Confirmed Bug description: System freezes completely shortly after login. A deadlock occurs between the nvidia-modeset kernel thread and the KMS thread. Requires hard reboot to recover. Hardware: Lenovo 83JM (BIOS PZCN49WW 2025-06-06) GPU: NVIDIA GeForce RTX 5050 laptop (hybrid GPU with Intel i915) Driver: nvidia 595.71.05 (Open Kernel Module) Kernel: 7.0.0-27-generic (Ubuntu 26.04) --- Kernel log (Jul 02 ~03:58) --- INFO: task KMS thread:5195 blocked for more than 122 seconds. task:KMS thread state:D pid:5195 nvkms_ioctl_from_kapi_try_pmlock+0x55/0xd0 [nvidia_modeset] ApplyModeSetConfig+0x357/0xba0 [nvidia_modeset] nv_drm_atomic_apply_modeset_config+0x80b/0x9c0 [nvidia_drm] drm_atomic_commit+0x6c/0xf0 nv_drm_ioctl+0x38/0x3f0 [nvidia_drm] INFO: task KMS thread:5195 blocked on a semaphore likely last held by task nvidia-modeset/:511 task:nvidia-modeset/ state:R (running but stuck) pid:511 RIP: nvWriteGpEntry+0xa4/0x370 [nvidia_modeset] nvPushKickoff+0x28/0x50 [nvidia_modeset] PrefetchHelperSurfaceEvo+0x45c/0x650 [nvidia_modeset] nvDIFRPrefetchSurfaces+0x135/0x1f0 [nvidia_modeset] DifrPrefetchEventDeferredWork+0x16/0x30 [nvidia_modeset] nvkms_kthread_q_callback+0xe9/0x1a0 [nvidia_modeset] (Repeated every ~2 min for 20+ minutes, from 122s to 1228s blocked) --- Additional errors at driver load --- NVRM: NV_ERR_INVALID_DATA from SBIOS for platform power mode and target temperature nvidia_init_module: "Unpatched return thunk in use" (kernel taint OE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158978/+subscriptions