[Bug 2150732] Re: Screen stays black after resuming from sleep

Workaround: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0 i915.enable_dpcd_backlight=0" -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150732 Title: Screen stays black after resuming from sleep Status in linux package in Ubuntu: Confirmed Status in linux-hwe-7.0 package in Ubuntu: Confirmed Bug description: After a "long" sleep (let's say more than 10 mins, but this is not clearly defined yet) when waking up, the screen stays black. I can confirm the system is responsive, the fingerprint sensor activates, it connects to the WiFi properly, it's really just the graphics part. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 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/controlC0: a.dubois 5856 F.... pipewire a.dubois 5867 F.... wireplumber /dev/snd/seq: a.dubois 5856 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 12:07:57 2026 InstallationDate: Installed on 2026-02-27 (62 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: LENOVO 21KWS15400 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-24 (6 days ago) dmi.bios.date: 03/02/2026 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: N48ET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KWS15400 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN48ET33W(1.20):bd03/02/2026:br1.20:efr1.15:svnLENOVO:pn21KWS15400:pvrThinkPadP1Gen7:rvnLENOVO:rn21KWS15400:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KW_BU_Think_FM_ThinkPadP1Gen7:pfaThinkPadP1Gen7: dmi.product.family: ThinkPad P1 Gen 7 dmi.product.name: 21KWS15400 dmi.product.sku: LENOVO_MT_21KW_BU_Think_FM_ThinkPad P1 Gen 7 dmi.product.version: ThinkPad P1 Gen 7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150732/+subscriptions

[Bug 2162928] [NEW] [amdgpu][Navi 44] Intermittent poweroff hang on 7.0.0-27/28/29; 7.0.0-22 and nomodeset shut down reliably

Public bug reported: Ubuntu release: Ubuntu 26.04 LTS (Kubuntu, resolute), amd64 Hardware: - GPU: PowerColor AMD Radeon RX 9060 XT / Navi 44 [1002:7590], subsystem [148c:2437] - Motherboard: Gigabyte B650 GAMING X AX V2 rev. 1.2 - BIOS: F41 dated 2026-05-21 - Secure Boot: enabled - All monitors are connected to the RX 9060 XT - The Ryzen integrated GPU has been disabled in BIOS for an additional isolation test Current relevant software: - Failing kernel: Ubuntu 7.0.0-29.29-generic (upstream base 7.0.12) - AMD graphics firmware: linux-firmware-amd-graphics 20260319.git217ca6e4-0ubuntu3.1 - Kernel driver: amdgpu Problem: Poweroff intermittently fails at the final stage. The displays and USB devices turn off, but the computer remains powered indefinitely: the case power light remains on and the fans appear to continue running. A hard reset/power-off is then required. The failure occurs both when shutting down from KDE and with: sudo systemctl poweroff It also occurred after shutting down from SDDM, so it is not dependent on a logged-in KDE session. Persistent journal logging reaches systemd- shutdown, filesystem synchronization, and process termination, then stops without recording the component that prevents final power removal. Expected result: The machine should completely power off within several seconds, as it does with kernel 7.0.0-22 and when amdgpu is bypassed with nomodeset. Reproduction: 1. Boot Ubuntu normally using kernel 7.0.0-29-generic with amdgpu loaded. 2. Run `sudo systemctl poweroff` or select Shut Down from KDE. 3. Repeat the boot/poweroff cycle because the failure is intermittent. 4. On a failed attempt, the displays and USB devices turn off but the power LED and fans remain on indefinitely. Isolation results: - Kernel 7.0.0-29 with normal amdgpu operation: intermittent poweroff hangs reproduced multiple times. - Kernel 7.0.0-27 with normal amdgpu operation: hung on the first shutdown test. - The problem was already observed with kernel 7.0.0-28 and remains present with 7.0.0-29. - Kernel 7.0.0-29 booted with `nomodeset`: 5 out of 5 shutdown tests completed cleanly and almost immediately. - Kernel 7.0.0-22 with normal amdgpu operation: 4 out of 4 shutdown tests completed cleanly and quickly. - Fedora Workstation 44 live USB with normal graphics: 3 out of 3 shutdown tests completed cleanly. - Disabling the unused Ryzen/Raphael integrated GPU in BIOS did not help; the first normal shutdown with only the RX 9060 XT present hung. - Updating the motherboard BIOS to F41 did not help. - `amdgpu.runpm=0` did not resolve the problem. - Stopping OneDrive before shutdown did not help. - The failure has occurred after KDE, SDDM, and direct systemctl poweroff tests, making a KDE session or ordinary userspace service unlikely to be necessary for the failure. This appears to be a regression in the Ubuntu kernel's amdgpu shutdown path between Ubuntu kernels 7.0.0-22 (upstream base 7.0.0) and 7.0.0-27 (upstream base 7.0.6). I can test additional proposed kernels if requested. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: chrism 2704 F.... wireplumber /dev/snd/controlC1: chrism 2704 F.... wireplumber /dev/snd/controlC0: chrism 2704 F.... wireplumber /dev/snd/seq: chrism 2699 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Aug 5 12:08:19 2026 InstallationDate: Installed on 2026-03-24 (135 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) IwDevWlp9s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. B650 GAMING X AX V2 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=618adf22-c64b-4c7d-8b93-6242ab08ed44 ro 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-18 (79 days ago) dmi.bios.date: 05/21/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B650 GAMING X AX V2 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.:bvrF41:bd05/21/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnB650GAMINGXAXV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB650GAMINGXAXV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB650MB: dmi.product.family: B650 MB dmi.product.name: B650 GAMING X AX V2 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 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/2162928 Title: [amdgpu][Navi 44] Intermittent poweroff hang on 7.0.0-27/28/29; 7.0.0-22 and nomodeset shut down reliably Status in linux package in Ubuntu: New Bug description: Ubuntu release: Ubuntu 26.04 LTS (Kubuntu, resolute), amd64 Hardware: - GPU: PowerColor AMD Radeon RX 9060 XT / Navi 44 [1002:7590], subsystem [148c:2437] - Motherboard: Gigabyte B650 GAMING X AX V2 rev. 1.2 - BIOS: F41 dated 2026-05-21 - Secure Boot: enabled - All monitors are connected to the RX 9060 XT - The Ryzen integrated GPU has been disabled in BIOS for an additional isolation test Current relevant software: - Failing kernel: Ubuntu 7.0.0-29.29-generic (upstream base 7.0.12) - AMD graphics firmware: linux-firmware-amd-graphics 20260319.git217ca6e4-0ubuntu3.1 - Kernel driver: amdgpu Problem: Poweroff intermittently fails at the final stage. The displays and USB devices turn off, but the computer remains powered indefinitely: the case power light remains on and the fans appear to continue running. A hard reset/power-off is then required. The failure occurs both when shutting down from KDE and with: sudo systemctl poweroff It also occurred after shutting down from SDDM, so it is not dependent on a logged-in KDE session. Persistent journal logging reaches systemd-shutdown, filesystem synchronization, and process termination, then stops without recording the component that prevents final power removal. Expected result: The machine should completely power off within several seconds, as it does with kernel 7.0.0-22 and when amdgpu is bypassed with nomodeset. Reproduction: 1. Boot Ubuntu normally using kernel 7.0.0-29-generic with amdgpu loaded. 2. Run `sudo systemctl poweroff` or select Shut Down from KDE. 3. Repeat the boot/poweroff cycle because the failure is intermittent. 4. On a failed attempt, the displays and USB devices turn off but the power LED and fans remain on indefinitely. Isolation results: - Kernel 7.0.0-29 with normal amdgpu operation: intermittent poweroff hangs reproduced multiple times. - Kernel 7.0.0-27 with normal amdgpu operation: hung on the first shutdown test. - The problem was already observed with kernel 7.0.0-28 and remains present with 7.0.0-29. - Kernel 7.0.0-29 booted with `nomodeset`: 5 out of 5 shutdown tests completed cleanly and almost immediately. - Kernel 7.0.0-22 with normal amdgpu operation: 4 out of 4 shutdown tests completed cleanly and quickly. - Fedora Workstation 44 live USB with normal graphics: 3 out of 3 shutdown tests completed cleanly. - Disabling the unused Ryzen/Raphael integrated GPU in BIOS did not help; the first normal shutdown with only the RX 9060 XT present hung. - Updating the motherboard BIOS to F41 did not help. - `amdgpu.runpm=0` did not resolve the problem. - Stopping OneDrive before shutdown did not help. - The failure has occurred after KDE, SDDM, and direct systemctl poweroff tests, making a KDE session or ordinary userspace service unlikely to be necessary for the failure. This appears to be a regression in the Ubuntu kernel's amdgpu shutdown path between Ubuntu kernels 7.0.0-22 (upstream base 7.0.0) and 7.0.0-27 (upstream base 7.0.6). I can test additional proposed kernels if requested. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: chrism 2704 F.... wireplumber /dev/snd/controlC1: chrism 2704 F.... wireplumber /dev/snd/controlC0: chrism 2704 F.... wireplumber /dev/snd/seq: chrism 2699 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Aug 5 12:08:19 2026 InstallationDate: Installed on 2026-03-24 (135 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) IwDevWlp9s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. B650 GAMING X AX V2 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=618adf22-c64b-4c7d-8b93-6242ab08ed44 ro 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-18 (79 days ago) dmi.bios.date: 05/21/2026 dmi.bios.release: 5.41 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F41 dmi.board.asset.tag: Default string dmi.board.name: B650 GAMING X AX V2 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.:bvrF41:bd05/21/2026:br5.41:svnGigabyteTechnologyCo.,Ltd.:pnB650GAMINGXAXV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB650GAMINGXAXV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB650MB: dmi.product.family: B650 MB dmi.product.name: B650 GAMING X AX V2 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/2162928/+subscriptions

