[Bug 1872401] Re: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM

This issue is not being referenced in out hint database. Closing it. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1872401 Title: vmx_nm_test in ubuntu_kvm_unit_tests interrupted on X-oracle-4.15 / B-oracle-4.15 / X-KVM / B-KVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Bug description: [Impact] When running kvm-unit-tests under a guest, it will be paused, requiring a reset. When running the same test on a host (vmx_nm_test), it will fail. [Test case] Grab kvm-unit-tests, build it and run: TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "vmx_nm_test" If done inside a guest, when the host runs the bionic 4.15 kernel, the guest will pause. [Potential regressions] Nested KVM could stop working. Floating point could stop working on KVM guests, though the code that relied on this was already removed from Bionic. ------------------------------ This issue was first spotted on Mar.16 [1] The ubuntu_kvm_unit_tests will be interrupted on X-oracle-4.15 on both VM.Standard2.1 and VM.Standard2.16, this is not a regression since it can be reproduced with 4.15.0-1031-oracle #34~16.04.1: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_nm_test'  BUILD_HEAD=4671e4ba  timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.da3iFrsCzC -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.h2DFw8L0AF  enabling apic  paging enabled  cr0 = 80010011  cr3 = 477000  cr4 = 20  Test suite: vmx_nm_test client_loop: send disconnect: Broken pipe (node disconnected here) Before the test started, this can be found in syslog: Apr 13 06:26:25 selfprovisioned-phlin-kvm-unit kernel: [ 1073.529005] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. After that, noting was printed and node disconnected. If you try to run this case manually, it will stop at: # ./vmx_nm_test BUILD_HEAD=4671e4ba ready!!! timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.ZcGrnXu6se -smp 1 -cpu host,+vmx -append vmx_nm_test # -initrd /tmp/tmp.ADjEOAcRKM enabling ap (stopped here, even the "enabling apic" string was not printed) It looks like this is a new test case added since the cycle of 4.15.0-1037.41~16.04.1-oracle [1] https://bugs.launchpad.net/ubuntu-kernel- tests/+bug/1867623/comments/2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-1031-oracle 4.15.0-1031.34~16.04.1 ProcVersionSignature: User Name 4.15.0-1031.34~16.04.1-oracle 4.15.18 Uname: Linux 4.15.0-1031-oracle x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Apr 13 05:18:03 2020 ProcEnviron:  TERM=xterm-256color  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/bash SourcePackage: linux-signed-oracle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1872401/+subscriptions

[Bug 2159008] [NEW] System freeze on ASUS Zenbook UX3404VA (i9 13900H) login screen in 26.04 LTS

Public bug reported: Dear Ubuntu Developers / Kernel Team, I am writing to report a critical issue I am encountering with Ubuntu 26.04 LTS on my ASUS Zenbook UX3404VA (Intel Core i9 13900H, Iris Xe Graphics). The Issue: Upon installing Ubuntu 26.04 LTS, the system freezes consistently immediately after the user authentication stage. The screen stops responding entirely, although the keyboard remains responsive (no kernel panic). This behavior does not occur in Ubuntu 25.10, where all hardware components function correctly. System Details: Laptop: ASUS Zenbook UX3404VA Processor: Intel Core i9-13900H (Raptor Lake) Graphics: Intel Iris Xe Graphics OS Version: Ubuntu 26.04 LTS (Freeze observed) / Ubuntu 25.10 (Stable) Environment: Default GNOME/Wayland Troubleshooting Attempted: Verified that Ubuntu 25.10 is completely stable on the same hardware. The freeze specifically occurs at the transition from the login manager to the desktop session, suggesting a potential regression in the xe vs i915 driver handling or a Wayland/Mutter incompatibility in the 26.04 kernel. The issue appears to be related to GPU hardware acceleration during session initialization. I would appreciate it if you could investigate this regression, as it affects the stability of the latest LTS release on this specific laptop model. Please let me know if you need any specific logs (e.g., journalctl -b -1) or debug information to help pinpoint the cause. Thank you for your hard work and support. Best regards, Ali Beheshti ** 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/2159008 Title: System freeze on ASUS Zenbook UX3404VA (i9 13900H) login screen in 26.04 LTS Status in linux package in Ubuntu: New Bug description: Dear Ubuntu Developers / Kernel Team, I am writing to report a critical issue I am encountering with Ubuntu 26.04 LTS on my ASUS Zenbook UX3404VA (Intel Core i9 13900H, Iris Xe Graphics). The Issue: Upon installing Ubuntu 26.04 LTS, the system freezes consistently immediately after the user authentication stage. The screen stops responding entirely, although the keyboard remains responsive (no kernel panic). This behavior does not occur in Ubuntu 25.10, where all hardware components function correctly. System Details: Laptop: ASUS Zenbook UX3404VA Processor: Intel Core i9-13900H (Raptor Lake) Graphics: Intel Iris Xe Graphics OS Version: Ubuntu 26.04 LTS (Freeze observed) / Ubuntu 25.10 (Stable) Environment: Default GNOME/Wayland Troubleshooting Attempted: Verified that Ubuntu 25.10 is completely stable on the same hardware. The freeze specifically occurs at the transition from the login manager to the desktop session, suggesting a potential regression in the xe vs i915 driver handling or a Wayland/Mutter incompatibility in the 26.04 kernel. The issue appears to be related to GPU hardware acceleration during session initialization. I would appreciate it if you could investigate this regression, as it affects the stability of the latest LTS release on this specific laptop model. Please let me know if you need any specific logs (e.g., journalctl -b -1) or debug information to help pinpoint the cause. Thank you for your hard work and support. Best regards, Ali Beheshti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159008/+subscriptions

[Bug 2154172] Re: GRO managed-frag use-after-free leading to local privilege escalation

This bug is awaiting verification that the linux- nvidia-7.0/7.0.0-1015.15~24.04.1 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-noble-linux- nvidia-7.0' to 'verification-done-noble-linux-nvidia-7.0'. If the problem still exists, change the tag 'verification-needed-noble-linux- nvidia-7.0' to 'verification-failed-noble-linux-nvidia-7.0'. 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-noble-linux-nvidia-7.0-v2 verification-needed-noble-linux-nvidia-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154172 Title: GRO managed-frag use-after-free leading to local privilege escalation Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux source package in Questing: Fix Released Status in linux source package in Resolute: Fix Released Bug description: [ Impact ] skb_gro_receive() in net/core/gro.c transfers frag descriptors from a source skb into a GRO accumulator without checking the SKBFL_MANAGED_FRAG_REFS flag. A managed-frag skb does not hold a per-frag page reference; the caller owns page lifetime. When such frags are appended to a non-managed accumulator, skb_release_data() later calls put_page() on frags it never get_page()'d, producing a page refcount underflow. The resulting use-after-free is reachable by an unprivileged local user via io_uring SEND_ZC with fixed buffers over a GRO-enabled interface, and yields local privilege escalation. The bug was introduced upstream by commit 753f1ca4e1e5 ("net: introduce managed frags infrastructure"), which first landed in v5.20/v6.0. [ Fix ] commit 4db79a322db8c97f7b73b8a347395ef4d685eb40 ("net: gro: don't merge zcopy skbs") Refuse to merge in skb_gro_receive() when either side has SKBFL_MANAGED_FRAG_REFS or any zerocopy flag set. Landed in net.git for v7.1-rc5. [ Test Plan ] A user-space reproducer is run on a VM with the candidate kernel installed. sha256(/etc/passwd) is captured pre and post. Patched kernel: reproducer self-reports failure, sha256 unchanged. Unpatched kernel: reproducer succeeds, sha256 changes during the run. [ Where Problems Could Occur ] The fix only refuses a merge in a case that was always unsafe. The visible effect is that GRO occasionally produces one more segment-sized skb than otherwise on flows that mix managed and non-managed frags. Tiny throughput change in an uncommon path, no crash or correctness risk. No userspace API change, no kernel ABI change, no module change. [ Other Info ] No CVE ID assigned at the time of filing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154172/+subscriptions

