Public bug reported: Since a few kernel upgrades ago, I am experiencing consistent Wi-Fi connection failures on my 5GHz network. The connection drops repeatedly with the specific error: AP is in CSA process, reject auth. Reverting to 7.0.0-27 does not fix it, neither does the latest mainline 7.1.x. Wifi has been working without problems since I installed 26.04 so this problem came with some of the latest kernel upgrades. It happens at random, eg at fresh boot or after waking from suspend. Connecting to eg mobile hotspot works 100% of the time, so this problem seems to be related to 5GHz wifi. OS: Ubuntu 26.04 Kernel: 7.0.0-29-generic Hardware: Lenovo ThinkPad X1 Carbon Gen 12 Network Card: Intel Wi-Fi 6E AX211 160MHz Firmware: 89.123cf747.0 ma-b0-gf-a0-89.ucode Logs: Aug 06 10:48:25 ThinkPad-X1-Carbon-Gen-12 kernel: wlp0s20f3: AP is in CSA process, reject auth Aug 06 10:48:37 ThinkPad-X1-Carbon-Gen-12 wpa_supplicant[7651]: wlp0s20f3: SME: Authentication request to the driver failed Aug 06 10:48:37 ThinkPad-X1-Carbon-Gen-12 kernel: wlp0s20f3: AP is in CSA process, reject auth Steps to Reproduce: Attempt to connect to a 5GHz Wi-Fi network (WPA2-Personal). Observe the connection failing to complete the handshake. Observe the CSA process error in the logs. Steps Already Taken (Troubleshooting): Added options iwlwifi disable_11ax=Y to /etc/modprobe.d/iwlwifi.conf. Tested with mobile hotspot (which seems to work, likely due to different frequency/channel handling). None of the above user-space workarounds resolved the issue, suggesting a regression in the kernel/firmware handling of mac80211 management frames. sudo lshw -C network *-network description: Wireless interface product: Meteor Lake PCH CNVi WiFi vendor: Intel Corporation physical id: 14.3 bus info: pci@0000:00:14.3 logical name: wlp0s20f3 version: 20 serial: 98:bd:80:b4:65:f4 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=7.0.0-29-generic firmware=89.123cf747.0 ma-b0-gf-a0-89.uc ip=10.208.104.226 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:400-3ff irq:18 memory:401a704000-401a707fff lspci -nnk | grep -A3 Network 00:08.0 System peripheral [0880]: Intel Corporation Meteor Lake-P Gaussian & Neural-Network Accelerator [8086:7e4c] (rev 20) Subsystem: Lenovo Device [17aa:231e] 00:0a.0 Signal processing controller [1180]: Intel Corporation Meteor Lake-P Platform Monitoring Technology [8086:7d0d] (rev 01) Subsystem: Lenovo Device [17aa:231e] -- 00:14.3 Network controller [0280]: Intel Corporation Meteor Lake PCH CNVi WiFi [8086:7e40] (rev 20) Subsystem: Intel Corporation Device [8086:0090] Kernel driver in use: iwlwifi Kernel modules: iwlwifi 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: martin 4174 F.... pipewire martin 4196 F.... wireplumber /dev/snd/seq: martin 4174 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 7 00:13:12 2026 InstallationDate: Installed on 2025-12-28 (221 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: LENOVO 21KC005EMX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash preempt=full rcu_nocbs=all crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M preempt=full threadirqs rcu_nocbs=all 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-03-19 (140 days ago) dmi.bios.date: 04/07/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: N3YET84W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KC005EMX 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.29 dmi.modalias: dmi:bvnLENOVO:bvrN3YET84W(1.49):bd04/07/2026:br1.49:efr1.29:svnLENOVO:pn21KC005EMX:pvrThinkPadX1CarbonGen12:rvnLENOVO:rn21KC005EMX:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KC_BU_Think_FM_ThinkPadX1CarbonGen12:pfaThinkPadX1CarbonGen12: dmi.product.family: ThinkPad X1 Carbon Gen 12 dmi.product.name: 21KC005EMX dmi.product.sku: LENOVO_MT_21KC_BU_Think_FM_ThinkPad X1 Carbon Gen 12 dmi.product.version: ThinkPad X1 Carbon Gen 12 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Description changed: - Since upgrading to kernel 7.0.0-27 on my Lenovo ThinkPad X1 Carbon Gen - 12, I am experiencing consistent Wi-Fi connection failures on my 5GHz - network. The connection drops repeatedly with the specific error: AP is - in CSA process, reject auth. + Since a few kernel upgrades ago, I am experiencing consistent Wi-Fi + connection failures on my 5GHz network. The connection drops repeatedly + with the specific error: AP is in CSA process, reject auth. Reverting to + 7.0.0-27 does not fix it, neither does the latest mainline 7.1.x. Wifi + has been working without problems since I installed 26.04 so this + problem came with some of the latest kernel upgrades. It happens at + random, eg at fresh boot or after waking from suspend. Connecting to eg + mobile hotspot works 100% of the time, so this problem seems to be + related to 5GHz wifi. OS: Ubuntu 26.04 - Kernel: 7.0.0-27-generic + Kernel: 7.0.0-29-generic Hardware: Lenovo ThinkPad X1 Carbon Gen 12 Network Card: Intel Wi-Fi 6E AX211 160MHz Firmware: 89.123cf747.0 ma-b0-gf-a0-89.ucode Logs: Aug 06 10:48:25 ThinkPad-X1-Carbon-Gen-12 kernel: wlp0s20f3: AP is in CSA process, reject auth Aug 06 10:48:37 ThinkPad-X1-Carbon-Gen-12 wpa_supplicant[7651]: wlp0s20f3: SME: Authentication request to the driver failed Aug 06 10:48:37 ThinkPad-X1-Carbon-Gen-12 kernel: wlp0s20f3: AP is in CSA process, reject auth Steps to Reproduce: - Attempt to connect to a 5GHz Wi-Fi network (WPA2-Personal). - Observe the connection failing to complete the handshake. - Observe the CSA process error in the logs. + Attempt to connect to a 5GHz Wi-Fi network (WPA2-Personal). + Observe the connection failing to complete the handshake. + Observe the CSA process error in the logs. Steps Already Taken (Troubleshooting): - Added options iwlwifi disable_11ax=Y to /etc/modprobe.d/iwlwifi.conf. - Tested with mobile hotspot (which seems to work, likely due to different frequency/channel handling). - None of the above user-space workarounds resolved the issue, suggesting a regression in the kernel/firmware handling of mac80211 management frames. + Added options iwlwifi disable_11ax=Y to /etc/modprobe.d/iwlwifi.conf. + Tested with mobile hotspot (which seems to work, likely due to different frequency/channel handling). + None of the above user-space workarounds resolved the issue, suggesting a regression in the kernel/firmware handling of mac80211 management frames. sudo lshw -C network - *-network - description: Wireless interface - product: Meteor Lake PCH CNVi WiFi - vendor: Intel Corporation - physical id: 14.3 - bus info: pci@0000:00:14.3 - logical name: wlp0s20f3 - version: 20 - serial: 98:bd:80:b4:65:f4 - width: 64 bits - clock: 33MHz - capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless - configuration: broadcast=yes driver=iwlwifi driverversion=7.0.0-29-generic firmware=89.123cf747.0 ma-b0-gf-a0-89.uc ip=10.208.104.226 latency=0 link=yes multicast=yes wireless=IEEE 802.11 - resources: iomemory:400-3ff irq:18 memory:401a704000-401a707fff - + *-network + description: Wireless interface + product: Meteor Lake PCH CNVi WiFi + vendor: Intel Corporation + physical id: 14.3 + bus info: pci@0000:00:14.3 + logical name: wlp0s20f3 + version: 20 + serial: 98:bd:80:b4:65:f4 + width: 64 bits + clock: 33MHz + capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless + configuration: broadcast=yes driver=iwlwifi driverversion=7.0.0-29-generic firmware=89.123cf747.0 ma-b0-gf-a0-89.uc ip=10.208.104.226 latency=0 link=yes multicast=yes wireless=IEEE 802.11 + resources: iomemory:400-3ff irq:18 memory:401a704000-401a707fff lspci -nnk | grep -A3 Network 00:08.0 System peripheral [0880]: Intel Corporation Meteor Lake-P Gaussian & Neural-Network Accelerator [8086:7e4c] (rev 20) - Subsystem: Lenovo Device [17aa:231e] + Subsystem: Lenovo Device [17aa:231e] 00:0a.0 Signal processing controller [1180]: Intel Corporation Meteor Lake-P Platform Monitoring Technology [8086:7d0d] (rev 01) - Subsystem: Lenovo Device [17aa:231e] + Subsystem: Lenovo Device [17aa:231e] -- 00:14.3 Network controller [0280]: Intel Corporation Meteor Lake PCH CNVi WiFi [8086:7e40] (rev 20) - Subsystem: Intel Corporation Device [8086:0090] - Kernel driver in use: iwlwifi - Kernel modules: iwlwifi + Subsystem: Intel Corporation Device [8086:0090] + Kernel driver in use: iwlwifi + Kernel modules: iwlwifi 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: martin 4174 F.... pipewire - martin 4196 F.... wireplumber - /dev/snd/seq: martin 4174 F.... pipewire + USER PID ACCESS COMMAND + /dev/snd/controlC0: martin 4174 F.... pipewire + martin 4196 F.... wireplumber + /dev/snd/seq: martin 4174 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 7 00:13:12 2026 InstallationDate: Installed on 2025-12-28 (221 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: LENOVO 21KC005EMX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash preempt=full rcu_nocbs=all crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M preempt=full threadirqs rcu_nocbs=all 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-03-19 (140 days ago) dmi.bios.date: 04/07/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: N3YET84W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KC005EMX 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.29 dmi.modalias: dmi:bvnLENOVO:bvrN3YET84W(1.49):bd04/07/2026:br1.49:efr1.29:svnLENOVO:pn21KC005EMX:pvrThinkPadX1CarbonGen12:rvnLENOVO:rn21KC005EMX:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KC_BU_Think_FM_ThinkPadX1CarbonGen12:pfaThinkPadX1CarbonGen12: dmi.product.family: ThinkPad X1 Carbon Gen 12 dmi.product.name: 21KC005EMX dmi.product.sku: LENOVO_MT_21KC_BU_Think_FM_ThinkPad X1 Carbon Gen 12 dmi.product.version: ThinkPad X1 Carbon Gen 12 dmi.sys.vendor: LENOVO -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162998 Title: Intel AX211 Wi-Fi fails to connect (5GHz) - "AP is in CSA process, reject auth" kernel regression Status in linux package in Ubuntu: New Bug description: Since a few kernel upgrades ago, I am experiencing consistent Wi-Fi connection failures on my 5GHz network. The connection drops repeatedly with the specific error: AP is in CSA process, reject auth. Reverting to 7.0.0-27 does not fix it, neither does the latest mainline 7.1.x. Wifi has been working without problems since I installed 26.04 so this problem came with some of the latest kernel upgrades. It happens at random, eg at fresh boot or after waking from suspend. Connecting to eg mobile hotspot works 100% of the time, so this problem seems to be related to 5GHz wifi. OS: Ubuntu 26.04 Kernel: 7.0.0-29-generic Hardware: Lenovo ThinkPad X1 Carbon Gen 12 Network Card: Intel Wi-Fi 6E AX211 160MHz Firmware: 89.123cf747.0 ma-b0-gf-a0-89.ucode Logs: Aug 06 10:48:25 ThinkPad-X1-Carbon-Gen-12 kernel: wlp0s20f3: AP is in CSA process, reject auth Aug 06 10:48:37 ThinkPad-X1-Carbon-Gen-12 wpa_supplicant[7651]: wlp0s20f3: SME: Authentication request to the driver failed Aug 06 10:48:37 ThinkPad-X1-Carbon-Gen-12 kernel: wlp0s20f3: AP is in CSA process, reject auth Steps to Reproduce: Attempt to connect to a 5GHz Wi-Fi network (WPA2-Personal). Observe the connection failing to complete the handshake. Observe the CSA process error in the logs. Steps Already Taken (Troubleshooting): Added options iwlwifi disable_11ax=Y to /etc/modprobe.d/iwlwifi.conf. Tested with mobile hotspot (which seems to work, likely due to different frequency/channel handling). None of the above user-space workarounds resolved the issue, suggesting a regression in the kernel/firmware handling of mac80211 management frames. sudo lshw -C network *-network description: Wireless interface product: Meteor Lake PCH CNVi WiFi vendor: Intel Corporation physical id: 14.3 bus info: pci@0000:00:14.3 logical name: wlp0s20f3 version: 20 serial: 98:bd:80:b4:65:f4 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=7.0.0-29-generic firmware=89.123cf747.0 ma-b0-gf-a0-89.uc ip=10.208.104.226 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: iomemory:400-3ff irq:18 memory:401a704000-401a707fff lspci -nnk | grep -A3 Network 00:08.0 System peripheral [0880]: Intel Corporation Meteor Lake-P Gaussian & Neural-Network Accelerator [8086:7e4c] (rev 20) Subsystem: Lenovo Device [17aa:231e] 00:0a.0 Signal processing controller [1180]: Intel Corporation Meteor Lake-P Platform Monitoring Technology [8086:7d0d] (rev 01) Subsystem: Lenovo Device [17aa:231e] -- 00:14.3 Network controller [0280]: Intel Corporation Meteor Lake PCH CNVi WiFi [8086:7e40] (rev 20) Subsystem: Intel Corporation Device [8086:0090] Kernel driver in use: iwlwifi Kernel modules: iwlwifi 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: martin 4174 F.... pipewire martin 4196 F.... wireplumber /dev/snd/seq: martin 4174 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 7 00:13:12 2026 InstallationDate: Installed on 2025-12-28 (221 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: LENOVO 21KC005EMX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash preempt=full rcu_nocbs=all crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M preempt=full threadirqs rcu_nocbs=all 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-03-19 (140 days ago) dmi.bios.date: 04/07/2026 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: N3YET84W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KC005EMX 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.29 dmi.modalias: dmi:bvnLENOVO:bvrN3YET84W(1.49):bd04/07/2026:br1.49:efr1.29:svnLENOVO:pn21KC005EMX:pvrThinkPadX1CarbonGen12:rvnLENOVO:rn21KC005EMX:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KC_BU_Think_FM_ThinkPadX1CarbonGen12:pfaThinkPadX1CarbonGen12: dmi.product.family: ThinkPad X1 Carbon Gen 12 dmi.product.name: 21KC005EMX dmi.product.sku: LENOVO_MT_21KC_BU_Think_FM_ThinkPad X1 Carbon Gen 12 dmi.product.version: ThinkPad X1 Carbon Gen 12 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162998/+subscriptions
четверг
[Bug 2162904] Re: amdgpu panel self-refresh on dual-gpu laptops causes complete built-in panel freeze and severe system instability
** Summary changed: - amdgpu panel self-refresh on dual-gpu laptops causes partial system freeze + amdgpu panel self-refresh on dual-gpu laptops causes complete built-in panel freeze and severe system instability -- 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 complete built-in panel freeze and severe system instability 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 2162971] [NEW] Unset config parameter in kernel config file
Public bug reported: The config files shipped with the linux kernels 7.0.0.28+29 (that are the ones i tested) in Ubuntu 26.04 lack the definition of the config parameter CONFIG_SCHED_PROXY_EXEC. all other config values seam to be set. This results in the question about the value of the parameter while building the kernel image or modules. While running the build process in interactive mode, this do not result in problems because I can simply answer the question about the config parameter. However, running the build process in non-interactive mode, the question is still raised by the linux kernel build process but no one answers it and the build process is stuck. This especially occurs while building dkms modules. Testing this can easily be done by building the pivccu dkms modules. Instructions: https://github.com/alexreinert/debmatic/blob/master/docs/setup/otheros.md ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-modules-7.0.0-29-generic 7.0.0-29.29 [modified: boot/config-7.0.0-29-generic] ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: zfs AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-29-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: Error: [Errno 2] No such file or directory: 'fuser' 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: unknown Date: Thu Aug 6 17:17:11 2026 InstallationDate: Installed on 2026-08-01 (5 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: retsamarret 001-004-[F4-425_Plus] ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=a3583b7e-aa16-413b-954c-4ed33a310e20 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2025 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: MTWL0101.V07 dmi.board.asset.tag: Default string dmi.board.name: M-TWLN01 dmi.board.vendor: Default string dmi.board.version: Default string 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.:bvrMTWL0101.V07:bd11/08/2025:br5.26:svnretsamarret:pn001-004-[F4-425_Plus]:pvrDefaultstring:rvnDefaultstring:rnM-TWLN01:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:sku0A450A46JF01ADLN:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: 001-004-[F4-425_Plus] dmi.product.sku: 0A450A46JF01ADLN dmi.product.version: Default string dmi.sys.vendor: retsamarret ** 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/2162971 Title: Unset config parameter in kernel config file Status in linux package in Ubuntu: New Bug description: The config files shipped with the linux kernels 7.0.0.28+29 (that are the ones i tested) in Ubuntu 26.04 lack the definition of the config parameter CONFIG_SCHED_PROXY_EXEC. all other config values seam to be set. This results in the question about the value of the parameter while building the kernel image or modules. While running the build process in interactive mode, this do not result in problems because I can simply answer the question about the config parameter. However, running the build process in non- interactive mode, the question is still raised by the linux kernel build process but no one answers it and the build process is stuck. This especially occurs while building dkms modules. Testing this can easily be done by building the pivccu dkms modules. Instructions: https://github.com/alexreinert/debmatic/blob/master/docs/setup/otheros.md ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-modules-7.0.0-29-generic 7.0.0-29.29 [modified: boot/config-7.0.0-29-generic] ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: zfs AlsaVersion: Advanced Linux Sound Architecture Driver Version k7.0.0-29-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: Error: [Errno 2] No such file or directory: 'fuser' 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: unknown Date: Thu Aug 6 17:17:11 2026 InstallationDate: Installed on 2026-08-01 (5 days ago) InstallationMedia: Ubuntu-Server 26.04 "Resolute Raccoon" - Release amd64 (20260420.1) MachineType: retsamarret 001-004-[F4-425_Plus] ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=a3583b7e-aa16-413b-954c-4ed33a310e20 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2025 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: MTWL0101.V07 dmi.board.asset.tag: Default string dmi.board.name: M-TWLN01 dmi.board.vendor: Default string dmi.board.version: Default string 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.:bvrMTWL0101.V07:bd11/08/2025:br5.26:svnretsamarret:pn001-004-[F4-425_Plus]:pvrDefaultstring:rvnDefaultstring:rnM-TWLN01:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:sku0A450A46JF01ADLN:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: 001-004-[F4-425_Plus] dmi.product.sku: 0A450A46JF01ADLN dmi.product.version: Default string dmi.sys.vendor: retsamarret To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162971/+subscriptions
[Bug 2162959] Re: System hangs on shutdown/reboot ~50% of the time since kernel 7.0.0-28 (PCI/ASPM regression)
** Description changed: ### Summary System intermittently hangs during shutdown and reboot on kernel 7.0.0-28-generic and 7.0.0-29-generic. The issue does not occur on 7.0.0-27-generic. Adding `pcie_aspm=off` kernel boot parameter completely resolves the issue. ### Symptoms - ~50% of shutdown/reboot attempts result in a hang - Display turns off, but: USB peripherals remain powered (LEDs on keyboard/joystick), power LED on case stays lit, fans keep spinning - System never completes power-off; requires holding the physical power button - Affects both shutdown and reboot (not just power-off) - The issue is a race condition — not 100% reproducible but very frequent ### Reproduction 1. Boot with kernel 7.0.0-28-generic or 7.0.0-29-generic 2. Shut down or reboot the system 3. Approximately 50% of attempts will hang after journal stops (after `systemd-shutdown[1]: Sending SIGTERM to remaining processes...`) ### Bisect Results - **7.0.0-27-generic** (upstream v7.0.6): OK — no hangs - **7.0.0-28-generic** (upstream v7.0.12): BROKEN — hangs ~50% - **7.0.0-29-generic** (upstream v7.0.12 + CVE fixes): BROKEN — hangs ~50% ### Workaround - Adding `pcie_aspm=off` to kernel boot parameters completely eliminates - the issue. + Adding pcie_aspm=off to kernel boot parameters seems to reduce the + frequency of the issue but does not fully eliminate it ### Suspected Patches The regression was introduced in 7.0.0-28 which includes a large upstream stable bump (v7.0.6 → v7.0.12). Two ASPM-related patches are the most likely culprits: 1. **`PCI/ASPM: Fix link state exit during switch upstream function removal`** (from upstream v7.0.12 stable) - Directly relevant: the GPU is connected through a PCIe switch (Navi 10 XL Upstream/Downstream Port). This patch modifies behavior during switch upstream function removal, which occurs at shutdown/reboot. A race condition in link state exit could explain the intermittent hang. 2. **`SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of`** (LP: #2072679) - Ubuntu-specific patch originally targeting Tiger Lake idle states. On AMD X570, the BIOS may intentionally not expose ASPM control; forcing OS control could lead to incorrect link state transitions during teardown. The fact that the GPU sits behind a PCIe switch makes patch #1 especially suspicious — the patch title literally describes the scenario (switch upstream function removal). ### Hardware - **CPU:** AMD Ryzen 7 5800X3D - **Motherboard:** Gigabyte X570 AORUS ELITE - **BIOS:** F40 (2025-10-28), American Megatrends International - **GPU:** AMD Radeon RX 6700 XT (Navi 22) [1002:73df] — connected via PCIe switch (Navi 10 XL Upstream [1002:1478] / Downstream [1002:1479]) - **NIC:** Intel I211 Gigabit - **NVMe:** 2× Phison E18 PCIe4 ### PCIe Topology (relevant) ``` [00:03.1] AMD Starship/Matisse GPP Bridge └─[09:00.0] AMD/ATI Navi 10 XL Upstream Port of PCI Express Switch └─[0a:00.0] AMD/ATI Navi 10 XL Downstream Port of PCI Express Switch ├─[0b:00.0] AMD/ATI Navi 22 (RX 6700 XT) └─[0b:00.1] AMD/ATI Navi 21/23 HDMI/DP Audio Controller ``` ### System Info - **OS:** Ubuntu 26.04 LTS (Resolute) - **Kernel (broken):** 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC (7.0.12) - **Kernel (working):** 7.0.0-27-generic (7.0.6) - **ASPM policy:** `[default] performance powersave powersupersave` - **ACPI Power Buttons:** PWRB (PNP0C0C:00) + PWRF (LNXPWRBN:00) ### Journal (last entries before hang) ``` systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[414]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-journald[414]: Journal stopped ``` (System hangs after this point — no further progress, hard power-off required) ### Additional Notes - `amdgpu.runpm=0` was tested on 7.0.0-28 — did NOT help (rules out amdgpu runtime PM) - The `drm_fb_helper_damage_work hogged CPU for >10000us` warning appears in kernel logs, but this may be unrelated - The issue affects both shutdown and reboot equally, ruling out ACPI wakeup GPE issues ### Related - LP: #2072679 (SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of) - LP: #2156636 (Resolute update: v7.0.12 upstream stable release) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-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: tommyq 2222 F.... wireplumber /dev/snd/controlC1: tommyq 2222 F.... wireplumber /dev/snd/controlC0: tommyq 2222 F.... wireplumber /dev/snd/seq: tommyq 2198 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 6 15:37:11 2026 InstallationDate: Installed on 2022-11-11 (1364 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcEnviron: LANG=cs_CZ.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=6e49607c-2ecc-46c8-869f-dca543a37ec6 ro ipv6.disable_ipv6=1 pcie_aspm=off quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-28 (131 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F40 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string 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.:bvrF40:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Description changed: ### Summary System intermittently hangs during shutdown and reboot on kernel 7.0.0-28-generic and 7.0.0-29-generic. The issue does not occur on - 7.0.0-27-generic. Adding `pcie_aspm=off` kernel boot parameter - completely resolves the issue. + 7.0.0-27-generic. ### Symptoms - ~50% of shutdown/reboot attempts result in a hang - Display turns off, but: USB peripherals remain powered (LEDs on keyboard/joystick), power LED on case stays lit, fans keep spinning - System never completes power-off; requires holding the physical power button - Affects both shutdown and reboot (not just power-off) - The issue is a race condition — not 100% reproducible but very frequent ### Reproduction 1. Boot with kernel 7.0.0-28-generic or 7.0.0-29-generic 2. Shut down or reboot the system 3. Approximately 50% of attempts will hang after journal stops (after `systemd-shutdown[1]: Sending SIGTERM to remaining processes...`) ### Bisect Results - **7.0.0-27-generic** (upstream v7.0.6): OK — no hangs - **7.0.0-28-generic** (upstream v7.0.12): BROKEN — hangs ~50% - **7.0.0-29-generic** (upstream v7.0.12 + CVE fixes): BROKEN — hangs ~50% ### Workaround Adding pcie_aspm=off to kernel boot parameters seems to reduce the frequency of the issue but does not fully eliminate it ### Suspected Patches The regression was introduced in 7.0.0-28 which includes a large upstream stable bump (v7.0.6 → v7.0.12). Two ASPM-related patches are the most likely culprits: 1. **`PCI/ASPM: Fix link state exit during switch upstream function removal`** (from upstream v7.0.12 stable) - Directly relevant: the GPU is connected through a PCIe switch (Navi 10 XL Upstream/Downstream Port). This patch modifies behavior during switch upstream function removal, which occurs at shutdown/reboot. A race condition in link state exit could explain the intermittent hang. 2. **`SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of`** (LP: #2072679) - Ubuntu-specific patch originally targeting Tiger Lake idle states. On AMD X570, the BIOS may intentionally not expose ASPM control; forcing OS control could lead to incorrect link state transitions during teardown. The fact that the GPU sits behind a PCIe switch makes patch #1 especially suspicious — the patch title literally describes the scenario (switch upstream function removal). ### Hardware - **CPU:** AMD Ryzen 7 5800X3D - **Motherboard:** Gigabyte X570 AORUS ELITE - **BIOS:** F40 (2025-10-28), American Megatrends International - **GPU:** AMD Radeon RX 6700 XT (Navi 22) [1002:73df] — connected via PCIe switch (Navi 10 XL Upstream [1002:1478] / Downstream [1002:1479]) - **NIC:** Intel I211 Gigabit - **NVMe:** 2× Phison E18 PCIe4 ### PCIe Topology (relevant) ``` [00:03.1] AMD Starship/Matisse GPP Bridge └─[09:00.0] AMD/ATI Navi 10 XL Upstream Port of PCI Express Switch └─[0a:00.0] AMD/ATI Navi 10 XL Downstream Port of PCI Express Switch ├─[0b:00.0] AMD/ATI Navi 22 (RX 6700 XT) └─[0b:00.1] AMD/ATI Navi 21/23 HDMI/DP Audio Controller ``` ### System Info - **OS:** Ubuntu 26.04 LTS (Resolute) - **Kernel (broken):** 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC (7.0.12) - **Kernel (working):** 7.0.0-27-generic (7.0.6) - **ASPM policy:** `[default] performance powersave powersupersave` - **ACPI Power Buttons:** PWRB (PNP0C0C:00) + PWRF (LNXPWRBN:00) ### Journal (last entries before hang) ``` systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[414]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-journald[414]: Journal stopped ``` (System hangs after this point — no further progress, hard power-off required) ### Additional Notes - `amdgpu.runpm=0` was tested on 7.0.0-28 — did NOT help (rules out amdgpu runtime PM) - The `drm_fb_helper_damage_work hogged CPU for >10000us` warning appears in kernel logs, but this may be unrelated - The issue affects both shutdown and reboot equally, ruling out ACPI wakeup GPE issues ### Related - LP: #2072679 (SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of) - LP: #2156636 (Resolute update: v7.0.12 upstream stable release) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-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: tommyq 2222 F.... wireplumber /dev/snd/controlC1: tommyq 2222 F.... wireplumber /dev/snd/controlC0: tommyq 2222 F.... wireplumber /dev/snd/seq: tommyq 2198 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 6 15:37:11 2026 InstallationDate: Installed on 2022-11-11 (1364 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcEnviron: LANG=cs_CZ.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=6e49607c-2ecc-46c8-869f-dca543a37ec6 ro ipv6.disable_ipv6=1 pcie_aspm=off quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-28 (131 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F40 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string 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.:bvrF40:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162959 Title: System hangs on shutdown/reboot ~50% of the time since kernel 7.0.0-28 (PCI/ASPM regression) Status in linux package in Ubuntu: New Bug description: ### Summary System intermittently hangs during shutdown and reboot on kernel 7.0.0-28-generic and 7.0.0-29-generic. The issue does not occur on 7.0.0-27-generic. ### Symptoms - ~50% of shutdown/reboot attempts result in a hang - Display turns off, but: USB peripherals remain powered (LEDs on keyboard/joystick), power LED on case stays lit, fans keep spinning - System never completes power-off; requires holding the physical power button - Affects both shutdown and reboot (not just power-off) - The issue is a race condition — not 100% reproducible but very frequent ### Reproduction 1. Boot with kernel 7.0.0-28-generic or 7.0.0-29-generic 2. Shut down or reboot the system 3. Approximately 50% of attempts will hang after journal stops (after `systemd-shutdown[1]: Sending SIGTERM to remaining processes...`) ### Bisect Results - **7.0.0-27-generic** (upstream v7.0.6): OK — no hangs - **7.0.0-28-generic** (upstream v7.0.12): BROKEN — hangs ~50% - **7.0.0-29-generic** (upstream v7.0.12 + CVE fixes): BROKEN — hangs ~50% ### Workaround Adding pcie_aspm=off to kernel boot parameters seems to reduce the frequency of the issue but does not fully eliminate it ### Suspected Patches The regression was introduced in 7.0.0-28 which includes a large upstream stable bump (v7.0.6 → v7.0.12). Two ASPM-related patches are the most likely culprits: 1. **`PCI/ASPM: Fix link state exit during switch upstream function removal`** (from upstream v7.0.12 stable) - Directly relevant: the GPU is connected through a PCIe switch (Navi 10 XL Upstream/Downstream Port). This patch modifies behavior during switch upstream function removal, which occurs at shutdown/reboot. A race condition in link state exit could explain the intermittent hang. 2. **`SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of`** (LP: #2072679) - Ubuntu-specific patch originally targeting Tiger Lake idle states. On AMD X570, the BIOS may intentionally not expose ASPM control; forcing OS control could lead to incorrect link state transitions during teardown. The fact that the GPU sits behind a PCIe switch makes patch #1 especially suspicious — the patch title literally describes the scenario (switch upstream function removal). ### Hardware - **CPU:** AMD Ryzen 7 5800X3D - **Motherboard:** Gigabyte X570 AORUS ELITE - **BIOS:** F40 (2025-10-28), American Megatrends International - **GPU:** AMD Radeon RX 6700 XT (Navi 22) [1002:73df] — connected via PCIe switch (Navi 10 XL Upstream [1002:1478] / Downstream [1002:1479]) - **NIC:** Intel I211 Gigabit - **NVMe:** 2× Phison E18 PCIe4 ### PCIe Topology (relevant) ``` [00:03.1] AMD Starship/Matisse GPP Bridge └─[09:00.0] AMD/ATI Navi 10 XL Upstream Port of PCI Express Switch └─[0a:00.0] AMD/ATI Navi 10 XL Downstream Port of PCI Express Switch ├─[0b:00.0] AMD/ATI Navi 22 (RX 6700 XT) └─[0b:00.1] AMD/ATI Navi 21/23 HDMI/DP Audio Controller ``` ### System Info - **OS:** Ubuntu 26.04 LTS (Resolute) - **Kernel (broken):** 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC (7.0.12) - **Kernel (working):** 7.0.0-27-generic (7.0.6) - **ASPM policy:** `[default] performance powersave powersupersave` - **ACPI Power Buttons:** PWRB (PNP0C0C:00) + PWRF (LNXPWRBN:00) ### Journal (last entries before hang) ``` systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[414]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-journald[414]: Journal stopped ``` (System hangs after this point — no further progress, hard power-off required) ### Additional Notes - `amdgpu.runpm=0` was tested on 7.0.0-28 — did NOT help (rules out amdgpu runtime PM) - The `drm_fb_helper_damage_work hogged CPU for >10000us` warning appears in kernel logs, but this may be unrelated - The issue affects both shutdown and reboot equally, ruling out ACPI wakeup GPE issues ### Related - LP: #2072679 (SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of) - LP: #2156636 (Resolute update: v7.0.12 upstream stable release) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-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: tommyq 2222 F.... wireplumber /dev/snd/controlC1: tommyq 2222 F.... wireplumber /dev/snd/controlC0: tommyq 2222 F.... wireplumber /dev/snd/seq: tommyq 2198 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 6 15:37:11 2026 InstallationDate: Installed on 2022-11-11 (1364 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcEnviron: LANG=cs_CZ.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=6e49607c-2ecc-46c8-869f-dca543a37ec6 ro ipv6.disable_ipv6=1 pcie_aspm=off quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-28 (131 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F40 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string 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.:bvrF40:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162959/+subscriptions
[Bug 2162967] [NEW] Getac V110G3 Synaptics touchpad fails after S3 resume unless i8042 nomux=1
Public bug reported: # Getac V110G3 Synaptics touchpad fails after S3 resume unless `i8042.nomux=1` On a GETAC V110G3, the built-in Synaptics touchpad stops working after resuming from ACPI S3/deep suspend. ## System - Ubuntu 26.04 LTS - Kernel: 7.0.0-29-generic #29-Ubuntu - System vendor: GETAC - Product: V110G3 - BIOS: R1.25.070520, dated 2022-03-31 - Touchpad: Synaptics firmware 8.1, board ID 2439, firmware ID 1215751 - PNP IDs: SYN0c2a SYN0c00 PNP0f13 ## Steps To Reproduce 1. Boot normally without `i8042.nomux=1`. 2. Confirm the touchpad works. 3. Suspend using the deep/S3 sleep mode. 4. Resume the computer. 5. Attempt to use the touchpad. ## Expected Result The touchpad resumes and works normally. ## Actual Result The touchpad does not produce input after resume. Rebooting is required to restore it. Reloading `psmouse`, reloading `rmi_smbus`, and rebinding the i8042 controller do not recover the device. With the default PS/2 transport, the touchpad disappears from the input device registry after resume. Forcing the recommended SMBus transport with `psmouse.synaptics_intertouch=1` does not fix S3 resume. The kernel reports: ```text psmouse serio2: Failed to deactivate mouse on isa0060/serio2: -5 rmi4_smbus 4-002c: failed to get SMBus version number! rmi4_physical rmi4-00: rmi_driver_reset_handler: Failed to read current IRQ mask. rmi4_f01 rmi4-00.fn01: Failed to restore normal operation: -6. rmi4_f01 rmi4-00.fn01: Resume failed with code -6. rmi4_smbus 4-002c: Failed to resume device: -6 ``` The controller is normally detected as: ```text i8042: Detected active multiplexing controller, rev 1.1 serio: i8042 AUX0 port at 0x60,0x64 irq 12 serio: i8042 AUX1 port at 0x60,0x64 irq 12 serio: i8042 AUX2 port at 0x60,0x64 irq 12 serio: i8042 AUX3 port at 0x60,0x64 irq 12 ``` ## Tested Workarounds - `psmouse.synaptics_intertouch=1` alone: fails - `i8042.forcenorestore=1`: fails - `s2idle` instead of S3: works, but does not provide normal S3 power behavior - `i8042.nomux=1` with `psmouse.synaptics_intertouch=1`: works with genuine S3/deep suspend With `i8042.nomux=1`, the touchpad moves from multiplexed `serio2` to the standard `serio1` AUX port and resumes successfully after S3: ```text serio: i8042 AUX port at 0x60,0x64 irq 12 input: Synaptics TM2439-001 ``` Windows can suspend this same computer to S3 and resume the touchpad correctly. This system likely needs a `SERIO_QUIRK_NOMUX` DMI entry for: ```text DMI_SYS_VENDOR = "GETAC" DMI_PRODUCT_NAME = "V110G3" ``` 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: gela 3412 F.... wireplumber /dev/snd/seq: gela 3403 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 08:33:35 2026 InstallationDate: Installed on 2026-08-06 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: GETAC V110G3 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash psmouse.synaptics_intertouch=1 i8042.nomux=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2022 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: R1.25.070520 dmi.board.name: V110G3 dmi.board.vendor: GETAC dmi.chassis.type: 10 dmi.chassis.vendor: GETAC dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnINSYDECorp.:bvrR1.25.070520:bd03/31/2022:br1.25:efr1.5:svnGETAC:pnV110G3:pvr:rvnGETAC:rnV110G3:rvr:cvnGETAC:ct10:cvr:sku000000:pfaV110: dmi.product.family: V110 dmi.product.name: V110G3 dmi.product.sku: 000000 dmi.sys.vendor: GETAC ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "getac-v110g3-s3-touchpad-bug.md" https://bugs.launchpad.net/bugs/2162967/+attachment/5990023/+files/getac-v110g3-s3-touchpad-bug.md -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162967 Title: Getac V110G3 Synaptics touchpad fails after S3 resume unless i8042 nomux=1 Status in linux package in Ubuntu: New Bug description: # Getac V110G3 Synaptics touchpad fails after S3 resume unless `i8042.nomux=1` On a GETAC V110G3, the built-in Synaptics touchpad stops working after resuming from ACPI S3/deep suspend. ## System - Ubuntu 26.04 LTS - Kernel: 7.0.0-29-generic #29-Ubuntu - System vendor: GETAC - Product: V110G3 - BIOS: R1.25.070520, dated 2022-03-31 - Touchpad: Synaptics firmware 8.1, board ID 2439, firmware ID 1215751 - PNP IDs: SYN0c2a SYN0c00 PNP0f13 ## Steps To Reproduce 1. Boot normally without `i8042.nomux=1`. 2. Confirm the touchpad works. 3. Suspend using the deep/S3 sleep mode. 4. Resume the computer. 5. Attempt to use the touchpad. ## Expected Result The touchpad resumes and works normally. ## Actual Result The touchpad does not produce input after resume. Rebooting is required to restore it. Reloading `psmouse`, reloading `rmi_smbus`, and rebinding the i8042 controller do not recover the device. With the default PS/2 transport, the touchpad disappears from the input device registry after resume. Forcing the recommended SMBus transport with `psmouse.synaptics_intertouch=1` does not fix S3 resume. The kernel reports: ```text psmouse serio2: Failed to deactivate mouse on isa0060/serio2: -5 rmi4_smbus 4-002c: failed to get SMBus version number! rmi4_physical rmi4-00: rmi_driver_reset_handler: Failed to read current IRQ mask. rmi4_f01 rmi4-00.fn01: Failed to restore normal operation: -6. rmi4_f01 rmi4-00.fn01: Resume failed with code -6. rmi4_smbus 4-002c: Failed to resume device: -6 ``` The controller is normally detected as: ```text i8042: Detected active multiplexing controller, rev 1.1 serio: i8042 AUX0 port at 0x60,0x64 irq 12 serio: i8042 AUX1 port at 0x60,0x64 irq 12 serio: i8042 AUX2 port at 0x60,0x64 irq 12 serio: i8042 AUX3 port at 0x60,0x64 irq 12 ``` ## Tested Workarounds - `psmouse.synaptics_intertouch=1` alone: fails - `i8042.forcenorestore=1`: fails - `s2idle` instead of S3: works, but does not provide normal S3 power behavior - `i8042.nomux=1` with `psmouse.synaptics_intertouch=1`: works with genuine S3/deep suspend With `i8042.nomux=1`, the touchpad moves from multiplexed `serio2` to the standard `serio1` AUX port and resumes successfully after S3: ```text serio: i8042 AUX port at 0x60,0x64 irq 12 input: Synaptics TM2439-001 ``` Windows can suspend this same computer to S3 and resume the touchpad correctly. This system likely needs a `SERIO_QUIRK_NOMUX` DMI entry for: ```text DMI_SYS_VENDOR = "GETAC" DMI_PRODUCT_NAME = "V110G3" ``` 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: gela 3412 F.... wireplumber /dev/snd/seq: gela 3403 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 08:33:35 2026 InstallationDate: Installed on 2026-08-06 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: GETAC V110G3 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash psmouse.synaptics_intertouch=1 i8042.nomux=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2022 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: R1.25.070520 dmi.board.name: V110G3 dmi.board.vendor: GETAC dmi.chassis.type: 10 dmi.chassis.vendor: GETAC dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnINSYDECorp.:bvrR1.25.070520:bd03/31/2022:br1.25:efr1.5:svnGETAC:pnV110G3:pvr:rvnGETAC:rnV110G3:rvr:cvnGETAC:ct10:cvr:sku000000:pfaV110: dmi.product.family: V110 dmi.product.name: V110G3 dmi.product.sku: 000000 dmi.sys.vendor: GETAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162967/+subscriptions
[Bug 2162904] Re: amdgpu panel self-refresh on dual-gpu laptops causes partial system freeze
I prepared my patch and sent it to the kteam mailing list ("[SRU][R][PATCH 0/1] UBUNTU: SAUCE: drm/amdgpu: Do not enter PSR if multiple displays are active"), as well as upstream ("[PATCH 0/1] drm/amdgpu: Do not enter PSR if multiple displays are active") -- 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 2162945] Re: [UBUNTU 22.04] Non-root users are prompted to reset their password after PASS_MAX_DAYS expiry, despite having Public Key Authentication enabled.
Hello Dineshkanna, yes, this is the behavior on Ubuntu (and on many other Linux distributions): an expired password will block or interrupt an SSH session even if the user successfully authenticates using an SSH Public Key. Thi sis because PAM is used to handle system security and it's done in two phases, when logging in via ssh: - auth phase: sshd validates the cryptographic public key; this succeeds without checking your password - account phase: sshd hands the session over to PAM to verify account health via /etc/pam.d/sshd The PAM module pam_unix.so checks the user's password aging attributes in /etc/shadow (governed by PASS_MAX_DAYS). If the password is older than allowed, PAM returns an account expired error. OpenSSH then forces a password change or rejects the connection. There are two solutions: 1) <recommended> If specific non-root users or functional user accounts rely strictly on SSH keys, disable their password aging entirely and disable expiration for that specific user: sudo chage -M -1 <username> (verify: sudo chage -l <username> ) 2) Or configure PAM to bypass expiration for ssh generally (system-wide). It can be done by opening /etc/pam.d/sshd and commenting out line: # @include common-account and by explicitly adding the pam_unix.so module with the no_pass_expiry flag below it: account requisite pam_unix.so no_pass_expiry ** Package changed: linux (Ubuntu) => openssh (Ubuntu) ** Changed in: openssh (Ubuntu) Importance: Undecided => Medium ** Changed in: openssh (Ubuntu) Status: New => Opinion ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Opinion ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162945 Title: [UBUNTU 22.04] Non-root users are prompted to reset their password after PASS_MAX_DAYS expiry, despite having Public Key Authentication enabled. Status in Ubuntu on IBM z Systems: Opinion Status in openssh package in Ubuntu: Opinion Bug description: ---Problem Description--- Even when Public Key Authentication is configured and functioning correctly, non-root users are being forced to reset their passwords once the maximum password age (PASS_MAX_DAYS) is exceeded. This behavior contradicts the expected functionality, where password expiry should not impact users relying solely on key-based authentication. ---Steps to Reproduce--- 1. Create a Ubuntu 22.04 s390x zvsi. 2. Create a non root user. 3. Add the public key to the user home directory. 4. After the specified PASS_MAX_DAYS in /etc/login.defs try to login as the user. 5. The user is promted to enter the current password the reset the password. ---Note--- We are changing the PASS_MAX_DAYS to 90 days in the image for the best practices. We are enabling the PubkeyAuthentication We are disabling the PasswordAuthentication Contact Information = Dineshkanna / dineshkanna.m@ibm.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2162945/+subscriptions
[Bug 2162959] [NEW] System hangs on shutdown/reboot ~50% of the time since kernel 7.0.0-28 (PCI/ASPM regression)
Public bug reported: ### Summary System intermittently hangs during shutdown and reboot on kernel 7.0.0-28-generic and 7.0.0-29-generic. The issue does not occur on 7.0.0-27-generic. Adding `pcie_aspm=off` kernel boot parameter completely resolves the issue. ### Symptoms - ~50% of shutdown/reboot attempts result in a hang - Display turns off, but: USB peripherals remain powered (LEDs on keyboard/joystick), power LED on case stays lit, fans keep spinning - System never completes power-off; requires holding the physical power button - Affects both shutdown and reboot (not just power-off) - The issue is a race condition — not 100% reproducible but very frequent ### Reproduction 1. Boot with kernel 7.0.0-28-generic or 7.0.0-29-generic 2. Shut down or reboot the system 3. Approximately 50% of attempts will hang after journal stops (after `systemd-shutdown[1]: Sending SIGTERM to remaining processes...`) ### Bisect Results - **7.0.0-27-generic** (upstream v7.0.6): OK — no hangs - **7.0.0-28-generic** (upstream v7.0.12): BROKEN — hangs ~50% - **7.0.0-29-generic** (upstream v7.0.12 + CVE fixes): BROKEN — hangs ~50% ### Workaround Adding `pcie_aspm=off` to kernel boot parameters completely eliminates the issue. ### Suspected Patches The regression was introduced in 7.0.0-28 which includes a large upstream stable bump (v7.0.6 → v7.0.12). Two ASPM-related patches are the most likely culprits: 1. **`PCI/ASPM: Fix link state exit during switch upstream function removal`** (from upstream v7.0.12 stable) - Directly relevant: the GPU is connected through a PCIe switch (Navi 10 XL Upstream/Downstream Port). This patch modifies behavior during switch upstream function removal, which occurs at shutdown/reboot. A race condition in link state exit could explain the intermittent hang. 2. **`SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of`** (LP: #2072679) - Ubuntu-specific patch originally targeting Tiger Lake idle states. On AMD X570, the BIOS may intentionally not expose ASPM control; forcing OS control could lead to incorrect link state transitions during teardown. The fact that the GPU sits behind a PCIe switch makes patch #1 especially suspicious — the patch title literally describes the scenario (switch upstream function removal). ### Hardware - **CPU:** AMD Ryzen 7 5800X3D - **Motherboard:** Gigabyte X570 AORUS ELITE - **BIOS:** F40 (2025-10-28), American Megatrends International - **GPU:** AMD Radeon RX 6700 XT (Navi 22) [1002:73df] — connected via PCIe switch (Navi 10 XL Upstream [1002:1478] / Downstream [1002:1479]) - **NIC:** Intel I211 Gigabit - **NVMe:** 2× Phison E18 PCIe4 ### PCIe Topology (relevant) ``` [00:03.1] AMD Starship/Matisse GPP Bridge └─[09:00.0] AMD/ATI Navi 10 XL Upstream Port of PCI Express Switch └─[0a:00.0] AMD/ATI Navi 10 XL Downstream Port of PCI Express Switch ├─[0b:00.0] AMD/ATI Navi 22 (RX 6700 XT) └─[0b:00.1] AMD/ATI Navi 21/23 HDMI/DP Audio Controller ``` ### System Info - **OS:** Ubuntu 26.04 LTS (Resolute) - **Kernel (broken):** 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC (7.0.12) - **Kernel (working):** 7.0.0-27-generic (7.0.6) - **ASPM policy:** `[default] performance powersave powersupersave` - **ACPI Power Buttons:** PWRB (PNP0C0C:00) + PWRF (LNXPWRBN:00) ### Journal (last entries before hang) ``` systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[414]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-journald[414]: Journal stopped ``` (System hangs after this point — no further progress, hard power-off required) ### Additional Notes - `amdgpu.runpm=0` was tested on 7.0.0-28 — did NOT help (rules out amdgpu runtime PM) - The `drm_fb_helper_damage_work hogged CPU for >10000us` warning appears in kernel logs, but this may be unrelated - The issue affects both shutdown and reboot equally, ruling out ACPI wakeup GPE issues ### Related - LP: #2072679 (SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of) - LP: #2156636 (Resolute update: v7.0.12 upstream stable release) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-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: tommyq 2222 F.... wireplumber /dev/snd/controlC1: tommyq 2222 F.... wireplumber /dev/snd/controlC0: tommyq 2222 F.... wireplumber /dev/snd/seq: tommyq 2198 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 6 15:37:11 2026 InstallationDate: Installed on 2022-11-11 (1364 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcEnviron: LANG=cs_CZ.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=6e49607c-2ecc-46c8-869f-dca543a37ec6 ro ipv6.disable_ipv6=1 pcie_aspm=off quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-28 (131 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F40 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string 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.:bvrF40:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Description changed: ### Summary System intermittently hangs during shutdown and reboot on kernel 7.0.0-28-generic and 7.0.0-29-generic. The issue does not occur on 7.0.0-27-generic. Adding `pcie_aspm=off` kernel boot parameter completely resolves the issue. ### Symptoms - ~50% of shutdown/reboot attempts result in a hang - Display turns off, but: USB peripherals remain powered (LEDs on keyboard/joystick), power LED on case stays lit, fans keep spinning - System never completes power-off; requires holding the physical power button - Affects both shutdown and reboot (not just power-off) - The issue is a race condition — not 100% reproducible but very frequent ### Reproduction 1. Boot with kernel 7.0.0-28-generic or 7.0.0-29-generic 2. Shut down or reboot the system 3. Approximately 50% of attempts will hang after journal stops (after `systemd-shutdown[1]: Sending SIGTERM to remaining processes...`) ### Bisect Results - **7.0.0-27-generic** (upstream v7.0.6): OK — no hangs - **7.0.0-28-generic** (upstream v7.0.12): BROKEN — hangs ~50% - **7.0.0-29-generic** (upstream v7.0.12 + CVE fixes): BROKEN — hangs ~50% ### Workaround Adding `pcie_aspm=off` to kernel boot parameters completely eliminates the issue. ### Suspected Patches The regression was introduced in 7.0.0-28 which includes a large upstream stable bump (v7.0.6 → v7.0.12). Two ASPM-related patches are the most likely culprits: 1. **`PCI/ASPM: Fix link state exit during switch upstream function removal`** (from upstream v7.0.12 stable) - - Directly relevant: the GPU is connected through a PCIe switch (Navi 10 XL Upstream/Downstream Port). This patch modifies behavior during switch upstream function removal, which occurs at shutdown/reboot. A race condition in link state exit could explain the intermittent hang. + - Directly relevant: the GPU is connected through a PCIe switch (Navi 10 XL Upstream/Downstream Port). This patch modifies behavior during switch upstream function removal, which occurs at shutdown/reboot. A race condition in link state exit could explain the intermittent hang. 2. **`SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of`** (LP: #2072679) - - Ubuntu-specific patch originally targeting Tiger Lake idle states. On AMD X570, the BIOS may intentionally not expose ASPM control; forcing OS control could lead to incorrect link state transitions during teardown. + - Ubuntu-specific patch originally targeting Tiger Lake idle states. On AMD X570, the BIOS may intentionally not expose ASPM control; forcing OS control could lead to incorrect link state transitions during teardown. The fact that the GPU sits behind a PCIe switch makes patch #1 especially suspicious — the patch title literally describes the scenario (switch upstream function removal). ### Hardware - **CPU:** AMD Ryzen 7 5800X3D - **Motherboard:** Gigabyte X570 AORUS ELITE - **BIOS:** F40 (2025-10-28), American Megatrends International - **GPU:** AMD Radeon RX 6700 XT (Navi 22) [1002:73df] — connected via PCIe switch (Navi 10 XL Upstream [1002:1478] / Downstream [1002:1479]) - **NIC:** Intel I211 Gigabit - **NVMe:** 2× Phison E18 PCIe4 ### PCIe Topology (relevant) ``` [00:03.1] AMD Starship/Matisse GPP Bridge - └─[09:00.0] AMD/ATI Navi 10 XL Upstream Port of PCI Express Switch - └─[0a:00.0] AMD/ATI Navi 10 XL Downstream Port of PCI Express Switch - ├─[0b:00.0] AMD/ATI Navi 22 (RX 6700 XT) - └─[0b:00.1] AMD/ATI Navi 21/23 HDMI/DP Audio Controller + └─[09:00.0] AMD/ATI Navi 10 XL Upstream Port of PCI Express Switch + └─[0a:00.0] AMD/ATI Navi 10 XL Downstream Port of PCI Express Switch + ├─[0b:00.0] AMD/ATI Navi 22 (RX 6700 XT) + └─[0b:00.1] AMD/ATI Navi 21/23 HDMI/DP Audio Controller ``` ### System Info - **OS:** Ubuntu 26.04 LTS (Resolute) - **Kernel (broken):** 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC (7.0.12) - **Kernel (working):** 7.0.0-27-generic (7.0.6) - **ASPM policy:** `[default] performance powersave powersupersave` - **ACPI Power Buttons:** PWRB (PNP0C0C:00) + PWRF (LNXPWRBN:00) ### Journal (last entries before hang) ``` systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[414]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-journald[414]: Journal stopped ``` (System hangs after this point — no further progress, hard power-off required) ### Additional Notes - - `amdgpu.runpm=0` was NOT tested yet (pcie_aspm=off was sufficient) + - `amdgpu.runpm=0` was tested on 7.0.0-28 — did NOT help (rules out amdgpu runtime PM) - The `drm_fb_helper_damage_work hogged CPU for >10000us` warning appears in kernel logs, but this may be unrelated - The issue affects both shutdown and reboot equally, ruling out ACPI wakeup GPE issues ### Related - LP: #2072679 (SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of) - LP: #2156636 (Resolute update: v7.0.12 upstream stable release) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-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: tommyq 2222 F.... wireplumber - /dev/snd/controlC1: tommyq 2222 F.... wireplumber - /dev/snd/controlC0: tommyq 2222 F.... wireplumber - /dev/snd/seq: tommyq 2198 F.... pipewire + USER PID ACCESS COMMAND + /dev/snd/controlC2: tommyq 2222 F.... wireplumber + /dev/snd/controlC1: tommyq 2222 F.... wireplumber + /dev/snd/controlC0: tommyq 2222 F.... wireplumber + /dev/snd/seq: tommyq 2198 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 6 15:37:11 2026 InstallationDate: Installed on 2022-11-11 (1364 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcEnviron: - LANG=cs_CZ.UTF-8 - LANGUAGE= - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR=<set> + LANG=cs_CZ.UTF-8 + LANGUAGE= + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=6e49607c-2ecc-46c8-869f-dca543a37ec6 ro ipv6.disable_ipv6=1 pcie_aspm=off quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: - 0: hci0: Bluetooth - Soft blocked: yes - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: yes + Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-28 (131 days ago) acpidump: - Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized - - This incident has been reported. + Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized + + This incident has been reported. dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F40 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string 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.:bvrF40:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162959 Title: System hangs on shutdown/reboot ~50% of the time since kernel 7.0.0-28 (PCI/ASPM regression) Status in linux package in Ubuntu: New Bug description: ### Summary System intermittently hangs during shutdown and reboot on kernel 7.0.0-28-generic and 7.0.0-29-generic. The issue does not occur on 7.0.0-27-generic. Adding `pcie_aspm=off` kernel boot parameter completely resolves the issue. ### Symptoms - ~50% of shutdown/reboot attempts result in a hang - Display turns off, but: USB peripherals remain powered (LEDs on keyboard/joystick), power LED on case stays lit, fans keep spinning - System never completes power-off; requires holding the physical power button - Affects both shutdown and reboot (not just power-off) - The issue is a race condition — not 100% reproducible but very frequent ### Reproduction 1. Boot with kernel 7.0.0-28-generic or 7.0.0-29-generic 2. Shut down or reboot the system 3. Approximately 50% of attempts will hang after journal stops (after `systemd-shutdown[1]: Sending SIGTERM to remaining processes...`) ### Bisect Results - **7.0.0-27-generic** (upstream v7.0.6): OK — no hangs - **7.0.0-28-generic** (upstream v7.0.12): BROKEN — hangs ~50% - **7.0.0-29-generic** (upstream v7.0.12 + CVE fixes): BROKEN — hangs ~50% ### Workaround Adding `pcie_aspm=off` to kernel boot parameters completely eliminates the issue. ### Suspected Patches The regression was introduced in 7.0.0-28 which includes a large upstream stable bump (v7.0.6 → v7.0.12). Two ASPM-related patches are the most likely culprits: 1. **`PCI/ASPM: Fix link state exit during switch upstream function removal`** (from upstream v7.0.12 stable) - Directly relevant: the GPU is connected through a PCIe switch (Navi 10 XL Upstream/Downstream Port). This patch modifies behavior during switch upstream function removal, which occurs at shutdown/reboot. A race condition in link state exit could explain the intermittent hang. 2. **`SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of`** (LP: #2072679) - Ubuntu-specific patch originally targeting Tiger Lake idle states. On AMD X570, the BIOS may intentionally not expose ASPM control; forcing OS control could lead to incorrect link state transitions during teardown. The fact that the GPU sits behind a PCIe switch makes patch #1 especially suspicious — the patch title literally describes the scenario (switch upstream function removal). ### Hardware - **CPU:** AMD Ryzen 7 5800X3D - **Motherboard:** Gigabyte X570 AORUS ELITE - **BIOS:** F40 (2025-10-28), American Megatrends International - **GPU:** AMD Radeon RX 6700 XT (Navi 22) [1002:73df] — connected via PCIe switch (Navi 10 XL Upstream [1002:1478] / Downstream [1002:1479]) - **NIC:** Intel I211 Gigabit - **NVMe:** 2× Phison E18 PCIe4 ### PCIe Topology (relevant) ``` [00:03.1] AMD Starship/Matisse GPP Bridge └─[09:00.0] AMD/ATI Navi 10 XL Upstream Port of PCI Express Switch └─[0a:00.0] AMD/ATI Navi 10 XL Downstream Port of PCI Express Switch ├─[0b:00.0] AMD/ATI Navi 22 (RX 6700 XT) └─[0b:00.1] AMD/ATI Navi 21/23 HDMI/DP Audio Controller ``` ### System Info - **OS:** Ubuntu 26.04 LTS (Resolute) - **Kernel (broken):** 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC (7.0.12) - **Kernel (working):** 7.0.0-27-generic (7.0.6) - **ASPM policy:** `[default] performance powersave powersupersave` - **ACPI Power Buttons:** PWRB (PNP0C0C:00) + PWRF (LNXPWRBN:00) ### Journal (last entries before hang) ``` systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[414]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-journald[414]: Journal stopped ``` (System hangs after this point — no further progress, hard power-off required) ### Additional Notes - `amdgpu.runpm=0` was tested on 7.0.0-28 — did NOT help (rules out amdgpu runtime PM) - The `drm_fb_helper_damage_work hogged CPU for >10000us` warning appears in kernel logs, but this may be unrelated - The issue affects both shutdown and reboot equally, ruling out ACPI wakeup GPE issues ### Related - LP: #2072679 (SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of) - LP: #2156636 (Resolute update: v7.0.12 upstream stable release) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-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: tommyq 2222 F.... wireplumber /dev/snd/controlC1: tommyq 2222 F.... wireplumber /dev/snd/controlC0: tommyq 2222 F.... wireplumber /dev/snd/seq: tommyq 2198 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 6 15:37:11 2026 InstallationDate: Installed on 2022-11-11 (1364 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcEnviron: LANG=cs_CZ.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=6e49607c-2ecc-46c8-869f-dca543a37ec6 ro ipv6.disable_ipv6=1 pcie_aspm=off quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-28 (131 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F40 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string 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.:bvrF40:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162959/+subscriptions
[Bug 2162952] [NEW] i915: eDP panel dead after S3 (deep) resume on 7.0.0-28, works on 6.17.0-35
Public bug reported: # i915: eDP panel dead after S3 (deep) resume on 7.0.0-28, works on 6.17.0-35 ## Summary On resume from S3 (`mem_sleep=deep`), the internal eDP panel is permanently dark. It is **unpowered, not merely unlit**. No userspace action recovers it — only a reboot. Regression: **6.17.0-35-generic works, 7.0.0-28-generic fails.** The bug is **specific to the S3/deep path** — `s2idle` on the same kernel resumes correctly. ## Test matrix | Kernel | mem_sleep | Panel on resume | |---|---|---| | 6.17.0-35-generic | deep (S3) | OK — 39 suspend cycles over 25 days, no failures | | 7.0.0-28-generic | deep (S3) | **FAIL** — dark, reboot-only recovery | | 7.0.0-28-generic | s2idle | OK — verified over a 32.5 min suspend | ## Key diagnostic detail After the failed resume, every software indicator reports a healthy display. A dead panel is indistinguishable from a live one via sysfs/xrandr: - `/sys/class/drm/card1-eDP-1/status` = `connected`, `enabled` = `enabled` - `xrandr` reports the output enabled, `link-status: Good`, `dpms On` - X is genuinely compositing live content into the panel's region (confirmed by sampling root-window pixels — real window content present) - `intel_backlight`: `actual_brightness` = 1023/1023, `bl_power` = 0; writes are accepted and read back correctly, but a full 0 -> max PWM sweep produces **zero** physical response - A full modeset (`xrandr --output eDP-1 --off` then `--mode ... `) does **not** relight it - **No eDP link-training errors or drm errors in the kernel log** — the resume path logs clean (GuC/HuC reload, mei_hdcp/mei_pxp rebind, nothing else) This points at panel power-sequencing (PPS) state not being restored on the S3 resume path, rather than a link, mode, or backlight-value problem. ## Hardware - Chassis: Elimina Pro V 16 (Clevo/Kapok barebone, subsystem 2564) - iGPU: Intel i915 `0000:00:02.0`, alderlake_p/raptorlake_p, device ID a7a8, integrated display version 13.00 stepping E0 - dGPU: NVIDIA `0000:01:00.0`, driver 595, hybrid/PRIME (external via HDMI-1-0 reverse-prime) - Panel: AUO B160QANAA.H, 2560x1600@165Hz, eDP-1, vrr_capable - Firmware default sleep state: `deep` (nothing forcing it on the kernel cmdline) - Ubuntu 24.04, GNOME on X11, systemd 255 ## Reproducer 1. Boot 7.0.0-28-generic with default `mem_sleep=deep` 2. Confirm the internal panel is lit 3. `systemctl suspend` 4. Wake via power button Internal panel stays dark. External displays are unaffected and continue working. ## Workaround Boot 6.17.0-35-generic. `mem_sleep_default=s2idle` also avoids the bug, but is **not usable on this platform**: S0ix never engages (`/sys/kernel/debug/pmc_core/slp_s0_residency_usec` stayed at **0** across a 32.5-minute suspend), giving 4.67 W average draw vs ~0.3-0.8 W for working S3 (9.2 %/hour battery drain). That may be a separate platform issue worth its own report. Sysinfo: === version === uname -a: Linux aidan-dunphy-Elimina-Pro-V-16 7.0.0-28-generic #28~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 15:50:57 UTC 2 x86_64 x86_64 x86_64 GNU/Linux /proc/version_signature: Ubuntu 7.0.0-28.28~24.04.1-generic 7.0.12 lsb_release: Ubuntu 24.04.4 LTS installed kernel pkg: linux-image-7.0.0-28-generic 7.0.0-28.28~24.04.1 fallback kernel pkg: linux-image-6.17.0-35-generic 6.17.0-35.35~24.04.1 cmdline: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=a06770dc-b95b-4687-8825-6650f2d58f13 ro quiet splash mem_sleep_default=s2idle vt.handoff=7 mem_sleep: [s2idle] deep === display hardware === 00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [UHD Graphics] [8086:a7a8] (rev 04) 00:06.2 PCI bridge [0604]: Intel Corporation Device [8086:a73d] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2d18] (rev a1) === drm connectors === card1-DP-1 disconnected enabled=disabled card1-DP-2 disconnected enabled=disabled card1-DP-3 disconnected enabled=disabled card1-DP-4 disconnected enabled=disabled card1-DP-5 disconnected enabled=disabled card1-eDP-1 connected enabled=enabled card1-HDMI-A-1 disconnected enabled=disabled card2-eDP-2 disconnected enabled=disabled card2-HDMI-A-2 connected enabled=disabled === panel EDID (eDP-1, base block) === 00ffffffffffff0006afb58100000000 17220104b5221678038235a5534a9e26 0f505400000001010101010101010101 0101010101011f6f00a0a0408f603020 aa0058d7100000180000000f00000000 00000000000000000020000000fd0c30 a522224e010a202020202020000000fc 004231363051414e41412e48200a0264 === nvidia driver === nvidia-driver-590-open 590.48.01-0ubuntu0.24.04.5 nvidia-driver-595-open 595.84-0ubuntu0.24.04.1 === i915 messages, current boot === Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Found alderlake_p/raptorlake_p (device ID a7a8) integrated display version 13.00 stepping E0 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.36.0 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Registered 4 planes with drm panic Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: fbcon: i915drmfb (fb0) is primary device Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915]) Aug 06 12:15:28 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.36.0 Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "display-bug-report.txt" https://bugs.launchpad.net/bugs/2162952/+attachment/5989983/+files/display-bug-report.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162952 Title: i915: eDP panel dead after S3 (deep) resume on 7.0.0-28, works on 6.17.0-35 Status in linux package in Ubuntu: New Bug description: # i915: eDP panel dead after S3 (deep) resume on 7.0.0-28, works on 6.17.0-35 ## Summary On resume from S3 (`mem_sleep=deep`), the internal eDP panel is permanently dark. It is **unpowered, not merely unlit**. No userspace action recovers it — only a reboot. Regression: **6.17.0-35-generic works, 7.0.0-28-generic fails.** The bug is **specific to the S3/deep path** — `s2idle` on the same kernel resumes correctly. ## Test matrix | Kernel | mem_sleep | Panel on resume | |---|---|---| | 6.17.0-35-generic | deep (S3) | OK — 39 suspend cycles over 25 days, no failures | | 7.0.0-28-generic | deep (S3) | **FAIL** — dark, reboot-only recovery | | 7.0.0-28-generic | s2idle | OK — verified over a 32.5 min suspend | ## Key diagnostic detail After the failed resume, every software indicator reports a healthy display. A dead panel is indistinguishable from a live one via sysfs/xrandr: - `/sys/class/drm/card1-eDP-1/status` = `connected`, `enabled` = `enabled` - `xrandr` reports the output enabled, `link-status: Good`, `dpms On` - X is genuinely compositing live content into the panel's region (confirmed by sampling root-window pixels — real window content present) - `intel_backlight`: `actual_brightness` = 1023/1023, `bl_power` = 0; writes are accepted and read back correctly, but a full 0 -> max PWM sweep produces **zero** physical response - A full modeset (`xrandr --output eDP-1 --off` then `--mode ... `) does **not** relight it - **No eDP link-training errors or drm errors in the kernel log** — the resume path logs clean (GuC/HuC reload, mei_hdcp/mei_pxp rebind, nothing else) This points at panel power-sequencing (PPS) state not being restored on the S3 resume path, rather than a link, mode, or backlight-value problem. ## Hardware - Chassis: Elimina Pro V 16 (Clevo/Kapok barebone, subsystem 2564) - iGPU: Intel i915 `0000:00:02.0`, alderlake_p/raptorlake_p, device ID a7a8, integrated display version 13.00 stepping E0 - dGPU: NVIDIA `0000:01:00.0`, driver 595, hybrid/PRIME (external via HDMI-1-0 reverse-prime) - Panel: AUO B160QANAA.H, 2560x1600@165Hz, eDP-1, vrr_capable - Firmware default sleep state: `deep` (nothing forcing it on the kernel cmdline) - Ubuntu 24.04, GNOME on X11, systemd 255 ## Reproducer 1. Boot 7.0.0-28-generic with default `mem_sleep=deep` 2. Confirm the internal panel is lit 3. `systemctl suspend` 4. Wake via power button Internal panel stays dark. External displays are unaffected and continue working. ## Workaround Boot 6.17.0-35-generic. `mem_sleep_default=s2idle` also avoids the bug, but is **not usable on this platform**: S0ix never engages (`/sys/kernel/debug/pmc_core/slp_s0_residency_usec` stayed at **0** across a 32.5-minute suspend), giving 4.67 W average draw vs ~0.3-0.8 W for working S3 (9.2 %/hour battery drain). That may be a separate platform issue worth its own report. Sysinfo: === version === uname -a: Linux aidan-dunphy-Elimina-Pro-V-16 7.0.0-28-generic #28~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 1 15:50:57 UTC 2 x86_64 x86_64 x86_64 GNU/Linux /proc/version_signature: Ubuntu 7.0.0-28.28~24.04.1-generic 7.0.12 lsb_release: Ubuntu 24.04.4 LTS installed kernel pkg: linux-image-7.0.0-28-generic 7.0.0-28.28~24.04.1 fallback kernel pkg: linux-image-6.17.0-35-generic 6.17.0-35.35~24.04.1 cmdline: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=a06770dc-b95b-4687-8825-6650f2d58f13 ro quiet splash mem_sleep_default=s2idle vt.handoff=7 mem_sleep: [s2idle] deep === display hardware === 00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [UHD Graphics] [8086:a7a8] (rev 04) 00:06.2 PCI bridge [0604]: Intel Corporation Device [8086:a73d] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2d18] (rev a1) === drm connectors === card1-DP-1 disconnected enabled=disabled card1-DP-2 disconnected enabled=disabled card1-DP-3 disconnected enabled=disabled card1-DP-4 disconnected enabled=disabled card1-DP-5 disconnected enabled=disabled card1-eDP-1 connected enabled=enabled card1-HDMI-A-1 disconnected enabled=disabled card2-eDP-2 disconnected enabled=disabled card2-HDMI-A-2 connected enabled=disabled === panel EDID (eDP-1, base block) === 00ffffffffffff0006afb58100000000 17220104b5221678038235a5534a9e26 0f505400000001010101010101010101 0101010101011f6f00a0a0408f603020 aa0058d7100000180000000f00000000 00000000000000000020000000fd0c30 a522224e010a202020202020000000fc 004231363051414e41412e48200a0264 === nvidia driver === nvidia-driver-590-open 590.48.01-0ubuntu0.24.04.5 nvidia-driver-595-open 595.84-0ubuntu0.24.04.1 === i915 messages, current boot === Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Found alderlake_p/raptorlake_p (device ID a7a8) integrated display version 13.00 stepping E0 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adlp_dmc.bin (v2.20) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.36.0 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Registered 4 planes with drm panic Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1 Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: fbcon: i915drmfb (fb0) is primary device Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Aug 06 12:15:21 aidan-dunphy-Elimina-Pro-V-16 kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915]) Aug 06 12:15:28 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.36.0 Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915]) Aug 06 12:55:27 aidan-dunphy-Elimina-Pro-V-16 kernel: mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162952/+subscriptions