[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system

I also confirm that 7.0.0-17 from proposed solves the random ~1 second freezes - mostly happening in games, but not exclusively - which started after the migration from 25.10 to 26.04 / 7.0.0.14. I have an AMD Ryzen 7 8700F and a RX 9060 XT. -- 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: Confirmed Status in linux source package in Resolute: Confirmed 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 2148630] Re: Brightness control does not work at all on ROG Zephyrus G14 GA403WP laptop

Thanks for confirming that brightness dimming works again on kernel 7.0.0-15-generic — that's great news. I'll go ahead and mark this bug as Fix Released. One quick note: you mentioned concern about Ubuntu potentially missing the pixel-shifting anti-burning feature that Asus provides on Windows. That's a separate (and valid) concern from the brightness-control fix we just confirmed. If you'd like, feel free to file a new bug specifically about OLED pixel shifting support — that would be best tracked as its own issue rather than folded into this resolved report. Thanks again for your help testing and closing this out. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** No longer affects: linux (Ubuntu Resolute) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148630 Title: Brightness control does not work at all on ROG Zephyrus G14 GA403WP laptop Status in linux package in Ubuntu: Fix Released Bug description: I am not sure if this is the right package to raise this bug on. The brightness control for the built in display on this laptop does not work at all, booted into the Resolute daily live distro. Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260415) Happy to pull logs once I can work out which package is actually responsible for display control. This is an OLED so it's pretty critical for dimming to work. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: gnome-control-center 1:50.0-0ubuntu4 ProcVersionSignature: Ubuntu 7.0.0-13.13-generic 7.0.0-rc7 Uname: Linux 7.0.0-13-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 26.04.2 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:20:53 2026 LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260415) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148630/+subscriptions

[Bug 2148630] Re: Brightness control does not work at all on ROG Zephyrus G14 GA403WP laptop

Thanks Roy. I don't use Ubuntu full time on this, I have the release version of 26.04 installed on an external drive for now. I think this can be closed, dimming works as of 7.0.0-15-generic. (although I would be concerned Ubuntu is missing the pixel-shifting anti-burning stuff that Asus apparently has on Windows) For others, I will add that there's now two backlight devices in /sys # ls /sys/class/backlight/ amdgpu_bl2 nvidia_0 Maybe I managed to grab a daily just before support was added? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148630 Title: Brightness control does not work at all on ROG Zephyrus G14 GA403WP laptop Status in linux package in Ubuntu: Incomplete Status in linux source package in Resolute: New Bug description: I am not sure if this is the right package to raise this bug on. The brightness control for the built in display on this laptop does not work at all, booted into the Resolute daily live distro. Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260415) Happy to pull logs once I can work out which package is actually responsible for display control. This is an OLED so it's pretty critical for dimming to work. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: gnome-control-center 1:50.0-0ubuntu4 ProcVersionSignature: Ubuntu 7.0.0-13.13-generic 7.0.0-rc7 Uname: Linux 7.0.0-13-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 26.04.2 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:20:53 2026 LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260415) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148630/+subscriptions

[Bug 2143301] Re: Enable new Intel WCL soundwire support