[Bug 2158229] Re: MT7925 wifi is hard blocked on Dell's machine

This bug is awaiting verification that the linux- hwe-7.0/7.0.0-28.28~24.04.1 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-noble-linux- hwe-7.0' to 'verification-done-noble-linux-hwe-7.0'. If the problem still exists, change the tag 'verification-needed-noble-linux-hwe-7.0' to 'verification-failed-noble-linux-hwe-7.0'. 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-noble-linux-hwe-7.0-v2 verification-needed-noble-linux-hwe-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158229 Title: MT7925 wifi is hard blocked on Dell's machine Status in linux package in Ubuntu: New Status in linux-hwe-7.0 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-hwe-7.0 source package in Noble: Fix Committed Status in linux-oem-6.17 source package in Noble: In Progress Status in linux source package in Questing: In Progress Status in linux-hwe-7.0 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: In Progress Status in linux-hwe-7.0 source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux source package in Stonking: New Status in linux-hwe-7.0 source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: [Impact] The Wi-Fi is hard blocked on Dell systems (CIDs: 202505-36757, 202501-36195, 202501-36253) and HP systems with Mediatek MT7925 cards. The wireless connection cannot be used. The rfkill state shows: $ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes [Fix] We revert the hardware rfkill polling feature for Mediatek MT7925 cards. This polling feature was introduced upstream in v6.16. We also revert the local DMI quirk for HP systems since polling is now disabled. Reverted commits: • Revert "wifi: mt76: mt7925: add rfkill_poll for hardware rfkill" (reverts upstream commit e54b870212c079bef4ff61238f8c1278a14d1863 from v6.16) • Revert local DMI quirk commit for HP systems (reverts local commit 20c9b07dcea9d49c876c9532a48a6dc88f43d0f9) [Test Plan] Check the rfkill state on affected hardware: $ rfkill list Without the patches: The Wireless LAN interface shows "Hard blocked: yes". The Wi-Fi connection does not work. With the patches: The Wireless LAN interface shows "Hard blocked: no". The Wi-Fi connection works. [Where problems could occur] This change affects the mt76 Mediatek wireless driver. If a system has a physical wireless switch that needs software polling, the switch will stop working. Toggling the physical switch would not change the Wi-Fi block state. ========================================================= [Impact] The wifi is hard blocked and can't be used randomly. [Test] 1. Boot up Machine 2. Run `rfkill list` to check wlan0 block state Wireless: Mediatek Inc. - 14c3:7925 ubuntu@localhost:~$ rfkill list 0: hci0: Bluetooth  Soft blocked: no  Hard blocked: no 1: phy0: Wireless LAN  Soft blocked: no  Hard blocked: yes [Affected Machines] 202505-36757 202501-36195 202501-36253 [Similar Issue] https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.14/+bug/2127044 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1020-oem 6.17.0-1020.20 ProcVersionSignature: Ubuntu 6.17.0-1020.20-oem 6.17.13 Uname: Linux 6.17.0-1020-oem x86_64 ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: ubuntu 1918 F.... pipewire                       ubuntu 1922 F.... wireplumber  /dev/snd/controlC0: ubuntu 1922 F.... wireplumber  /dev/snd/seq: ubuntu 1918 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Jun 25 05:43:16 2026 DistributionChannelDescriptor:  # This is the distribution channel descriptor for Ubuntu 24.04 for Dell  # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor  canonical-oem-somerville-noble-oem-24.04b-proposed-20250604-520 InstallationDate: Installed on 2026-05-07 (49 days ago) InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250603) IwConfig:  lo no wireless extensions.  enp195s0f0 no wireless extensions.  wlp194s0 no wireless extensions. MachineType: Dell Inc. Dell Pro Max 14 MC14255 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1020-oem root=UUID=881d0e73-6adc-444d-90b2-9491672e82b1 ro quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-6.17.0-1020-oem N/A  linux-backports-modules-6.17.0-1020-oem N/A  linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2025 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0WT010 dmi.board.vendor: Dell Inc. dmi.board.version: D01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd09/09/2025:br1.4:efr1.3:svnDellInc.:pnDellProMax14MC14255:pvr:rvnDellInc.:rn0WT010:rvrD01:cvnDellInc.:ct10:cvr:sku0D80: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 MC14255 dmi.product.sku: 0D80 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158229/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-meta-azure-6.17/6.17.0-1021.21~24.04.1)

All autopkgtests for the newly accepted linux-meta-azure-6.17 (6.17.0-1021.21~24.04.1) for noble have finished running. The following regressions have been reported in tests triggered by the package: dkms/3.0.11-1ubuntu13 (amd64) dpdk-kmods/unknown (amd64) lxc/unknown (amd64) systemd/unknown (arm64) zfs-linux/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/noble/update_excuses.html#linux-meta-azure-6.17 [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 2158993] [NEW] System hard-freezes after failed suspend (Xwayland freeze timeout) with nvidia-driver-595-open — deadlock in nvidia_modeset/console

