*** This bug is a duplicate of bug 2161182 *** https://bugs.launchpad.net/bugs/2161182 Since this bug was reported. BIOS on laptop was upgraded to 1.44. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161928 Title: Kernel regression: internal display becomes abnormally dim with 7.0.0-28 Status in linux package in Ubuntu: New Bug description: **Kernel regression: internal display becomes abnormally dim with 7.0.0-28** On my Dell Latitude 7390 running Ubuntu Cinnamon 26.04, the internal laptop display becomes abnormally dim when booted with Linux kernel 7.0.0-28-generic. The problem started immediately after upgrading from kernel 7.0.0-27 to 7.0.0-28. I tested both kernels on the same computer: * 7.0.0-28-generic: internal display is abnormally dim. * 7.0.0-27-generic: display brightness is normal. Booting 7.0.0-27 immediately restores normal display brightness. There is no external monitor connected. The problem affects only the built-in laptop display. This appears to be a kernel regression introduced in 7.0.0-28. Please investigate possible changes to the Intel i915 DRM/display/backlight subsystem. 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.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: user-meir 3893 F.... pipewire user-meir 3897 F.... wireplumber /dev/snd/pcmC0D0p: user-meir 3893 F...m pipewire /dev/snd/seq: user-meir 3893 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Jul 27 15:07:58 2026 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Latitude 7390 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=f1f51d68-fa8a-4c38-b218-a14509b07bc9 ro quiet splash SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 11/06/2024 dmi.bios.release: 1.41 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.41.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.41.0:bd11/06/2024:br1.41:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku081B:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161928/+subscriptions
воскресенье
[Bug 2162679] [NEW] amdgpu: NULL pointer dereference in dc_allow_idle_optimizations_internal via dm_ism_delayed_work_func (IPS race), plus separate unexplained silent full-system hangs on kernel 7.0.0-27/28
Public bug reported: Hardware: MSI Bravo 15 A4DDR, AMD Ryzen APU with hybrid graphics - iGPU: AMD Renoir (Radeon Vega, PCI 0000:08:00.0) - dGPU: AMD Navi 14 (Radeon RX 5500M, PCI 0000:03:00.0) Kernel: linux-image-generic-hwe-26.04, versions 7.0.0-27 and 7.0.0-28 (Xubuntu 26.04) Previously stable on kernel 6.12.86 with no issues. ISSUE 1 (confirmed, root-caused via kdump crash dump): NULL pointer dereference at dc_allow_idle_optimizations_internal+0x20/0x3c0 [amdgpu], address 00000000000000b4, triggered via workqueue call chain: dm_ism_delayed_work_func -> amdgpu_dm_ism_commit_event -> dm_ism_dispatch_power_state -> dm_ism_commit_idle_optimization_state -> dc_allow_idle_optimizations_internal This occurred during a PCI hot-remove test of the dGPU (echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove), where a background Idle Power State (IPS) management workqueue raced against device teardown. Full vmcore and dmesg captured via kdump-tools, available on request. Workaround: booting with amdgpu.dcdebugmask=0x800 (DC_DISABLE_IPS) has prevented recurrence of this specific crash signature for [X] days since applying. Note: amdgpu.dpm=0 was tried first as a broader workaround but caused a complete boot failure (system would not reach the login screen / display never initialized). ISSUE 2 (unresolved, separate failure mode): Independent of Issue 1, the system also experiences intermittent complete silent hangs requiring a hard power-off/reboot - no kernel panic, no oops, no journal entries logged near the freeze time, no watchdog trip, and kdump does NOT trigger (no crash dump produced). Journal logging simply stops abruptly with no preceding errors or warnings. Pattern observed across ~10 occurrences over several weeks: - Uptime before hang varies widely: as little as ~4 minutes after login, up to 10+ hours of uptime. - Frequently but not always correlates with Google Chrome being open/in use (both idle background tabs and active text/article browsing, not specifically video playback). - Occurs on both kernel 7.0.0-27 and 7.0.0-28. - Did not occur on kernel 6.12.86 prior to upgrade. - Ruled out: RAM fault (memtest86+, ~13 hours run, one full pass completed, 0 errors). Chrome hardware acceleration disabled did not prevent recurrence. amdgpu.dcdebugmask=0x800 (applied for Issue 1) has not prevented recurrence. Requesting guidance on further diagnostics to capture Issue 2, since standard kdump/journald logging does not capture any trace of this hang. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: bosha 5400 F.... wireplumber /dev/snd/controlC0: bosha 5400 F.... wireplumber /dev/snd/seq: bosha 5387 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Aug 2 13:51:58 2026 InstallationDate: Installed on 2026-04-24 (100 days ago) InstallationMedia: Xubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. Bravo 15 A4DDR ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=54f59859-2b42-4007-8746-3db7be7a25fb ro quiet splash crashkernel=384M-:128M amdgpu.dcdebugmask=0x800 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2026 dmi.bios.release: 1.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16WKAMS.116 dmi.board.asset.tag: Default string dmi.board.name: MS-16WK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16WKAMS.116:bd02/12/2026:br1.22:svnMicro-StarInternationalCo.,Ltd.:pnBravo15A4DDR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16WK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16WK.1:pfaBr: dmi.product.family: Br dmi.product.name: Bravo 15 A4DDR dmi.product.sku: 16WK.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/2162679 Title: amdgpu: NULL pointer dereference in dc_allow_idle_optimizations_internal via dm_ism_delayed_work_func (IPS race), plus separate unexplained silent full-system hangs on kernel 7.0.0-27/28 Status in linux package in Ubuntu: New Bug description: Hardware: MSI Bravo 15 A4DDR, AMD Ryzen APU with hybrid graphics - iGPU: AMD Renoir (Radeon Vega, PCI 0000:08:00.0) - dGPU: AMD Navi 14 (Radeon RX 5500M, PCI 0000:03:00.0) Kernel: linux-image-generic-hwe-26.04, versions 7.0.0-27 and 7.0.0-28 (Xubuntu 26.04) Previously stable on kernel 6.12.86 with no issues. ISSUE 1 (confirmed, root-caused via kdump crash dump): NULL pointer dereference at dc_allow_idle_optimizations_internal+0x20/0x3c0 [amdgpu], address 00000000000000b4, triggered via workqueue call chain: dm_ism_delayed_work_func -> amdgpu_dm_ism_commit_event -> dm_ism_dispatch_power_state -> dm_ism_commit_idle_optimization_state -> dc_allow_idle_optimizations_internal This occurred during a PCI hot-remove test of the dGPU (echo 1 > /sys/bus/pci/devices/0000:03:00.0/remove), where a background Idle Power State (IPS) management workqueue raced against device teardown. Full vmcore and dmesg captured via kdump-tools, available on request. Workaround: booting with amdgpu.dcdebugmask=0x800 (DC_DISABLE_IPS) has prevented recurrence of this specific crash signature for [X] days since applying. Note: amdgpu.dpm=0 was tried first as a broader workaround but caused a complete boot failure (system would not reach the login screen / display never initialized). ISSUE 2 (unresolved, separate failure mode): Independent of Issue 1, the system also experiences intermittent complete silent hangs requiring a hard power-off/reboot - no kernel panic, no oops, no journal entries logged near the freeze time, no watchdog trip, and kdump does NOT trigger (no crash dump produced). Journal logging simply stops abruptly with no preceding errors or warnings. Pattern observed across ~10 occurrences over several weeks: - Uptime before hang varies widely: as little as ~4 minutes after login, up to 10+ hours of uptime. - Frequently but not always correlates with Google Chrome being open/in use (both idle background tabs and active text/article browsing, not specifically video playback). - Occurs on both kernel 7.0.0-27 and 7.0.0-28. - Did not occur on kernel 6.12.86 prior to upgrade. - Ruled out: RAM fault (memtest86+, ~13 hours run, one full pass completed, 0 errors). Chrome hardware acceleration disabled did not prevent recurrence. amdgpu.dcdebugmask=0x800 (applied for Issue 1) has not prevented recurrence. Requesting guidance on further diagnostics to capture Issue 2, since standard kdump/journald logging does not capture any trace of this hang. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: bosha 5400 F.... wireplumber /dev/snd/controlC0: bosha 5400 F.... wireplumber /dev/snd/seq: bosha 5387 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Aug 2 13:51:58 2026 InstallationDate: Installed on 2026-04-24 (100 days ago) InstallationMedia: Xubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. Bravo 15 A4DDR ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=54f59859-2b42-4007-8746-3db7be7a25fb ro quiet splash crashkernel=384M-:128M amdgpu.dcdebugmask=0x800 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2026 dmi.bios.release: 1.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16WKAMS.116 dmi.board.asset.tag: Default string dmi.board.name: MS-16WK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16WKAMS.116:bd02/12/2026:br1.22:svnMicro-StarInternationalCo.,Ltd.:pnBravo15A4DDR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16WK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16WK.1:pfaBr: dmi.product.family: Br dmi.product.name: Bravo 15 A4DDR dmi.product.sku: 16WK.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/2162679/+subscriptions
[Bug 2162673] [NEW] System hang/reboot on kernel 7.0.0-28-generic with repeated amdgpu MODE1 resets (Ryzen 7 5700X + RX 7600)
Public bug reported: System hang/reboot on kernel 7.0.0-28-generic (AMD Ryzen 7 5700X, RX 7600). journalctl shows repeated amdgpu MODE1 reset events throughout the day (00:05, 06:47, 08:06) preceding a fatal crash at 15:46 that triggered kdump. Crash dump shows: WARNING: kernel/workqueue.c:2351 at __queue_work.part.0+0x190/0x390, CPU#2: swapper/2/0 with multiple CPUs dumping backtraces simultaneously. The crash coincided with a snap app (office365webdesktop) attempting GPU-accelerated Vulkan/DRI initialization. Kernel 7.0.0-22 has been stable as a workaround. dmesg attached: /var/crash/202608011547/dmesg.202608011547 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 14:58:17 2026 InstallationDate: Installed on 2026-04-23 (101 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp6s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. B550M AORUS ELITE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=67cd9e19-bcef-4463-95ea-5dbdd9b6019e ro quiet splash processor.max_cstate=1 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/14/2026 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FHb dmi.board.asset.tag: Default string dmi.board.name: B550M AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFHb:bd04/14/2026:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MAORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MAORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB550MB: dmi.product.family: B550 MB dmi.product.name: B550M AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology 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/2162673 Title: System hang/reboot on kernel 7.0.0-28-generic with repeated amdgpu MODE1 resets (Ryzen 7 5700X + RX 7600) Status in linux package in Ubuntu: New Bug description: System hang/reboot on kernel 7.0.0-28-generic (AMD Ryzen 7 5700X, RX 7600). journalctl shows repeated amdgpu MODE1 reset events throughout the day (00:05, 06:47, 08:06) preceding a fatal crash at 15:46 that triggered kdump. Crash dump shows: WARNING: kernel/workqueue.c:2351 at __queue_work.part.0+0x190/0x390, CPU#2: swapper/2/0 with multiple CPUs dumping backtraces simultaneously. The crash coincided with a snap app (office365webdesktop) attempting GPU-accelerated Vulkan/DRI initialization. Kernel 7.0.0-22 has been stable as a workaround. dmesg attached: /var/crash/202608011547/dmesg.202608011547 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 14:58:17 2026 InstallationDate: Installed on 2026-04-23 (101 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp6s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. B550M AORUS ELITE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=67cd9e19-bcef-4463-95ea-5dbdd9b6019e ro quiet splash processor.max_cstate=1 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/14/2026 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FHb dmi.board.asset.tag: Default string dmi.board.name: B550M AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFHb:bd04/14/2026:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MAORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MAORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB550MB: dmi.product.family: B550 MB dmi.product.name: B550M AORUS ELITE dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162673/+subscriptions
[Bug 2111521] Re: nvme no longer detected on boot after upgrade to 6.8.0-60
Adding a data point on non-NVMe hardware potentially affected by the same underlying mechanism (PCI Configuration Request Retry Status / RRS polling rework, d591f6804e7e). System: Gigabyte GA-EP31-DS3L (Intel P31/ICH7, 2008), Ubuntu 24.04.4 LTS Affected devices (SATA controllers, not NVMe): - ASMedia ASM1064 SATA controller [1b21:1064] on PCIe 03:00.0 - Marvell 88SE9215 SATA controller [1b4b:9215] on PCIe 04:00.0 Symptom: On kernel 6.8.0-136-generic, boot intermittently hangs for 10-25+ minutes with hung_task warnings on zpool/vdev_open/zio_wait (ZFS pool import stalling on real disk vdev open, not just PCIe link negotiation - I already ruled out the ASMedia empty-port staggered spin-up issue separately via ahci.mask_port_map + libahci.ignore_sss). Same hardware, same disks, cold boot: kernel 6.8.0-134-generic consistently boots in 2-4 minutes with no hangs at all. Also noticed my SSD system disk (SanDisk SDSSDA24, sdf) took over 3 minutes between "Attached SCSI disk" and mount on the slow 136 boot - an SSD delay of that magnitude on the same hardware/disk that mounts almost instantly on 134 suggests this isn't purely a spinning-disk spin-up issue, and points toward something at the PCI/enumeration layer rather than the storage device itself. Current workaround: pinned GRUB default + apt-mark hold to 6.8.0-134-generic. Happy to provide dmesg/lspci output from both kernels if useful. Attaching kernel logs from both the slow (6.8.0-136) and fast (6.8.0-134) boots on this hardware, plus lspci -vvv output for both affected SATA controllers. ** Attachment added: "lp2111521-logs-ep31ds3l.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111521/+attachment/5988695/+files/lp2111521-logs-ep31ds3l.zip -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2111521 Title: nvme no longer detected on boot after upgrade to 6.8.0-60 Status in linux package in Ubuntu: Fix Released Status in linux-hwe-6.11 package in Ubuntu: New Status in linux source package in Noble: Fix Released Status in linux-hwe-6.11 source package in Noble: New Status in linux source package in Plucky: Fix Released Status in linux-hwe-6.11 source package in Plucky: Won't Fix Status in linux source package in Questing: Fix Released Status in linux-hwe-6.11 source package in Questing: Won't Fix Status in linux package in Debian: Confirmed Bug description: [Impact] An Intel nvme stops working after upgrade to noble 6.8.0-60, that is because a upstream stable commit d591f6804e7e ("PCI: Wait for device readiness with Configuration RRS") introduced this regression, and other than noble, the ubuntu plucky, questing and mainline kernel are all impacted. So far a formal fix is not ready yet, PCI maintainer has been working on it for almost 1.5 month, the ubuntu users want the bug get fixed asap, otherwise their servers couldn't upgrade the ubuntu kernel. As a temporary fix, I wrote a SAUCE patch to apply a quirk to this Intel nvme device. After the mainline kernel has a formal fix, we could revert this SAUCE patch and introduce the formal one. Upstream mailing list discussion: https://lore.kernel.org/linux-pci/20250611101442.387378-1-hui.wang@canonical.com/T/ [Fix] apply a SAUCE patch, this will set a specific quirk to this Intel nvme device [Test] I patched noble and unstable kernels and built them, then shared the deb to bug reporters, they tested with the patched kernel, the nvme worked as before [Where problems could occur] This quirk is specific to the Intel nvme device 8086:0a54, so it is safe to other devices, if it has chance to introduce regression, it will make this Intel nvme device stop working if the nvme connects to a differnt VMD or pci root port, but this regression chance is very low since this quirk just disable the RRS polling, and let pci_dev_wait() work as before. Short version: booting 6.8.0-59-generic or any earlier version from the grub menu works; 6.8.0-60-generic dumps me at the initramfs prompt with no disks. We have some servers running Ubuntu 24.04.2 LTS. They have NVME solid-state disks which (in a working kernel) are detected as follows: [ 3.537968] nvme nvme0: pci function 10000:01:00.0 [ 3.539285] nvme 10000:01:00.0: PCI INT A: no GSI [ 5.897819] nvme nvme0: 32/0/0 default/read/poll queues [ 5.905451] nvme nvme0: Ignoring bogus Namespace Identifiers [ 5.909057] nvme0n1: p1 p2 p3 On the PCI bus they look like this: 10000:01:00.0 Non-Volatile memory controller [0108]: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] [8086:0a54] $ ls -l /sys/class/nvme/nvme0 lrwxrwxrwx 1 root root 0 May 22 16:56 /sys/class/nvme/nvme0 -> ../../devices/pci0000:d7/0000:d7:05.5/pci10000:00/10000:00:02.0/10000:01:00.0/nvme/nvme0 Four identical servers updated their kernel this morning to: ii linux-image-6.8.0-60-generic 6.8.0-60.63 amd64 Signed kernel image generic ...and rebooted. All four failed to come up and ended up at the (initramfs) prompt. Rebooting and selecting 6.8.0-59-generic from the grub menu allowed them to boot as normal. There is no sign that the initramfs generation went wrong (on all four servers) and the initramfs does contain all the same nvme modules for -60 that the one for -59 does. I am at a loss to explain this, and the initramfs environment is a bit limited for debugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111521/+subscriptions
[Bug 1117804] Re: ausearch doesn't show AppArmor denial messages
This bug was fixed in the package audit - 1:4.1.2-1ubuntu1 --------------- audit (1:4.1.2-1ubuntu1) stonking; urgency=medium * Fix AppArmor AVC events not appearing in `ausearch` (LP: #1117804) - d/p/lp1117804-audit-ausearch-do-not-require-tclass.patch -- Alex Ramírez <alex.ramirez@canonical.com> Tue, 14 Jul 2026 17:20:31 +0000 ** Changed in: audit (Ubuntu Stonking) Status: Fix Committed => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in audit source package in Jammy: In Progress Status in audit source package in Noble: In Progress Status in audit source package in Questing: Won't Fix Status in audit source package in Resolute: In Progress Status in audit source package in Stonking: Fix Released Bug description: [ Impact ] * The following command should display all AppArmor AVC events: `ausearch --message AVC`; however, it doesn't work: ``` yachie@virtual:/etc/apparmor.d$ ausearch --message AVC <no matches> ``` * Users currently must inspect `/var/log/audit.log` to find the missing AppArmor AVC events: ``` yachie@virtual:/etc/apparmor.d$ sudo cat /var/log/audit.log type=AVC msg=audit(1774470501.870:1117918): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/2009624/cmdline" pid=106062 comm="in:imuxsock" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 FSUID="root" OUID="root" type=AVC msg=audit(1774470501.927:1117919): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/2009636/cmdline" pid=106062 comm="in:imuxsock" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 FSUID="root" OUID="root" ``` * The root cause is that `ausearch` is checking for a `tclass` field in the AppArmor events, because AppArmor is using event id `1400` (assigned to SELinux) instead of `1500`. * AppArmor events don't have a `tclass` field, so `ausearch` treats every AppArmor event as 'malformed' and hides them. We can reveal the 'malformed' events with the `--debug` flag: ``` yachie@virtual:~$ ausearch --message AVC --debug ( ... a ton of unrelated events ... ) Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.176:616): apparmor="AUDIT" operation="change_onexec" class="file" info="change_profile unprivileged unconfined converted to stacking" profile="unconfined" name="lsb_release" pid=5443 comm="aa-exec" Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:617): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/nsswitch.conf" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:618): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/passwd" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:619): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/bash.bashrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:620): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bashrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:621): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bash_history" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:622): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bash_history" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:623): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/inputrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 <no matches> ``` * This bug makes `auditd` very difficult to use on Ubuntu: having the `auditd` package installed hides AVC events from the kernel log AND `ausearch` doesn't reveal them, making AppArmor events seemingly vanish unless you know where to look. [ Test plan ] # Install the relevant packages 1. sudo apt install apparmor auditd # Run the reproducer 2. aa-exec --profile=lsb_release bash # generates a ton of denials; see below: ``` root@jammy-vm:~# aa-exec --profile lsb_release bash bash: /etc/bash.bashrc: Permission denied bash: /root/.bashrc: Permission denied bash-5.1# exit ``` # Run `ausearch` and search for AVC events 3. ausearch --message AVC 3a. Unpatched package output (fail): ``` root@jammy-vm:~# ausearch --message AVC <no matches> ``` 3b. Patched package output (success): ``` root@jammy-vm:~# ausearch --message AVC ---- time->Tue Jul 14 21:03:18 2026 type=PROCTITLE msg=audit(1784062998.789:100): proctitle="bash" type=SYSCALL msg=audit(1784062998.789:100): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7f6a7274c150 a2=80000 a3=0 items=0 ppid=562 pid=3449 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=4294967295 comm="bash" exe="/usr/bin/bash" subj=lsb_release key=(null) type=AVC msg=audit(1784062998.789:100): apparmor="DENIED" operation="open" profile="lsb_release" name="/etc/nsswitch.conf" pid=3449 comm="bash" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ---- time->Tue Jul 14 21:03:18 2026 type=PROCTITLE msg=audit(1784062998.789:101): proctitle="bash" type=SYSCALL msg=audit(1784062998.789:101): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7f6a7274c2ac a2=80000 a3=0 items=0 ppid=562 pid=3449 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=4294967295 comm="bash" exe="/usr/bin/bash" subj=lsb_release key=(null) type=AVC msg=audit(1784062998.789:101): apparmor="DENIED" operation="open" profile="lsb_release" name="/etc/passwd" pid=3449 comm="bash" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ---- ( ...continues ) ``` [ Where problems could occur ] * Currently, all AppArmor events are treated as 'malformed' SELinux events when they are actually well-formed AppArmor events. * This patch modifies the filtration behavior of `ausearch` by making the `tclass` field optional, thus making AppArmor events be treated as well-formed SELinux events. * The regression risk with this patch is such that potentially well- formed events will be hidden by `ausearch` unintentionally, or truly malformed events will be allowed past the filter. * One major caveat is that regressions with respect to actual SELinux events are difficult to test on Ubuntu; some malformed SELinux events would potentially be allowed through the filter with this patch, or well-formed SELinux events hidden. This patch essentially trades correctness in the SELinux case for correctness in the AppArmor case. [ Other info ] * Debian likely doesn't want this patch, as Debian officially won't be making any changes until upstream does [3]. * Upstream AppArmor can't move their event id to the `1500` range any time soon. AppArmor was moved to the `1400` range to align with the Linux kernel LSM infrastructure [2]. * Upstream `auditd` (audit-userspace) doesn't have anything to fix because it's AppArmor that's sending the events down the wrong channel [6]. * This patch comes from SUSE; they've been carrying it for well over a decade [4], and they seem to still be carrying it even after switching to SELinux by default [5]. Targeted releases: All currently supported releases and all releases moving forward until AppArmor moves back to the `1500` event range or Ubuntu switches to SELinux by default. [1] Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726 [2] AA using 1400 reason: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726#39 [3] Debian `wontfix` closure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726#88 [4] SUSE KB: https://support.scc.suse.com/s/kb/audit-log-file-that-has-the-apparmor-AVC-entries-that-ausearch-can-t-read-1583239408721?language=en_US [5] SUSE Patch: https://build.opensuse.org/projects/security/packages/audit/files/audit-ausearch-do-not-require-tclass.patch [6] Upstream audit-userspace bug report: https://github.com/linux-audit/audit-userspace/issues/351 [ Original bug (for posterity after over a decade) ] The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat <no matches> ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+subscriptions
[Bug 2162663] [NEW] ntfs3: kernel BUG at fs/iomap/buffered-io.c:1061 in iomap_write_end on buffered writes — fixed upstream by 70d3855594cf, needs cherry-pick (7.0.y is EOL)
Public bug reported: [Impact] The in-kernel ntfs3 driver in the resolute kernel (7.0.0-28.28, and all 7.0 kernels) crashes with a kernel BUG on ordinary buffered writes to NTFS volumes: kernel BUG at fs/iomap/buffered-io.c:1061! Oops: invalid opcode: 0000 [#1] SMP NOPTI RIP: 0010:iomap_write_end+0x1e0/0x1f0 Call Trace: iomap_write_iter+0x171/0x340 iomap_file_buffered_write+0xa6/0x110 ntfs_file_write_iter+0x267/0x310 [ntfs3] vfs_write+0x25b/0x490 ksys_write+0x71/0xf0 __x64_sys_write+0x19/0x30 do_syscall_64+0x105/0x5a0 The writing task dies inside the write path while holding the folio lock and the inode i_rwsem, so it becomes an unkillable D-state task with SIGKILL pending forever; any process that later touches the same file/directory also hangs in D. The volume cannot be unmounted; only a reboot recovers, with attendant NTFS corruption risk on a filesystem frequently shared with a Windows dual-boot. Real-world triggers observed on this machine (multiple independent crashes across 2026-07-09 .. 2026-08-02): npm/node_modules installs, tar extraction, Steam game downloads, and Steam's fossilize shader-cache workers (comm fossilize_repla) — i.e. any many-small-file write workload. This makes an NTFS Steam library or dev tree on ntfs3 effectively unusable. Reports of the same signature exist from Arch/CachyOS users (e.g. https://github.com/CachyOS/linux-cachyos/issues/84). [Root cause / upstream status] Regression introduced by the ntfs3 iomap conversion in 7.0 (commit 099ef9ab9203 "fs/ntfs3: implement iomap-based file operations"): resident (small, MFT-inline) attributes are mapped as IOMAP_INLINE extents, but the inline buffer is allocated without page-alignment guarantees, so iomap_write_end()'s inline-data validity BUG_ON fires probabilistically on writes to small files. Upstream tracking: https://bugzilla.kernel.org/show_bug.cgi?id=221446 Upstream fix (mainline 7.2-rc1, via the ntfs3 for-7.2 pull): commit 70d3855594cf6e8791970714b65cac3202d6160e "ntfs3: Allocate iomap inline_data using alloc_page" (Fixes: 099ef9ab9203; Closes: bugzilla #221446; signed off by the ntfs3 maintainer) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70d3855594cf6e8791970714b65cac3202d6160e Crucially, this fix is NOT in any 7.0.y stable release — upstream 7.0.y ended at 7.0.14 without it (verified against the 7.0.1–7.0.14 changelogs), and it is also absent from 7.1.y through 7.1.5 (verified against ChangeLog-7.1.5). The regular stable-update SRU flow therefore can NEVER deliver this fix to the resolute kernel; it needs an explicit cherry-pick. [Fix] Please cherry-pick 70d3855594cf into the resolute linux package. It is a small, contained fs/ntfs3 change (allocation-alignment fix), carries Fixes:/Closes: tags, and applies to the 7.0 ntfs3 tree, which already contains the offending 099ef9ab9203. [Test Plan] On any NTFS volume mounted with the in-kernel ntfs3 driver, run a many-small-file write workload (e.g. `npm install` of a large dependency tree, or a Steam download/shader-cache build, or untar of a source tree). On affected kernels this reproduces the BUG within minutes to hours (probabilistic, alignment-dependent). With the fix applied the workload completes; no iomap_write_end BUG, no D-state leftovers. [Regression potential] Low: one-liner-scale allocation change confined to fs/ntfs3's inline-data path, authored and signed off by the subsystem maintainer, shipped in mainline since 7.2-rc1. [Workarounds until fixed] - Mount NTFS volumes with userspace ntfs-3g (FUSE) instead of ntfs3 (does not crash), or - Keep write-heavy workloads (node_modules, Steam libraries, shader caches) off ntfs3 volumes; do Steam downloads for shared libraries from the Windows side. ** 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/2162663 Title: ntfs3: kernel BUG at fs/iomap/buffered-io.c:1061 in iomap_write_end on buffered writes — fixed upstream by 70d3855594cf, needs cherry-pick (7.0.y is EOL) Status in linux package in Ubuntu: New Bug description: [Impact] The in-kernel ntfs3 driver in the resolute kernel (7.0.0-28.28, and all 7.0 kernels) crashes with a kernel BUG on ordinary buffered writes to NTFS volumes: kernel BUG at fs/iomap/buffered-io.c:1061! Oops: invalid opcode: 0000 [#1] SMP NOPTI RIP: 0010:iomap_write_end+0x1e0/0x1f0 Call Trace: iomap_write_iter+0x171/0x340 iomap_file_buffered_write+0xa6/0x110 ntfs_file_write_iter+0x267/0x310 [ntfs3] vfs_write+0x25b/0x490 ksys_write+0x71/0xf0 __x64_sys_write+0x19/0x30 do_syscall_64+0x105/0x5a0 The writing task dies inside the write path while holding the folio lock and the inode i_rwsem, so it becomes an unkillable D-state task with SIGKILL pending forever; any process that later touches the same file/directory also hangs in D. The volume cannot be unmounted; only a reboot recovers, with attendant NTFS corruption risk on a filesystem frequently shared with a Windows dual-boot. Real-world triggers observed on this machine (multiple independent crashes across 2026-07-09 .. 2026-08-02): npm/node_modules installs, tar extraction, Steam game downloads, and Steam's fossilize shader-cache workers (comm fossilize_repla) — i.e. any many-small-file write workload. This makes an NTFS Steam library or dev tree on ntfs3 effectively unusable. Reports of the same signature exist from Arch/CachyOS users (e.g. https://github.com/CachyOS/linux-cachyos/issues/84). [Root cause / upstream status] Regression introduced by the ntfs3 iomap conversion in 7.0 (commit 099ef9ab9203 "fs/ntfs3: implement iomap-based file operations"): resident (small, MFT-inline) attributes are mapped as IOMAP_INLINE extents, but the inline buffer is allocated without page-alignment guarantees, so iomap_write_end()'s inline-data validity BUG_ON fires probabilistically on writes to small files. Upstream tracking: https://bugzilla.kernel.org/show_bug.cgi?id=221446 Upstream fix (mainline 7.2-rc1, via the ntfs3 for-7.2 pull): commit 70d3855594cf6e8791970714b65cac3202d6160e "ntfs3: Allocate iomap inline_data using alloc_page" (Fixes: 099ef9ab9203; Closes: bugzilla #221446; signed off by the ntfs3 maintainer) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70d3855594cf6e8791970714b65cac3202d6160e Crucially, this fix is NOT in any 7.0.y stable release — upstream 7.0.y ended at 7.0.14 without it (verified against the 7.0.1–7.0.14 changelogs), and it is also absent from 7.1.y through 7.1.5 (verified against ChangeLog-7.1.5). The regular stable-update SRU flow therefore can NEVER deliver this fix to the resolute kernel; it needs an explicit cherry-pick. [Fix] Please cherry-pick 70d3855594cf into the resolute linux package. It is a small, contained fs/ntfs3 change (allocation-alignment fix), carries Fixes:/Closes: tags, and applies to the 7.0 ntfs3 tree, which already contains the offending 099ef9ab9203. [Test Plan] On any NTFS volume mounted with the in-kernel ntfs3 driver, run a many-small-file write workload (e.g. `npm install` of a large dependency tree, or a Steam download/shader-cache build, or untar of a source tree). On affected kernels this reproduces the BUG within minutes to hours (probabilistic, alignment-dependent). With the fix applied the workload completes; no iomap_write_end BUG, no D-state leftovers. [Regression potential] Low: one-liner-scale allocation change confined to fs/ntfs3's inline-data path, authored and signed off by the subsystem maintainer, shipped in mainline since 7.2-rc1. [Workarounds until fixed] - Mount NTFS volumes with userspace ntfs-3g (FUSE) instead of ntfs3 (does not crash), or - Keep write-heavy workloads (node_modules, Steam libraries, shader caches) off ntfs3 volumes; do Steam downloads for shared libraries from the Windows side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162663/+subscriptions
[Bug 2162661] [NEW] suspend/resume doesn't work on 7.0.0-28-generic
Public bug reported: Acer Aspire A715-79G, BIOS 1.07.01TACI. Suspend/resume works on Linux 7.0.0-14-generic but hangs on 7.0.0-28-generic. Reproduces with Intel graphics (prime-select intel), so not NVIDIA-specific. Screen remains black after resume and requires a hard power-off. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 17:16:00 2026 InstallationDate: Installed on 2026-08-01 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Acer Aspire A715-79G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=a3b2a569-4309-4959-90ac-b2a74820763b 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/30/2024 dmi.bios.release: 7.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01TACI dmi.board.name: Aspire A715-79G dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01TACI:bd03/30/2024:br7.1:efr7.3:svnAcer:pnAspireA715-79G:pvrNotApplicable:rvnAcer:rnAspireA715-79G:rvrNotApplicable:cvnAcer:ct10:cvrN/A:sku0000000000000000:pfaAspire: dmi.product.family: Aspire dmi.product.name: Aspire A715-79G dmi.product.sku: 0000000000000000 dmi.product.version: Not Applicable dmi.sys.vendor: Acer ** 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/2162661 Title: suspend/resume doesn't work on 7.0.0-28-generic Status in linux package in Ubuntu: New Bug description: Acer Aspire A715-79G, BIOS 1.07.01TACI. Suspend/resume works on Linux 7.0.0-14-generic but hangs on 7.0.0-28-generic. Reproduces with Intel graphics (prime-select intel), so not NVIDIA-specific. Screen remains black after resume and requires a hard power-off. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 17:16:00 2026 InstallationDate: Installed on 2026-08-01 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Acer Aspire A715-79G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=a3b2a569-4309-4959-90ac-b2a74820763b 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/30/2024 dmi.bios.release: 7.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01TACI dmi.board.name: Aspire A715-79G dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01TACI:bd03/30/2024:br7.1:efr7.3:svnAcer:pnAspireA715-79G:pvrNotApplicable:rvnAcer:rnAspireA715-79G:rvrNotApplicable:cvnAcer:ct10:cvrN/A:sku0000000000000000:pfaAspire: dmi.product.family: Aspire dmi.product.name: Aspire A715-79G dmi.product.sku: 0000000000000000 dmi.product.version: Not Applicable dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162661/+subscriptions
суббота
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
Fwiw, -28 has a known AMDGPU performance regression. The details are available at: https://discourse.ubuntu.com/t/amdgpu-performance-regression-in-kernel-7-0-0-28-28/85237 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Fix Released Status in linux source package in Resolute: Fix Released Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
[Bug 2162631] Re: Intel backlight regression on Lenovo ThinkPad T450s after upgrading from Linux 7.0.0-27 to 7.0.0-28
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162631 Title: Intel backlight regression on Lenovo ThinkPad T450s after upgrading from Linux 7.0.0-27 to 7.0.0-28 Status in linux package in Ubuntu: New Bug description: Brightness control works correctly with Linux kernel `7.0.0-27-generic` but stops working after booting into `7.0.0-28-generic`. The brightness slider and sysfs values change normally, but the physical display brightness does not change. This appears to be an Intel i915 graphics driver regression introduced in kernel `7.0.0-28`. ## Hardware Laptop: * Lenovo ThinkPad T450s Graphics: * Intel integrated graphics * Intel Broadwell/ULT GPU * PCI device ID: 1616 Display: * Internal eDP panel ## Operating System Ubuntu 26.04 LTS (Resolute) Desktop session: * GNOME * Wayland ## Affected kernels ### Working kernel ``` Linux 7.0.0-27-generic ``` Brightness works normally. Kernel command line: ``` BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=06789976-622b-4eb6-9e48-b0a08facff37 ro quiet splash i915.enable_psr=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ``` ### Broken kernel ``` Linux 7.0.0-28-generic ``` Brightness control does not affect the physical display. Kernel command line: ``` BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=06789976-622b-4eb6-9e48-b0a08facff37 ro quiet splash i915.enable_psr=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ``` ## Reproduction steps 1. Boot into kernel: ``` 7.0.0-28-generic ``` 2. Change brightness using GNOME brightness controls or: ``` brightnessctl set 50% ``` 3. The brightness value changes, but the display brightness remains unchanged. 4. Boot into: ``` 7.0.0-27-generic ``` 5. Repeat the same test. Result: * Brightness works correctly on 7.0.0-27. ## Backlight interface The system exposes: ``` /sys/class/backlight/intel_backlight ``` Output: ``` lrwxrwxrwx intel_backlight -> ../../devices/pci0000:00/0000:00:02.0/drm/card1/card1-eDP-1/intel_backlight ``` Maximum brightness: ``` 1023 ``` On kernel 7.0.0-28: ``` brightness: 627 actual_brightness: 627 ``` Changing values works: ``` echo 100 | sudo tee /sys/class/backlight/intel_backlight/brightness 100 echo 800 | sudo tee /sys/class/backlight/intel_backlight/brightness 800 ``` However, the physical screen brightness does not change. ## i915 driver information Working kernel: ``` modinfo i915 srcversion: 042D149A3C0CF120B518B19 vermagic: 7.0.0-27-generic SMP preempt mod_unload modversions ``` Broken kernel: ``` modinfo i915 srcversion: 7F187B928024528F00EC733 vermagic: 7.0.0-28-generic SMP preempt mod_unload modversions ``` ## i915 logs from broken kernel ``` i915 0000:00:02.0: [drm] Found broadwell/ult (device ID 1616) integrated display version 8.00 stepping N/A i915 0000:00:02.0: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1 i915drmfb (fb0) is primary device ``` No obvious i915 errors appear. ## Additional testing The following kernel parameter was already enabled: ``` i915.enable_psr=0 ``` The issue remains. The following was tested: ``` echo 100 | sudo tee /sys/class/backlight/intel_backlight/brightness echo 800 | sudo tee /sys/class/backlight/intel_backlight/brightness ``` The sysfs values change, but hardware brightness does not. ## Expected behavior Changing brightness should physically change the display brightness. ## Actual behavior Brightness values update in sysfs and GNOME UI, but the display brightness remains unchanged. ## Regression range Last working: ``` 7.0.0-27-generic ``` First broken: ``` 7.0.0-28-generic ``` ## Possible cause This looks like a regression in the Intel i915 backlight handling introduced between kernel versions 7.0.0-27 and 7.0.0-28. 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.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jotech 4200 F.... wireplumber /dev/snd/controlC0: jotech 4200 F.... wireplumber /dev/snd/seq: jotech 4191 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 15:46:19 2026 InstallationDate: Installed on 2026-05-12 (81 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20BWS4BP00 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=06789976-622b-4eb6-9e48-b0a08facff37 ro quiet splash i915.enable_psr=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS4BP00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:br1.37:efr1.4:svnLENOVO:pn20BWS4BP00:pvrThinkPadT450s:rvnLENOVO:rn20BWS4BP00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:pfaThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS4BP00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162631/+subscriptions
[Bug 2142389] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot
Hello, I believe that I am experiencing the same issue, or at least one that is very closely related. My specs: Motherboard: ASUS CROSSHAIR VI HERO Memory: 48.0 GiB DDR4 3200 MHz (2×16 GB + 2×8 GB) Processor: Ryzen 7 1700X Graphics: Sapphire Nitro Radeon R9 380 Dual-X OC 4G Firmware Version: 8601 OS Name: Ubuntu 26.04 LTS OS Type: 64-bit GNOME Version: 50 Windowing System: Wayland Kernel Version: Linux 7.0.0-28-generic Display: I have three displays connected: two Dell P2419H monitors (1920×1080 @ 60 Hz) connected via DisplayPort and VGA, and a TV connected via HDMI. My primary display is the monitor connected through DisplayPort. The issue: When I leave my PC unattended for some time, the displays turn off as expected. However, when I try to wake them up, they never come back on, regardless of what key I press. Looking through the `journalctl` logs, I can see that pressing the power button is still logged, so this does not appear to be a complete OS crash. After troubleshooting the issue with an AI agent (Codex), comparing my `journalctl` logs with this report and also with https://gitlab.freedesktop.org/drm/amd/-/work_items/5123, I believe that my issue is closely related, although not identical. The last log entries before I have to perform a hard reset are consistently: 2026-08-01T20:30:48+02:00 kernel: amdgpu 0000:0b:00.0: last message was failed ret is 0 2026-08-01T20:30:56+02:00 kernel: amdgpu 0000:0b:00.0: last message was failed ret is 0 2026-08-01T20:31:02+02:00 kernel: amdgpu 0000:0b:00.0: last message was failed ret is 0 2026-08-01T20:31:07+02:00 kernel: amdgpu 0000:0b:00.0: last message was failed ret is 0 2026-08-01T20:31:15+02:00 kernel: amdgpu 0000:0b:00.0: last message was failed ret is 0 2026-08-01T20:31:18+02:00 systemd-logind: Power key pressed short. I have not found any `No EDID read` messages in my retained logs. However, I do repeatedly see: amdgpu 0000:0b:00.0: [drm] Failed to setup vendor infoframe on connector HDMI-A-1: -22 I also found these earlier GPU reset logs: 2026-07-28T21:35:13+02:00 kernel: amdgpu 0000:0b:00.0: AMDGPU device coredump file has been created 2026-07-28T21:35:13+02:00 kernel: amdgpu 0000:0b:00.0: ring uvd timeout, signaled seq=2, emitted seq=2 2026-07-28T21:35:13+02:00 kernel: amdgpu 0000:0b:00.0: GPU reset begin!. Source: 1 2026-07-30T20:11:59+02:00 kernel: amdgpu 0000:0b:00.0: AMDGPU device coredump file has been created 2026-07-30T20:11:59+02:00 kernel: amdgpu 0000:0b:00.0: ring uvd timeout, signaled seq=1705, emitted seq=1705 2026-07-30T20:11:59+02:00 kernel: amdgpu 0000:0b:00.0: GPU reset begin!. Source: 1 I am not entirely sure that these earlier GPU resets are related to the same issue. I have also had a couple of freezes where the screens did not go dark. They simply froze and stayed that way until I forcefully restarted the machine. Initially, I suspected that my GPU might be failing. However, after reading these reports, I am starting to think that this could be a software issue instead. I just wanted to share this information in case it helps narrow down the problem. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2142389 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: Confirmed Bug description: AMDGPU suspend → display black / no video after resume on Radeon R9 380 (No EDID read) Summary: After system suspend from Zorin OS 18 (Ubuntu 24.10 base, kernel 6.17.0-14), the system sometimes resumes but the display remains black (no signal). System continues running (fans/LEDs active), but monitor shows no output. Only hard reboot restores video. Steps to reproduce: Boot Zorin OS 18 (Ubuntu 24.10 kernel 6.17). Suspend system (e.g., via GNOME “Suspend”). Wait short period. Attempt to resume (mouse/keyboard). System wakes but display either shows garbled video or no output. Observed behavior: System appears not crashed (fans/LEDs/keyboard continue). Screen stays black or displays remnants but no usable video. Sometimes resume works, sometimes fails. Relevant log excerpt: amdgpu 0000:01:00.0: [drm] *ERROR* No EDID read. Hardware: Motherboard: Gigabyte B450 AORUS PRO WIFI CPU: AMD Ryzen 5 5500 GPU: AMD Radeon R9 380 Series (Tonga, amdgpu driver) Software environment: Zorin OS 18 Core (Ubuntu 24.10 base) kernel: 6.17.0-14-generic X11 session Workaround currently applied: Suspend disabled. System remains stable without suspend. Note: Bug appears related to video resume rather than system freeze; display subsystem (EDID handshake) may fail after suspend. Additional info: Similar reports of amdgpu black screen / suspend issues exist (e.g., Launchpad #2141216) and community discussions on black screen resume after suspend for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142389/+subscriptions
[Bug 2156644] Re: GNOME Panel & Activities Overview workspace thumbnails flickering issue
---------------------------------------- Update (Aug 1st): After recent kernel and system updates the workaround in my last update quit being viable for me as the issue started returning after about 15 minutes. I read somewhere that changing from fixed to VRR on one or all of your displays might help, only one of my displays supports VRR so I tried that and noticed it immediately stopped the 3003/gbm error flood and flickering and lasted about 17 hours before recurring. When it did, I simply toggled it back off and got another 10 hours or so of error/flicker free uptime. So I then worked with ChatGPT and Google AI to create a script to automate the toggling of VRR for my one monitor that supports it. After several trials and failures I finally got a script that automates this for me and provides a workaround I don't have to manage, I simply let it run in a terminal and check the output to see how many times it has had to execute, I'm currently at 2 days of uptime and the script has executed 6 times sporadically, keeping the canvas stable and flicker free. To bypass modern GNOME 50 D-Bus sandbox restrictions and resolve the MetaDrmBufferGbm leak without dropping the desktop session, you can force a full hardware graphics pipeline modeset by simultaneously re- asserting your entire multi-monitor coordinate matrix.Below is an automated Bash script that monitors journalctl for the gbm_surface_lock_front_buffer failed flood strings. Once triggered, it uses gdctl to instantly toggle between an equivalent VRR and Fixed refresh rate canvas matrix layout. This forces a clean hardware flush and releases the stale color buffers seamlessly without any visual panel blinks or interface stutter. Adjust the gdctl screen strings to match your unique hardware topology. ---------------------------------------- ```bash #!/bin/bash START_TIME=$(date +"%b %d %H:%M:%S") echo "$START_TIME 🚀 Auto-Purge Service started. Monitoring for pesky Mutter 50 buffer floods..." TOGGLE_STATE=0 COUNT=0 THRESHOLD=3 # We stream live into a reading descriptor exec 3< <(journalctl -b -f -n 0 | grep --line-buffered "gbm_surface_lock_front_buffer failed") while read -r line <&3 do ((COUNT++)) if [ $COUNT -ge $THRESHOLD ]; then LOG_TIME=$(date +"%b %d %H:%M:%S") echo "$LOG_TIME 🚨 Buffer leak flood detected ($COUNT errors)! Curses!!! Triggering REAL hardware pipeline reset..." if [ $TOGGLE_STATE -eq 0 ]; then gdctl set --logical-monitor --monitor HDMI-2 --mode "1920x1080@60.000" --scale 1.0 --x 1920 --y 1080 --logical-monitor --monitor HDMI-1 --mode "3840x2160@60.000" --scale 2.0 --x 916 --y 0 --logical-monitor --monitor DP-1 --mode "3840x2160@59.997" --scale 2.0 --x 0 --y 1080 --primary > /dev/null 2>&1 TOGGLE_STATE=1 echo "$LOG_TIME 🔄 gdctl: Entire layout flipped to FIXED mode -> Buffers Purged!" else gdctl set --logical-monitor --monitor HDMI-2 --mode "1920x1080@60.000" --scale 1.0 --x 1920 --y 1080 --logical-monitor --monitor HDMI-1 --mode "3840x2160@60.000" --scale 2.0 --x 916 --y 0 --logical-monitor --monitor DP-1 --mode "3840x2160@59.997+vrr" --scale 2.0 --x 0 --y 1080 --primary > /dev/null 2>&1 TOGGLE_STATE=0 echo "$LOG_TIME 🔄 gdctl: Entire layout flipped to VRR mode -> Buffers Purged!" fi echo "$LOG_TIME ⏳ Entering a 30 second Cool Breeze Mode..." sleep 30 # GHOST PURGE: Read and immediately throw away any backlog lines left over from the flood while read -t 0.1 -r ghost_line <&3; do : # Doing nothing dumps the line directly into the trash bin done COUNT=0 RESUME_TIME=$(date +"%b %d %H:%M:%S") echo "$RESUME_TIME 🟢 Cool Breeze Mode finished. Resuming fresh active monitoring..." fi done ``` ---------------------------------------- Use code with caution. ---------------------------------------- If one of the displays does not support VRR the same result might be achieved by simply changing one display between 60.000 Hz and 59.940 Hz but I haven't tried that as the script above is working great for my situation. If this quits working for me after additional kernel/system updates or if this is no longer needed I will update this thread, but for now this works great for me. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156644 Title: GNOME Panel & Activities Overview workspace thumbnails flickering issue Status in linux package in Ubuntu: New Bug description: GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver). System: Ubuntu 26.04 (upgraded from 24.04) GNOME Shell 50.1 / Mutter 50.1 Wayland session (no Xorg session available) Intel Alder Lake-N UHD Graphics (i915 driver) Three displays (all 1920×1080 @ 60Hz) Symptoms: After several hours of uptime, GNOME Activities Overview becomes visually corrupted. Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner). The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected. Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in minutes, rebooting it returns after several hours. No GPU resets, hangs, or DRM errors appear in journalctl. I’ve tried: Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs. Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned. Adding i915.enable_psr=0 i915.enable_fbc=0 to GRUB also did not solve the issue. Tested different kernels (including older kernel) No change in long-term behavior. Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions). Observations: The issue does not affect application rendering or the desktop outside of Activities Overview. It appears only after extended uptime (hours), not immediately after login. The issue is reproducible across reboots and kernel versions. No relevant errors in journalctl related to i915, DRM, or GPU resets. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 19:46:59 2026 InstallationDate: Installed on 2023-10-25 (962 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: GMKtec NucBox G2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=4f8f8593-25f0-4c7b-8445-d8bc2891550a ro quiet splash i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (3 days ago) dmi.bios.date: 06/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.27 dmi.board.asset.tag: Default string dmi.board.name: GMKtec dmi.board.vendor: GMKtec dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 0 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.27:bd06/08/2023:br5.27:svnGMKtec:pnNucBoxG2:pvrDefaultstring:rvnGMKtec:rnGMKtec:rvrDefaultstring:cvnDefaultstring:ct0:cvrDefaultstring:skuG2:pfaMINI: dmi.product.family: MINI dmi.product.name: NucBox G2 dmi.product.sku: G2 dmi.product.version: Default string dmi.sys.vendor: GMKtec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2156644/+subscriptions
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
Apologies for the noise - it's not as simple as running on battery, it happens on power as well. However, I can un-stick the laptop by removing and replacing the power. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Fix Released Status in linux source package in Resolute: Fix Released Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
[Bug 2162631] Re: Intel backlight regression on Lenovo ThinkPad T450s after upgrading from Linux 7.0.0-27 to 7.0.0-28
i had to move back to 7.0.0-27 so i can use the pc well -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162631 Title: Intel backlight regression on Lenovo ThinkPad T450s after upgrading from Linux 7.0.0-27 to 7.0.0-28 Status in linux package in Ubuntu: New Bug description: Brightness control works correctly with Linux kernel `7.0.0-27-generic` but stops working after booting into `7.0.0-28-generic`. The brightness slider and sysfs values change normally, but the physical display brightness does not change. This appears to be an Intel i915 graphics driver regression introduced in kernel `7.0.0-28`. ## Hardware Laptop: * Lenovo ThinkPad T450s Graphics: * Intel integrated graphics * Intel Broadwell/ULT GPU * PCI device ID: 1616 Display: * Internal eDP panel ## Operating System Ubuntu 26.04 LTS (Resolute) Desktop session: * GNOME * Wayland ## Affected kernels ### Working kernel ``` Linux 7.0.0-27-generic ``` Brightness works normally. Kernel command line: ``` BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=06789976-622b-4eb6-9e48-b0a08facff37 ro quiet splash i915.enable_psr=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ``` ### Broken kernel ``` Linux 7.0.0-28-generic ``` Brightness control does not affect the physical display. Kernel command line: ``` BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=06789976-622b-4eb6-9e48-b0a08facff37 ro quiet splash i915.enable_psr=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ``` ## Reproduction steps 1. Boot into kernel: ``` 7.0.0-28-generic ``` 2. Change brightness using GNOME brightness controls or: ``` brightnessctl set 50% ``` 3. The brightness value changes, but the display brightness remains unchanged. 4. Boot into: ``` 7.0.0-27-generic ``` 5. Repeat the same test. Result: * Brightness works correctly on 7.0.0-27. ## Backlight interface The system exposes: ``` /sys/class/backlight/intel_backlight ``` Output: ``` lrwxrwxrwx intel_backlight -> ../../devices/pci0000:00/0000:00:02.0/drm/card1/card1-eDP-1/intel_backlight ``` Maximum brightness: ``` 1023 ``` On kernel 7.0.0-28: ``` brightness: 627 actual_brightness: 627 ``` Changing values works: ``` echo 100 | sudo tee /sys/class/backlight/intel_backlight/brightness 100 echo 800 | sudo tee /sys/class/backlight/intel_backlight/brightness 800 ``` However, the physical screen brightness does not change. ## i915 driver information Working kernel: ``` modinfo i915 srcversion: 042D149A3C0CF120B518B19 vermagic: 7.0.0-27-generic SMP preempt mod_unload modversions ``` Broken kernel: ``` modinfo i915 srcversion: 7F187B928024528F00EC733 vermagic: 7.0.0-28-generic SMP preempt mod_unload modversions ``` ## i915 logs from broken kernel ``` i915 0000:00:02.0: [drm] Found broadwell/ult (device ID 1616) integrated display version 8.00 stepping N/A i915 0000:00:02.0: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1 i915drmfb (fb0) is primary device ``` No obvious i915 errors appear. ## Additional testing The following kernel parameter was already enabled: ``` i915.enable_psr=0 ``` The issue remains. The following was tested: ``` echo 100 | sudo tee /sys/class/backlight/intel_backlight/brightness echo 800 | sudo tee /sys/class/backlight/intel_backlight/brightness ``` The sysfs values change, but hardware brightness does not. ## Expected behavior Changing brightness should physically change the display brightness. ## Actual behavior Brightness values update in sysfs and GNOME UI, but the display brightness remains unchanged. ## Regression range Last working: ``` 7.0.0-27-generic ``` First broken: ``` 7.0.0-28-generic ``` ## Possible cause This looks like a regression in the Intel i915 backlight handling introduced between kernel versions 7.0.0-27 and 7.0.0-28. 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.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jotech 4200 F.... wireplumber /dev/snd/controlC0: jotech 4200 F.... wireplumber /dev/snd/seq: jotech 4191 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 15:46:19 2026 InstallationDate: Installed on 2026-05-12 (81 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20BWS4BP00 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=06789976-622b-4eb6-9e48-b0a08facff37 ro quiet splash i915.enable_psr=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS4BP00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:br1.37:efr1.4:svnLENOVO:pn20BWS4BP00:pvrThinkPadT450s:rvnLENOVO:rn20BWS4BP00:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s:pfaThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS4BP00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162631/+subscriptions