@anthonywong Just would like to check, is this SRU blocked on something else? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2143301 Title: Enable new Intel WCL soundwire support Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in firmware-sof source package in Noble: Fix Committed Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in firmware-sof source package in Questing: Fix Committed Status in linux source package in Questing: New Status in linux-oem-6.17 source package in Questing: Invalid Status in firmware-sof source package in Resolute: Fix Released Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] New Dell Slate-1-Piece and Congo platform powered by Intel WildcatLake will have no basic audio functions w/o new firmware-sof which has the new DSP firmware and TPLG files ================ kernel ============================== Realtek on WCL: (Congo WCL) https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/sound/soc/codecs/rt722-sdca.c?id=a27539810e1e61efcfdeb51777ed875dc61e9d49 [git.kernel.org] CirrusLogic on WCL: (Slate-1-Piece WCL) https://lore.kernel.org/linux-sound/aYMpbnzi%2FUTO5Fqs@opensource.cirrus.com/T/#t <=============== firmware-sof ======================== [Fix] c78aea2df366275fed6c7b090bae3575951de57f Add 2.14.1 signed firmware binaries for Intel MTL+ targets f3e02da867b54e6061190d7ff1549e4f00bba17c Add 2.14.1 firmware binaries for Intel MTL and newer targets cdd3c8f9dd879a51dc8ed3c9aa0b7b0a49c108d8 Add 2.14 tools and topology binaries for Intel MTL and newer targets 11fc822288122b83296e634e8508f483c289d565 v2.14.x: add topologies for v2.14.2 e65a0d4f3ffceaf8a01df7f519707ffaf69746ef v2.14.x: add topologies for v2.14.3 [Test Case] 1. Boot up the machine of new Dell Intel WCL Congo and Slate-1-Piece platform powered by Intel WCL 2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices 3. Click test icon for basic audio output functions 4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions. 5. Test on machines of Intel ARL/LNL/MTL/PTL platforms for possible regression [Where problems could occur] Per comment from Intel, the primary requirement is that the topology file (sof-ptl-foo.tplg) and DSP firmware (sof-ptl.ri) are a pair and need to be from the same major version. If we upgrade of FW for only a single generation (e.g. only for WCL) This will be problematic. The main problem is that you may have two platforms (let’s say PTL and ARL) using same topology files. If you update FW for only PTL, you should also update the topology files used by PTL (FW+tplg always a pair!), but then if one of the topology files is used by some ARL products you may have problems (-> scenario 2 problem on ARL then). So we need to upgrade the DSP FW and the TPLG both for all MTL+ platforms (include ARL/LNL/MTL/PTL/WCL) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2143301/+subscriptions

[Bug 2154075] Re: [REGRESSION] ASUS Zenbook S16 UM5606GA (Ryzen AI 9 HX470) graphical freeze before login with Ubuntu 26.04 kernel 7.0.x, fixed by kernel 6.17

