All autopkgtests for the newly accepted linux-meta-gcp (6.8.0-1064.72) 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) glibc/2.39-0ubuntu8.7 (amd64, arm64) lxc/1:5.0.3-2ubuntu7.2 (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-gcp [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 2158858] Please test proposed package
Hello Chris, or anyone else affected, Accepted linux-firmware-misc into resolute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware- misc/20260319.git217ca6e4-0ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- resolute to verification-done-resolute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-resolute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158858 Title: Fix no audio output and mute hotkey not working on HP ZBook 8 G2a Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-misc package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-firmware source package in Noble: Fix Committed Status in linux-oem-6.17 source package in Noble: New Status in linux source package in Resolute: New Status in linux-firmware source package in Resolute: Invalid Status in linux-firmware-misc source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] No audio output from the built-in speaker and the speaker and mic mute LEDs never turn on on affected HP systems (SSIDs 0x103c:0x8f94 and 0x103c:0x8f95). ================ Linux Kernel ======================== [Fix] Add the ALC245_FIXUP_HP_TAS2781_I2C_MUTE_LED quirk to enable speaker and mic mute LEDs for SSIDs 0x103c:0x8f94 and 0x103c:0x8f95. ================ linux-firmware ======================== [Fix] Backport upstream fix a16ce5c67 ("linux-firmware: Add firmware for new projects") [Test Plan] 1. Boot up the affected machine 2. Check the audio output by pressing `Test speakers` on the g-d-d sound menu. 3. Press the speaker and mic mute keys and verify the following - Speaker muted: LED is on - Speaker not muted: LED is off - Mic muted: LED is on - Mic not muted: LED is off [Where problems could occur] This change is restricted on particular SSIDs. Should be no risk of regression. -- PR: Noble: https://kernel.ubuntu.com/forgejo/kernel/linux-firmware/pulls/393 Resolute: https://kernel.ubuntu.com/forgejo/kernel/linux-firmware/pulls/394 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2158858/+subscriptions
[Bug 2158858] Re: Fix no audio output and mute hotkey not working on HP ZBook 8 G2a
** Changed in: linux-oem-6.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware-misc (Ubuntu) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158858 Title: Fix no audio output and mute hotkey not working on HP ZBook 8 G2a Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-misc package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-firmware source package in Noble: Fix Committed Status in linux-oem-6.17 source package in Noble: New Status in linux source package in Resolute: New Status in linux-firmware source package in Resolute: Invalid Status in linux-firmware-misc source package in Resolute: Fix Committed Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] No audio output from the built-in speaker and the speaker and mic mute LEDs never turn on on affected HP systems (SSIDs 0x103c:0x8f94 and 0x103c:0x8f95). ================ Linux Kernel ======================== [Fix] Add the ALC245_FIXUP_HP_TAS2781_I2C_MUTE_LED quirk to enable speaker and mic mute LEDs for SSIDs 0x103c:0x8f94 and 0x103c:0x8f95. ================ linux-firmware ======================== [Fix] Backport upstream fix a16ce5c67 ("linux-firmware: Add firmware for new projects") [Test Plan] 1. Boot up the affected machine 2. Check the audio output by pressing `Test speakers` on the g-d-d sound menu. 3. Press the speaker and mic mute keys and verify the following - Speaker muted: LED is on - Speaker not muted: LED is off - Mic muted: LED is on - Mic not muted: LED is off [Where problems could occur] This change is restricted on particular SSIDs. Should be no risk of regression. -- PR: Noble: https://kernel.ubuntu.com/forgejo/kernel/linux-firmware/pulls/393 Resolute: https://kernel.ubuntu.com/forgejo/kernel/linux-firmware/pulls/394 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2158858/+subscriptions
[Bug 2160514] [NEW] System freezes on kernel 7.0.0-27-generic (Ubuntu 26.04), requires hard power-off
Public bug reported: System hangs/freezes completely (no input response, screen frozen) into a normal desktop session, with no consistent trigger application or workload. Only recovery is holding the power button to force shutdown. Hardware: Dell Latitude 7490, Intel Core i7-8650U, Samsung MZVLB256HAHQ NVMe SSD OS: Ubuntu 26.04 LTS (fresh install) Kernel: 7.0.0-27-generic (only kernel version available, no older kernel to test against) Desktop: GNOME 50 on Wayland (GNOME-on-Xorg not available on this Ubuntu version) Frequency: Occurs across multiple separate boot sessions, Confirmed via `journalctl --list-boots` showing multiple sessions ending abruptly mid-log with no shutdown.target reached, unlike normal shutdowns which show a clean unmount sequence. Diagnostics already ruled out: - Thermal: CPU temps normal (35-46°C) both from `sensors` and via `journalctl -b -1 | grep -i therm` showing no throttling/warning events near freeze times - Memory: no OOM kill events found in journal - Disk health: SMART overall-health PASSED, 0 media/data integrity errors, 11% wear NVMe SMART data shows 6,122 unsafe shutdowns vs 5,086 power cycles, consistent with repeated forced power-offs due to this freeze, not user habit. One investigated freeze session showed unusual activity in the ~1 minute before the log went silent: ProtonVPN interface teardown, a burst of UFW-blocked IPv6 packets, and repeated DNSSEC validation failures via systemd-resolved. However, the user has also experienced this same freeze pattern with no VPN or custom network configuration installed at all (including on a separate Linux Mint installation), so this network activity is likely coincidental rather than causal. A matching report was found on Framework Community (https://community.frame.work/t/ubuntu-26-04-suspend-resume-crash-on-kernel-7-0-0-27/83394) describing the same kernel build (7.0.0-27) causing freezes with filesystem dropping to read-only, on different hardware (Framework 13, 12th Gen Intel). This suggests a kernel-level regression in this specific point release rather than a hardware-specific issue. Steps to reproduce: None consistent — freeze occurs spontaneously during normal use, regardless of running applications. Expected behavior: System remains responsive during normal desktop use. Actual behavior: Complete freeze requiring hard power-off, no error logged before the freeze (system appears to stop writing to the journal entirely once frozen). 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/controlC0: mysteries 4046 F.... wireplumber /dev/snd/seq: mysteries 4028 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 16:51:25 2026 InstallationDate: Installed on 2026-07-11 (2 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 413c:81b6 Dell Computer Corp. DW5811e Snapdragon™ X7 LTE MachineType: Dell Inc. Latitude 7490 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=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2025 dmi.bios.release: 1.44 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.44.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.44.0:bd04/08/2025:br1.44:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell 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/2160514 Title: System freezes on kernel 7.0.0-27-generic (Ubuntu 26.04), requires hard power-off Status in linux package in Ubuntu: New Bug description: System hangs/freezes completely (no input response, screen frozen) into a normal desktop session, with no consistent trigger application or workload. Only recovery is holding the power button to force shutdown. Hardware: Dell Latitude 7490, Intel Core i7-8650U, Samsung MZVLB256HAHQ NVMe SSD OS: Ubuntu 26.04 LTS (fresh install) Kernel: 7.0.0-27-generic (only kernel version available, no older kernel to test against) Desktop: GNOME 50 on Wayland (GNOME-on-Xorg not available on this Ubuntu version) Frequency: Occurs across multiple separate boot sessions, Confirmed via `journalctl --list-boots` showing multiple sessions ending abruptly mid-log with no shutdown.target reached, unlike normal shutdowns which show a clean unmount sequence. Diagnostics already ruled out: - Thermal: CPU temps normal (35-46°C) both from `sensors` and via `journalctl -b -1 | grep -i therm` showing no throttling/warning events near freeze times - Memory: no OOM kill events found in journal - Disk health: SMART overall-health PASSED, 0 media/data integrity errors, 11% wear NVMe SMART data shows 6,122 unsafe shutdowns vs 5,086 power cycles, consistent with repeated forced power-offs due to this freeze, not user habit. One investigated freeze session showed unusual activity in the ~1 minute before the log went silent: ProtonVPN interface teardown, a burst of UFW-blocked IPv6 packets, and repeated DNSSEC validation failures via systemd-resolved. However, the user has also experienced this same freeze pattern with no VPN or custom network configuration installed at all (including on a separate Linux Mint installation), so this network activity is likely coincidental rather than causal. A matching report was found on Framework Community (https://community.frame.work/t/ubuntu-26-04-suspend-resume-crash-on-kernel-7-0-0-27/83394) describing the same kernel build (7.0.0-27) causing freezes with filesystem dropping to read-only, on different hardware (Framework 13, 12th Gen Intel). This suggests a kernel-level regression in this specific point release rather than a hardware-specific issue. Steps to reproduce: None consistent — freeze occurs spontaneously during normal use, regardless of running applications. Expected behavior: System remains responsive during normal desktop use. Actual behavior: Complete freeze requiring hard power-off, no error logged before the freeze (system appears to stop writing to the journal entirely once frozen). 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/controlC0: mysteries 4046 F.... wireplumber /dev/snd/seq: mysteries 4028 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 16:51:25 2026 InstallationDate: Installed on 2026-07-11 (2 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 413c:81b6 Dell Computer Corp. DW5811e Snapdragon™ X7 LTE MachineType: Dell Inc. Latitude 7490 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=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2025 dmi.bios.release: 1.44 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.44.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.44.0:bd04/08/2025:br1.44:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160514/+subscriptions
[Bug 2159786] Re: IOMMU Grouping bug in 6.8.0-134 generic kernel
*** This bug is a duplicate of bug 2158934 *** https://bugs.launchpad.net/bugs/2158934 ** This bug has been marked a duplicate of bug 2158934 Regression related to IOMMU grouping -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159786 Title: IOMMU Grouping bug in 6.8.0-134 generic kernel Status in linux package in Ubuntu: Confirmed Bug description: I have update from kernel 6.8.0-124-generic to 6.8.0-134-generic On the old kernel GRUB_DEFAULT="gnulinux-advanced-4e04515f-2415-4fcd-8904-9f192b693d8e>gnulinux-6.8.0-124-generic-advanced-4e04515f-2415-4fcd-8904-9f192b693d8e" GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=0 GRUB_DISABLE_OS_PROBER=true GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amd_iommu=on iommu=pt" GRUB_CMDLINE_LINUX="" bogdan@gpu-server:~$ uname -r 6.8.0-124-generic bogdan@gpu-server:~$ ./iommu.sh IOMMU Group 0 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 10 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 11 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 12 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 13 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) IOMMU Group 13 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) IOMMU Group 14 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0 [1022:1440] IOMMU Group 14 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1 [1022:1441] IOMMU Group 14 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2 [1022:1442] IOMMU Group 14 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3 [1022:1443] IOMMU Group 14 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4 [1022:1444] IOMMU Group 14 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5 [1022:1445] IOMMU Group 14 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6 [1022:1446] IOMMU Group 14 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7 [1022:1447] IOMMU Group 15 01:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. Device [2646:5027] (rev 01) IOMMU Group 16 02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream [1022:57ad] IOMMU Group 17 03:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] IOMMU Group 18 03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] IOMMU Group 19 03:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] IOMMU Group 1 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 20 03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] IOMMU Group 21 03:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] IOMMU Group 21 08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 21 08:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 21 08:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 22 03:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] IOMMU Group 22 09:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 23 03:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] IOMMU Group 23 0a:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 24 04:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. Device [2646:5028] (rev 03) IOMMU Group 25 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] IOMMU Group 26 06:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) IOMMU Group 27 07:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) IOMMU Group 28 0b:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2f04] (rev a1) IOMMU Group 28 0b:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:2f80] (rev a1) IOMMU Group 29 0c:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD104 [GeForce RTX 4070 SUPER] [10de:2783] (rev a1) IOMMU Group 29 0c:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22bc] (rev a1) IOMMU Group 2 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 30 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] IOMMU Group 31 0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 32 0e:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486] IOMMU Group 33 0e:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 34 0e:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] IOMMU Group 3 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 4 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 5 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 6 00:03.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 7 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 8 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 9 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] But when I ran apt update && apt upgrade, when the new kernel was installed bogdan@gpu-server:~$ uname -r ./iommu.sh 6.8.0-134-generic IOMMU Group 0 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 0 00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 0 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 0 01:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. Device [2646:5027] (rev 01) IOMMU Group 0 02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream [1022:57ad] IOMMU Group 0 03:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] IOMMU Group 0 03:03.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] IOMMU Group 0 03:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] IOMMU Group 0 03:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a3] IOMMU Group 0 03:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] IOMMU Group 0 03:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] IOMMU Group 0 03:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:57a4] IOMMU Group 0 04:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. Device [2646:5028] (rev 03) IOMMU Group 0 05:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] IOMMU Group 0 06:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) IOMMU Group 0 07:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) IOMMU Group 0 08:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 0 08:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 0 08:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 0 09:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 0 0a:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 1 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 2 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 2 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 2 00:03.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] IOMMU Group 2 0b:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2f04] (rev a1) IOMMU Group 2 0b:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:2f80] (rev a1) IOMMU Group 2 0c:00.0 VGA compatible controller [0300]: NVIDIA Corporation AD104 [GeForce RTX 4070 SUPER] [10de:2783] (rev a1) IOMMU Group 2 0c:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22bc] (rev a1) IOMMU Group 3 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 4 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 5 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 5 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 5 0d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] IOMMU Group 6 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 6 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 6 0e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 6 0e:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486] IOMMU Group 6 0e:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 6 0e:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] IOMMU Group 7 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) IOMMU Group 7 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) IOMMU Group 8 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0 [1022:1440] IOMMU Group 8 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1 [1022:1441] IOMMU Group 8 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2 [1022:1442] IOMMU Group 8 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3 [1022:1443] IOMMU Group 8 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4 [1022:1444] IOMMU Group 8 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5 [1022:1445] IOMMU Group 8 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6 [1022:1446] IOMMU Group 8 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7 [1022:1447] I used the same GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amd_iommu=on iommu=pt" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159786/+subscriptions
[Bug 2158934] Re: Regression related to IOMMU grouping
yes it does work -- 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: Invalid Status in linux source package in Noble: Fix Committed 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 2156559] Re: Fix no sound output device on Dell GhostRider PTL no camera SKU
This bug is awaiting verification that the linux-xuantie/7.0.0-1005.5 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-xuantie' to 'verification-done- resolute-linux-xuantie'. If the problem still exists, change the tag 'verification-needed-resolute-linux-xuantie' to 'verification-failed- resolute-linux-xuantie'. 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-xuantie-v2 verification-needed-resolute-linux-xuantie -- 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 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 2160457] [NEW] Kernel panic in srso_safe_ret / kick_ilb during sched_tick on AMD Ryzen 7 4800U (Zen2)
Public bug reported: DESCRIPTION: == Summary == Repeated kernel panics on AMD Ryzen 7 4800U (Renoir/Zen2) triggered by the SRSO (Speculative Return Stack Overflow) mitigation interacting with the scheduler tick path. The system crashes every 1-11 days with no user-space trigger. Crashes occur in both linux-image-7.0.0-22-generic and linux-image-7.0.0-27-generic. Workaround: processor.max_cstate=1 (preventing deep C-states avoids the crash path). == Hardware == - System: AZW (Beelink) SER Mini PC - CPU: AMD Ryzen 7 4800U with Radeon Graphics (Zen2 / Renoir) - Microcode: 0x0860010d (updated from 0x08600106 at boot) - GPU: AMD Renoir [Radeon Vega Series] (integrated, amdgpu driver) - RAM: 16GB DDR4 - BIOS: SER_V1.14_P3C6M43_B_Link (03/24/2022) — latest available for this model - NVMe storage == Software == - Ubuntu 26.04 LTS (fresh install on 2026-05-26) - Kernel: 7.0.0-22-generic and 7.0.0-27-generic (both affected) - amd64-microcode: 3.20251202.1ubuntu2 - linux-firmware: 20260319.git217ca6e4.1ubuntu - Boot params: quiet splash crashkernel=... - Active mitigation: srso_return_thunk (confirmed via dmesg) - NOPTI active == Crash #1 — 2026-07-10 (kernel 7.0.0-27) == Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 0 Comm: swapper/0 RIP: 0010:srso_safe_ret+0x0/0x20 Call Trace: <IRQ> sched_tick+0x48/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x9a/0xd0 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1b/0x20 RIP: 0010:cpuidle_enter_state+0xca/0x700 cpuidle_enter+0x30/0x50 cpuidle_idle_call+0x16b/0x1f0 do_idle+0x94/0xf0 </TASK> == Crash #2 — 2026-07-12 (kernel 7.0.0-27) == BUG: unable to handle page fault for address: ffffffff99053b04 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD bc447067 P4D bc447067 PUD bc448063 PMD 0 Oops: Oops: 0002 [#1] SMP NOPTI CPU: 0 UID: 1000 PID: 2680076 Comm: curl RIP: 0010:kick_ilb+0x6e/0x180 Call Trace: <TASK> kick_ilb+0x52/0x180 nohz_balancer_kick+0x92/0x2d0 sched_balance_trigger+0x4c/0x90 sched_tick+0xf9/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x44/0xd0 asm_sysvec_apic_timer_interrupt+0x1b/0x20 </TASK> == Additional context == - amdgpu driver logs "dm_irq_work_func [amdgpu] hogged CPU for >13333us" 35+ times per boot, suggesting IRQ pressure on the scheduler tick path. - Both crashes occur on CPU 0 during timer interrupt → sched_tick. - Crash #1 is an invalid opcode in the SRSO safe_ret thunk itself. - Crash #2 is a page fault in kick_ilb writing to an unmapped kernel address (PMD 0), suggesting corrupted per-cpu data or text patching issue in the SRSO path. - The system was stable for 14 days once (when amdgpu initialized without errors). - Full kdump vmcores are available in /var/crash/ for all crashes. == Crash frequency == 6+ crashes since 2026-05-29, intervals ranging from 1.5 to 11 days. No specific user-space trigger identified — crashes happen during idle or light workloads (cron jobs, curl). == Workaround == Adding processor.max_cstate=1 to kernel boot parameters prevents the CPU from entering deep C-states where the crash occurs. This confirms the interaction between cpuidle exit path, SRSO return thunks, and sched_tick. == Possible root cause == The SRSO mitigation (srso_return_thunk / srso_safe_ret) appears to have a bug in the text patching or in the interaction with the scheduler's nohz/idle balancer on AMD Zen2 processors when exiting deep C-states. The amdgpu driver hogging the CPU in interrupt context likely increases the probability of hitting the race condition. == Kdump files == /var/crash/202607101059/ — Crash #1 (srso_safe_ret) /var/crash/202607120124/ — Crash #2 (kick_ilb) Both contain full vmcore dumps and dmesg extracts. 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/controlC1: gdm-greeter 2490 F.... wireplumber /dev/snd/controlC0: gdm-greeter 2490 F.... wireplumber /dev/snd/seq: gdm-greeter 2474 F.... pipewire CasperMD5CheckResult: unknown Date: Sun Jul 12 12:34:59 2026 InstallationDate: Installed on 2026-05-26 (47 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp2s0Link: Not connected. MachineType: AZW SER ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=3cc618bf-7287-4c56-86b6-9ddbfe59a14a ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.14_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.14_P3C6M43_B_Link:bd03/24/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4:pfaSER: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160457 Title: Kernel panic in srso_safe_ret / kick_ilb during sched_tick on AMD Ryzen 7 4800U (Zen2) Status in linux package in Ubuntu: New Bug description: DESCRIPTION: == Summary == Repeated kernel panics on AMD Ryzen 7 4800U (Renoir/Zen2) triggered by the SRSO (Speculative Return Stack Overflow) mitigation interacting with the scheduler tick path. The system crashes every 1-11 days with no user-space trigger. Crashes occur in both linux-image-7.0.0-22-generic and linux-image-7.0.0-27-generic. Workaround: processor.max_cstate=1 (preventing deep C-states avoids the crash path). == Hardware == - System: AZW (Beelink) SER Mini PC - CPU: AMD Ryzen 7 4800U with Radeon Graphics (Zen2 / Renoir) - Microcode: 0x0860010d (updated from 0x08600106 at boot) - GPU: AMD Renoir [Radeon Vega Series] (integrated, amdgpu driver) - RAM: 16GB DDR4 - BIOS: SER_V1.14_P3C6M43_B_Link (03/24/2022) — latest available for this model - NVMe storage == Software == - Ubuntu 26.04 LTS (fresh install on 2026-05-26) - Kernel: 7.0.0-22-generic and 7.0.0-27-generic (both affected) - amd64-microcode: 3.20251202.1ubuntu2 - linux-firmware: 20260319.git217ca6e4.1ubuntu - Boot params: quiet splash crashkernel=... - Active mitigation: srso_return_thunk (confirmed via dmesg) - NOPTI active == Crash #1 — 2026-07-10 (kernel 7.0.0-27) == Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 0 Comm: swapper/0 RIP: 0010:srso_safe_ret+0x0/0x20 Call Trace: <IRQ> sched_tick+0x48/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x9a/0xd0 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1b/0x20 RIP: 0010:cpuidle_enter_state+0xca/0x700 cpuidle_enter+0x30/0x50 cpuidle_idle_call+0x16b/0x1f0 do_idle+0x94/0xf0 </TASK> == Crash #2 — 2026-07-12 (kernel 7.0.0-27) == BUG: unable to handle page fault for address: ffffffff99053b04 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD bc447067 P4D bc447067 PUD bc448063 PMD 0 Oops: Oops: 0002 [#1] SMP NOPTI CPU: 0 UID: 1000 PID: 2680076 Comm: curl RIP: 0010:kick_ilb+0x6e/0x180 Call Trace: <TASK> kick_ilb+0x52/0x180 nohz_balancer_kick+0x92/0x2d0 sched_balance_trigger+0x4c/0x90 sched_tick+0xf9/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x44/0xd0 asm_sysvec_apic_timer_interrupt+0x1b/0x20 </TASK> == Additional context == - amdgpu driver logs "dm_irq_work_func [amdgpu] hogged CPU for >13333us" 35+ times per boot, suggesting IRQ pressure on the scheduler tick path. - Both crashes occur on CPU 0 during timer interrupt → sched_tick. - Crash #1 is an invalid opcode in the SRSO safe_ret thunk itself. - Crash #2 is a page fault in kick_ilb writing to an unmapped kernel address (PMD 0), suggesting corrupted per-cpu data or text patching issue in the SRSO path. - The system was stable for 14 days once (when amdgpu initialized without errors). - Full kdump vmcores are available in /var/crash/ for all crashes. == Crash frequency == 6+ crashes since 2026-05-29, intervals ranging from 1.5 to 11 days. No specific user-space trigger identified — crashes happen during idle or light workloads (cron jobs, curl). == Workaround == Adding processor.max_cstate=1 to kernel boot parameters prevents the CPU from entering deep C-states where the crash occurs. This confirms the interaction between cpuidle exit path, SRSO return thunks, and sched_tick. == Possible root cause == The SRSO mitigation (srso_return_thunk / srso_safe_ret) appears to have a bug in the text patching or in the interaction with the scheduler's nohz/idle balancer on AMD Zen2 processors when exiting deep C-states. The amdgpu driver hogging the CPU in interrupt context likely increases the probability of hitting the race condition. == Kdump files == /var/crash/202607101059/ — Crash #1 (srso_safe_ret) /var/crash/202607120124/ — Crash #2 (kick_ilb) Both contain full vmcore dumps and dmesg extracts. 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/controlC1: gdm-greeter 2490 F.... wireplumber /dev/snd/controlC0: gdm-greeter 2490 F.... wireplumber /dev/snd/seq: gdm-greeter 2474 F.... pipewire CasperMD5CheckResult: unknown Date: Sun Jul 12 12:34:59 2026 InstallationDate: Installed on 2026-05-26 (47 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp2s0Link: Not connected. MachineType: AZW SER ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=3cc618bf-7287-4c56-86b6-9ddbfe59a14a ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.14_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.14_P3C6M43_B_Link:bd03/24/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4:pfaSER: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160457/+subscriptions
[Bug 2160453] [NEW] i915: DPLL/PHY hang on Meteor Lake (Dell Pro Max 16 Plus) with TB5 dock after suspend/resume - flip_done timeout, system freeze
Public bug reported: ## Summary Dell Pro Max 16 Plus laptop running Ubuntu 26.04 with Intel Meteor Lake iGPU (`i915`) and NVIDIA RTX PRO 5000 (hybrid graphics) repeatedly freezes with black screen(s). The system remains running (compute continues, fans spin) but the desktop becomes completely unresponsive. Recovery requires dock power-cycle, suspend/resume, SSH reboot, or hard reset. The kernel logs show repeated `i915` display driver failures in the DPLL/PHY/pipe A path, especially during suspend/resume and display power-state transitions. A Dell Thunderbolt 5 dock with a 5120x2160 external monitor exacerbates the issue. Kernel parameter `i915.enable_psr=0` was applied but did not resolve suspend/resume failures. --- ## Hardware | Component | Details | |---|---| | Laptop | Dell Pro Max 16 Plus MB16250/0K8XPY | | BIOS | 2.6.1 (03/16/2026) | | CPU/GPU (integrated) | Intel Meteor Lake, PCI `8086:7d67`, driver `i915` | | GPU (discrete) | NVIDIA RTX PRO 5000 Blackwell, driver `nvidia 595.71.05` | | RAM | 128 GB | | Internal display | eDP-1 (built-in OLED panel) | | External monitor | Dell U4025QW 40" ultrawide, 5120x2160 | | Dock | Dell Thunderbolt 5 Dock (SD25TB5 / K2 DOCK) | | Dock link | TB5, 120 Gb/s, left-side Thunderbolt port | | Monitor connection | DisplayPort (dock DP port; previously USB-C, same bug) | --- ## Software | Component | Version | |---|---| | OS | Ubuntu 26.04 LTS (resolute) | | Kernel | 7.0.0-27-generic (#27-Ubuntu SMP PREEMPT_DYNAMIC) | | Mesa | 26.0.3-1ubuntu1 | | libdrm | 2.4.131-1 | | linux-firmware-intel-graphics | 20260319.git217ca6e4-0ubuntu2.1 | | Desktop | GNOME Shell 50.1, Wayland | | Kernel cmdline | `i915.enable_psr=0` (PSR disabled, bug persists) | --- ## Symptoms 1. One or both screens go black 2. Keyboard/mouse input stops responding 3. System is NOT fully dead — background processes (e.g. vLLM compute) may continue 4. No clean shutdown — logs stop abruptly until hard reset or recovery action 5. Disconnecting monitor/dock during freeze does not help (compositor blocked in kernel ioctl) 6. Toggling dock power off/on DOES recover the display link --- ## Triggers (confirmed across multiple incidents) | Trigger | Confirmed | |---|---| | Suspend / resume (lid close, idle suspend) | Yes — most reliable trigger | | Overnight idle (display power management) | Yes | | Stopping GPU workload (vLLM exit) | Yes — likely GPU power-state change | | External monitor via dock at 5120x2160 | Contributes — DP link retraining failures | | Monitor hotplug / dock reconnect | Yes | --- ## Kernel error signature (repeated in every incident) ``` i915 0000:00:02.0: [drm] *ERROR* flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] commit wait timed out i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns i915 0000:00:02.0: [drm] *ERROR* PHY A failed to change powerdown state i915 0000:00:02.0: [drm] Port A PLL not unlocked i915 0000:00:02.0: [drm] port_clock mismatch: expected 540000, found 61440 i915 0000:00:02.0: [drm] pixel_rate mismatch: expected 317250, found 36096 ``` During suspend/resume, errors occur in: - `intel_display_driver_resume` → `i915_drm_resume` - `intel_dp_retrain_link` → `intel_encoder_link_check_work_fn` Also seen: ``` pcieport 0000:00:01.0: PCIe Bus Error: ACSViol (Thunderbolt controller) NVRM: RmHandleDNotifierEvent: Failed to handle ACPI D-Notifier event, status=0x11 ``` No `NMI watchdog`, `soft lockup`, or `hung_task` messages — kernel appears alive, display commit path is deadlocked. --- ## Incident timeline ### Incident 1 — 2026-07-10 ~20:23 - Hard reset required - Last log: `flip_done timed out` at 20:23:43 - Reboot at 20:26:48 ### Incident 2 — 2026-07-11 ~10:14 - Overnight computation, spontaneous freeze (no user interaction) - Both screens black, unresponsive - Hard reset, reboot at 10:31:55 ### Incident 3 — 2026-07-11 ~17:51 - After login, exiting vLLM - Recovered via dock power-cycle (no hard reset) ### Incident 4 — 2026-07-12 ~10:44 - Suspend/resume (lid close) - Same i915 errors during `i915_drm_resume` - Recovered without hard reset (~1 minute) --- ## What was tried | Mitigation | Result | |---|---| | `i915.enable_psr=0` kernel parameter | Active in cmdline; bug persists on suspend/resume | | Monitor USB-C → DisplayPort on dock | Display path changed (DP-7 → DP-10); suspend/resume still fails | | Dock on TB5 port (left side, 120 Gb/s) | Correct port confirmed; bug persists | | Dock power-cycle | Recovers display (workaround, not fix) | --- ## Display topology ``` Laptop (Intel i915, card1) ├── eDP-1: internal panel (always connected) └── DP-10: external Dell U4025QW via TB5 dock DisplayPort NVIDIA (card2): all outputs disconnected (compute only, vLLM) ``` External display is driven by **Intel i915**, not NVIDIA, even with vLLM using the discrete GPU. --- ## Steps to reproduce 1. Dell Pro Max 16 Plus with BIOS 2.6.1 2. Connect Dell TB5 dock to left-side Thunderbolt 5 port 3. Connect Dell U4025QW (or similar 5K display) via DisplayPort on dock 4. Boot Ubuntu 26.04 with kernel 7.0.0-27-generic 5. Use dual-monitor setup (internal + external) 6. Suspend the system (close lid or `systemctl suspend`) 7. Resume **Expected:** Normal desktop **Actual:** Black screen(s), input frozen; kernel logs show i915 DPLL/flip_done errors Alternative trigger: leave system idle overnight with external monitor connected. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "logs" https://bugs.launchpad.net/bugs/2160453/+attachment/5981380/+files/dell.zip -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160453 Title: i915: DPLL/PHY hang on Meteor Lake (Dell Pro Max 16 Plus) with TB5 dock after suspend/resume - flip_done timeout, system freeze Status in linux package in Ubuntu: New Bug description: ## Summary Dell Pro Max 16 Plus laptop running Ubuntu 26.04 with Intel Meteor Lake iGPU (`i915`) and NVIDIA RTX PRO 5000 (hybrid graphics) repeatedly freezes with black screen(s). The system remains running (compute continues, fans spin) but the desktop becomes completely unresponsive. Recovery requires dock power-cycle, suspend/resume, SSH reboot, or hard reset. The kernel logs show repeated `i915` display driver failures in the DPLL/PHY/pipe A path, especially during suspend/resume and display power-state transitions. A Dell Thunderbolt 5 dock with a 5120x2160 external monitor exacerbates the issue. Kernel parameter `i915.enable_psr=0` was applied but did not resolve suspend/resume failures. --- ## Hardware | Component | Details | |---|---| | Laptop | Dell Pro Max 16 Plus MB16250/0K8XPY | | BIOS | 2.6.1 (03/16/2026) | | CPU/GPU (integrated) | Intel Meteor Lake, PCI `8086:7d67`, driver `i915` | | GPU (discrete) | NVIDIA RTX PRO 5000 Blackwell, driver `nvidia 595.71.05` | | RAM | 128 GB | | Internal display | eDP-1 (built-in OLED panel) | | External monitor | Dell U4025QW 40" ultrawide, 5120x2160 | | Dock | Dell Thunderbolt 5 Dock (SD25TB5 / K2 DOCK) | | Dock link | TB5, 120 Gb/s, left-side Thunderbolt port | | Monitor connection | DisplayPort (dock DP port; previously USB-C, same bug) | --- ## Software | Component | Version | |---|---| | OS | Ubuntu 26.04 LTS (resolute) | | Kernel | 7.0.0-27-generic (#27-Ubuntu SMP PREEMPT_DYNAMIC) | | Mesa | 26.0.3-1ubuntu1 | | libdrm | 2.4.131-1 | | linux-firmware-intel-graphics | 20260319.git217ca6e4-0ubuntu2.1 | | Desktop | GNOME Shell 50.1, Wayland | | Kernel cmdline | `i915.enable_psr=0` (PSR disabled, bug persists) | --- ## Symptoms 1. One or both screens go black 2. Keyboard/mouse input stops responding 3. System is NOT fully dead — background processes (e.g. vLLM compute) may continue 4. No clean shutdown — logs stop abruptly until hard reset or recovery action 5. Disconnecting monitor/dock during freeze does not help (compositor blocked in kernel ioctl) 6. Toggling dock power off/on DOES recover the display link --- ## Triggers (confirmed across multiple incidents) | Trigger | Confirmed | |---|---| | Suspend / resume (lid close, idle suspend) | Yes — most reliable trigger | | Overnight idle (display power management) | Yes | | Stopping GPU workload (vLLM exit) | Yes — likely GPU power-state change | | External monitor via dock at 5120x2160 | Contributes — DP link retraining failures | | Monitor hotplug / dock reconnect | Yes | --- ## Kernel error signature (repeated in every incident) ``` i915 0000:00:02.0: [drm] *ERROR* flip_done timed out i915 0000:00:02.0: [drm] *ERROR* [CRTC:150:pipe A] commit wait timed out i915 0000:00:02.0: [drm] DPLL 0: pll hw state mismatch WARNING: drivers/gpu/drm/i915/display/intel_dpll_mgr.c:4945 at verify_single_dpll_state WARNING: drivers/gpu/drm/i915/display/intel_modeset_verify.c:225 at verify_crtc_state i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns i915 0000:00:02.0: [drm] *ERROR* PHY A failed to change powerdown state i915 0000:00:02.0: [drm] Port A PLL not unlocked i915 0000:00:02.0: [drm] port_clock mismatch: expected 540000, found 61440 i915 0000:00:02.0: [drm] pixel_rate mismatch: expected 317250, found 36096 ``` During suspend/resume, errors occur in: - `intel_display_driver_resume` → `i915_drm_resume` - `intel_dp_retrain_link` → `intel_encoder_link_check_work_fn` Also seen: ``` pcieport 0000:00:01.0: PCIe Bus Error: ACSViol (Thunderbolt controller) NVRM: RmHandleDNotifierEvent: Failed to handle ACPI D-Notifier event, status=0x11 ``` No `NMI watchdog`, `soft lockup`, or `hung_task` messages — kernel appears alive, display commit path is deadlocked. --- ## Incident timeline ### Incident 1 — 2026-07-10 ~20:23 - Hard reset required - Last log: `flip_done timed out` at 20:23:43 - Reboot at 20:26:48 ### Incident 2 — 2026-07-11 ~10:14 - Overnight computation, spontaneous freeze (no user interaction) - Both screens black, unresponsive - Hard reset, reboot at 10:31:55 ### Incident 3 — 2026-07-11 ~17:51 - After login, exiting vLLM - Recovered via dock power-cycle (no hard reset) ### Incident 4 — 2026-07-12 ~10:44 - Suspend/resume (lid close) - Same i915 errors during `i915_drm_resume` - Recovered without hard reset (~1 minute) --- ## What was tried | Mitigation | Result | |---|---| | `i915.enable_psr=0` kernel parameter | Active in cmdline; bug persists on suspend/resume | | Monitor USB-C → DisplayPort on dock | Display path changed (DP-7 → DP-10); suspend/resume still fails | | Dock on TB5 port (left side, 120 Gb/s) | Correct port confirmed; bug persists | | Dock power-cycle | Recovers display (workaround, not fix) | --- ## Display topology ``` Laptop (Intel i915, card1) ├── eDP-1: internal panel (always connected) └── DP-10: external Dell U4025QW via TB5 dock DisplayPort NVIDIA (card2): all outputs disconnected (compute only, vLLM) ``` External display is driven by **Intel i915**, not NVIDIA, even with vLLM using the discrete GPU. --- ## Steps to reproduce 1. Dell Pro Max 16 Plus with BIOS 2.6.1 2. Connect Dell TB5 dock to left-side Thunderbolt 5 port 3. Connect Dell U4025QW (or similar 5K display) via DisplayPort on dock 4. Boot Ubuntu 26.04 with kernel 7.0.0-27-generic 5. Use dual-monitor setup (internal + external) 6. Suspend the system (close lid or `systemctl suspend`) 7. Resume **Expected:** Normal desktop **Actual:** Black screen(s), input frozen; kernel logs show i915 DPLL/flip_done errors Alternative trigger: leave system idle overnight with external monitor connected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160453/+subscriptions
[Bug 2160452] [NEW] Touchpad broke after updating linux kernel to 7.0.0-27-generic
Public bug reported: Hi, After updating the linux kernel from 7.0.0-22-generic to 7.0.0-27-generic the touchpad completely stopped working. I tried restarting the drivers (i2c_hid_api driver), and rebooting my computer, without success. I booted back in ubuntu using the 7.0.0-22-generic kernel and it worked again. OS version: Ubuntu 26.04 LTS, firmware version E16V1IMS.112 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: heart 3714 F.... wireplumber /dev/snd/controlC1: heart 3714 F.... wireplumber /dev/snd/seq: heart 3698 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:40:46 2026 InstallationDate: Installed on 2026-05-05 (68 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. GS66 Stealth 10SF ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-kitty ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rootflags=subvol=@ quiet splash intel_iommu=on iommu=pt 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: 11/19/2020 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16V1IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-16V1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16V1IMS.112:bd11/19/2020:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnGS66Stealth10SF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16V1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16V1.1:pfaGS: dmi.product.family: GS dmi.product.name: GS66 Stealth 10SF dmi.product.sku: 16V1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160452 Title: Touchpad broke after updating linux kernel to 7.0.0-27-generic Status in linux package in Ubuntu: New Bug description: Hi, After updating the linux kernel from 7.0.0-22-generic to 7.0.0-27-generic the touchpad completely stopped working. I tried restarting the drivers (i2c_hid_api driver), and rebooting my computer, without success. I booted back in ubuntu using the 7.0.0-22-generic kernel and it worked again. OS version: Ubuntu 26.04 LTS, firmware version E16V1IMS.112 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: heart 3714 F.... wireplumber /dev/snd/controlC1: heart 3714 F.... wireplumber /dev/snd/seq: heart 3698 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:40:46 2026 InstallationDate: Installed on 2026-05-05 (68 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. GS66 Stealth 10SF ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-kitty ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rootflags=subvol=@ quiet splash intel_iommu=on iommu=pt 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: 11/19/2020 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16V1IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-16V1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16V1IMS.112:bd11/19/2020:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnGS66Stealth10SF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16V1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16V1.1:pfaGS: dmi.product.family: GS dmi.product.name: GS66 Stealth 10SF dmi.product.sku: 16V1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160452/+subscriptions
[Bug 2150776] Re: Ubuntu 26.04 GNOME Wayland: random short display/presentation freezes on AMD RX 7900 XT while apps continue running
Same symptom on different hardware — RX 9060 XT (RDNA4) Adding a data point from a different GPU generation, since this doesn't appear to be RX 7900 XT/RDNA3-specific. Hardware: AMD RX 9060 XT / Navi 44 (RDNA4), PCI ID [1002:7590] Kernel: 7.1.2-070102-generic (mainline build, #202606271039 SMP PREEMPT_DYNAMIC, Sat Jun 27 2026) Symptom: Identical "dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us N times" workqueue warnings, recurring across boots. Example from one boot (kernel monotonic timestamps, wall-clock range Jul 11 19:21:52 - Jul 12 00:37:29 — note the count climbs across the boot rather than resetting): [ 370.797119] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND [ 455.037142] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 5 times, consider switching to WQ_UNBOUND [ 4037.810198] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 7 times, consider switching to WQ_UNBOUND [ 5131.830194] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 11 times, consider switching to WQ_UNBOUND [19307.125552] workqueue: dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us 19 times, consider switching to WQ_UNBOUND Ruled out via systematic testing (12+ hours real usage under all three conditions simultaneously): 1. VRR/FreeSync — confirmed disabled at both the Xorg driver level (VariableRefresh: disabled) and the KWin compositor level (vrrPolicy: Never on both outputs). Warning still fired. 2. DPM/mclk power-state switching — GPU pinned to power_dpm_force_performance_level=high for the entire session (static top pstate, no automatic transitions). Warning still fired. 3. Refresh rate/modeset switching — both monitors static at 3440x1440@60Hz for the whole boot, no modeset or hotplug events in kernel or Xorg logs. Warning still fired. Since all three of the obvious triggers were independently ruled out, this points toward the underlying mechanism rather than any of the usual suspects (adaptive sync, power states, or display timing changes). Looked into the driver code and found dm_handle_vmin_vmax_update is a workqueue handler introduced specifically to offload dc_stream_adjust_vmin_vmax() off the interrupt handler so it can wait on dc_lock instead of racing it (see the amd-gfx patch thread on "fix dmub access race condition"): https://www.mail-archive.com/amd-gfx@lists.freedesktop.org/msg126413.html So the warning itself looks like the race-condition fix's own offload mechanism hitting contention, rather than being triggered by any user-facing setting. Happy to provide full journalctl -k output or test a debug kernel build if that'd help narrow it down further. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150776 Title: Ubuntu 26.04 GNOME Wayland: random short display/presentation freezes on AMD RX 7900 XT while apps continue running Status in linux package in Ubuntu: Confirmed Bug description: After installing Ubuntu 26.04 LTS, the display randomly freezes for a short time, usually a few hundred milliseconds to around one second. This is most visible in games and video playback, but it can also happen outside games (e.g. watching a video or just using Ubuntu). During the freeze, the application/game continues running. For example, in Counter-Strike 2 or Albion Online, if I am moving when the freeze happens, after the screen updates again my character is farther ahead. This suggests the system/game/input are still running, but the display/presentation stops updating temporarily. Audio usually continues normally. Very rarely, during longer freezes, audio repeats/stutters briefly. This did not happen on the same hardware with Ubuntu 24.04.4, Ubuntu 25.04, or Ubuntu 25.10. It started only on Ubuntu 26.04. Hardware: - CPU: AMD Ryzen 7 7700X - GPU: AMD Radeon RX 7900 XT / Navi 31 - Motherboard: ASRock B650M Pro RS WiFi - RAM: 32 GB - Monitors: 2x Dell S2721HS, 1920x1080, 60/74.97 Hz Software: - Ubuntu 26.04 LTS - GNOME Shell 50.1 - Wayland session - Mutter/libmutter 50.1 - Kernel 7.0.0-15-generic - Mesa 26.0.3 - RADV/radeonsi - Xwayland 24.1.10 What I tried: - Disabled VRR: no change - Tested 60 Hz and 74.97 Hz: no useful change - Disabled second monitor: no change - Disabled all GNOME Shell extensions: no change - Created a clean new user account and tested there: still freezes - Disabled Ryzen iGPU so only RX 7900 XT remained visible: still freezes - Updated motherboard BIOS from 1.30 to 4.20: no change - Tried amdgpu.dcdebugmask=0x12, 0x20012, 0x20052: no change - Tried runtime power_dpm_force_performance_level=high: no change - Tried MUTTER_DEBUG_FORCE_KMS_MODE=simple, MUTTER_DEBUG_KMS_THREAD_TYPE=user, MUTTER_DEBUG_DISABLE_HW_CURSORS=1: no change - Tried disabling unredirect/direct scanout through GNOME Looking Glass: no change - Kernel logs do not show amdgpu ring timeout or GPU reset during freezes - dmesg did show repeated AMD display-manager workqueue warnings: "dm_handle_vmin_vmax_update [amdgpu] hogged CPU for >10000us" Expected: The display should continue presenting frames smoothly. Actual: The visible display freezes briefly, then jumps forward, while the application continues running underneath. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: libmutter-18-0 50.1-0ubuntu2 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 21:47:54 2026 InstallationDate: Installed on 2026-04-29 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150776/+subscriptions
[Bug 2160443] Re: Graphics driver fails in kernel 6.8.0-134
Please give output of: sudo apt dist-upgrade ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160443 Title: Graphics driver fails in kernel 6.8.0-134 Status in linux package in Ubuntu: Incomplete Bug description: On a MacBook Air 2013 running linux mint 22.3 xfce, kernel 6.8.0-124 works perfectly with the intel graphics card (intel hd graphics 5000). However, in kernel 6.8.0-134 the screen is immediately black after booting and any editing of the bootloader eg with nomodeset or i915.modeset=1 does not work. Booting into GRUB and selecting 6.8.0-124 works and I've now held the boot into kernel 6.8.0-124. When booting into 6.8.0-124 in recovery mode and running dpkg the following errors were reported: linux-headers-6.8.0-134-generic linux-headers-generic linux-generic linux-image-6.8.0-134-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160443/+subscriptions
[Bug 2160443] [NEW] Graphics driver fails in kernel 6.8.0-134
You have been subscribed to a public bug: On a MacBook Air 2013 running linux mint 22.3 xfce, kernel 6.8.0-124 works perfectly with the intel graphics card (intel hd graphics 5000). However, in kernel 6.8.0-134 the screen is immediately black after booting and any editing of the bootloader eg with nomodeset or i915.modeset=1 does not work. Booting into GRUB and selecting 6.8.0-124 works and I've now held the boot into kernel 6.8.0-124. When booting into 6.8.0-124 in recovery mode and running dpkg the following errors were reported: linux-headers-6.8.0-134-generic linux-headers-generic linux-generic linux-image-6.8.0-134-generic ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- Graphics driver fails in kernel 6.8.0-134 https://bugs.launchpad.net/bugs/2160443 You received this bug notification because you are subscribed to linux in Ubuntu.