[Bug 2072612]

Hello, I want to reopen this issue as in latest fedora workstation (with all stable updates, and latest kernel) this is issue re-appeared. I have a Lenovo IdeaPad Pro 16 with AMD 7840HS and Nvidia GTX 4050. The only workaround for the touchpad to work are these commands: sudo rmmod i2c_hid_acpi i2c_hid sudo modprobe i2c_hid_acpi -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2072612 Title: Lenovo touchpad intermittently stops working with i2c_designware errors Status in Linux: Invalid Status in linux package in Ubuntu: Opinion Bug description: Hi. When using my laptop, I frequently experience the touchpad suddenly cease working. Sometimes there's a few seconds' warning with reduced responsiveness, and sometimes it's completely sudden. I experienced this in Kubuntu 22.04, and I still experience it after upgrading to 24.04. Output from kern.log when it happens often looks like this: 2024-07-09T21:31:51.573862-04:00 machinename kernel: i2c_designware AMDI0010:00: controller timed out 2024-07-09T21:31:51.577113-04:00 machinename kernel: i2c_designware AMDI0010:00: timeout in disabling adapter 2024-07-09T21:31:51.596828-04:00 machinename kernel: i2c_designware AMDI0010:00: timeout waiting for bus ready 2024-07-09T21:32:45.928870-04:00 machinename kernel: message repeated 2652 times: [ i2c_designware AMDI0010:00: timeout waiting for bus ready] The only workaround I've found is to sleep/hibernate or shut down the laptop; it always works again on reboot. Since I upgraded to 24.04, I sometimes have the additional problem that I can't sleep the laptop when this is happening. I get errors that say "kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" when I try. Note that the problem did not happen between my most recent boot and the generation of the attached files via "ubuntu-bug linux". ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-36-generic 6.8.0-36.36 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jul 9 22:02:03 2024 InstallationDate: Installed on 2021-11-28 (954 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82ND ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=1ae6eb8d-78a6-4fdd-affc-4d1e32c995d6 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:  linux-restricted-modules-6.8.0-36-generic N/A  linux-backports-modules-6.8.0-36-generic N/A  linux-firmware 20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-06-27 (12 days ago) dmi.bios.date: 03/26/2024 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: H6CN22WW(V1.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 6 13ALC6 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrH6CN22WW(V1.15):bd03/26/2024:br1.22:efr1.22:svnLENOVO:pn82ND:pvrYoga613ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga613ALC6:skuLENOVO_MT_82ND_BU_idea_FM_Yoga613ALC6: dmi.product.family: Yoga 6 13ALC6 dmi.product.name: 82ND dmi.product.sku: LENOVO_MT_82ND_BU_idea_FM_Yoga 6 13ALC6 dmi.product.version: Yoga 6 13ALC6 dmi.sys.vendor: LENOVO modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-04-23T07:30:10 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2072612/+subscriptions

[Bug 2161904] Re: i915 backlight brightness control broken on ThinkPad T470 after kernel 7.0.0-28 (works on -27)

Tested with kernel 7.0.0-29-generic on the same ThinkPad T470 (i915, Intel HD Graphics 620) referenced in this report. The backlight regression is still present: pressing the brightness keys (F6) shows the OSD indicator, but actual screen brightness does not change. Same symptom as previously reported on 7.0.0-28. Writing directly to /sys/class/backlight/intel_backlight/brightness also has no effect, consistent with prior testing. Reverted to 7.0.0-27-generic, where brightness control works normally again. Note: suspend/resume (lid close/open) was not re-tested on 7.0.0-29 in this round — will update if/when tested. System info: uname -r on failing kernel: 7.0.0-29-generic Only one backlight interface present: intel_backlight (no acpi_video0) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161904 Title: i915 backlight brightness control broken on ThinkPad T470 after kernel 7.0.0-28 (works on -27) Status in linux package in Ubuntu: New Bug description: Backlight brightness control stopped working after upgrading from kernel 7.0.0-27 to 7.0.0-28 on ThinkPad T470 (Intel HD Graphics 620). The KDE brightness OSD appears and F5/F6 keys respond, but the actual screen brightness does not change. Writing directly to /sys/class/backlight/intel_backlight/brightness has no effect either. Booting back into 7.0.0-27 restores full brightness control. Only one backlight interface exists (intel_backlight, no acpi_video0). This appears to be an i915 regression in 7.0.0-28. A user with a ThinkPad X250 (also Intel HD Graphics) reported the identical issue on the Ubuntu Discourse forum, also resolved by reverting to 7.0.0-27: https://discourse.ubuntu.com/t/screen-brightness-using-kernel-7-0-0-28-on-lenovo-thinkpad-x250-intel-hd-graphics/85267 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 AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-27-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: joel 2850 F.... pipewire joel 2861 F.... wireplumber /dev/snd/pcmC0D0p: joel 2850 F...m pipewire /dev/snd/seq: joel 2850 F.... pipewire CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Jul 27 11:57:16 2026 InstallationDate: Installed on 2026-07-02 (25 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: LENOVO 20JNS28G00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/vg0-lv--0 ro 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. RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2024 dmi.bios.release: 1.79 dmi.bios.vendor: LENOVO dmi.bios.version: N1QETA4W (1.79 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JNS28G00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: PE03BQ37 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrN1QETA4W(1.79):bd11/05/2024:br1.79:efr1.36:svnLENOVO:pn20JNS28G00:pvrThinkPadT470W10DG:rvnLENOVO:rn20JNS28G00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20JN_BU_Think_FM_ThinkPadT470W10DG:pfaThinkPadT470W10DG: dmi.product.family: ThinkPad T470 W10DG dmi.product.name: 20JNS28G00 dmi.product.sku: LENOVO_MT_20JN_BU_Think_FM_ThinkPad T470 W10DG dmi.product.version: ThinkPad T470 W10DG dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161904/+subscriptions