Public bug reported: # Bug Report: System hard-freezes after failed suspend (Xwayland freeze timeout) with NVIDIA 595-open driver — deadlock between nvidia_modeset and console/fbcon subsystem ## Summary On a desktop system with an NVIDIA RTX 4070 Ti (nvidia-driver-595-open, 595.71.05) running Ubuntu 26.04 "resolute" on kernel 7.0.0-27-generic, attempting to suspend (`mem_sleep_default=deep`, S3) intermittently fails as follows: 1. `Freezing user space processes` fails after the default 20s timeout because a userspace task (observed: `Xwayland`, correlated with an active Steam client) refuses to freeze in time. 2. The kernel aborts the suspend and falls back to `fbcon: Taking over console`. 3. During this fallback, the NVIDIA driver's internal memory-management code (`NVRM: GPU0 nvAssertFailedNoLog`, `kern_bus_gv100.c:388`, `mmu_walk*.c`) begins emitting a continuous stream of assertion failures — one burst approximately every 30 seconds — indicating GPU virtual-address-space mapping has entered a broken state. 4. A kernel worker thread (`kworker/0:1`, workqueue `fbcon_register_existing_fbs`) becomes stuck for 245+ seconds inside `nvkms_ioctl_from_kapi` / `GetDynamicDisplayInfo`, waiting on an rwsem held (apparently) by the NVIDIA driver. 5. `systemd-sleep`, attempting `pm_restore_console` as part of aborting the suspend, blocks indefinitely on `console_lock`, which the kernel explicitly reports as "likely last held by task kworker/0:1:11" — i.e. the same stuck worker from step 4. 6. This is a genuine circular-wait deadlock between the console/VT subsystem and the NVIDIA kernel module, not a simple slow device. 7. The system does not always crash immediately after this deadlock — it can continue running for several hours in a visibly degraded state (other services such as `cups.service` and `fwupd-refresh.service` begin entering restart loops, killed repeatedly with SIGKILL and never exiting cleanly) before eventually becoming totally unresponsive and requiring a hard power-button reset. No further kernel log entries are written between the last responsive log line and the forced reboot, consistent with a full system lockup rather than a clean panic. This has now been observed and diagnosed across three separate incidents over the space of about 48 hours, all sharing the same signature (failed freeze → NVRM assertion cascade → eventual hard freeze requiring power- cycle). ## System Information - **Ubuntu release:** 26.04 "resolute" (resolute-updates, resolute-security) - **Kernel:** 7.0.0-27-generic - **CPU:** AMD Ryzen 7 5700X3D - **GPU:** NVIDIA RTX 4070 Ti (PCI ID 10DE:2782, subsystem 1462:5132) - **NVIDIA driver package:** nvidia-driver-595-open, version 595.71.05-0ubuntu0.26.04.1 (also nvidia-driver-590-open installed but not active/default) - **Display stack:** GNOME on Wayland (Xwayland for X11 apps) - **Kernel command line (GRUB_CMDLINE_LINUX_DEFAULT):** ``` quiet splash nvidia-drm.modeset=1 mem_sleep_default=deep usbcore.autosuspend=-1 ``` - **`/sys/power/mem_sleep`:** `s2idle [deep]` (deep in use) ## Workarounds already tried 1. **Switched sleep mode from `deep` (S3) to `s2idle`** — did **not** prevent the freeze-timeout/deadlock pattern; the underlying trigger (Xwayland refusing to freeze) is independent of the ACPI sleep mode. 2. **Added `/etc/modprobe.d/nvidia-suspend-fix.conf`:** ``` options nvidia NVreg_PreserveVideoMemoryAllocations=1 options nvidia NVreg_TemporaryFilePath=/var/tmp options nvidia NVreg_UseKernelSuspendNotifiers=0 ``` Confirmed active via `/proc/driver/nvidia/params` after reboot. This reduced the frequency of memory-corruption symptoms somewhat but **did not eliminate** the underlying freeze-timeout → NVRM assertion → deadlock sequence; it recurred on a subsequent night with this configuration active. ## Steps to Reproduce (best current understanding) 1. Have an X11/Xwayland-backed application under load at the moment the system is asked to suspend — in the two clearest captures, a Steam client was active and had logged `CSteamEngine::BMainLoop appears to have stalled > 15 seconds` at the same timestamp as the freeze failure. 2. Trigger suspend (automatic idle suspend via `systemd-logind`/GNOME power settings, or manual). 3. Kernel begins `Freezing user space processes`; if Xwayland does not freeze within 20s, the kernel aborts the freeze and logs `Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0)`. 4. From this point, NVRM assertion-failure spam begins, and eventually the fbcon/console_lock deadlock described above can occur. 5. System may continue running in a degraded state for hours before a full hard freeze. ## Expected Behavior If a task refuses to freeze in time, the kernel should cleanly abort the suspend and return the system to a fully functional state, without leaving the NVIDIA driver or the console subsystem in a corrupted/deadlocked state. ## Actual Behavior The abort path itself deadlocks: `nvidia_modeset`'s internal locking (exercised via the `fbcon_register_existing_fbs` workqueue triggered by `fbcon: Taking over console`) contends with `systemd-sleep`'s own console-restore path (`pm_restore_console` → `console_lock`), and the two can end up blocking on each other. The system may appear to "recover" superficially but is left in a state that leads to cascading failures (other systemd services entering unkillable SIGKILL-retry loops) and, eventually, a full unrecoverable freeze. ## Log Evidence (key excerpts, kernel 7.0.0-27-generic) ``` kernel: PM: suspend entry (deep) kernel: Filesystems sync: 0.353 seconds kernel: Freezing user space processes kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0): kernel: fbcon: Taking over console kernel: task:Xwayland state:R running task stack:0 pid:5165 tgid:5165 ppid:4743 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NULL != pIter->pMap @ virt_mem_allocator_gm107.c:2024 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: progress == entryIndexHi - entryIndexLo + 1 @ mmu_walk_map.c:170 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ mmu_walk.c:541 kernel: NVRM: GPU0 mmuWalkMap: Failed to map VA Range 0x2f000000 to 0x2f1fffff. Status = 0x00000040 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (pKernelBus->pReadToFlush != NULL || pKernelBus->virtualBar2[GPU_GFID_PF].pCpuMapping != NULL) @ kern_bus_gv100.c:388 [... this block repeats roughly every 30 seconds for several minutes ...] kernel: INFO: task kworker/0:1:11 blocked for more than 245 seconds. kernel: Tainted: G O 7.0.0-27-generic #27-Ubuntu kernel: task:kworker/0:1 state:D stack:0 pid:11 tgid:11 ppid:2 kernel: Workqueue: events fbcon_register_existing_fbs kernel: Call Trace: kernel: rwsem_down_read_slowpath+... kernel: down_read+0x48/0xd0 kernel: nvkms_ioctl_from_kapi+0xdc/0xf0 [nvidia_modeset] kernel: GetDynamicDisplayInfo+0x9c/0x190 [nvidia_modeset] ... kernel: INFO: task systemd-sleep:35518 blocked for more than 245 seconds. kernel: task:systemd-sleep state:D stack:0 pid:35518 tgid:35518 ppid:1 kernel: Call Trace: kernel: down+0x5e/0x80 kernel: console_lock+0x2f/0x50 kernel: vt_move_to_console+0x19/0xb0 kernel: pm_restore_console+0x4d/0x70 kernel: enter_state+0x120/0x610 kernel: pm_suspend+0x49/0x90 kernel: INFO: task systemd-sleep:35518 blocked on a semaphore likely last held by task kworker/0:1:11 ``` Later the same night, unrelated services begin failing identically (repeated SIGKILL, never exiting): ``` systemd[1]: cups.service: start operation timed out. Terminating. systemd[1]: cups.service: State 'stop-sigterm' timed out. Killing. systemd[1]: cups.service: Killing process 35995 (9) with signal SIGKILL. systemd[1]: cups.service: Processes still around after SIGKILL. Ignoring. [cycle repeats ~35 times over 4+ hours] ``` No further journal entries follow the last cycle; the machine was unresponsive and required a hard power-button reset. ## Note on driver versions checked At the time of filing, NVIDIA's production branch had advanced to 595.84 (released 2026-06-17), one release ahead of the 595.71.05 installed here. I checked whether 595.84 was available as a packaged driver for Ubuntu 26.04 "resolute" before filing, to rule out that this was already fixed: - `resolute-updates` / `resolute-security` (official Ubuntu archive): only 595.71.05 - `ppa:graphics-drivers/ppa`: only 595.71.05 for `resolute` - NVIDIA's own CUDA apt repository (`developer.download.nvidia.com/compute/cuda/repos/ubuntu2604`): does not carry a `nvidia-driver-595-open` package matching 595.84 either (only unrelated tooling from the newer 610.x feature branch, e.g. `nvidia-settings`/`libxnvctrl0` 610.43.02) 595.84 is therefore only available as NVIDIA's `.run` installer for this Ubuntu release at present, which was intentionally not used here to avoid DKMS/Secure Boot conflicts with the distro-packaged driver. This report is filed against 595.71.05; it is not yet known whether 595.84 resolves the issue. ## Note on driver versions checked At the time of filing, NVIDIA's production branch had advanced to 595.84 (released 2026-06-17), one release ahead of the 595.71.05 installed here. I checked whether 595.84 was available as a packaged driver for Ubuntu 26.04 "resolute" before filing, to rule out that this was already fixed: - `resolute-updates` / `resolute-security` (official Ubuntu archive): only 595.71.05 - `ppa:graphics-drivers/ppa`: only 595.71.05 for `resolute` - NVIDIA's own CUDA apt repository (`developer.download.nvidia.com/compute/cuda/repos/ubuntu2604`): does not carry a `nvidia-driver-595-open` package matching 595.84 either (only unrelated tooling from the newer 610.x feature branch, e.g. `nvidia-settings`/`libxnvctrl0` 610.43.02) 595.84 is therefore only available as NVIDIA's `.run` installer for this Ubuntu release at present, which was intentionally not used here to avoid DKMS/Secure Boot conflicts with the distro-packaged driver. This report is filed against 595.71.05; it is not yet known whether 595.84 resolves the issue. The 595.84 changelog lists "Fixed a bug that could cause suspend and resume to fail on systems with runtime D3 (RTD3) power management enabled." I checked whether this applies here: ``` $ cat /proc/driver/nvidia/gpus/*/power Runtime D3 status: Disabled by default ... ``` RTD3 is disabled by default on this system (single desktop GPU with a directly-attached display, no hybrid/Optimus setup), so this specific changelog entry likely does not describe the same bug — the deadlock documented below appears unrelated to RTD3 and is filed as a distinct issue. ## Possibly related upstream reports - Ubuntu Launchpad bug **#2149963** (package `linux`) — RTX 50-series + nvidia-open 595/580 on kernel 7.0.0-14-generic, Ubuntu 26.04 "resolute": s2idle resume never completes after lid-close, requires hard reset. Same kernel/driver generation, same distro release; different GPU generation and different sleep mode (s2idle vs deep here), but the same overall "suspend/resume path never returns, only a hard reset recovers" symptom. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149963 ## Attachments to include when filing - Output of `ubuntu-bug linux` (for current package/version/apport metadata) — note: current `dmesg` will NOT contain the incident logs, since a hard reset clears the kernel ring buffer. - Full `journalctl` excerpts spanning each incident (attach as separate `.txt` files), specifically the windows around each `PM: suspend entry` through the last log line before the gap indicating the hard reset. - Output of `cat /proc/driver/nvidia/params | grep -iE 'Preserve|Kernel|Temp'` showing the modprobe workaround is active. - `nvidia-bug-report.sh` output (run `sudo nvidia-bug-report.sh`, attach the resulting `nvidia-bug-report.log.gz`) if it can be captured after a fresh incident before rebooting away the state. 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: beniu 4376 F.... wireplumber /dev/snd/controlC1: beniu 4376 F.... wireplumber /dev/snd/controlC0: beniu 4376 F.... wireplumber /dev/snd/seq: beniu 4356 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 2 19:32:21 2026 InstallationDate: Installed on 2026-02-21 (131 days ago) InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) MachineType: System manufacturer System Product Name ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=625d6275-b0c0-4dac-b793-5b840ac8fbf9 ro quiet splash nvidia-drm.modeset=1 mem_sleep_default=deep usbcore.autosuspend=-1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5901:bd10/03/2025:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Patch added: "journalctl log from freeze boot" https://bugs.launchpad.net/bugs/2158993/+attachment/5979947/+files/log_hardreset2.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158993 Title: System hard-freezes after failed suspend (Xwayland freeze timeout) with nvidia-driver-595-open — deadlock in nvidia_modeset/console Status in linux package in Ubuntu: New Bug description: # Bug Report: System hard-freezes after failed suspend (Xwayland freeze timeout) with NVIDIA 595-open driver — deadlock between nvidia_modeset and console/fbcon subsystem ## Summary On a desktop system with an NVIDIA RTX 4070 Ti (nvidia- driver-595-open, 595.71.05) running Ubuntu 26.04 "resolute" on kernel 7.0.0-27-generic, attempting to suspend (`mem_sleep_default=deep`, S3) intermittently fails as follows: 1. `Freezing user space processes` fails after the default 20s timeout because a userspace task (observed: `Xwayland`, correlated with an active Steam client) refuses to freeze in time. 2. The kernel aborts the suspend and falls back to `fbcon: Taking over console`. 3. During this fallback, the NVIDIA driver's internal memory-management code (`NVRM: GPU0 nvAssertFailedNoLog`, `kern_bus_gv100.c:388`, `mmu_walk*.c`) begins emitting a continuous stream of assertion failures — one burst approximately every 30 seconds — indicating GPU virtual-address-space mapping has entered a broken state. 4. A kernel worker thread (`kworker/0:1`, workqueue `fbcon_register_existing_fbs`) becomes stuck for 245+ seconds inside `nvkms_ioctl_from_kapi` / `GetDynamicDisplayInfo`, waiting on an rwsem held (apparently) by the NVIDIA driver. 5. `systemd-sleep`, attempting `pm_restore_console` as part of aborting the suspend, blocks indefinitely on `console_lock`, which the kernel explicitly reports as "likely last held by task kworker/0:1:11" — i.e. the same stuck worker from step 4. 6. This is a genuine circular-wait deadlock between the console/VT subsystem and the NVIDIA kernel module, not a simple slow device. 7. The system does not always crash immediately after this deadlock — it can continue running for several hours in a visibly degraded state (other services such as `cups.service` and `fwupd-refresh.service` begin entering restart loops, killed repeatedly with SIGKILL and never exiting cleanly) before eventually becoming totally unresponsive and requiring a hard power-button reset. No further kernel log entries are written between the last responsive log line and the forced reboot, consistent with a full system lockup rather than a clean panic. This has now been observed and diagnosed across three separate incidents over the space of about 48 hours, all sharing the same signature (failed freeze → NVRM assertion cascade → eventual hard freeze requiring power-cycle). ## System Information - **Ubuntu release:** 26.04 "resolute" (resolute-updates, resolute-security) - **Kernel:** 7.0.0-27-generic - **CPU:** AMD Ryzen 7 5700X3D - **GPU:** NVIDIA RTX 4070 Ti (PCI ID 10DE:2782, subsystem 1462:5132) - **NVIDIA driver package:** nvidia-driver-595-open, version 595.71.05-0ubuntu0.26.04.1 (also nvidia-driver-590-open installed but not active/default) - **Display stack:** GNOME on Wayland (Xwayland for X11 apps) - **Kernel command line (GRUB_CMDLINE_LINUX_DEFAULT):** ``` quiet splash nvidia-drm.modeset=1 mem_sleep_default=deep usbcore.autosuspend=-1 ``` - **`/sys/power/mem_sleep`:** `s2idle [deep]` (deep in use) ## Workarounds already tried 1. **Switched sleep mode from `deep` (S3) to `s2idle`** — did **not** prevent the freeze-timeout/deadlock pattern; the underlying trigger (Xwayland refusing to freeze) is independent of the ACPI sleep mode. 2. **Added `/etc/modprobe.d/nvidia-suspend-fix.conf`:** ``` options nvidia NVreg_PreserveVideoMemoryAllocations=1 options nvidia NVreg_TemporaryFilePath=/var/tmp options nvidia NVreg_UseKernelSuspendNotifiers=0 ``` Confirmed active via `/proc/driver/nvidia/params` after reboot. This reduced the frequency of memory-corruption symptoms somewhat but **did not eliminate** the underlying freeze-timeout → NVRM assertion → deadlock sequence; it recurred on a subsequent night with this configuration active. ## Steps to Reproduce (best current understanding) 1. Have an X11/Xwayland-backed application under load at the moment the system is asked to suspend — in the two clearest captures, a Steam client was active and had logged `CSteamEngine::BMainLoop appears to have stalled > 15 seconds` at the same timestamp as the freeze failure. 2. Trigger suspend (automatic idle suspend via `systemd-logind`/GNOME power settings, or manual). 3. Kernel begins `Freezing user space processes`; if Xwayland does not freeze within 20s, the kernel aborts the freeze and logs `Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0)`. 4. From this point, NVRM assertion-failure spam begins, and eventually the fbcon/console_lock deadlock described above can occur. 5. System may continue running in a degraded state for hours before a full hard freeze. ## Expected Behavior If a task refuses to freeze in time, the kernel should cleanly abort the suspend and return the system to a fully functional state, without leaving the NVIDIA driver or the console subsystem in a corrupted/deadlocked state. ## Actual Behavior The abort path itself deadlocks: `nvidia_modeset`'s internal locking (exercised via the `fbcon_register_existing_fbs` workqueue triggered by `fbcon: Taking over console`) contends with `systemd-sleep`'s own console-restore path (`pm_restore_console` → `console_lock`), and the two can end up blocking on each other. The system may appear to "recover" superficially but is left in a state that leads to cascading failures (other systemd services entering unkillable SIGKILL-retry loops) and, eventually, a full unrecoverable freeze. ## Log Evidence (key excerpts, kernel 7.0.0-27-generic) ``` kernel: PM: suspend entry (deep) kernel: Filesystems sync: 0.353 seconds kernel: Freezing user space processes kernel: Freezing user space processes failed after 20.001 seconds (1 tasks refusing to freeze, wq_busy=0): kernel: fbcon: Taking over console kernel: task:Xwayland state:R running task stack:0 pid:5165 tgid:5165 ppid:4743 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NULL != pIter->pMap @ virt_mem_allocator_gm107.c:2024 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: progress == entryIndexHi - entryIndexLo + 1 @ mmu_walk_map.c:170 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: NV_OK == status @ mmu_walk.c:541 kernel: NVRM: GPU0 mmuWalkMap: Failed to map VA Range 0x2f000000 to 0x2f1fffff. Status = 0x00000040 kernel: NVRM: GPU0 nvAssertFailedNoLog: Assertion failed: (pKernelBus->pReadToFlush != NULL || pKernelBus->virtualBar2[GPU_GFID_PF].pCpuMapping != NULL) @ kern_bus_gv100.c:388 [... this block repeats roughly every 30 seconds for several minutes ...] kernel: INFO: task kworker/0:1:11 blocked for more than 245 seconds. kernel: Tainted: G O 7.0.0-27-generic #27-Ubuntu kernel: task:kworker/0:1 state:D stack:0 pid:11 tgid:11 ppid:2 kernel: Workqueue: events fbcon_register_existing_fbs kernel: Call Trace: kernel: rwsem_down_read_slowpath+... kernel: down_read+0x48/0xd0 kernel: nvkms_ioctl_from_kapi+0xdc/0xf0 [nvidia_modeset] kernel: GetDynamicDisplayInfo+0x9c/0x190 [nvidia_modeset] ... kernel: INFO: task systemd-sleep:35518 blocked for more than 245 seconds. kernel: task:systemd-sleep state:D stack:0 pid:35518 tgid:35518 ppid:1 kernel: Call Trace: kernel: down+0x5e/0x80 kernel: console_lock+0x2f/0x50 kernel: vt_move_to_console+0x19/0xb0 kernel: pm_restore_console+0x4d/0x70 kernel: enter_state+0x120/0x610 kernel: pm_suspend+0x49/0x90 kernel: INFO: task systemd-sleep:35518 blocked on a semaphore likely last held by task kworker/0:1:11 ``` Later the same night, unrelated services begin failing identically (repeated SIGKILL, never exiting): ``` systemd[1]: cups.service: start operation timed out. Terminating. systemd[1]: cups.service: State 'stop-sigterm' timed out. Killing. systemd[1]: cups.service: Killing process 35995 (9) with signal SIGKILL. systemd[1]: cups.service: Processes still around after SIGKILL. Ignoring. [cycle repeats ~35 times over 4+ hours] ``` No further journal entries follow the last cycle; the machine was unresponsive and required a hard power-button reset. ## Note on driver versions checked At the time of filing, NVIDIA's production branch had advanced to 595.84 (released 2026-06-17), one release ahead of the 595.71.05 installed here. I checked whether 595.84 was available as a packaged driver for Ubuntu 26.04 "resolute" before filing, to rule out that this was already fixed: - `resolute-updates` / `resolute-security` (official Ubuntu archive): only 595.71.05 - `ppa:graphics-drivers/ppa`: only 595.71.05 for `resolute` - NVIDIA's own CUDA apt repository (`developer.download.nvidia.com/compute/cuda/repos/ubuntu2604`): does not carry a `nvidia-driver-595-open` package matching 595.84 either (only unrelated tooling from the newer 610.x feature branch, e.g. `nvidia-settings`/`libxnvctrl0` 610.43.02) 595.84 is therefore only available as NVIDIA's `.run` installer for this Ubuntu release at present, which was intentionally not used here to avoid DKMS/Secure Boot conflicts with the distro-packaged driver. This report is filed against 595.71.05; it is not yet known whether 595.84 resolves the issue. ## Note on driver versions checked At the time of filing, NVIDIA's production branch had advanced to 595.84 (released 2026-06-17), one release ahead of the 595.71.05 installed here. I checked whether 595.84 was available as a packaged driver for Ubuntu 26.04 "resolute" before filing, to rule out that this was already fixed: - `resolute-updates` / `resolute-security` (official Ubuntu archive): only 595.71.05 - `ppa:graphics-drivers/ppa`: only 595.71.05 for `resolute` - NVIDIA's own CUDA apt repository (`developer.download.nvidia.com/compute/cuda/repos/ubuntu2604`): does not carry a `nvidia-driver-595-open` package matching 595.84 either (only unrelated tooling from the newer 610.x feature branch, e.g. `nvidia-settings`/`libxnvctrl0` 610.43.02) 595.84 is therefore only available as NVIDIA's `.run` installer for this Ubuntu release at present, which was intentionally not used here to avoid DKMS/Secure Boot conflicts with the distro-packaged driver. This report is filed against 595.71.05; it is not yet known whether 595.84 resolves the issue. The 595.84 changelog lists "Fixed a bug that could cause suspend and resume to fail on systems with runtime D3 (RTD3) power management enabled." I checked whether this applies here: ``` $ cat /proc/driver/nvidia/gpus/*/power Runtime D3 status: Disabled by default ... ``` RTD3 is disabled by default on this system (single desktop GPU with a directly-attached display, no hybrid/Optimus setup), so this specific changelog entry likely does not describe the same bug — the deadlock documented below appears unrelated to RTD3 and is filed as a distinct issue. ## Possibly related upstream reports - Ubuntu Launchpad bug **#2149963** (package `linux`) — RTX 50-series + nvidia-open 595/580 on kernel 7.0.0-14-generic, Ubuntu 26.04 "resolute": s2idle resume never completes after lid-close, requires hard reset. Same kernel/driver generation, same distro release; different GPU generation and different sleep mode (s2idle vs deep here), but the same overall "suspend/resume path never returns, only a hard reset recovers" symptom. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149963 ## Attachments to include when filing - Output of `ubuntu-bug linux` (for current package/version/apport metadata) — note: current `dmesg` will NOT contain the incident logs, since a hard reset clears the kernel ring buffer. - Full `journalctl` excerpts spanning each incident (attach as separate `.txt` files), specifically the windows around each `PM: suspend entry` through the last log line before the gap indicating the hard reset. - Output of `cat /proc/driver/nvidia/params | grep -iE 'Preserve|Kernel|Temp'` showing the modprobe workaround is active. - `nvidia-bug-report.sh` output (run `sudo nvidia-bug-report.sh`, attach the resulting `nvidia-bug-report.log.gz`) if it can be captured after a fresh incident before rebooting away the state. 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: beniu 4376 F.... wireplumber /dev/snd/controlC1: beniu 4376 F.... wireplumber /dev/snd/controlC0: beniu 4376 F.... wireplumber /dev/snd/seq: beniu 4356 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 2 19:32:21 2026 InstallationDate: Installed on 2026-02-21 (131 days ago) InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) MachineType: System manufacturer System Product Name ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=625d6275-b0c0-4dac-b793-5b840ac8fbf9 ro quiet splash nvidia-drm.modeset=1 mem_sleep_default=deep usbcore.autosuspend=-1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5901:bd10/03/2025:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158993/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-fde/5.15.0-1117.126)