** 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/2154075 Title: [REGRESSION] ASUS Zenbook S16 UM5606GA (Ryzen AI 9 HX470) graphical freeze before login with Ubuntu 26.04 kernel 7.0.x, fixed by kernel 6.17 Status in linux package in Ubuntu: New Bug description: System experiences a reproducible graphical freeze during boot on Ubuntu 26.04 when using Ubuntu kernel 7.0.x. Hardware: * ASUS Zenbook S16 UM5606GA * AMD Ryzen AI 9 HX470 * integrated AMD graphics * BIOS version: UM5606GA.305 * BIOS date: 2026-02-25 * Secure Boot enabled Affected kernels: * 7.0.0-15-generic (fails) Known-good kernels: * 6.17.0-29-generic (works correctly) The issue appears shortly before the graphical login prompt should appear. Symptoms: * display freezes before login screen * mouse cursor may briefly move after resume from suspend * GUI remains visually frozen * keyboard and GUI actions occasionally appear after subsequent wake events * SSH access continues to function normally * system does not panic or reboot This suggests the kernel remains operational while the graphics/display stack hangs. Environment: * Ubuntu 26.04 userspace * GNOME * both Wayland and Xorg tested * same Mesa userspace for both working and failing kernels Regression evidence: The following configuration changes were tested and reverted unless otherwise noted: 1. Booting Ubuntu 26.04 live environment using "Safe graphics" Result: * works correctly 2. Booting installed system with: nomodeset Result: * works correctly * accelerated graphics unavailable 3. GRUB: set gfxpayload=keep Result: * Ubuntu live environment boots correctly in safe graphics mode 4. Kernel parameter: amdgpu.dcdebugmask=0x12 Result: * no improvement 5. Kernel parameter: amdgpu.mes=0 Result: * no improvement 6. Kernel parameter: amdgpu.dc=0 Result: * system freezes earlier during splash screen * SSH remains operational 7. Kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Result: * no improvement 8. Kernel parameter: pcie_aspm=off Result: * no improvement 9. Forced Xorg instead of Wayland Result: * same behavior 10. Replaced /lib/firmware/amdgpu firmware files with Ubuntu 24.04 versions Result: * no improvement * reverted afterward 11. Ubuntu 24.04 live environment Result: * boots correctly without safe graphics 12. Installed Ubuntu kernel: 6.17.0-29-generic Packages installed: * linux-headers-6.17.0-29-generic * linux-image-6.17.0-29-generic * linux-modules-6.17.0-29-generic * linux-tools-6.17.0-29-generic Result: * fully stable system * accelerated graphics functional * graphical login works correctly * suspend/resume functional Current working kernel: Linux aeon 6.17.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Tue May 5 19:42:34 UTC 2026 x86_64 GNU/Linux Conclusion: This appears to be a regression introduced in Ubuntu kernel 7.0.x affecting AMDGPU graphics initialization or display handling on Ryzen AI 9 HX470 / Strix Point hardware. The issue does not appear specific to: * GNOME * Wayland * Xorg * userspace Mesa because the same userspace environment works correctly under kernel 6.17. Suspected subsystem: * amdgpu * DRM/DCN * DMUB/DMCUB * modesetting * display core * Ryzen AI / Strix Point graphics enablement Potential duplicates / related reports: 1. Bug #2148753 linux-firmware-amd-graphics graphical boot regression on Ryzen AI ASUS Zenbook systems https://bugs.launchpad.net/ubuntu/+source/linux-firmware-amd-graphics/+bug/2148753 Mirror: https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg6269039.html 2. Bug #2147541 Ryzen AI platform regression under Ubuntu 26.04 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147541 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sat May 23 17:32:03 2026 InstallationDate: Installed on 2026-05-15 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS Zenbook S16 UM5606GA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-15-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 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/25/2026 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM5606GA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM5606GA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5606GA.305:bd02/25/2026:br5.35:efr3.3:svnASUS:pnZenbookS16UM5606GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5606GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaZenbookS16: dmi.product.family: Zenbook S16 dmi.product.name: Zenbook S16 UM5606GA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154075/+subscriptions

[Bug 2154059] Re: Kernel 7.0.0-15 freezes during suspend entry; pm_test=freezer hangs and requires hard power-off

