[Bug 1230629] New: Lenovo T14 Gen 5 (Intel Meteor Lake) immediately wakes up from suspend
https://bugzilla.suse.com/show_bug.cgi?id=1230629 Bug ID: 1230629 Summary: Lenovo T14 Gen 5 (Intel Meteor Lake) immediately wakes up from suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: shundhammer@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877385 --> https://bugzilla.suse.com/attachment.cgi?id=877385&action=edit Tarball with system logs, hwinfo, packages info, BIOS screenshots My brand new Lenovo ThinkPad T14 Gen 5 (Intel Core 5 Ultra 125U with Meteor Lake chipset) immediately wakes up again when I try to suspend it to RAM, and there are some errors in the logs: sudo systemctl suspend ...screen goes black... ...screen flickers... ...power LED blinks... ...screen comes back again... ...network status icon shows disconnected... ...network reconnects... -> the machine is back awake as if nothing ever happened. This happens with the current Slowroll kernel and with the current Tumbleweed kernel. It does work with a Xubuntu 22.04.01 LTS live ISO with the older 6.8 kernel, though: - kernel-default-6.10.9-1.1.x86_64 (Tumbleweed) -> wakes up immediately - kernel-default-6.10.8-1.1.x86_64 (Slowroll) -> wakes up immediately - kernel 6.8.? (Xubuntu 22.04.01 live ISO) -> suspends as expected, resumes as expected
inxi
CPU: 12-core (2-mt/10-st) Intel Core Ultra 5 125U (-MST AMCP-) speed/min/max: 400/400/4300:3600:2100 MHz Kernel: 6.10.9-1-default x86_64 Up: 0h 7m Mem: 1.08/15.12 GiB (7.1%) Storage: 953.87 GiB (12.2% used) Procs: 361 Shell: Zsh inxi: 3.3.36
I already did update the (UEFI) BIOS to the latest one, reset the BIOS settings to factory defaults, and updated the kernel-firmware packages to the latest one from Tumbleweed; none of that helped. For more system info, please see the attached tarball: Lenovo-T14-suspend-bug ├── BIOS-screenshots │ ├── T14-BIOS-01-Main.jpg │ ├── T14-BIOS-02-Power-Settings.jpg │ └── T17-BIOS-03-Power-On.jpg ├── hardware │ ├── hwinfo.log │ ├── inxi-full.log │ ├── inxi.log │ └── inxi-machine.log ├── messages │ ├── dmesg-after-suspend.log │ ├── dmesg-before-suspend.log │ ├── dmesg.diff │ ├── journalctl-b-after-suspend.log │ ├── journalctl-b-before-suspend.log │ └── journalctl-b.diff └── packages ├── rpm-qa-last.txt └── zypp-history.log journalctl -b diff before and after the suspend:
Sep 17 10:35:22 meteor systemd-logind[976]: The system will suspend now! Sep 17 10:35:22 meteor ModemManager[1079]: <info> [sleep-monitor-systemd] system is about to suspend Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7931] manager: sleep: sleep requested (sleeping: no enabled: yes) Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7932] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7938] manager: NetworkManager state is now ASLEEP Sep 17 10:35:22 meteor NetworkManager[1089]: <info> [1726562122.7940] device (wlp0s20f3): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Sep 17 10:35:22 meteor sudo[2349]: pam_unix(sudo:session): session closed for user root Sep 17 10:35:22 meteor systemd[1]: Starting Network Manager Script Dispatcher Service... Sep 17 10:35:22 meteor systemd[1]: Started Network Manager Script Dispatcher Service. Sep 17 10:35:22 meteor kernel: wlp0s20f3: deauthenticating from c8:0e:14:46:50:44 by local choice (Reason: 3=DEAUTH_LEAVING) Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0377] device (wlp0s20f3): supplicant interface state: completed -> disconnected Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0379] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): canceled DHCP transaction Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0384] dhcp4 (wlp0s20f3): state changed no lease Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): canceled DHCP transaction Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0386] dhcp6 (wlp0s20f3): state changed no lease Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.0819] device (wlp0s20f3): set-hw-addr: set MAC address to D6:6B:75:DD:7E:C9 (scanning) Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1987] device (wlp0s20f3): supplicant interface state: disconnected -> interface_disabled Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1988] device (wlp0s20f3): supplicant interface state: interface_disabled -> disconnected Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.1991] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') Sep 17 10:35:23 meteor chronyd[1208]: Removed source fd00::ca0e:14ff:fe46:503e Sep 17 10:35:23 meteor chronyd[1208]: Source 192.168.178.1 offline Sep 17 10:35:23 meteor chronyd[1208]: Can't synchronise: no selectable sources Sep 17 10:35:23 meteor chronyd[1208]: Source 85.215.189.120 offline Sep 17 10:35:23 meteor dns-dnsmasq.sh[2368]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit Sep 17 10:35:23 meteor NetworkManager[1089]: <info> [1726562123.3482] device (wlp0s20f3): set-hw-addr: reset MAC address to 28:A0:6B:33:40:FA (unmanage) Sep 17 10:35:23 meteor systemd[1]: Reached target Sleep. Sep 17 10:35:23 meteor systemd[1]: Starting System Suspend... Sep 17 10:35:23 meteor dns-dnsmasq.sh[2384]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit Sep 17 10:35:23 meteor systemd-sleep[2378]: User sessions remain unfrozen (add $SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=1 to override), Sep 17 10:35:23 meteor systemd-sleep[2378]: relying on kernel to perform the freeze. Sep 17 10:35:23 meteor systemd-sleep[2378]: This is a temporary downstream workaround for https://github.com/systemd/systemd/issues/33083. Sep 17 10:35:23 meteor systemd-sleep[2392]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend Sep 17 10:35:23 meteor systemd-sleep[2378]: Performing sleep operation 'suspend'... Sep 17 10:35:23 meteor kernel: PM: suspend entry (s2idle) Sep 17 10:35:23 meteor kernel: Filesystems sync: 0.002 seconds Sep 17 10:35:24 meteor kernel: Freezing user space processes Sep 17 10:35:24 meteor kernel: Freezing user space processes completed (elapsed 0.001 seconds) Sep 17 10:35:24 meteor kernel: OOM killer disabled. Sep 17 10:35:24 meteor kernel: Freezing remaining freezable tasks Sep 17 10:35:24 meteor kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) Sep 17 10:35:24 meteor kernel: printk: Suspending console(s) (use no_console_suspend to debug) Sep 17 10:35:24 meteor kernel: e1000e: EEE TX LPI TIMER: 00000011 Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: pci_pm_suspend(): e1000e_pm_suspend [e1000e] returns -2 Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: dpm_run_callback(): pci_pm_suspend returns -2 Sep 17 10:35:24 meteor kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 Sep 17 10:35:24 meteor kernel: PM: Some devices failed to suspend, or early wake event detected Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.29.2 Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.29.2 Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4 Sep 17 10:35:24 meteor kernel: nvme nvme0: 14/0/0 default/read/poll queues Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: submission enabled Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled Sep 17 10:35:24 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: RC enabled Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80 Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 Sep 17 10:35:24 meteor kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 Sep 17 10:35:24 meteor kernel: mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915]) Sep 17 10:35:24 meteor kernel: OOM killer enabled. Sep 17 10:35:24 meteor kernel: Restarting tasks ... done. Sep 17 10:35:24 meteor kernel: random: crng reseeded on system resumption Sep 17 10:35:25 meteor kernel: PM: suspend exit Sep 17 10:35:25 meteor kernel: PM: suspend entry (s2idle) Sep 17 10:35:25 meteor kernel: Filesystems sync: 0.019 seconds Sep 17 10:35:26 meteor kernel: Freezing user space processes Sep 17 10:35:26 meteor kernel: Freezing user space processes completed (elapsed 0.001 seconds) Sep 17 10:35:26 meteor kernel: OOM killer disabled. Sep 17 10:35:26 meteor kernel: Freezing remaining freezable tasks Sep 17 10:35:26 meteor kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) Sep 17 10:35:26 meteor kernel: printk: Suspending console(s) (use no_console_suspend to debug) Sep 17 10:35:26 meteor kernel: e1000e: EEE TX LPI TIMER: 00000011 Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: pci_pm_suspend(): e1000e_pm_suspend [e1000e] returns -2 Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: dpm_run_callback(): pci_pm_suspend returns -2 Sep 17 10:35:26 meteor kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 Sep 17 10:35:26 meteor kernel: PM: Some devices failed to suspend, or early wake event detected Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.29.2 Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT0: GUC: RC enabled Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.29.2 Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4 Sep 17 10:35:26 meteor kernel: nvme nvme0: 14/0/0 default/read/poll queues Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: submission enabled Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled Sep 17 10:35:26 meteor kernel: i915 0000:00:02.0: [drm] GT1: GUC: RC enabled Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80 Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0 Sep 17 10:35:26 meteor kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4 Sep 17 10:35:26 meteor kernel: mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915]) Sep 17 10:35:26 meteor kernel: OOM killer enabled. Sep 17 10:35:26 meteor kernel: Restarting tasks ... done. Sep 17 10:35:26 meteor kernel: random: crng reseeded on system resumption Sep 17 10:35:26 meteor systemd[1502]: Started dbus-:1.2-org.xfce.Xfconf@1.service. Sep 17 10:35:26 meteor systemd-sleep[2378]: Failed to put system to sleep. System resumed again: No such file or directory Sep 17 10:35:26 meteor kernel: PM: suspend exit Sep 17 10:35:26 meteor systemd-sleep[2468]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend Sep 17 10:35:26 meteor systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Sep 17 10:35:26 meteor systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Sep 17 10:35:26 meteor systemd[1]: Failed to start System Suspend. Sep 17 10:35:26 meteor systemd[1]: Dependency failed for Suspend. Sep 17 10:35:26 meteor systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Sep 17 10:35:26 meteor systemd-logind[976]: Operation 'suspend' finished. Sep 17 10:35:26 meteor systemd[1]: Stopped target Sleep. Sep 17 10:35:26 meteor ModemManager[1079]: <info> [sleep-monitor-systemd] system is resuming Sep 17 10:35:26 meteor NetworkManager[1089]: <info> [1726562126.5424] manager: sleep: wake requested (sleeping: yes enabled: yes) Sep 17 10:35:26 meteor NetworkManager[1089]: <info> [1726562126.5425] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') Sep 17 10:35:28 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error Sep 17 10:35:29 meteor ModemManager[1079]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin Sep 17 10:35:29 meteor ModemManager[1079]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin Sep 17 10:35:29 meteor NetworkManager[1089]: <info> [1726562129.9289] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Sep 17 10:35:29 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down Sep 17 10:35:31 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error Sep 17 10:35:33 meteor systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3875] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3884] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.3887] manager: NetworkManager state is now DISCONNECTED Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4327] device (wlp0s20f3): supplicant interface state: internal-starting -> disconnected Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4327] device (p2p-dev-wlp0s20f3): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', sys-iface-state: 'removed') Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4331] Wi-Fi P2P device controlled by interface wlp0s20f3 created Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4333] manager: (p2p-dev-wlp0s20f3): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5) Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4335] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4337] device (wlp0s20f3): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Sep 17 10:35:34 meteor NetworkManager[1089]: <info> [1726562134.4341] device (p2p-dev-wlp0s20f3): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1404] policy: auto-activating connection 'wlp0s20f3' (ed77ffbb-f7b5-3841-8b21-258e99306b9f) Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1409] device (wlp0s20f3): Activation: starting connection 'wlp0s20f3' (ed77ffbb-f7b5-3841-8b21-258e99306b9f) Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1409] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1413] manager: NetworkManager state is now CONNECTING Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1418] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1422] device (wlp0s20f3): Activation: (wifi) access point 'wlp0s20f3' has security, but secrets are required. Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1422] device (wlp0s20f3): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1425] sup-iface[2dde45278d9b93ec,1,wlp0s20f3]: wps: type pbc start... Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1437] device (wlp0s20f3): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1440] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1443] device (wlp0s20f3): Activation: (wifi) connection 'wlp0s20f3' has security, and secrets exist. No new secrets needed. Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'ssid' value 'Hundhammer' Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'scan_ssid' value '1' Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'bgscan' value 'simple:30:-65:300' Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE' Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1444] Config: added 'auth_alg' value 'OPEN' Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1445] Config: added 'psk' value '<hidden>' Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1452] device (wlp0s20f3): supplicant interface state: disconnected -> scanning Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1452] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1955] device (wlp0s20f3): supplicant interface state: scanning -> authenticating Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.1955] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating Sep 17 10:35:38 meteor kernel: wlp0s20f3: authenticate with c8:0e:14:46:50:44 (local address=28:a0:6b:33:40:fa) Sep 17 10:35:38 meteor kernel: wlp0s20f3: send auth to c8:0e:14:46:50:44 (try 1/3) Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2279] device (wlp0s20f3): supplicant interface state: authenticating -> associating Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2279] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Sep 17 10:35:38 meteor kernel: wlp0s20f3: authenticated Sep 17 10:35:38 meteor kernel: wlp0s20f3: associate with c8:0e:14:46:50:44 (try 1/3) Sep 17 10:35:38 meteor kernel: wlp0s20f3: RX AssocResp from c8:0e:14:46:50:44 (capab=0x1511 status=0 aid=5) Sep 17 10:35:38 meteor kernel: wlp0s20f3: associated Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2422] device (wlp0s20f3): supplicant interface state: associating -> associated Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2422] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2493] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.2493] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3140] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3141] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Hundhammer" Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3141] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed Sep 17 10:35:38 meteor kernel: wlp0s20f3: Limiting TX power to 20 (23 - 3) dBm as advertised by c8:0e:14:46:50:44 Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3359] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3364] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.3439] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.178.166, acd pending Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5129] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.178.166 Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5134] policy: set 'wlp0s20f3' (wlp0s20f3) as default for IPv4 routing and DNS Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.5196] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor systemd[1]: Starting Network Manager Script Dispatcher Service... Sep 17 10:35:38 meteor systemd[1]: Started Network Manager Script Dispatcher Service. Sep 17 10:35:38 meteor chronyd[1208]: Source 192.168.178.1 online Sep 17 10:35:38 meteor chronyd[1208]: Source 85.215.189.120 online Sep 17 10:35:38 meteor dns-dnsmasq.sh[2493]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6113] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6116] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6120] manager: NetworkManager state is now CONNECTED_SITE Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.6128] device (wlp0s20f3): Activation: successful, device activated. Sep 17 10:35:38 meteor chronyd[1208]: Could not add source 192.168.178.1 : Already in use Sep 17 10:35:38 meteor dns-dnsmasq.sh[2520]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit Sep 17 10:35:38 meteor dns-dnsmasq.sh[2534]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit Sep 17 10:35:38 meteor NetworkManager[1089]: <info> [1726562138.7622] manager: NetworkManager state is now CONNECTED_GLOBAL Sep 17 10:35:38 meteor chronyd[1208]: Selected source 192.168.178.1 Sep 17 10:35:38 meteor dns-dnsmasq.sh[2547]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5709] dhcp6 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5717] policy: set 'wlp0s20f3' (wlp0s20f3) as default for IPv6 routing and DNS Sep 17 10:35:39 meteor NetworkManager[1089]: <info> [1726562139.5833] dhcp6 (wlp0s20f3): state changed new lease Sep 17 10:35:39 meteor chronyd[1208]: Could not add source 192.168.178.1 : Already in use Sep 17 10:35:39 meteor chronyd[1208]: Added source fd00::ca0e:14ff:fe46:503e Sep 17 10:35:39 meteor dns-dnsmasq.sh[2576]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit Sep 17 10:35:49 meteor systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Sep 17 10:36:13 meteor sudo[2589]: pam_unix(sudo:session): session opened for user root(uid=0) by sh(uid=1000) Sep 17 10:36:13 meteor sudo[2589]: pam_unix(sudo:session): session closed for user root Sep 17 10:36:25 meteor sudo[2593]: pam_unix(sudo:session): session opened for user root(uid=0) by sh(uid=1000)
It doesn't make a difference if I use "sudo systemctl suspend", select "suspend" from the LightDM menu or from the Xfce4 menu, or if I close the laptop lid. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c1 --- Comment #1 from Stefan Hundhammer <shundhammer@suse.com> --- Hibernating works as expected, though. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86-64 OS|Other |openSUSE Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- You can check older kernels in my OBS repos, home:tiwai:kernel:6.8, home:tiwai:kernel:6.7, etc. The repo "standard" is for Tumbleweed. Also, check 6.11 kernel from OBS Kernel:HEAD repo. We'll move to 6.11, so it makes little sense to stick with 6.10.x for debugging. If the problem persists with 6.11, try to unload e1000e module and test the suspend. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c3 --- Comment #3 from Stefan Hundhammer <shundhammer@suse.com> --- OK, will try. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c4 --- Comment #4 from Stefan Hundhammer <shundhammer@suse.com> --- 'sudo rmmod e1000e' helped. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c5 --- Comment #5 from Stefan Hundhammer <shundhammer@suse.com> --- The problem persists with https://download.opensuse.org/repositories/Kernel:/HEAD/standard/x86_64/kern... But now that I know that the problem is with the e1000e module, I can blacklist that one: I can't recall the last time that I needed cabled Ethernet with any of my laptops. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c6 --- Comment #6 from Takashi Iwai <tiwai@suse.com> --- Well, if it's a regression, we need to report it to the upstream. Could you try to figure out which kernel version started showing the bad behavior? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c7 --- Comment #7 from Stefan Hundhammer <shundhammer@suse.com> --- For others reading this bug: My workaround was to blacklist the e1000e kernel module which is needed for cabled Ethernet (WiFi works just fine without it). What you need to do for that is to create a file in /etc/modprobe.d like this: % cat /etc/modprobe.d/10-blacklist.conf blacklist e1000e ...and from now on, suspend works fine. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c8 --- Comment #8 from Stefan Hundhammer <shundhammer@suse.com> --- (In reply to Takashi Iwai from comment #6)
Well, if it's a regression, we need to report it to the upstream.
Could you try to figure out which kernel version started showing the bad behavior?
I can try that, yes. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c9 --- Comment #9 from Stefan Hundhammer <shundhammer@suse.com> --- Your kernel-default-6.8.9 suspends (and resumes) just fine: https://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.8/standard... Of course I double-checked that the e1000e module was actually loaded. It also did not complain in dmesg or in 'sudo journalctl -b'. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c10 --- Comment #10 from Stefan Hundhammer <shundhammer@suse.com> --- Your kernel-default-6.9.9 also suspends and resumes just fine: https://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.9/standard... Also e1000e loaded, and I see messages, but no errors from it in the journal. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c11 --- Comment #11 from Stefan Hundhammer <shundhammer@suse.com> --- Your kernel-default-6.10.10 shows the problem: It suspends for a moment, and then it resumes immediately: https://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.10/standar... And the e1000e module complains in 'sudo journalctl -b':
Sep 17 19:09:16 meteor kernel: e1000e: Intel(R) PRO/1000 Network Driver Sep 17 19:09:16 meteor kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. Sep 17 19:09:16 meteor kernel: e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Sep 17 19:09:16 meteor kernel: e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock Sep 17 19:09:16 meteor kernel: e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) c4:ef:bb:34:c3:e2 Sep 17 19:09:16 meteor kernel: e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection Sep 17 19:09:16 meteor kernel: e1000e 0000:00:1f.6 eth0: MAC: 16, PHY: 12, PBA No: FFFFFF-0FF Sep 17 19:09:16 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0 Sep 17 19:10:26 meteor kernel: e1000e: EEE TX LPI TIMER: 00000011 Sep 17 19:10:26 meteor kernel: e1000e 0000:00:1f.6: PM: pci_pm_suspend(): e1000e_pm_suspend [e1000e] returns -2 Sep 17 19:10:26 meteor kernel: e1000e 0000:00:1f.6: PM: dpm_run_callback(): pci_pm_suspend returns -2 Sep 17 19:10:26 meteor kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 Sep 17 19:10:28 meteor kernel: e1000e: EEE TX LPI TIMER: 00000011 Sep 17 19:10:28 meteor kernel: e1000e 0000:00:1f.6: PM: pci_pm_suspend(): e1000e_pm_suspend [e1000e] returns -2 Sep 17 19:10:28 meteor kernel: e1000e 0000:00:1f.6: PM: dpm_run_callback(): pci_pm_suspend returns -2 Sep 17 19:10:28 meteor kernel: e1000e 0000:00:1f.6: PM: failed to suspend async: error -2 Sep 17 19:10:30 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error Sep 17 19:10:31 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down Sep 17 19:10:33 meteor kernel: e1000e 0000:00:1f.6 enp0s31f6: Hardware Error -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c12 --- Comment #12 from Stefan Hundhammer <shundhammer@suse.com> --- Notice that all the time the same kernel-firmware packages were in use. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c13 --- Comment #13 from Stefan Hundhammer <shundhammer@suse.com> --- I just moved through the kernel-default-6.10.x in the Slowroll update repo: https://download.opensuse.org/update/slowroll/repo/oss/x86_64/ I moved all the way back to kernel-default-6.10.3 (the oldest 6.10.x kernel in that repo), and they all showed the problem. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c14 --- Comment #14 from Stefan Hundhammer <shundhammer@suse.com> --- For completeness: kernel-default-6.9.9 from the official Slowroll update repo also suspends and resumes fine: https://download.opensuse.org/update/slowroll/repo/oss/x86_64/kernel-default... e1000e module loaded and visible in 'sudo journalctl -b', but just normal messages, no errors. So we established that kernel-default-6.9.9 does not have this problem, but kernel-default-6.10.3 or later have it. This is as far as I can narrow this down right now. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c15 --- Comment #15 from Takashi Iwai <tiwai@suse.com> --- OK, thanks. There have been a few changes that are relevant with e1000e runtime PM between 6.9 and 6.10. We need to identify the culprit change. I'm building three test 6.10.x kernels with the reverts. They are being built in OBS home:tiwai:bsc1230629-r1, home:tiwai:bsc1230629-r2 and home:tiwai:bsc1230629-r3 repos. Once after the builds of those finished (takes an hour or so), please test them. Start from r1, and if it still fails, continue to the next. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c16 Frank Krüger <fkrueger@mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger@mailbox.org --- Comment #16 from Frank Krüger <fkrueger@mailbox.org> --- Just a wild guess: There was a similar bug report upstream, but the reporter claims its fixed with kernel 6.10: https://bugzilla.kernel.org/show_bug.cgi?id=218940. See also https://bugzilla.kernel.org/show_bug.cgi?id=218936 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c17 --- Comment #17 from Takashi Iwai <tiwai@suse.com> --- (In reply to Frank Krüger from comment #16)
Just a wild guess: There was a similar bug report upstream, but the reporter claims its fixed with kernel 6.10: https://bugzilla.kernel.org/show_bug.cgi?id=218940. See also https://bugzilla.kernel.org/show_bug.cgi?id=218936
They are likely relevant. But the fact that it happens with 6.10.9 and 6.11.0 kernels implies that either the fix isn't perfect or it's a different bug. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c18 --- Comment #18 from Stefan Hundhammer <shundhammer@suse.com> --- Takashi, I just tested your -r1, -r2 and -r3 kernels: -r1 and -r2 still show the problem with the same symptoms as in comment #11. https://download.opensuse.org/repositories/home:/tiwai:/bsc1230629-r1/standa... ^^^^^^^^^^^^^^^^^^^^ still broken https://download.opensuse.org/repositories/home:/tiwai:/bsc1230629-r2/standa... ^^^^^^^^^^^^^^^^^^^^ still broken -r3 fixes the problem: suspend and resume work as expected, and there are no more errors from e1000e in the journal: https://download.opensuse.org/repositories/home:/tiwai:/bsc1230629-r3/standa... ^^^^^^^^^^^^^^^^^^^ the good one -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c19 --- Comment #19 from Stefan Hundhammer <shundhammer@suse.com> --- Side note: The sleep on this laptop appears to be a *very* "light" sleep: When the lid is still open, it awakens to the slightest touch of the touchpad or any key on the keyboard. But that is probably a completely different problem, if it is a problem at all. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c20 --- Comment #20 from Stefan Hundhammer <shundhammer@suse.com> --- See also bug #1230418 - possibly related (?) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c21 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(shundhammer@suse. | |com) --- Comment #21 from Takashi Iwai <tiwai@suse.com> --- OK, it means that we need to revert back up to the commit bfd546a552e140b0a4c8a21527c39d6d21addb28 e1000e: move force SMBUS near the end of enable_ulp function Although there are two more fixes over it, Stefan's problem still persists. And now I noticed that there is a new fix in Linus tree for 6.12-rc1, commit 0a6ad4d9e1690c7faa3a53f762c877e477093657 e1000e: avoid failing the system during pm_suspend This sounds like the fix. I'm now building another test kernel with this patch in OBS home:tiwai:bsc1230629-patched repo. Please give it a try later. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c22 --- Comment #22 from Takashi Iwai <tiwai@suse.com> --- (In reply to Stefan Hundhammer from comment #20)
See also bug #1230418 - possibly related (?)
Unlikely. And, the problem of the sensitive touchpad and keyboard during the sleep is a known issue. It's a sort of designed behavior. IIRC, you can tweak via sysfs adjustment. Take a look at an example for Arch Wiki (for older Thinkpad models, though): https://wiki.archlinux.org/title/Lenovo_ThinkPad_T14s_(AMD)_Gen_3 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c23 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shundhammer@suse. | |com) | --- Comment #23 from Stefan Hundhammer <shundhammer@suse.com> --- (In reply to Takashi Iwai from comment #21)
I'm now building another test kernel with this patch in OBS home:tiwai:bsc1230629-patched repo. Please give it a try later.
Yes, this one also fixes the problem. Thx! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c24 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #24 from Takashi Iwai <tiwai@suse.com> --- Good to hear. Now the fix was pushed to master/for-next. It should be included in the next stable kernel update with 6.11. You can keep my test kernel until the fix kernel is released for TW (or apply the workaround with e10001 blacklisting). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c25 --- Comment #25 from Frank Krüger <fkrueger@mailbox.org> --- (In reply to Stefan Hundhammer from comment #19)
Side note: The sleep on this laptop appears to be a *very* "light" sleep: When the lid is still open, it awakens to the slightest touch of the touchpad or any key on the keyboard. JFYI: This is strange, in fact, I have a T14 Gen 1 (AMD) and after suspend, with the lid still open, it only wakes up when pressing Fn, as expected. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c29 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #29 from Stefan Hundhammer <shundhammer@suse.com> --- I can confirm that the problem is indeed fixed in kernel-default-6.11.0 that just arrived in Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c30 --- Comment #30 from Frank Krüger <fkrueger@mailbox.org> --- (In reply to Stefan Hundhammer from comment #29)
I can confirm that the problem is indeed fixed in kernel-default-6.11.0 that just arrived in Tumbleweed.
By the way, do you also observe maximum backlight after wakeup from resume by opening the lid for kernel >= 6.11? Anyway, it's a differnent issue. Thx. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1230629 https://bugzilla.suse.com/show_bug.cgi?id=1230629#c31 --- Comment #31 from Stefan Hundhammer <shundhammer@suse.com> --- (In reply to Frank Krüger from comment #30)
By the way, do you also observe maximum backlight after wakeup from resume by opening the lid for kernel >= 6.11? Anyway, it's a differnent issue. Thx.
No, it's the same value that I suspended with; I just checked. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com