[Bug 2162919] [NEW] after updating to the latest kernel my brightness controling is not working. I run the bug report commant to se if does something I think it might be related to that.

Public bug reported: I don't know much about the essue but my brighness control is not working. slider works but no effect on the screen. I have a lenovo p51s laptop. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: shubham-mamodiya 4744 F.... wireplumber /dev/snd/seq: shubham-mamodiya 4731 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 21:46:50 2026 InstallationDate: Installed on 2026-07-06 (30 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20JY0009US ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-ghostty ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2023 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET64W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JY0009US 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.18 dmi.modalias: dmi:bvnLENOVO:bvrN1VET64W(1.54):bd07/14/2023:br1.54:efr1.18:svnLENOVO:pn20JY0009US:pvrThinkPadP51sW10DG:rvnLENOVO:rn20JY0009US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20JY_BU_Think_FM_ThinkPadP51sW10DG:pfaThinkPadP51sW10DG: dmi.product.family: ThinkPad P51s W10DG dmi.product.name: 20JY0009US dmi.product.sku: LENOVO_MT_20JY_BU_Think_FM_ThinkPad P51s W10DG dmi.product.version: ThinkPad P51s W10DG dmi.sys.vendor: LENOVO ** 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/2162919 Title: after updating to the latest kernel my brightness controling is not working. I run the bug report commant to se if does something I think it might be related to that. Status in linux package in Ubuntu: New Bug description: I don't know much about the essue but my brighness control is not working. slider works but no effect on the screen. I have a lenovo p51s laptop. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: shubham-mamodiya 4744 F.... wireplumber /dev/snd/seq: shubham-mamodiya 4731 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 21:46:50 2026 InstallationDate: Installed on 2026-07-06 (30 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20JY0009US ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-ghostty ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2023 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET64W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JY0009US 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.18 dmi.modalias: dmi:bvnLENOVO:bvrN1VET64W(1.54):bd07/14/2023:br1.54:efr1.18:svnLENOVO:pn20JY0009US:pvrThinkPadP51sW10DG:rvnLENOVO:rn20JY0009US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20JY_BU_Think_FM_ThinkPadP51sW10DG:pfaThinkPadP51sW10DG: dmi.product.family: ThinkPad P51s W10DG dmi.product.name: 20JY0009US dmi.product.sku: LENOVO_MT_20JY_BU_Think_FM_ThinkPad P51s W10DG dmi.product.version: ThinkPad P51s W10DG dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162919/+subscriptions

[Bug 2162908] [NEW] Panel backlight control non-functional on Meteor Lake Arc Graphics after kernel 7.0.0-28 (regression from 7.0.0-27)

Public bug reported: SUMMARY Panel backlight control stopped working after a kernel update. Brightness hotkeys and the desktop slider respond visually, and writes to /sys/class/backlight/intel_backlight/brightness are accepted and read back correctly, but the physical panel brightness never actually changes. ENVIRONMENT - Laptop: Lenovo ThinkPad, Meteor Lake platform, hybrid Intel/NVIDIA - iGPU: Intel Meteor Lake-P [Intel Arc Graphics], PCI ID 8086:7d55, driver in use: i915 - dGPU: NVIDIA AD107GLM [RTX 500 Ada Generation Laptop GPU] - OS: Ubuntu 26.04 (resolute) - Backlight device: /sys/class/backlight/intel_backlight, type = raw - Display server: Wayland / GNOME KNOWN-GOOD / KNOWN-BAD KERNELS 7.0.0-27-generic: working 7.0.0-28-generic: broken 7.0.0-29-generic: broken Regression introduced between 7.0.0-27 and 7.0.0-28, still present in 7.0.0-29. linux-firmware-intel-graphics was also upgraded in the same apt transaction as the 27->28 kernel bump, so the root cause could be in i915 itself or in the bundled firmware blob. STEPS TO REPRODUCE 1. Boot 7.0.0-28-generic or later. 2. cat /sys/class/backlight/intel_backlight/type -> raw 3. sudo tee /sys/class/backlight/intel_backlight/brightness <<< 32767 cat .../brightness -> correctly shows 32767, but screen does not change 4. sudo tee /sys/class/backlight/intel_backlight/brightness <<< 1000 cat .../brightness -> correctly shows 1000, screen still does not change EXPECTED Panel brightness should track the sysfs value, as it does on 7.0.0-27-generic. ACTUAL Value is written and read back correctly; physical backlight is unaffected. ISOLATION ALREADY PERFORMED - Reproduces identically in prime-select intel, on-demand, and nvidia modes -> not a PRIME/GPU-switching issue. - lspci -k confirms i915 (not xe) is bound in all cases. - Direct sysfs writes behave the same as hotkeys/GUI slider -> not a desktop/logind/permissions issue. - i915.enable_dpcd_backlight=1 and =2 kernel parameters tested, no change. - Reproduces identically across nvidia-driver-595-open, 610-open, and 610 (proprietary) -> not NVIDIA-driver-specific. - Confirmed by kernel downgrade: reinstalling and booting 7.0.0-27-generic (Intel-only, no NVIDIA module for that kernel) restores working brightness control. Rebooting into 28 or 29 reproduces the failure immediately. DMESG (broken kernel) thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) input: Video Bus as /devices/pci0000:00/acpi.video_bus.0/input/input14 No i915-specific backlight/panel/edp/pwm messages appear in dmesg on the broken kernels. RELATED (BUT LIKELY DISTINCT) REPORT https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1087 describes an NVIDIA-driver-specific backlight regression on the 595 series. This report reproduces independent of NVIDIA involvement (Intel-only mode is also broken), so it is likely a separate i915/kernel issue rather than the same root cause. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: gian 6457 F.... pipewire gian 6477 F.... wireplumber /dev/snd/seq: gian 6457 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 16:07:04 2026 InstallationDate: Installed on 2026-04-24 (103 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21G20009UK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2026 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: R2DET42W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 21G20009UK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR2DET42W(1.27):bd04/24/2026:br1.27:efr1.18:svnLENOVO:pn21G20009UK:pvrThinkPadP14sGen5:rvnLENOVO:rn21G20009UK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21G2_BU_Think_FM_ThinkPadP14sGen5:pfaThinkPadP14sGen5: dmi.product.family: ThinkPad P14s Gen 5 dmi.product.name: 21G20009UK dmi.product.sku: LENOVO_MT_21G2_BU_Think_FM_ThinkPad P14s Gen 5 dmi.product.version: ThinkPad P14s Gen 5 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "lspci-verbose.txt" https://bugs.launchpad.net/bugs/2162908/+attachment/5989730/+files/lspci-verbose.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162908 Title: Panel backlight control non-functional on Meteor Lake Arc Graphics after kernel 7.0.0-28 (regression from 7.0.0-27) Status in linux package in Ubuntu: New Bug description: SUMMARY Panel backlight control stopped working after a kernel update. Brightness hotkeys and the desktop slider respond visually, and writes to /sys/class/backlight/intel_backlight/brightness are accepted and read back correctly, but the physical panel brightness never actually changes. ENVIRONMENT - Laptop: Lenovo ThinkPad, Meteor Lake platform, hybrid Intel/NVIDIA - iGPU: Intel Meteor Lake-P [Intel Arc Graphics], PCI ID 8086:7d55, driver in use: i915 - dGPU: NVIDIA AD107GLM [RTX 500 Ada Generation Laptop GPU] - OS: Ubuntu 26.04 (resolute) - Backlight device: /sys/class/backlight/intel_backlight, type = raw - Display server: Wayland / GNOME KNOWN-GOOD / KNOWN-BAD KERNELS 7.0.0-27-generic: working 7.0.0-28-generic: broken 7.0.0-29-generic: broken Regression introduced between 7.0.0-27 and 7.0.0-28, still present in 7.0.0-29. linux-firmware-intel-graphics was also upgraded in the same apt transaction as the 27->28 kernel bump, so the root cause could be in i915 itself or in the bundled firmware blob. STEPS TO REPRODUCE 1. Boot 7.0.0-28-generic or later. 2. cat /sys/class/backlight/intel_backlight/type -> raw 3. sudo tee /sys/class/backlight/intel_backlight/brightness <<< 32767 cat .../brightness -> correctly shows 32767, but screen does not change 4. sudo tee /sys/class/backlight/intel_backlight/brightness <<< 1000 cat .../brightness -> correctly shows 1000, screen still does not change EXPECTED Panel brightness should track the sysfs value, as it does on 7.0.0-27-generic. ACTUAL Value is written and read back correctly; physical backlight is unaffected. ISOLATION ALREADY PERFORMED - Reproduces identically in prime-select intel, on-demand, and nvidia modes -> not a PRIME/GPU-switching issue. - lspci -k confirms i915 (not xe) is bound in all cases. - Direct sysfs writes behave the same as hotkeys/GUI slider -> not a desktop/logind/permissions issue. - i915.enable_dpcd_backlight=1 and =2 kernel parameters tested, no change. - Reproduces identically across nvidia-driver-595-open, 610-open, and 610 (proprietary) -> not NVIDIA-driver-specific. - Confirmed by kernel downgrade: reinstalling and booting 7.0.0-27-generic (Intel-only, no NVIDIA module for that kernel) restores working brightness control. Rebooting into 28 or 29 reproduces the failure immediately. DMESG (broken kernel) thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) input: Video Bus as /devices/pci0000:00/acpi.video_bus.0/input/input14 No i915-specific backlight/panel/edp/pwm messages appear in dmesg on the broken kernels. RELATED (BUT LIKELY DISTINCT) REPORT https://github.com/NVIDIA/open-gpu-kernel-modules/issues/1087 describes an NVIDIA-driver-specific backlight regression on the 595 series. This report reproduces independent of NVIDIA involvement (Intel-only mode is also broken), so it is likely a separate i915/kernel issue rather than the same root cause. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: gian 6457 F.... pipewire gian 6477 F.... wireplumber /dev/snd/seq: gian 6457 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 16:07:04 2026 InstallationDate: Installed on 2026-04-24 (103 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21G20009UK ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2026 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: R2DET42W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 21G20009UK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 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.18 dmi.modalias: dmi:bvnLENOVO:bvrR2DET42W(1.27):bd04/24/2026:br1.27:efr1.18:svnLENOVO:pn21G20009UK:pvrThinkPadP14sGen5:rvnLENOVO:rn21G20009UK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21G2_BU_Think_FM_ThinkPadP14sGen5:pfaThinkPadP14sGen5: dmi.product.family: ThinkPad P14s Gen 5 dmi.product.name: 21G20009UK dmi.product.sku: LENOVO_MT_21G2_BU_Think_FM_ThinkPad P14s Gen 5 dmi.product.version: ThinkPad P14s Gen 5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162908/+subscriptions

[Bug 2162904] [NEW] amdgpu panel self-refresh on dual-gpu laptops causes partial system freeze

Public bug reported: BugLink: https://bugs.launchpad.net/bugs/2162904 On some laptops with a dGPU and an iGPU, the DMCUB's state transition between sleep and wake states on the laptop's built-in panel will (at irregular but frequent intervals, a few times per day in my experience) cause the amdgpu driver to stop working correctly. While some users have reported similar bugs that occur even when no external display is connected, I have personally only experienced this error when I have an external display connected. Given the inconsistency, my suspicion is that this is a race condition that is substantially exacerbated when multiple displays are attached (potentially moreso when this involves interactions between the amdgpu and NVIDIA modules, as in my laptop's case). The issue typically occurs when many applications are open. In my case, this is usually when I have a game or various dev tools active on the external monitor, and Discord (mostly visibly idle) on the built-in panel. Some of us in the community have also noticed correlation with Chromium-based apps being open, but I don't believe causation has been proven for that yet. [ Impact ] When the issue occurs, the user's built-in panel will freeze completely. If connected to an external monitor, that external monitor continues to work, as do many other parts of the system. However, they'll quickly start to notice that various parts of the system that interact with the gpu will fail to work correctly. Trying to drag windows from the frozen monitor to the external monitor will continue to partially work, but eventually will start breaking (ex: artifacts will start appearing, gnome menus for alt+tab will start freezing in place, shutdown menu will be empty, attempting to shutdown will cause unexpected hangs and possibly panics). Background audio and related things usually still work at this point, but many odd things will be failing (ex: won't be able to switch to virtual TTY, seemingly can't even use sysrq+reisub). At this stage, it is only a matter of time before the system becomes completely unusable, at which point the user will need to hard poweroff and boot again. The following dmesg output appears around the same time as when the failure occurs: [24076.056392] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24076.288041] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24076.518883] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24086.631908] amdgpu 0000:07:00.0: [drm] *ERROR* [CRTC:364:crtc-0] flip_done timed out From the data I have gathered, this is the only output that I have observed to be consistent across all instances of this failure mode on my machine. Various upstream discussions exist detailing this and related issues on varying hardware/kernels/distros, where this also tends to be consistent. Triaged as "High" given how disruptive this is for impacted users. [ Fix ] As far as I can tell, the underlying issue here is a race condition that occurs between some combination of the DMCUB, amdgpu kernel module, device firmware, and possibly also nvidia module on impacted systems. I have not been able to find a concrete patch series that fixes the race condition itself, and it seems that work is still ongoing upstream to improve amdgpu module recovery when this happens. Given the intrusiveness of this issue, my proposal is to simply disable the panel self-refresh feature whenever an external display is connected. Various community findings [0] had previously suggested doing this via the `amdgpu.dcdebugmask=0x10` kernel option. I have had this enabled for 3+ weeks, which has eliminated the crashes for me. My proposed patch has the same impact, but only when an external display is connected rather than unconditionally (so we don't lose the power saving benefit of PSR in the scenario where this bug does not occur nearly as much). I will forward this upstream as well, but I propose applying this as UBUNTU: SAUCE since upstream will likely prefer to keep working to fix the underlying issue (which, if successful, should allow us to drop my patch.) [ Where problems could occur ] Since disabling panel self-refresh means that the built-in panel will always refresh at its standard refresh rate, users may experience decreased battery life if not connected to power. HOWEVER, given that we only disable it *when an external display is connected*, I expect that the vast majority of laptop users will not be meaningfully impacted. With the exception of people using mobile external monitors, I would expect most users who have an external display attached to typically also be connected to power. Additionally, while I have never reproduced this bug when only using my built-in panel (with no external monitor attached), related reports across other distros indicate the underlying bug might still be possible with only the built-in monitor - so this patch may not resolve the bug for 100% of users (but I am confident that it will drastically reduce if not eliminate incidence for configs like mine) [ Test Plan ] Install the patched kernel from -proposed (once it lands there) and do the following: 1) sudo watch -n 0.5 cat /sys/kernel/debug/dri/0000:07:00.0/eDP-2/psr_state # (switch eDP-2 to your built in panel identifier). You should see it switch between "0" and nonzero values when no external display is connected (indicating that PSR is still active and switching to/from sleep state regularly). After connecting an external display, confirm that only 0 is shown even when builtin panel isn't drawing (indicating that PSR has been disabled when the second display is connected). 2) Use your machine normally for 1-2 weeks and confirm that the bug does not reproduce. (It typically reproduces within 1 day, so 1-2 weeks should be a comfortable amount of time here.) [ Additional Information ] Upstream bug: https://gitlab.freedesktop.org/drm/amd/-/work_items/5394 System info: Ubuntu 26.04 Linux 7.0.0-27-generic Wayland GNOME 50 Hardware info: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA503RM_GA503RM FW version: GA503RM.318 AMD Ryzen™ 9 6900HS with Radeon™ Graphics × 16 iGPU: AMD Radeon™ 680M dGPU: NVIDIA GeForce RTX™ 3060 Laptop GPU 16.0 GiB RAM [0] ex: https://askubuntu.com/questions/1566809/ubuntu-26-04-lts- probably-unstable-driver-amdgpu ** Affects: linux (Ubuntu) Importance: High Assignee: Mitchell Augustin (mitchellaugustin) Status: In Progress ** Affects: linux (Ubuntu Resolute) Importance: High Assignee: Mitchell Augustin (mitchellaugustin) Status: In Progress ** Affects: linux (Ubuntu Stonking) Importance: High Assignee: Mitchell Augustin (mitchellaugustin) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin) ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Stonking) Importance: Undecided Assignee: Mitchell Augustin (mitchellaugustin) Status: New ** Changed in: linux (Ubuntu Resolute) Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin) ** Changed in: linux (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux (Ubuntu Stonking) Status: New => In Progress ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => High ** Changed in: linux (Ubuntu Stonking) Importance: Undecided => High ** Description changed: On some laptops with a dGPU and an iGPU, the DMCUB's state transition between sleep and wake states on the laptop's built-in panel will (at irregular but frequent intervals, a few times per day in my experience) cause the amdgpu driver to stop working correctly. While some users have reported similar bugs that occur even when no external display is connected, I have personally only experienced this error when I have an external display connected. Given the inconsistency, my suspicion is that this is a race condition that is at least substantially exacerbated when multiple displays are attached (potentially moreso when this involves interactions between the amdgpu and NVIDIA modules, as in my laptop's case). The issue typically occurs when many applications are open. In my case, this is usually when I have a game or various dev tools active on the external monitor, and Discord (mostly visibly idle) on the built-in panel. Some of us in the community have also noticed correlation with Chromium-based apps being open. [ Impact ] - When the issue occurs, the user's built-in panel will freeze completely. If connected to an external monitor, that external monitor continues to work, as do many other parts of the system. However, they'll quickly start to notice that various parts of the system that interact with the gpu will fail to work correctly. + When the issue occurs, the user's built-in panel will freeze completely. If connected to an external monitor, that external monitor continues to work, as do many other parts of the system. However, they'll quickly start to notice that various parts of the system that interact with the gpu will fail to work correctly. Trying to drag windows from the frozen monitor to the external monitor will continue to partially work, but eventually will start breaking (ex: artifacts will start appearing, gnome menus for alt+tab will start freezing in place, shutdown menu will be empty, attempting to shutdown will cause unexpected hangs and possibly panics). Background audio and related things usually still work at this point, but many odd things will be failing (ex: won't be able to switch to virtual TTY, seemingly can't even use sysrq+reisub). At this stage, the user will need to hard poweroff and boot again. The following dmesg output appears around the same time as when the failure occurs: [24076.056392] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24076.288041] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24076.518883] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24086.631908] amdgpu 0000:07:00.0: [drm] *ERROR* [CRTC:364:crtc-0] flip_done timed out From the data I have gathered, this is the only output that I have observed to be consistent across all instances of this failure mode on my machine. Various upstream discussions exist detailing this and related issues on varying hardware/kernels/distros, where this also tends to be consistent. + Triaged as "High" given how disruptive this is for impacted users. + [ Fix ] As far as I can tell, the underlying issue here is a race condition that occurs between some combination of the DMCUB, amdgpu kernel module, device firmware, and possibly also nvidia module on impacted systems. I have not been able to find a concrete patch series that fixes the race condition itself, and it seems that work is still ongoing upstream to improve amdgpu module recovery when this happens. Given the intrusiveness of this issue, my proposal is to simply disable the panel self-refresh feature whenever an external display is connected. + Various community findings [0] had previously suggested doing this via + the `amdgpu.dcdebugmask=0x10` kernel option. I have had this enabled for + 3+ weeks, which has eliminated the crashes for me. My proposed patch has + the same impact, but only when an external display is connected rather + than unconditionally (so we don't lose the power saving benefit of PSR + in the scenario where this bug does not occur nearly as much). [ Where problems could occur ] Since disabling panel self-refresh means that the built-in panel will always refresh at its standard refresh rate, users may experience decreased battery life if not connected to power. HOWEVER, given that we only disable it *when an external display is connected*, I expect that the vast majority of laptop users will not be meaningfully impacted. With the exception of people using mobile external monitors, I would expect most users who have an external display attached to typically also be connected to power. Additionally, while I have never reproduced this bug when only using my built-in panel (with no external monitor attached), related reports across other distros indicate the underlying bug might still be possible with only the built-in monitor - so this patch may not resolve the bug for 100% of users (but I am confident that it will drastically reduce if not eliminate incidence for configs like mine) [ Test Plan ] Install the patched kernel from -proposed and do the following: 1) sudo watch -n 0.5 cat /sys/kernel/debug/dri/0000:07:00.0/eDP-2/psr_state # (switch eDP-2 to your built in panel identifier). You should see it switch between "0" and nonzero values when no external display is connected (indicating that PSR is still active and switching to/from sleep state regularly). After connecting an external display, confirm that only 0 is shown even when builtin panel isn't drawing (indicating that PSR has been disabled when the second display is connected). 2) Use your machine normally for 1-2 weeks and confirm that the bug does not reproduce. (It typically reproduces within 1 day, so 1-2 weeks should be a comfortable amount of time here.) [ Additional Information ] Upstream bug: https://gitlab.freedesktop.org/drm/amd/-/work_items/5394 System info: Ubuntu 26.04 Linux 7.0.0-27-generic Wayland GNOME 50 Hardware info: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA503RM_GA503RM FW version: GA503RM.318 AMD Ryzen™ 9 6900HS with Radeon™ Graphics × 16 iGPU: AMD Radeon™ 680M dGPU: NVIDIA GeForce RTX™ 3060 Laptop GPU 16.0 GiB RAM + + [0] ex: https://askubuntu.com/questions/1566809/ubuntu-26-04-lts- + probably-unstable-driver-amdgpu -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162904 Title: amdgpu panel self-refresh on dual-gpu laptops causes partial system freeze Status in linux package in Ubuntu: In Progress Status in linux source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2162904 On some laptops with a dGPU and an iGPU, the DMCUB's state transition between sleep and wake states on the laptop's built-in panel will (at irregular but frequent intervals, a few times per day in my experience) cause the amdgpu driver to stop working correctly. While some users have reported similar bugs that occur even when no external display is connected, I have personally only experienced this error when I have an external display connected. Given the inconsistency, my suspicion is that this is a race condition that is substantially exacerbated when multiple displays are attached (potentially moreso when this involves interactions between the amdgpu and NVIDIA modules, as in my laptop's case). The issue typically occurs when many applications are open. In my case, this is usually when I have a game or various dev tools active on the external monitor, and Discord (mostly visibly idle) on the built-in panel. Some of us in the community have also noticed correlation with Chromium-based apps being open, but I don't believe causation has been proven for that yet. [ Impact ] When the issue occurs, the user's built-in panel will freeze completely. If connected to an external monitor, that external monitor continues to work, as do many other parts of the system. However, they'll quickly start to notice that various parts of the system that interact with the gpu will fail to work correctly. Trying to drag windows from the frozen monitor to the external monitor will continue to partially work, but eventually will start breaking (ex: artifacts will start appearing, gnome menus for alt+tab will start freezing in place, shutdown menu will be empty, attempting to shutdown will cause unexpected hangs and possibly panics). Background audio and related things usually still work at this point, but many odd things will be failing (ex: won't be able to switch to virtual TTY, seemingly can't even use sysrq+reisub). At this stage, it is only a matter of time before the system becomes completely unusable, at which point the user will need to hard poweroff and boot again. The following dmesg output appears around the same time as when the failure occurs: [24076.056392] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24076.288041] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24076.518883] amdgpu 0000:07:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data [24086.631908] amdgpu 0000:07:00.0: [drm] *ERROR* [CRTC:364:crtc-0] flip_done timed out From the data I have gathered, this is the only output that I have observed to be consistent across all instances of this failure mode on my machine. Various upstream discussions exist detailing this and related issues on varying hardware/kernels/distros, where this also tends to be consistent. Triaged as "High" given how disruptive this is for impacted users. [ Fix ] As far as I can tell, the underlying issue here is a race condition that occurs between some combination of the DMCUB, amdgpu kernel module, device firmware, and possibly also nvidia module on impacted systems. I have not been able to find a concrete patch series that fixes the race condition itself, and it seems that work is still ongoing upstream to improve amdgpu module recovery when this happens. Given the intrusiveness of this issue, my proposal is to simply disable the panel self-refresh feature whenever an external display is connected. Various community findings [0] had previously suggested doing this via the `amdgpu.dcdebugmask=0x10` kernel option. I have had this enabled for 3+ weeks, which has eliminated the crashes for me. My proposed patch has the same impact, but only when an external display is connected rather than unconditionally (so we don't lose the power saving benefit of PSR in the scenario where this bug does not occur nearly as much). I will forward this upstream as well, but I propose applying this as UBUNTU: SAUCE since upstream will likely prefer to keep working to fix the underlying issue (which, if successful, should allow us to drop my patch.) [ Where problems could occur ] Since disabling panel self-refresh means that the built-in panel will always refresh at its standard refresh rate, users may experience decreased battery life if not connected to power. HOWEVER, given that we only disable it *when an external display is connected*, I expect that the vast majority of laptop users will not be meaningfully impacted. With the exception of people using mobile external monitors, I would expect most users who have an external display attached to typically also be connected to power. Additionally, while I have never reproduced this bug when only using my built-in panel (with no external monitor attached), related reports across other distros indicate the underlying bug might still be possible with only the built-in monitor - so this patch may not resolve the bug for 100% of users (but I am confident that it will drastically reduce if not eliminate incidence for configs like mine) [ Test Plan ] Install the patched kernel from -proposed (once it lands there) and do the following: 1) sudo watch -n 0.5 cat /sys/kernel/debug/dri/0000:07:00.0/eDP-2/psr_state # (switch eDP-2 to your built in panel identifier). You should see it switch between "0" and nonzero values when no external display is connected (indicating that PSR is still active and switching to/from sleep state regularly). After connecting an external display, confirm that only 0 is shown even when builtin panel isn't drawing (indicating that PSR has been disabled when the second display is connected). 2) Use your machine normally for 1-2 weeks and confirm that the bug does not reproduce. (It typically reproduces within 1 day, so 1-2 weeks should be a comfortable amount of time here.) [ Additional Information ] Upstream bug: https://gitlab.freedesktop.org/drm/amd/-/work_items/5394 System info: Ubuntu 26.04 Linux 7.0.0-27-generic Wayland GNOME 50 Hardware info: ASUSTeK COMPUTER INC. ROG Zephyrus G15 GA503RM_GA503RM FW version: GA503RM.318 AMD Ryzen™ 9 6900HS with Radeon™ Graphics × 16 iGPU: AMD Radeon™ 680M dGPU: NVIDIA GeForce RTX™ 3060 Laptop GPU 16.0 GiB RAM [0] ex: https://askubuntu.com/questions/1566809/ubuntu-26-04-lts- probably-unstable-driver-amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162904/+subscriptions

[Bug 2162887] Re: Add 0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch

This patch will fix https://bugs.launchpad.net/kobuk/+bug/2159612 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162887 Title: Add 0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch Status in linux package in Ubuntu: New Bug description: [ Impact ] DPMO issue in TWL system as it stuck at random iteration and observed spam/dump message when board is idle or before login to the system or after running some command. [Fix] Apply patch in https://bugs.launchpad.net/kobuk/+bug/2159612/+attachment/5983976/+files/0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch (similar as attached patch provided from Jianfeng) [ Test Plan ] 1) Flash IFWI & BKC to TWL CRB 2) Apply settings for Warm Reset: sudo nano /etc/systemd/system.conf#DefaultTimeoutStopSec=90s --> DefaultTimeoutStopSec=5s 3) Trigger WR x 500 iterations 4) With the patch applied, both Warm reboot and Cold reboot test has passed. [ Where problems could occur ] [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162887/+subscriptions

[Bug 2162887] [NEW] Add 0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch

Public bug reported: [ Impact ] DPMO issue in TWL system as it stuck at random iteration and observed spam/dump message when board is idle or before login to the system or after running some command. [Fix] Apply patch in https://bugs.launchpad.net/kobuk/+bug/2159612/+attachment/5983976/+files/0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch (similar as attached patch provided from Jianfeng) [ Test Plan ] 1) Flash IFWI & BKC to TWL CRB 2) Apply settings for Warm Reset: sudo nano /etc/systemd/system.conf#DefaultTimeoutStopSec=90s --> DefaultTimeoutStopSec=5s 3) Trigger WR x 500 iterations 4) With the patch applied, both Warm reboot and Cold reboot test has passed. [ Where problems could occur ] [ Other Info ] N/A ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch" https://bugs.launchpad.net/bugs/2162887/+attachment/5989665/+files/0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162887 Title: Add 0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch Status in linux package in Ubuntu: New Bug description: [ Impact ] DPMO issue in TWL system as it stuck at random iteration and observed spam/dump message when board is idle or before login to the system or after running some command. [Fix] Apply patch in https://bugs.launchpad.net/kobuk/+bug/2159612/+attachment/5983976/+files/0001-usb-typec-tipd-mask-interrupt-across-suspend-to-fix-.patch (similar as attached patch provided from Jianfeng) [ Test Plan ] 1) Flash IFWI & BKC to TWL CRB 2) Apply settings for Warm Reset: sudo nano /etc/systemd/system.conf#DefaultTimeoutStopSec=90s --> DefaultTimeoutStopSec=5s 3) Trigger WR x 500 iterations 4) With the patch applied, both Warm reboot and Cold reboot test has passed. [ Where problems could occur ] [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162887/+subscriptions

[Bug 2162843] Lspci-vt.txt

apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2162843/+attachment/5989461/+files/Lspci-vt.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162843 Title: Regression: io_uring provided buffer ring registration (IORING_REGISTER_PBUF_RING) returns -EINVAL for valid requests on 6.8.0-136 and 6.8.0-137 Status in linux package in Ubuntu: New Bug description: SUMMARY Starting with linux-image-6.8.0-136-generic (noble/24.04), registering an io_uring provided buffer ring (IORING_REGISTER_PBUF_RING) with a valid struct io_uring_buf_reg fails with EINVAL (errno 22). It succeeds on 6.8.0-134-generic and on mainline 7.0.0-28-generic. 6.8.0-137-generic is also affected, so the defect is carried in the noble 6.8 branch, not a one-off build. Provided buffer rings are a standard, documented io_uring feature, so this breaks any application that uses them. REPRODUCED ON OUR HARDWARE (single machine, kernel is the only variable) Same host, booted each kernel in turn and ran the attached reproducer: 6.8.0-134-generic -> register_buf_ring: OK 6.8.0-136-generic -> register_buf_ring: Invalid argument (EINVAL) 6.8.0-134-generic -> OK again after rebooting back A production networking service on that host that registers an io_uring buffer ring on startup aborts under -136 with SIGABRT (systemd Result: core-dump) at the failed registration, and starts normally again on -134. uname -a on the failing boot: Linux 6.8.0-136-generic #136-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 21:53:05 UTC 2026 x86_64 STEPS TO REPRODUCE Build and run the attached pbufring.c (pure liburing, ~20 lines): sudo apt-get install -y liburing-dev gcc gcc -o pbufring pbufring.c -luring ./pbufring Expected (good kernel): register_buf_ring: OK Observed (6.8.0-136 / -137): register_buf_ring: Invalid argument kernel.io_uring_disabled = 0 and /proc/sys/kernel/io_uring_group = -1 on all machines, so this is not an io_uring lockdown / AppArmor difference; the registration path itself rejects a valid request. SUSPECTED CAUSE Failure is in io_uring provided-buffer-ring registration validation (io_uring/kbuf.c, io_register_pbuf_ring(), reserved-field / struct checking). A valid io_uring_buf_reg (reserved fields zeroed; ring_addr/ring_entries/bgid set) is rejected; mainline is fine. Please check the noble backport of that validation, in particular the cherry-pick of upstream commit 1724849072854a66861d461b298b04612702d685 ("io_uring/kbuf: use mem_is_zero()"), which replaced the manual reg.resv[0]||resv[1]||resv[2] check with a mem_is_zero() call. If applied over the wrong offset/size it would zero-check bytes that legitimately carry ring_addr/ring_entries/bgid and reject every real registration. Note the current noble git tip shows the correct manual resv check, so a fix may already be staged; please confirm whether it is queued for 6.8.0-138 and expedite, since -137 shipped still broken. WORKAROUNDS (not fixes) Downgrade to 6.8.0-134-generic and reboot; or, application-side, avoid the provided- buffer-ring path where the code supports a fallback. ENVIRONMENT Ubuntu 24.04 LTS (noble), x86_64. Regression introduced between 6.8.0-134 and 6.8.0-136; also present in 6.8.0-137. --- ProblemType: Bug AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Aug 4 10:34 seq crw-rw---- 1 root audio 116, 33 Aug 4 10:34 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-134-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20250122 CloudSubPlatform: config-disk (/dev/nvme0n1p5) DistroRelease: Ubuntu 24.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: AsrockRack To be filled by O.E.M. NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-134-generic root=UUID=c0b38019-7891-470a-b184-151bcdd42d58 ro nomodeset iommu=pt console=tty0 console=ttyS1,115200n8 amd_pstate=disable quiet splash ipv6.disable=1 vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 RelatedPackageVersions: linux-restricted-modules-6.8.0-134-generic N/A linux-backports-modules-6.8.0-134-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image noble Uname: Linux 6.8.0-134-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/17/2024 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 20.01.OV03 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B650D4U3-2Q/BCM dmi.board.vendor: ASRockRack dmi.board.version: 3.01A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr20.01.OV03:bd10/17/2024:br5.35:svnAsrockRack:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASRockRack:rnB650D4U3-2Q/BCM:rvr3.01A:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AsrockRack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162843/+subscriptions

[Bug 2162843] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2162843/+attachment/5989460/+files/Lspci.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162843 Title: Regression: io_uring provided buffer ring registration (IORING_REGISTER_PBUF_RING) returns -EINVAL for valid requests on 6.8.0-136 and 6.8.0-137 Status in linux package in Ubuntu: New Bug description: SUMMARY Starting with linux-image-6.8.0-136-generic (noble/24.04), registering an io_uring provided buffer ring (IORING_REGISTER_PBUF_RING) with a valid struct io_uring_buf_reg fails with EINVAL (errno 22). It succeeds on 6.8.0-134-generic and on mainline 7.0.0-28-generic. 6.8.0-137-generic is also affected, so the defect is carried in the noble 6.8 branch, not a one-off build. Provided buffer rings are a standard, documented io_uring feature, so this breaks any application that uses them. REPRODUCED ON OUR HARDWARE (single machine, kernel is the only variable) Same host, booted each kernel in turn and ran the attached reproducer: 6.8.0-134-generic -> register_buf_ring: OK 6.8.0-136-generic -> register_buf_ring: Invalid argument (EINVAL) 6.8.0-134-generic -> OK again after rebooting back A production networking service on that host that registers an io_uring buffer ring on startup aborts under -136 with SIGABRT (systemd Result: core-dump) at the failed registration, and starts normally again on -134. uname -a on the failing boot: Linux 6.8.0-136-generic #136-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 21:53:05 UTC 2026 x86_64 STEPS TO REPRODUCE Build and run the attached pbufring.c (pure liburing, ~20 lines): sudo apt-get install -y liburing-dev gcc gcc -o pbufring pbufring.c -luring ./pbufring Expected (good kernel): register_buf_ring: OK Observed (6.8.0-136 / -137): register_buf_ring: Invalid argument kernel.io_uring_disabled = 0 and /proc/sys/kernel/io_uring_group = -1 on all machines, so this is not an io_uring lockdown / AppArmor difference; the registration path itself rejects a valid request. SUSPECTED CAUSE Failure is in io_uring provided-buffer-ring registration validation (io_uring/kbuf.c, io_register_pbuf_ring(), reserved-field / struct checking). A valid io_uring_buf_reg (reserved fields zeroed; ring_addr/ring_entries/bgid set) is rejected; mainline is fine. Please check the noble backport of that validation, in particular the cherry-pick of upstream commit 1724849072854a66861d461b298b04612702d685 ("io_uring/kbuf: use mem_is_zero()"), which replaced the manual reg.resv[0]||resv[1]||resv[2] check with a mem_is_zero() call. If applied over the wrong offset/size it would zero-check bytes that legitimately carry ring_addr/ring_entries/bgid and reject every real registration. Note the current noble git tip shows the correct manual resv check, so a fix may already be staged; please confirm whether it is queued for 6.8.0-138 and expedite, since -137 shipped still broken. WORKAROUNDS (not fixes) Downgrade to 6.8.0-134-generic and reboot; or, application-side, avoid the provided- buffer-ring path where the code supports a fallback. ENVIRONMENT Ubuntu 24.04 LTS (noble), x86_64. Regression introduced between 6.8.0-134 and 6.8.0-136; also present in 6.8.0-137. --- ProblemType: Bug AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Aug 4 10:34 seq crw-rw---- 1 root audio 116, 33 Aug 4 10:34 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-134-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20250122 CloudSubPlatform: config-disk (/dev/nvme0n1p5) DistroRelease: Ubuntu 24.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: AsrockRack To be filled by O.E.M. NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-134-generic root=UUID=c0b38019-7891-470a-b184-151bcdd42d58 ro nomodeset iommu=pt console=tty0 console=ttyS1,115200n8 amd_pstate=disable quiet splash ipv6.disable=1 vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 RelatedPackageVersions: linux-restricted-modules-6.8.0-134-generic N/A linux-backports-modules-6.8.0-134-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image noble Uname: Linux 6.8.0-134-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/17/2024 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 20.01.OV03 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B650D4U3-2Q/BCM dmi.board.vendor: ASRockRack dmi.board.version: 3.01A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr20.01.OV03:bd10/17/2024:br5.35:svnAsrockRack:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASRockRack:rnB650D4U3-2Q/BCM:rvr3.01A:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: AsrockRack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162843/+subscriptions

[Bug 2162843] Re: Regression: io_uring provided buffer ring registration (IORING_REGISTER_PBUF_RING) returns -EINVAL for valid requests on 6.8.0-136 and 6.8.0-137

** Tags added: kernel-bug regression-release regression-update ** Tags added: noble -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162843 Title: Regression: io_uring provided buffer ring registration (IORING_REGISTER_PBUF_RING) returns -EINVAL for valid requests on 6.8.0-136 and 6.8.0-137 Status in linux package in Ubuntu: New Bug description: SUMMARY Starting with linux-image-6.8.0-136-generic (noble/24.04), registering an io_uring provided buffer ring (IORING_REGISTER_PBUF_RING) with a valid struct io_uring_buf_reg fails with EINVAL (errno 22). It succeeds on 6.8.0-134-generic and on mainline 7.0.0-28-generic. 6.8.0-137-generic is also affected, so the defect is carried in the noble 6.8 branch, not a one-off build. Provided buffer rings are a standard, documented io_uring feature, so this breaks any application that uses them. REPRODUCED ON OUR HARDWARE (single machine, kernel is the only variable) Same host, booted each kernel in turn and ran the attached reproducer: 6.8.0-134-generic -> register_buf_ring: OK 6.8.0-136-generic -> register_buf_ring: Invalid argument (EINVAL) 6.8.0-134-generic -> OK again after rebooting back A production networking service on that host that registers an io_uring buffer ring on startup aborts under -136 with SIGABRT (systemd Result: core-dump) at the failed registration, and starts normally again on -134. uname -a on the failing boot: Linux 6.8.0-136-generic #136-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 21:53:05 UTC 2026 x86_64 STEPS TO REPRODUCE Build and run the attached pbufring.c (pure liburing, ~20 lines): sudo apt-get install -y liburing-dev gcc gcc -o pbufring pbufring.c -luring ./pbufring Expected (good kernel): register_buf_ring: OK Observed (6.8.0-136 / -137): register_buf_ring: Invalid argument kernel.io_uring_disabled = 0 and /proc/sys/kernel/io_uring_group = -1 on all machines, so this is not an io_uring lockdown / AppArmor difference; the registration path itself rejects a valid request. SUSPECTED CAUSE Failure is in io_uring provided-buffer-ring registration validation (io_uring/kbuf.c, io_register_pbuf_ring(), reserved-field / struct checking). A valid io_uring_buf_reg (reserved fields zeroed; ring_addr/ring_entries/bgid set) is rejected; mainline is fine. Please check the noble backport of that validation, in particular the cherry-pick of upstream commit 1724849072854a66861d461b298b04612702d685 ("io_uring/kbuf: use mem_is_zero()"), which replaced the manual reg.resv[0]||resv[1]||resv[2] check with a mem_is_zero() call. If applied over the wrong offset/size it would zero-check bytes that legitimately carry ring_addr/ring_entries/bgid and reject every real registration. Note the current noble git tip shows the correct manual resv check, so a fix may already be staged; please confirm whether it is queued for 6.8.0-138 and expedite, since -137 shipped still broken. WORKAROUNDS (not fixes) Downgrade to 6.8.0-134-generic and reboot; or, application-side, avoid the provided- buffer-ring path where the code supports a fallback. ENVIRONMENT Ubuntu 24.04 LTS (noble), x86_64. Regression introduced between 6.8.0-134 and 6.8.0-136; also present in 6.8.0-137. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162843/+subscriptions

[Bug 2162012] Re: Backport: "firmware: arm_ffa: Respect firmware advertised RX/TX buffer size limits"

This was applied to R/N:hwe-6.17 kernels. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162012 Title: Backport: "firmware: arm_ffa: Respect firmware advertised RX/TX buffer size limits" Status in linux package in Ubuntu: New Status in linux-hwe-7.0 package in Ubuntu: New Status in linux-nvidia-7.0 package in Ubuntu: In Progress Status in linux-nvidia-bos package in Ubuntu: In Progress Status in linux-hwe-7.0 source package in Noble: In Progress Status in linux-nvidia-7.0 source package in Noble: New Status in linux-nvidia-bos source package in Noble: New Status in linux source package in Resolute: In Progress Status in linux-hwe-7.0 source package in Resolute: In Progress Status in linux-nvidia-7.0 source package in Resolute: New Status in linux-nvidia-bos source package in Resolute: New Status in linux source package in Stonking: New Status in linux-hwe-7.0 source package in Stonking: New Status in linux-nvidia-7.0 source package in Stonking: In Progress Status in linux-nvidia-bos source package in Stonking: In Progress Bug description: [ Summary ] A recent stable-update pulled two v7.1 FF-A commits into the linux-nvidia 7.0 branches, but not the third commit in the chain. The result is that FF-A fails to initialise on 64K page kernels whose firmware rejects a 64K RX/TX buffer, taking every FF-A device with it. This backports the missing fix. ### The regression Stable-updates applied these two, both of which first shipped upstream in **v7.1**: | Backport | Upstream | BugLink | |---|---|---| | `7bfaed6b412b` firmware: arm_ffa: Use the correct buffer size during RXTX_MAP | `83210251fd70` | LP #2156385 | | `105dac1d2c92` firmware: arm_ffa: Align RxTx buffer size before mapping | `0399e3f872ca` | LP #2156390 | The first makes the driver advertise `PAGE_ALIGN(rxtx_bufsz)` to firmware; the second is its follow-up fix. Both landed in `Ubuntu-nvidia-bos-7.0.0-2016.16`, the most recent tag on this branch. Earlier tags are not affected. The third commit in the chain, which fixes the fallout from the first, only landed upstream in **v7.2-rc4**:     53716a4d745f firmware: arm_ffa: Respect firmware advertised RX/TX buffer size limits [ Impact ] On a 64K page kernel the driver takes the firmware advertised minimum RX/TX buffer size, rounds it up to `PAGE_SIZE`, and asks firmware to map that. FF-A implementations before v1.2 advertise no maximum and may simply reject the rounded up size. There is no clamp and no retry, so probe fails:     ARM FF-A: Driver version 1.2     ARM FF-A: Firmware version 1.1 found     ARM FF-A: failed to register FFA RxTx buffers and no FF-A devices are registered at all. Anything sitting on FF-A goes with it, including TPM over FF-A. Trigger is `PAGE_SIZE` greater than the advertised minimum, so the 64K flavours. Platforms with FF-A v1.2 or later firmware are unaffected, since the advertised maximum is then respected. [ Fix ] Backport of `53716a4d745f`. It decodes the maximum buffer size that FF-A v1.2+ reports, clamps the page aligned minimum to it, and where no maximum is advertised retries `RXTX_MAP` at the advertised minimum if the rounded size is rejected with `INVALID_PARAMETERS`. [ Test Plan ] Tested on an Arm server reporting FF-A firmware version 1.1, running a 64K page kernel built from this branch's own `nvidia-bos-64k` flavour annotations. Before, on the unmodified branch tip:     ARM FF-A: failed to register FFA RxTx buffers     /sys/bus/arm_ffa/devices/ -> empty After, with this commit applied:     ARM FF-A: Firmware version 1.1 found     ARM FF-A: Failed to create IRQ mapping!     /sys/bus/arm_ffa/devices/ -> arm-ffa-1 .. arm-ffa-5 All five partitions enumerate again. The remaining "Failed to create IRQ mapping" line is pre-existing and also present on the distro kernel that predates the regression. No new BUG, WARNING or call traces. [ Where Problems Could Occur ] A regression in this fix could cause issues with the ARM FF-A driver's partition enumeration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162012/+subscriptions