** 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/2154059 Title: Kernel 7.0.0-15 freezes during suspend entry; pm_test=freezer hangs and requires hard power-off Status in linux package in Ubuntu: New Bug description: I am reporting a suspend failure on Ubuntu with kernel 7.0.0-15-generic. The laptop freezes during suspend entry and requires a hard power-off using the power button. This appears to be a suspend-entry failure rather than a normal resume failure, because the system does not cleanly return and no normal suspend/resume completion is recorded. The suspend failure happens in all of these cases: - Suspend from the power menu - Suspend from terminal using systemctl suspend - Suspend by closing the laptop lid Kernel: Linux jamshaid-laptop 7.0.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 22 16:06:43 UTC 2026 x86_64 GNU/Linux Kernel command line includes: mem_sleep_default=s2idle Sleep mode: cat /sys/power/mem_sleep Output: [s2idle] deep I followed Ubuntu DebuggingKernelSuspend: https://wiki.ubuntu.com/DebuggingKernelSuspend I tested pm_test=freezer. Commands used: sudo sh -c 'echo freezer > /sys/power/pm_test' cat /sys/power/pm_test sudo systemctl suspend Result: The system froze during pm_test=freezer and did not return automatically. I had to hard power off using the power button. After reboot, I restored pm_test: sudo sh -c 'echo none > /sys/power/pm_test' cat /sys/power/pm_test Output: [none] core processors platform devices freezer I did not continue with devices/platform/processors/core because freezer is already the first failing pm_test stage. suspend_stats after reboot: success: 0 fail: 0 failed_freeze: 0 failed_prepare: 0 failed_suspend: 0 failed_suspend_late: 0 failed_suspend_noirq: 0 failed_resume_noirq: 0 failed_resume_early: 0 failed_resume: 0 failures: last_failed_dev: last_failed_errno: 0 last_failed_step: Important log lines around the freezer test: May 23 08:36:32 jamshaid-laptop sudo[9734]: jamshaid : TTY=/dev/pts/0 ; PWD=/home/jamshaid/suspend-debug ; USER=root ; COMMAND=/usr/bin/sh -c echo freezer > /sys/power/pm_test May 23 08:36:32 jamshaid-laptop sudo[9745]: jamshaid : TTY=/dev/pts/0 ; PWD=/home/jamshaid/suspend-debug ; USER=root ; COMMAND=/usr/bin/systemctl suspend May 23 08:36:32 jamshaid-laptop systemd-logind[2163]: The system will suspend now! May 23 08:36:32 jamshaid-laptop ModemManager[1992]: [sleep-monitor-systemd] system is about to suspend May 23 08:36:32 jamshaid-laptop NetworkManager[1919]: manager: sleep: sleep requested May 23 08:36:33 jamshaid-laptop kernel: r8169 0000:02:00.0 eno1: Link is Down May 23 08:36:33 jamshaid-laptop kernel: wlo1: deauthenticating from <AP> by local choice (Reason: 3=DEAUTH_LEAVING) There is no clean return/resume recorded. The system required hard power-off. Relevant hardware/drivers observed in logs: - HP laptop, ACPI DSDT model 88DD - AMD Renoir integrated GPU using amdgpu - NVIDIA proprietary driver 580.142 loaded - Realtek RTL8852AE Wi-Fi using rtw89_8852ae - Realtek Bluetooth firmware rtl8852au - r8169 Ethernet - s2idle is selected Other notable log messages: - ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT in \_SB.WMID.WQBZ / \_SB.WMID.WQBE - ACPI video duplicate device warning - NVIDIA proprietary module taints kernel - rtw89_8852ae firmware loads successfully before the test The bug was filed using: ubuntu-bug linux so apport system information should already be attached automatically. I am attaching the collected suspend-debug archive with: - previous boot full journal - previous boot kernel journal - grep of suspend/freezer/PM/systemd-suspend/logind/error lines - suspend_stats - mem_sleep - pm_test result Summary: - Suspend fails from power menu, terminal, and lid close. - Kernel: 7.0.0-15-generic - Sleep mode: [s2idle] deep - pm_test=freezer fails. - The laptop freezes and requires hard power-off. - The first failing pm_test stage is freezer, so I stopped there. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jamshaid 5291 F.... wireplumber /dev/snd/controlC0: jamshaid 5291 F.... wireplumber /dev/snd/seq: jamshaid 5268 F.... pipewire CRDA: global country PK: DFS-UNSET (2400 - 2500 @ 40), (N/A, 30), (N/A) (5725 - 5875 @ 80), (N/A, 30), (N/A) (5945 - 6425 @ 320), (N/A, 23), (N/A), NO-OUTDOOR CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 23 08:46:20 2026 InstallationDate: Installed on 2024-05-17 (735 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec2xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=bce83742-7090-4ac2-ab36-67b0bfb3a0e9 ro quiet splash mem_sleep_default=s2idle 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: Upgraded to resolute on 2026-05-16 (6 days ago) dmi.bios.date: 12/10/2025 dmi.bios.release: 15.31 dmi.bios.vendor: AMI dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 88DD dmi.board.vendor: HP dmi.board.version: 96.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 96.34 dmi.modalias: dmi:bvnAMI:bvrF.31:bd12/10/2025:br15.31:efr96.34:svnHP:pnHPPavilionGamingLaptop15-ec2xxx:pvr:rvnHP:rn88DD:rvr96.34:cvnHP:ct10:cvrChassisVersion:sku450D8PA#UUF:pfa103C_5335KVHPPavilion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec2xxx dmi.product.sku: 450D8PA#UUF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154059/+subscriptions

