Public bug reported:
## Summary
After upgrading my HP OMEN 16 laptop from Ubuntu 25.10 to Ubuntu 26.04
LTS, suspend/resume regressed on kernel `7.0.0-15-generic`.
The laptop enters suspend, but on wake it does not recover properly. The
display remains black and the system appears unrecoverable from the
keyboard. Magic SysRq did not work during the failed test, so I had to
hard power off the laptop.
The same machine, with the same GRUB kernel parameters and same patched
DSDT boot entry, suspends and resumes correctly on kernel
`6.17.0-23-generic`.
This looks like a regression between `6.17.0-23-generic` and
`7.0.0-15-generic`.
---
## Hardware
Laptop:
```text
OMEN by HP Transcend Gaming Laptop 16-u0xxx / HP OMEN 16
```
CPU:
```text
Intel 13th Gen Core i9 HX
```
GPU:
```text
NVIDIA GeForce RTX 4070 Laptop GPU
```
Architecture:
```text
x86-64
```
Firmware:
```text
Firmware version: F.38
Firmware date: Thu 2025-11-06
```
Display:
```text
Internal eDP panel
2560x1600
High refresh rate panel, up to 240 Hz
```
Hybrid graphics:
```text
Intel iGPU drives the internal eDP panel
NVIDIA dGPU also present
```
---
## Software
Current OS:
```text
Ubuntu 26.04 LTS
GNOME 50
Wayland
```
Working kernel:
```text
6.17.0-23-generic
```
Failing kernel:
```text
7.0.0-15-generic
```
NVIDIA driver observed in logs:
```text
NVIDIA UNIX x86_64 Kernel Module 580.142
```
Sleep mode:
```text
$ cat /sys/power/state
freeze mem disk
$ cat /sys/power/mem_sleep
[s2idle] deep
```
The system is using `s2idle`, not `deep`.
---
## Important background
This laptop uses a patched DSDT loaded through GRUB:
```grub
acpi /boot/dsdt.aml
```
The patched DSDT was originally used to work around ACPI-related
hardware issues on this HP OMEN 16, including touchpad/audio/boot
stability problems.
The custom GRUB entry currently boots with these kernel parameters:
```text
quiet splash i915.enable_psr=0 nvidia-drm.modeset=1 acpi_backlight=native
```
The full command line on the failing kernel was:
```text
BOOT_IMAGE=/boot/vmlinuz root=UUID=9d22f5a3-b1a5-44f1-867a-a5a29c5cbe87 ro
quiet splash i915.enable_psr=0 nvidia-drm.modeset=1 acpi_backlight=native
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
```
The same GRUB parameters are used when testing kernel
`6.17.0-23-generic`, and suspend/resume works on that kernel.
---
## What works
With kernel:
```text
6.17.0-23-generic
```
the laptop suspends and resumes normally using `s2idle`.
I tested the same patched DSDT boot entry and same important parameters:
```text
i915.enable_psr=0 nvidia-drm.modeset=1 acpi_backlight=native
```
Result:
```text
6.17 suspend works
```
---
## What fails
With kernel:
```text
7.0.0-15-generic
```
the laptop enters suspend, but cannot resume properly.
Observed behavior:
```text
1. Run systemctl suspend
2. Laptop enters suspend
3. Wake attempt does not restore the screen/system
4. Display remains black
5. Magic SysRq did not work
6. Hard shutdown was required
```
Result:
```text
7.0 suspend failed
```
This was reproduced more than once.
---
## Relevant boot / display information
The internal panel is on Intel/i915.
Earlier diagnostic output showed:
```text
/sys/class/drm/card1-eDP-1
connected
enabled
2560x1600
```
Driver mapping:
```text
/sys/class/drm/card1/device/driver -> /sys/bus/pci/drivers/i915
/sys/class/drm/card2/device/driver -> /sys/bus/pci/drivers/nvidia
```
Backlight is controlled correctly by:
```text
/sys/class/backlight/intel_backlight
```
The brightness issue was separately fixed by:
```text
acpi_backlight=native
```
---
## Relevant failing kernel log
Before testing suspend on kernel `7.0.0-15-generic`, I added a marker:
```bash
logger "OMEN_TEST: before kernel 7 suspend test $(date -Is)"
```
Relevant log sequence from the failed boot:
```text
May 16 11:39:57 OMEN16 ball[63933]: OMEN_TEST: before kernel 7 suspend test
2026-05-16T11:39:57+07:00
May 16 11:43:32 OMEN16 systemd-logind[3024]: The system will suspend now!
May 16 11:43:32 OMEN16 ModemManager[3345]: <msg> [sleep-monitor-systemd] system
is about to suspend
May 16 11:43:32 OMEN16 ModemManager[3345]: <msg> [sleep-monitor-systemd] ready
to sleep; dropping inhibitor
May 16 11:43:32 OMEN16 NetworkManager[3091]: <info> [1778906612.2638] manager:
sleep: sleep requested (sleeping: no enabled: yes)
May 16 11:43:32 OMEN16 NetworkManager[3091]: <info> [1778906612.2714] manager:
NetworkManager state is now DISABLED (ASLEEP)
May 16 11:43:32 OMEN16 NetworkManager[3091]: <info> [1778906612.2716] device
(wlo1): state change: activated -> deactivating (reason 'sleeping',
managed-type: 'full')
May 16 11:43:32 OMEN16 gnome-shell[22364]: Cursor update failed:
drmModeAtomicCommit: Invalid argument
May 16 11:43:33 OMEN16 systemd[1]: Reached target sleep.target - Sleep.
May 16 11:43:33 OMEN16 systemd[1]: Starting grub-initrd-fallback.service - GRUB
failed boot detection...
May 16 11:43:33 OMEN16 systemd[1]: Starting nvidia-suspend.service - NVIDIA
system suspend actions...
May 16 11:43:33 OMEN16 suspend[71250]: nvidia-suspend.service
May 16 11:43:33 OMEN16 logger[71250]: <13>May 16 11:43:33 suspend:
nvidia-suspend.service
May 16 11:43:33 OMEN16 systemd[1]: Finished grub-initrd-fallback.service - GRUB
failed boot detection.
May 16 11:43:35 OMEN16 systemd[1]: nvidia-suspend.service: Deactivated
successfully.
May 16 11:43:35 OMEN16 systemd[1]: Finished nvidia-suspend.service - NVIDIA
system suspend actions.
May 16 11:43:35 OMEN16 systemd[1]: nvidia-suspend.service: Consumed 1.435s CPU
time over 2.342s wall clock time, 16.6M memory peak.
May 16 11:43:35 OMEN16 systemd[1]: Starting systemd-suspend.service - System
Suspend...
May 16 11:43:35 OMEN16 systemd-sleep[71523]: Successfully froze unit
'user.slice'.
May 16 11:43:35 OMEN16 systemd-sleep[71523]: Performing sleep operation
'suspend'...
```
The log stops after:
```text
Performing sleep operation 'suspend'...
```
There is no successful resume log after that. The machine required hard
power-off.
---
## NVIDIA suspend services
NVIDIA suspend/resume/hibernate services are installed and enabled:
```text
nvidia-suspend.service: enabled
nvidia-resume.service: enabled
nvidia-hibernate.service: enabled
```
NVIDIA pre-suspend service completed successfully before the failure:
```text
nvidia-suspend.service: Deactivated successfully.
Finished nvidia-suspend.service - NVIDIA system suspend actions.
```
This suggests the failure happens after userspace and NVIDIA pre-suspend
preparation, during the actual kernel suspend transition or resume path.
---
## Other notable log lines from kernel 7.0 boot
Kernel 7.0 boot showed NVIDIA and i915 loading:
```text
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 580.142
nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver
[drm] Initialized nvidia-drm ... for 0000:01:00.0
nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes
```
i915 loaded and initialized:
```text
i915 0000:00:02.0: [drm] Found alderlake_s/raptorlake_s (device ID a788)
integrated display version 12.00 stepping D0
i915 0000:00:02.0: [drm] Finished loading DMC firmware
i915/adls_dmc_ver2_01.bin (v2.1)
i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.49.4
i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
i915 0000:00:02.0: [drm] GT0: SLPC enabled
i915 0000:00:02.0: [drm] GT0: RC enabled
[drm] Initialized i915 1.6.0 for 0000:00:02.0
```
There was also a GNOME/DRM warning right before suspend:
```text
gnome-shell[22364]: Cursor update failed: drmModeAtomicCommit: Invalid argument
```
I do not know whether this is related or only incidental.
---
## ACPI / DSDT notes
The system uses a patched DSDT through GRUB. The custom entry contains:
```grub
acpi /boot/dsdt.aml
```
The boot log for kernel 7.0 showed a DSDT with Intel iASL compiler tag:
```text
ACPI: DSDT ... (v02 HPQOEM 8BB3 00000002 INTL 20250807)
```
This suggests the patched/recompiled DSDT is being used.
The same patched DSDT works with kernel `6.17.0-23-generic`.
Therefore, this looks less like a DSDT regression and more like a kernel
7.0 suspend regression on this hardware.
---
## Expected behavior
The system should enter suspend and resume normally using `s2idle`, as
it does with kernel:
```text
6.17.0-23-generic
```
---
## Actual behavior
With kernel:
```text
7.0.0-15-generic
```
the system hangs/fails during suspend/resume and requires hard shutdown.
---
## Reproduction steps
```bash
# Boot kernel 7.0.0-15-generic
uname -r
# confirms:
# 7.0.0-15-generic
cat /sys/power/mem_sleep
# confirms:
# [s2idle] deep
sudo journalctl --flush
logger "OMEN_TEST: before kernel 7 suspend test $(date -Is)"
systemctl suspend
```
Then wake the laptop.
Result:
```text
Display/system does not recover.
Magic SysRq did not work.
Hard shutdown required.
```
Same test on `6.17.0-23-generic` works.
---
## Current workaround
Boot the older kernel:
```text
6.17.0-23-generic
```
using the same patched DSDT entry and same important kernel parameters.
The custom GRUB entry can be pinned to:
```grub
linux /boot/vmlinuz-6.17.0-23-generic ...
initrd /boot/initrd.img-6.17.0-23-generic
```
instead of using:
```grub
linux /boot/vmlinuz ...
initrd /boot/initrd.img ...
```
because `/boot/vmlinuz` currently points to the newer, failing kernel.
---
## Request
Could Ubuntu kernel maintainers please advise how to debug or report
this as a kernel suspend regression?
I can provide additional logs or run specific commands if needed, but
because the failure requires hard shutdown, I would prefer cautious,
one-test-at-a-time diagnostics.
The key regression appears to be:
```text
6.17.0-23-generic: s2idle suspend/resume works
7.0.0-15-generic: s2idle suspend/resume fails/hangs
```
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-15-generic 7.0.0-15.15
ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0
Uname: Linux 7.0.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.34.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: ball 9909 F.... pipewire
ball 9929 F.... wireplumber
/dev/snd/controlC0: ball 9929 F.... wireplumber
/dev/snd/seq: ball 9909 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 12:34:14 2026
InstallationDate: Installed on 2025-10-27 (201 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: HP OMEN by HP Transcend Gaming Laptop 16-u0xxx
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz
root=UUID=9d22f5a3-b1a5-44f1-867a-a5a29c5cbe87 ro quiet splash
i915.enable_psr=0 nvidia-drm.modeset=1 acpi_backlight=native
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-05-14 (2 days ago)
dmi.bios.date: 11/06/2025
dmi.bios.release: 15.38
dmi.bios.vendor: Insyde
dmi.bios.version: F.38
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8BB3
dmi.board.vendor: HP
dmi.board.version: 64.50
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 64.50
dmi.modalias:
dmi:bvnInsyde:bvrF.38:bd11/06/2025:br15.38:efr64.50:svnHP:pnOMENbyHPTranscendGamingLaptop16-u0xxx:pvrType1ProductConfigId:rvnHP:rn8BB3:rvr64.50:cvnHP:ct10:cvrChassisVersion:sku8F463PA#AKL:pfa103C_5335M7HPOMEN:
dmi.product.family: 103C_5335M7 HP OMEN
dmi.product.name: OMEN by HP Transcend Gaming Laptop 16-u0xxx
dmi.product.sku: 8F463PA#AKL
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: kernel-bug regression s2idle suspend
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2152741
Title:
HP OMEN 16: s2idle suspend/resume regression, 6.17.0-23 works but
7.0.0-15 hangs on resume
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152741/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