All autopkgtests for the newly accepted linux-restricted-modules-azure-fde (5.15.0-1117.126) 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) nvidia-graphics-drivers-390/running (i386) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (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-azure-fde [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 2158935] Re: Fix FTBFS on noble for kernels with bcmasp

** Description changed: [ Impact ] noble-stable-2026-06-16 introduced a patch with hunks that applied - trivially despite using the incorrect field `eee_cfg` being used in 6.8 - context. Since the subsystem in which these mistakes were present is not - compiled in generic by default, the compilation error was not caught - until now. + trivially despite using a field `eee_cfg` which is not in 6.8 context. + Since the subsystem in which these mistakes were present is not compiled + in generic by default, the compilation error was not caught until now. + + In order to fix this issue, pick the changes which introduce `eee_cfg` + as a field of `struct phy_device`. [ Test Plan ] Kernel should compile properly after patch application. [ Where problems could occur ] Since the previous state was already a regression, there is no real risk of getting much worse. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158935 Title: Fix FTBFS on noble for kernels with bcmasp Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Noble: In Progress Status in linux-azure source package in Noble: In Progress Bug description: [ Impact ] noble-stable-2026-06-16 introduced a patch with hunks that applied trivially despite using a field `eee_cfg` which is not in 6.8 context. Since the subsystem in which these mistakes were present is not compiled in generic by default, the compilation error was not caught until now. In order to fix this issue, pick the changes which introduce `eee_cfg` as a field of `struct phy_device`. [ Test Plan ] Kernel should compile properly after patch application. [ Where problems could occur ] Since the previous state was already a regression, there is no real risk of getting much worse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158935/+subscriptions

[Bug 2158934] [NEW] Regression related to IOMMU grouping

Public bug reported: Title: Regression: PCI commit 7a126c1b6cfa ("Enable ACS after configuring IOMMU for OF platforms") merges IOMMU groups on AMD x86, breaks VFIO passthrough — needs revert 817daf163312 backported Package: linux (Ubuntu) — noble, 6.8 kernel Is this a regression? Yes. Summary Upstream commit 7a126c1b6cfa ("PCI: Enable ACS after configuring IOMMU for OF platforms") was backported into Ubuntu's noble 6.8 kernel in 6.8.0-130.130 (as part of syncing to upstream stable v6.12.75; see changelog entry for LP: #2150809). This commit moves pci_enable_acs() into pci_dma_configure(), which runs on all platforms, not just OF/Device-Tree ones. On AMD x86 systems this changes ACS evaluation timing relative to IOMMU group assignment, causing devices that previously sat in isolated IOMMU groups to merge into one — breaking VFIO PCI passthrough. This is a known upstream regression, already fixed via revert commit 817daf163312 ("PCI: Revert 'Enable ACS after configuring IOMMU for OF platforms'"), bisected and confirmed on AMD-Vi hardware. See: https://forum.level1techs.com/t/iommu-group-regression-in-linux-kernel-6-12-75/247479 The revert is absent from Ubuntu's noble 6.8 changelogs from 6.8.0-130.130 through 6.8.0-134.134. Impact VFIO PCI passthrough fails with: vfio 0000:0b:00.0: group 2 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. Reproduction (my system) 6.8.0-124-generic (pre-regression): two AMD 1022:1453 GPP bridges, each with a downstream NVIDIA GP107 GPU, sit in separate IOMMU groups (16 and 17). 6.8.0-134-generic (regressed): the same two bridges and both GPUs merge into a single IOMMU group. Both kernels use identical cmdline (amd_iommu iommu=pt) and identical vfio-pci binding via /etc/modprobe.d/vfio.conf (subsystem-ID matched). System info CPU/chipset: AMD Family 17h (Zen), AMD 400-series chipset GPUs: 2x NVIDIA GP107 [GTX 1050 Ti] (10de:1c82) + audio functions (10de:0fb9) Working: 6.8.0-124-generic (6.8.0-124.124) Broken: 6.8.0-134-generic (6.8.0-134.134) Requested fix Backport 817daf163312 into the noble 6.8 stable branch. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-134-generic 6.8.0-134.134 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 Uname: Linux 6.8.0-134-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: macro 2576 F.... wireplumber /dev/snd/controlC0: macro 2576 F.... wireplumber /dev/snd/seq: macro 2574 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jul 1 17:29:33 2026 InstallationDate: Installed on 2018-10-20 (2811 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-134-generic root=UUID=6eb14018-7030-43e9-bfbd-634e324040e2 ro quiet splash amd_iommu=on iommu=pt vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-134-generic N/A linux-backports-modules-6.8.0-134-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1001 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1001:bd09/27/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158934 Title: Regression related to IOMMU grouping Status in linux package in Ubuntu: New Bug description: Title: Regression: PCI commit 7a126c1b6cfa ("Enable ACS after configuring IOMMU for OF platforms") merges IOMMU groups on AMD x86, breaks VFIO passthrough — needs revert 817daf163312 backported Package: linux (Ubuntu) — noble, 6.8 kernel Is this a regression? Yes. Summary Upstream commit 7a126c1b6cfa ("PCI: Enable ACS after configuring IOMMU for OF platforms") was backported into Ubuntu's noble 6.8 kernel in 6.8.0-130.130 (as part of syncing to upstream stable v6.12.75; see changelog entry for LP: #2150809). This commit moves pci_enable_acs() into pci_dma_configure(), which runs on all platforms, not just OF/Device-Tree ones. On AMD x86 systems this changes ACS evaluation timing relative to IOMMU group assignment, causing devices that previously sat in isolated IOMMU groups to merge into one — breaking VFIO PCI passthrough. This is a known upstream regression, already fixed via revert commit 817daf163312 ("PCI: Revert 'Enable ACS after configuring IOMMU for OF platforms'"), bisected and confirmed on AMD-Vi hardware. See: https://forum.level1techs.com/t/iommu-group-regression-in-linux-kernel-6-12-75/247479 The revert is absent from Ubuntu's noble 6.8 changelogs from 6.8.0-130.130 through 6.8.0-134.134. Impact VFIO PCI passthrough fails with: vfio 0000:0b:00.0: group 2 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. Reproduction (my system) 6.8.0-124-generic (pre-regression): two AMD 1022:1453 GPP bridges, each with a downstream NVIDIA GP107 GPU, sit in separate IOMMU groups (16 and 17). 6.8.0-134-generic (regressed): the same two bridges and both GPUs merge into a single IOMMU group. Both kernels use identical cmdline (amd_iommu iommu=pt) and identical vfio-pci binding via /etc/modprobe.d/vfio.conf (subsystem-ID matched). System info CPU/chipset: AMD Family 17h (Zen), AMD 400-series chipset GPUs: 2x NVIDIA GP107 [GTX 1050 Ti] (10de:1c82) + audio functions (10de:0fb9) Working: 6.8.0-124-generic (6.8.0-124.124) Broken: 6.8.0-134-generic (6.8.0-134.134) Requested fix Backport 817daf163312 into the noble 6.8 stable branch. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-134-generic 6.8.0-134.134 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 Uname: Linux 6.8.0-134-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: macro 2576 F.... wireplumber /dev/snd/controlC0: macro 2576 F.... wireplumber /dev/snd/seq: macro 2574 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jul 1 17:29:33 2026 InstallationDate: Installed on 2018-10-20 (2811 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-134-generic root=UUID=6eb14018-7030-43e9-bfbd-634e324040e2 ro quiet splash amd_iommu=on iommu=pt vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-134-generic N/A linux-backports-modules-6.8.0-134-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1001 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1001:bd09/27/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158934/+subscriptions

[Bug 2158932] [NEW] Black screen on boot with Linux Kernel 6.8.0-134.134

Public bug reported: Using Linux Mint with Linux Kernel 6.8.0-124 with no issues. Update Manager showed new update for Linux Kernel available, version 6.8.0-134.134. Installed update and restarted system as instructed. Chose to launch Linux Mint from Grub boot menu (dual boot system with Windows 10), black screen results after selection, no splash screen, nothing. Reverted to Kernel 6.8.0-124 successfully via Timeshift from Linux Mint USB boot disk. Reattempted update to Kernel 6.8.0-134.134, same result: black screen after boot selection. Again reverted backto Kernel 6.8.0-124 successfully via Timeshift from Linux Mint USB boot disk. I have a second system (dual boot Linux Mint/Windows 10) with a similar hardware configuration but with an older Radeon RX580 that I was able to upgrade to Kernel 6.8.0-134.134 successfully. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2158932/+attachment/5979790/+files/lspci-vnvn.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158932 Title: Black screen on boot with Linux Kernel 6.8.0-134.134 Status in linux package in Ubuntu: New Bug description: Using Linux Mint with Linux Kernel 6.8.0-124 with no issues. Update Manager showed new update for Linux Kernel available, version 6.8.0-134.134. Installed update and restarted system as instructed. Chose to launch Linux Mint from Grub boot menu (dual boot system with Windows 10), black screen results after selection, no splash screen, nothing. Reverted to Kernel 6.8.0-124 successfully via Timeshift from Linux Mint USB boot disk. Reattempted update to Kernel 6.8.0-134.134, same result: black screen after boot selection. Again reverted backto Kernel 6.8.0-124 successfully via Timeshift from Linux Mint USB boot disk. I have a second system (dual boot Linux Mint/Windows 10) with a similar hardware configuration but with an older Radeon RX580 that I was able to upgrade to Kernel 6.8.0-134.134 successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158932/+subscriptions

[Bug 2158920] Re: noble-stable-2026-06-16 dropped a bracket causing FTBFS

** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158920 Title: noble-stable-2026-06-16 dropped a bracket causing FTBFS Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Noble: Confirmed Status in linux-azure source package in Noble: Fix Committed Bug description: [ Impact ] Azure kernels have recently been seeing FTBFS' due to a broken change introduced by upstream stable. Configs in that kernel bring out a compilation error due to a broken patch I adjusted in noble- stable-2026-06-16. [ Test Plan ] Kernel should compile properly after patch application. [ Where problems could occur ] Since the previous state was already a regression, there is no real risk of getting much worse. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158920/+subscriptions

[Bug 2158928] [NEW] Thinkpad T14 gen4 AMD: Frequent kernel panics on boot since 7.0.0-22

Public bug reported: I experience random kernel panic and lock on boot since kernel 7.0.0-22 at least, but happens also on 7.0.0-27. The kernel 7.0.0-15 seems to be fine but it would require multiple reboots. Jul 01 21:10:11 earl kernel: INFO: task kworker/u64:6:187 blocked for more than 122 seconds. Jul 01 21:10:11 earl kernel: Not tainted 7.0.0-27-generic #27-Ubuntu Jul 01 21:10:11 earl kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 01 21:10:11 earl kernel: task:kworker/u64:6 state:D stack:0 pid:187 tgid:187 ppid:2 task_flags:0x4208060 flags:0x00080000 Jul 01 21:10:11 earl kernel: Workqueue: pm pm_runtime_work Jul 01 21:10:11 earl kernel: Call Trace: Jul 01 21:10:11 earl kernel: <TASK> Jul 01 21:10:11 earl kernel: __schedule+0x2b2/0x630 Jul 01 21:10:11 earl kernel: schedule+0x27/0x90 Jul 01 21:10:11 earl kernel: schedule_timeout+0xcf/0x110 Jul 01 21:10:11 earl kernel: wait_for_completion+0x81/0x140 Jul 01 21:10:11 earl kernel: __flush_work+0x270/0x3c0 Jul 01 21:10:11 earl kernel: ? __pfx_wq_barrier_func+0x10/0x10 Jul 01 21:10:11 earl kernel: ? __pfx_pci_pm_runtime_suspend+0x10/0x10 Jul 01 21:10:11 earl kernel: flush_work+0x21/0x30 Jul 01 21:10:11 earl kernel: tb_ring_stop+0xd9/0x200 [thunderbolt] Jul 01 21:10:11 earl kernel: ? tb_switch_suspend+0x167/0x1b0 [thunderbolt] Jul 01 21:10:11 earl kernel: tb_ctl_stop+0x3c/0x100 [thunderbolt] Jul 01 21:10:11 earl kernel: ? tb_runtime_suspend+0x5c/0x70 [thunderbolt] Jul 01 21:10:11 earl kernel: tb_domain_runtime_suspend+0x3a/0x50 [thunderbolt] Jul 01 21:10:11 earl kernel: nhi_runtime_suspend+0x1f/0x50 [thunderbolt] Jul 01 21:10:11 earl kernel: pci_pm_runtime_suspend+0x6a/0x1a0 Jul 01 21:10:11 earl kernel: __rpm_callback+0x4b/0x1f0 Jul 01 21:10:11 earl kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Jul 01 21:10:11 earl kernel: ? ktime_get_mono_fast_ns+0x36/0xe0 Jul 01 21:10:11 earl kernel: ? __pfx_pci_pm_runtime_suspend+0x10/0x10 Jul 01 21:10:11 earl kernel: rpm_callback+0x77/0x80 Jul 01 21:10:11 earl kernel: rpm_suspend+0xe1/0x610 Jul 01 21:10:11 earl kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Jul 01 21:10:11 earl kernel: rpm_idle+0x247/0x360 Jul 01 21:10:11 earl kernel: pm_runtime_work+0x8d/0xa0 Jul 01 21:10:11 earl kernel: process_one_work+0x1ac/0x3d0 Jul 01 21:10:11 earl kernel: worker_thread+0x1b8/0x360 Jul 01 21:10:11 earl kernel: ? __pfx_worker_thread+0x10/0x10 Jul 01 21:10:11 earl kernel: kthread+0xf7/0x130 Jul 01 21:10:11 earl kernel: ? __pfx_kthread+0x10/0x10 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 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 21:19:59 2026 InstallationDate: Installed on 2025-04-12 (445 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 21K3S0DS00 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amdgpu.dcdebugmask=0x8000 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-05-19 (43 days ago) dmi.bios.date: 03/19/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET69W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3S0DS00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR2FET69W(1.49):bd03/19/2026:br1.49:efr1.33:svnLENOVO:pn21K3S0DS00:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3S0DS00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4:pfaThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3S0DS00 dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "kernel_lpxxxx_ubuntu7.0.0-27-boot-freeze.log" https://bugs.launchpad.net/bugs/2158928/+attachment/5979767/+files/kernel_lpxxxx_ubuntu7.0.0-27-boot-freeze.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158928 Title: Thinkpad T14 gen4 AMD: Frequent kernel panics on boot since 7.0.0-22 Status in linux package in Ubuntu: New Bug description: I experience random kernel panic and lock on boot since kernel 7.0.0-22 at least, but happens also on 7.0.0-27. The kernel 7.0.0-15 seems to be fine but it would require multiple reboots. Jul 01 21:10:11 earl kernel: INFO: task kworker/u64:6:187 blocked for more than 122 seconds. Jul 01 21:10:11 earl kernel: Not tainted 7.0.0-27-generic #27-Ubuntu Jul 01 21:10:11 earl kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 01 21:10:11 earl kernel: task:kworker/u64:6 state:D stack:0 pid:187 tgid:187 ppid:2 task_flags:0x4208060 flags:0x00080000 Jul 01 21:10:11 earl kernel: Workqueue: pm pm_runtime_work Jul 01 21:10:11 earl kernel: Call Trace: Jul 01 21:10:11 earl kernel: <TASK> Jul 01 21:10:11 earl kernel: __schedule+0x2b2/0x630 Jul 01 21:10:11 earl kernel: schedule+0x27/0x90 Jul 01 21:10:11 earl kernel: schedule_timeout+0xcf/0x110 Jul 01 21:10:11 earl kernel: wait_for_completion+0x81/0x140 Jul 01 21:10:11 earl kernel: __flush_work+0x270/0x3c0 Jul 01 21:10:11 earl kernel: ? __pfx_wq_barrier_func+0x10/0x10 Jul 01 21:10:11 earl kernel: ? __pfx_pci_pm_runtime_suspend+0x10/0x10 Jul 01 21:10:11 earl kernel: flush_work+0x21/0x30 Jul 01 21:10:11 earl kernel: tb_ring_stop+0xd9/0x200 [thunderbolt] Jul 01 21:10:11 earl kernel: ? tb_switch_suspend+0x167/0x1b0 [thunderbolt] Jul 01 21:10:11 earl kernel: tb_ctl_stop+0x3c/0x100 [thunderbolt] Jul 01 21:10:11 earl kernel: ? tb_runtime_suspend+0x5c/0x70 [thunderbolt] Jul 01 21:10:11 earl kernel: tb_domain_runtime_suspend+0x3a/0x50 [thunderbolt] Jul 01 21:10:11 earl kernel: nhi_runtime_suspend+0x1f/0x50 [thunderbolt] Jul 01 21:10:11 earl kernel: pci_pm_runtime_suspend+0x6a/0x1a0 Jul 01 21:10:11 earl kernel: __rpm_callback+0x4b/0x1f0 Jul 01 21:10:11 earl kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Jul 01 21:10:11 earl kernel: ? ktime_get_mono_fast_ns+0x36/0xe0 Jul 01 21:10:11 earl kernel: ? __pfx_pci_pm_runtime_suspend+0x10/0x10 Jul 01 21:10:11 earl kernel: rpm_callback+0x77/0x80 Jul 01 21:10:11 earl kernel: rpm_suspend+0xe1/0x610 Jul 01 21:10:11 earl kernel: ? srso_alias_return_thunk+0x5/0xfbef5 Jul 01 21:10:11 earl kernel: rpm_idle+0x247/0x360 Jul 01 21:10:11 earl kernel: pm_runtime_work+0x8d/0xa0 Jul 01 21:10:11 earl kernel: process_one_work+0x1ac/0x3d0 Jul 01 21:10:11 earl kernel: worker_thread+0x1b8/0x360 Jul 01 21:10:11 earl kernel: ? __pfx_worker_thread+0x10/0x10 Jul 01 21:10:11 earl kernel: kthread+0xf7/0x130 Jul 01 21:10:11 earl kernel: ? __pfx_kthread+0x10/0x10 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 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 21:19:59 2026 InstallationDate: Installed on 2025-04-12 (445 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 21K3S0DS00 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amdgpu.dcdebugmask=0x8000 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-05-19 (43 days ago) dmi.bios.date: 03/19/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET69W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3S0DS00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR2FET69W(1.49):bd03/19/2026:br1.49:efr1.33:svnLENOVO:pn21K3S0DS00:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3S0DS00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4:pfaThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3S0DS00 dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158928/+subscriptions

[Bug 2158286] Re: NFC driver on Thinkpad T14 AMD gen4 causes a lot interrupts

Hi, Gabriela, here it is. on the current 7.0.0-27 journalctl -b 0 -k > kernel_lp2158286_ubuntu7.0.0-27.log $ cat top_ubuntu7.0.0-27.txt top - 19:11:31 up 6 min, 1 user, load average: 4.40, 1.88, 0.89 Tasks: 721 total, 1 running, 720 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.6 us, 3.9 sy, 0.0 ni, 95.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 30209.5 total, 16793.8 free, 5993.6 used, 7629.5 buff/cache MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 24215.9 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 787 root -51 0 0 0 0 S 33.3 0.0 2:03.80 irq/91-+ 4666 root 20 0 0 0 0 I 16.7 0.0 0:00.61 kworker+ 573 root 20 0 0 0 0 I 8.3 0.0 0:00.38 kworker+ 4664 root 20 0 0 0 0 I 8.3 0.0 0:00.97 kworker+ 17210 mastier 20 0 16468 6420 4236 R 8.3 0.0 0:00.02 top 1 root 20 0 28840 19068 11100 S 0.0 0.1 0:03.86 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 pool_wo+ 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ 5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ 6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ 7 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ 8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ ** Attachment added: "kernel_lp2158286_ubuntu7.0.0-27.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158286/+attachment/5979765/+files/kernel_lp2158286_ubuntu7.0.0-27.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158286 Title: NFC driver on Thinkpad T14 AMD gen4 causes a lot interrupts Status in linux package in Ubuntu: New Bug description: Recently on kernel 7.0.0-generic-22 (after upgrade from 24.04 to 26.04) my fans started to behave quite noisy even in Balanced mode (3000rpm), while in powersaving instead of going down to 0 RPM and still oscilate at 2200RPM level. So I researched and it seems there is NFC driver causing a lot interrupts  mastier@earl:~$ cat /proc/acpi/ibm/fan   status: enabled   speed: 3081   level: auto   mastier@earl:~$ sensors   thinkpad-isa-0000   Adapter: ISA adapter   fan1: 3077 RPM   fan2: 3077 RPM   CPU: +56.0°C ... The interrupts: mastier@earl:~$ top -b -n 1 -o +%CPU | head -n 20 top - 16:57:13 up 5:08, 1 user, load average: 1.13, 1.29, 1.05 Tasks: 736 total, 1 running, 735 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.4 us, 6.7 sy, 0.0 ni, 89.4 id, 0.0 wa, 0.0 hi, 0.6 si, 0.0 st MiB Mem : 30209.5 total, 2540.6 free, 14878.1 used, 10510.9 buff/cache MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 15331.4 avail Mem     PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND   13162 mastier 20 0 28.6g 900176 316932 S 91.7 2.9 16:06.74 firefox     773 root -51 0 0 0 0 S 33.3 0.0 96:47.99 irq/91-+    2186 root 20 0 1423172 57652 25748 S 8.3 0.2 1:55.52 tailsca+  136500 mastier 20 0 16464 6384 4204 R 8.3 0.0 0:00.02 top       1 root 20 0 28836 19296 11248 S 0.0 0.1 0:06.74 systemd       2 root 20 0 0 0 0 S 0.0 0.0 0:00.89 kthreadd       3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 pool_wo+ ...  $ grep "91:" /proc/interrupts   91: 0 0 0 0 0 834177081 0 0 0 0 0 0 0 0 0 0 amd_gpio 84 nxp-nci_i2c ```` so I unloaded this driver temporarily and now it looks better sudo rmmod nxp_nci_i2c sudo rmmod nxp_nci now looks better mastier@earl:~$ top -b -n 1 -o +%CPU | head -n 20 top - 17:14:56 up 5:26, 1 user, load average: 1.15, 0.92, 0.95 Tasks: 734 total, 1 running, 733 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.6 us, 1.6 sy, 0.0 ni, 94.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 30209.5 total, 1952.3 free, 15122.9 used, 10699.8 buff/cache MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 15086.6 avail Mem     PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND  148217 mastier 20 0 16464 6384 4204 R 16.7 0.0 0:00.03 top    8911 mastier 20 0 10.9g 423028 205996 S 8.3 1.4 24:40.69 gnome-s+   16791 mastier 20 0 2716908 131808 77456 S 8.3 0.4 0:45.95 Isolate+       1 root 20 0 28836 19296 11248 S 0.0 0.1 0:06.83 systemd       2 root 20 0 0 0 0 S 0.0 0.0 0:00.93 kthreadd       3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 pool_wo+       4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+       5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+       6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+       7 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+       8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+      10 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+      13 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker+ It seems to be the result of the following regression: https://patchew.org/linux/20260519-nfc-nxp-nci-i2c-restore-irq-trigger-fallback-v4-1-8580d8e18016@amd.com/ https://patchew.org/linux/20260511082611.12721-1-bartosz.golaszewski@oss.qualcomm.com/ also relevant thread: https://bbs.archlinux.org/viewtopic.php?id=312733 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 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 17:03:23 2026 InstallationDate: Installed on 2025-04-12 (439 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 21K3S0DS00 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro amdgpu.dcdebugmask=0x8000 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-05-19 (37 days ago) dmi.bios.date: 03/19/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET69W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3S0DS00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR2FET69W(1.49):bd03/19/2026:br1.49:efr1.33:svnLENOVO:pn21K3S0DS00:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3S0DS00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4:pfaThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3S0DS00 dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158286/+subscriptions