[Bug 2154079] Re: 0% battey after waking up from sleep with charger conected

** 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/2154079 Title: 0% battey after waking up from sleep with charger conected Status in linux package in Ubuntu: New Bug description: I have a Lenovo E495 CPU, Ryzen 3500U, and Vega 8 GPU. Bug: I plugged in the charger and clicked suspend. When I woke up my laptop, it had 0% battery. How did I fix it? In BIOS I disabled my battery and waited 2 minutes. The charger was disconnected when I disabled the battery. After that I turned on my laptop, and the battery % was 95%. Before I disabled the battery when I plugged in the charger the charging light was white, indicating that the battery is fully charged, but Linux said 0% battery. I have set up charging threshold: stop charging at 95% start at 85%. linux version ubuntu 26.04 LTS 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: merets 6220 F.... wireplumber /dev/snd/controlC0: merets 6220 F.... wireplumber /dev/snd/seq: merets 6209 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 23 19:41:05 2026 InstallationDate: Installed on 2026-01-26 (117 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: LENOVO 20NE000JMH ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=a6aee418-546d-496f-8a30-9557e398e9d2 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-26 (27 days ago) dmi.bios.date: 10/03/2024 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET51W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000JMH dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrR11ET51W(1.31):bd10/03/2024:br1.31:efr1.31:svnLENOVO:pn20NE000JMH:pvrThinkPadE495:rvnLENOVO:rn20NE000JMH:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:pfaThinkPadE495: dmi.product.family: ThinkPad E495 dmi.product.name: 20NE000JMH dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154079/+subscriptions

[Bug 2152546] Re: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot

*** This bug is a duplicate of bug 2142389 *** https://bugs.launchpad.net/bugs/2142389 Olá, Cesar! Tudo bem? Vi que o seu relatório de bug foi unificado aqui com o meu (o #2142389). Isso é excelente porque mostra aos desenvolvedores da Canonical que o comportamento na R9 380 não é um caso isolado e nos ajuda a concentrar as informações em um só lugar. Estamos organizando um tópico bem bacana e saudável lá no fórum Diolinux Plus para centralizar os testes de bancada, logs e soluções temporárias que a galera está encontrando para contornar essa falha de suspensão. Se quiser somar forças com a gente por lá e acompanhar o desenrolar dessa história de perto, o link do nosso espaço é este aqui: 👉 https://plus.diolinux.com.br/t/regressao-no-kernel-ameaca-gpus-amd-series-r5-r7-r9-e-rx-tongas-e-polaris/82166 Será muito bem-vindo para compartilhar suas percepções com o pessoal. Um abraço e vamos nos ajudando! 🐧🌿 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152546 Title: amdgpu (R9 380) fails to resume from suspend (deep sleep) – black screen, requires hard reboot Status in linux package in Ubuntu: Incomplete 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/2152546/+subscriptions

[Bug 2154053] Re: atlantic driver issue on kernel 7

** Summary changed: - atlatnic driver issue on kernel 7 + atlantic driver issue on kernel 7 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154053 Title: atlantic driver issue on kernel 7 Status in linux package in Ubuntu: New Bug description: I recently updated to Ubuntu 26.04 with a Kernel 7.0.0 I am having issue with the driver for my 10G card which worked fine on Ubuntu 25.10 with kernel 6.0.17. To confirm those error never occurred on Ubuntu 25.10, only since I updated to 26.04. NIC: AQC113 [1d6a:04c0] Behavior encountered: ❯ journalctl -k -b | grep -iE 'atlantic|link change|carrier|AER|PCIe Bus Error' May 21 18:50:54 motoko kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability] May 21 18:50:55 motoko kernel: pcieport 0000:00:01.1: AER: enabled with IRQ 27 May 21 18:50:55 motoko kernel: pcieport 0000:00:01.2: AER: enabled with IRQ 28 May 21 18:50:55 motoko kernel: pcieport 0000:00:03.1: AER: enabled with IRQ 29 May 21 18:50:55 motoko kernel: pcieport 0000:00:07.1: AER: enabled with IRQ 31 May 21 18:50:55 motoko kernel: pcieport 0000:00:08.1: AER: enabled with IRQ 32 May 21 18:50:55 motoko kernel: atlantic: Detect ATL2FW 105002a May 21 18:50:55 motoko kernel: atlantic 0000:06:00.0 enp6s0: renamed from eth1 May 21 18:50:55 motoko kernel: Modules linked in: nvidia(OE+) ee1004(+) snd_hda_core(+) snd_intel_dspcfg snd_intel_sdw_acpi snd_hwdep kvm snd_pcm irqbypass snd_seq_midi snd_seq_midi_event ghash_clmulni_intel aesni_intel snd_rawmidi rapl snd_seq mfd_aaeon eeepc_wmi(+) fjes(-) asus_wmi snd_seq_device sparse_keymap snd_timer input_leds(+) joydev(+) platform_profile wmi_bmof drm_ttm_helper snd ttm ccp i2c_piix4 video k10temp soundcore i2c_smbus mac_hid nfsd auth_rpcgss nfs_acl lockd grace sch_fq_codel sunrpc lp parport_pc ppdev parport msr efi_pstore nfnetlink dmi_sysfs autofs4 atlantic r8169 ahci macsec libahci realtek nvme nvme_core nvme_keyring nvme_auth hkdf wmi hid_generic usbhid uas hid usb_storage May 21 18:51:15 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 May 22 02:34:25 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 10000 new 0 May 22 02:34:41 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 May 22 02:34:49 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 10000 new 0 May 22 02:35:04 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 May 22 08:56:59 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 10000 new 0 May 22 08:57:09 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 Device: ethtool enp6s0 | grep -E 'Speed|Duplex|Link detected' ethtool -i enp6s0 | grep firmware netlink error: Operation not permitted Speed: 10000Mb/s Duplex: Full Link detected: yes firmware-version: 1.5.42 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gdm-greeter 3113 F.... wireplumber /dev/snd/controlC0: gdm-greeter 3113 F.... wireplumber /dev/snd/seq: gdm-greeter 3009 F.... pipewire CasperMD5CheckResult: pass Date: Fri May 22 18:19:59 2026 InstallationDate: Installed on 2024-05-26 (727 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: System manufacturer System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=f2b31c5a-0840-4e84-be10-e3a511e7c343 ro quiet splash pcie_aspm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-16 (6 days ago) dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154053/+subscriptions

[Bug 2153968] Re: After upgrading the kernel from 7.0.0-14 to 7.0.0-15 on a MacBook Pro 11,4 (Haswell, i915, Ubuntu 26.04), suspend on lid close stopped working.

Additional note: As a workaround, the system is currently running on kernel 7.0.0-14-generic. On this kernel, a separate backlight issue exists after resume — brightness is not restored to its previous level. This is fixed by adding acpi_backlight=native to GRUB_CMDLINE_LINUX_DEFAULT. This workaround was also tested on 7.0.0-15-generic, but did not resolve the backlight issue on that kernel. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153968 Title: After upgrading the kernel from 7.0.0-14 to 7.0.0-15 on a MacBook Pro 11,4 (Haswell, i915, Ubuntu 26.04), suspend on lid close stopped working. Status in linux package in Ubuntu: New Bug description: After upgrading the kernel from 7.0.0-14 to 7.0.0-15 on a MacBook Pro 11,4 (Haswell, i915, Ubuntu 26.04), suspend on lid close stopped working. The system goes to sleep but fails to resume — the screen remains black, keyboard and trackpad are unresponsive. The issue is absent on kernel 7.0.0-14. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-15-generic 7.0.0-15.15 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: elph 3715 F.... wireplumber /dev/snd/controlC0: elph 3715 F.... wireplumber /dev/snd/seq: elph 3699 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 22 10:39:47 2026 InstallationDate: Installed on 2026-04-26 (26 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 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader MachineType: Apple Inc. MacBookPro11,4 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=UUID=37a6c347-573a-443f-9173-51f2fc996c3c ro quiet splash acpi_osi=Darwin 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: 10/07/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 489.0.0.0.0 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvr489.0.0.0.0:bd10/07/2023:br0.1:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:sku:pfaMacBookPro: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153968/+subscriptions

[Bug 2154053] Re: atlatnic driver issue on kernel 7

Apparently this is not kernel related. I rebooted to 6.0.17 but I still see the issue ❯ journalctl -k -b | grep -iE 'atlantic|link change|carrier|AER|PCIe Bus Error' May 22 18:51:48 motoko kernel: atlantic: Detect ATL2FW 105002a May 22 18:51:48 motoko kernel: atlantic 0000:06:00.0 enp6s0: renamed from eth1 May 22 18:51:59 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 May 22 18:52:00 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 10000 new 0 May 22 18:52:08 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154053 Title: atlatnic driver issue on kernel 7 Status in linux package in Ubuntu: New Bug description: I recently updated to Ubuntu 26.04 with a Kernel 7.0.0 I am having issue with the driver for my 10G card which worked fine on Ubuntu 25.10 with kernel 6.0.17. To confirm those error never occurred on Ubuntu 25.10, only since I updated to 26.04. NIC: AQC113 [1d6a:04c0] Behavior encountered: ❯ journalctl -k -b | grep -iE 'atlantic|link change|carrier|AER|PCIe Bus Error' May 21 18:50:54 motoko kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability] May 21 18:50:55 motoko kernel: pcieport 0000:00:01.1: AER: enabled with IRQ 27 May 21 18:50:55 motoko kernel: pcieport 0000:00:01.2: AER: enabled with IRQ 28 May 21 18:50:55 motoko kernel: pcieport 0000:00:03.1: AER: enabled with IRQ 29 May 21 18:50:55 motoko kernel: pcieport 0000:00:07.1: AER: enabled with IRQ 31 May 21 18:50:55 motoko kernel: pcieport 0000:00:08.1: AER: enabled with IRQ 32 May 21 18:50:55 motoko kernel: atlantic: Detect ATL2FW 105002a May 21 18:50:55 motoko kernel: atlantic 0000:06:00.0 enp6s0: renamed from eth1 May 21 18:50:55 motoko kernel: Modules linked in: nvidia(OE+) ee1004(+) snd_hda_core(+) snd_intel_dspcfg snd_intel_sdw_acpi snd_hwdep kvm snd_pcm irqbypass snd_seq_midi snd_seq_midi_event ghash_clmulni_intel aesni_intel snd_rawmidi rapl snd_seq mfd_aaeon eeepc_wmi(+) fjes(-) asus_wmi snd_seq_device sparse_keymap snd_timer input_leds(+) joydev(+) platform_profile wmi_bmof drm_ttm_helper snd ttm ccp i2c_piix4 video k10temp soundcore i2c_smbus mac_hid nfsd auth_rpcgss nfs_acl lockd grace sch_fq_codel sunrpc lp parport_pc ppdev parport msr efi_pstore nfnetlink dmi_sysfs autofs4 atlantic r8169 ahci macsec libahci realtek nvme nvme_core nvme_keyring nvme_auth hkdf wmi hid_generic usbhid uas hid usb_storage May 21 18:51:15 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 May 22 02:34:25 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 10000 new 0 May 22 02:34:41 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 May 22 02:34:49 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 10000 new 0 May 22 02:35:04 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 May 22 08:56:59 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 10000 new 0 May 22 08:57:09 motoko kernel: atlantic 0000:06:00.0 enp6s0: atlantic: link change old 0 new 10000 Device: ethtool enp6s0 | grep -E 'Speed|Duplex|Link detected' ethtool -i enp6s0 | grep firmware netlink error: Operation not permitted Speed: 10000Mb/s Duplex: Full Link detected: yes firmware-version: 1.5.42 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gdm-greeter 3113 F.... wireplumber /dev/snd/controlC0: gdm-greeter 3113 F.... wireplumber /dev/snd/seq: gdm-greeter 3009 F.... pipewire CasperMD5CheckResult: pass Date: Fri May 22 18:19:59 2026 InstallationDate: Installed on 2024-05-26 (727 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: System manufacturer System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-15-generic root=UUID=f2b31c5a-0840-4e84-be10-e3a511e7c343 ro quiet splash pcie_aspm=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-16 (6 days ago) dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4021:bd08/09/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154053/+subscriptions

[Bug 2153962] Re: net/rds: reset op_nents when zerocopy page pin fails

** 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/2153962 Title: net/rds: reset op_nents when zerocopy page pin fails Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Questing: In Progress Status in linux source package in Resolute: In Progress Bug description: From https://lore.kernel.org/netdev/20260505234336.2132721-1-achender@kernel.org/ When iov_iter_get_pages2() fails in rds_message_zcopy_from_user(), the pinned pages are released with put_page(), and rm->data.op_mmp_znotifier is cleared. But we fail to properly clear rm->data.op_nents. Later when rds_message_purge() is called from rds_sendmsg() the cleanup loop iterates over the incorrectly non zero number of op_nents and frees them again. Fix this by properly resetting op_nents when it should be in rds_message_zcopy_from_user(). Fixes: 0cebaccef3ac ("rds: zerocopy Tx support.") Signed-off-by: Allison Henderson <achender@kernel.org> --- net/rds/message.c | 1 + 1 file changed, 1 insertion(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153962/+subscriptions

[Bug 2153976] Re: Fix graceful fault handling after FPU softirq changes causes hard freeze on EFI runtime calls

** 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/2153976 Title: Fix graceful fault handling after FPU softirq changes causes hard freeze on EFI runtime calls Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: New Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Running `sudo fwts uefirttime` on HP systems (CID: 202511-38089, 202511-38088, 02511-38091, 202511-38068, 202511-38069) with 6.17 causes a hardsystem freeze. The machine becomes unreachable by ping/SSH and requires a hardpower cycle. Root cause: commit d02198550423 ("x86/fpu: Improve crypto performance by making kernel-mode FPU reliably usable in softirqs") changed kernel_fpu_begin() to use local_bh_disable() instead of preempt_disable(). This sets SOFTIRQ_OFFSET in preempt_count during EFI runtime calls, making in_interrupt() return true in normal task context. The EFI graceful page fault handler efi_crash_gracefully_on_page_fault() uses in_interrupt() to bail out for faults in real interrupt context. With SOFTIRQ_OFFSET now set, the handler always bails out, leaving firmware page faults unhandled. This escalates to die() which also sees in_interrupt() as true and calls panic("Fatal exception in interrupt"), freezing the system. [Fix] Replace in_interrupt() with !in_task() in efi_crash_gracefully_on_page_fault(). This preserves the original intent of bailing for interrupts or NMI faults, while no longer falsely triggering from the FPU code path's local_bh_disable(). [Test Plan] 1. Boot affected HP machine with the patched 6.17-oem kernel. 2. Run:    $ sudo fwts uefirttime Without patch: system hard-freezes, requires power cycle. With patch: fwts completes (pass or fail), system remains responsive. [Where problems could occur] The change is in the EFI page fault handler (arch/x86/platform/efi/quirks.c). If !in_task() incorrectly identifies a real interrupt-context fault as task context, the handler would try to process it as an EFI firmware fault instead of letting the normal oops path handle it. This could mask real kernel bugs during interrupt-context EFI faults, though such faults are extremely rare. Also, a softirq taken between efi_rts_work.efi_rts_id assignment and the fpregs_lock() call could cause a page fault that gets misidentified. The use of !in_task() (which incorporates in_serving_softirq()) handles this window correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2153976/+subscriptions