HP Laptop 15-fc0xxx fails to resume after closing and reopening the lid on Ubuntu 26.04 LTS

Support and Help
,
1

Title

HP Laptop 15-fc0xxx fails to resume after closing and reopening the lid on Ubuntu 26.04 LTS

Problem Description

Hello Ubuntu Support Team,

I am experiencing a suspend/resume problem on my HP laptop running Ubuntu 26.04 LTS.

When I close the laptop lid, the system appears to enter suspend/sleep normally. However, when I open the lid again, the laptop does not properly resume.

The display remains black/off and my Ubuntu session does not become usable again. The expected behavior is that opening the lid should wake the laptop and restore the session, but instead the system appears to get stuck during resume.

Because of this issue, I cannot reliably use normal lid-close suspend. If I avoid suspend, the laptop continues running while the lid is closed, which causes unnecessary battery drain.

Expected behavior

Close lid
    ↓
System suspends
    ↓
Open lid
    ↓
System wakes
    ↓
Display/session becomes available

Actual behavior

Close lid
    ↓
System suspends
    ↓
Open lid
    ↓
Screen remains black / system does not properly resume

System Information

Operating System

Ubuntu 26.04 LTS
Codename: Resolute Raccoon

From /etc/os-release:

PRETTY_NAME="Ubuntu 26.04 LTS"
NAME="Ubuntu"
VERSION_ID="26.04"
VERSION="Ubuntu 26.04 LTS (Resolute Raccoon)"
VERSION_CODENAME=resolute
ID=ubuntu
ID_LIKE=debian
UBUNTU_CODENAME=resolute

Hardware

Hardware Vendor: HP
Hardware Model: HP Laptop 15-fc0xxx
Hardware SKU: B7UV7PA#ACJ
Hardware Version: 53.57

Firmware / BIOS

Firmware Version: F.25
Firmware Date: Mon 2026-04-20

Kernel

Linux HP-Laptop-15-fc0xxx 7.0.0-30-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 31 18:22:54 UTC 2026 x86_64 GNU/Linux

Kernel:

7.0.0-30-generic

Architecture:

x86_64

Desktop/session

Desktop Environment: GNOME
Display Server: Wayland

XDG_SESSION_TYPE=wayland
XDG_CURRENT_DESKTOP=ubuntu:GNOME
DESKTOP_SESSION=ubuntu

Suspend Configuration

I checked:

cat /sys/power/mem_sleep

The output is:

[s2idle]

So the system currently exposes s2idle.

I also checked:

cat /sys/power/state

and suspend statistics.

The system does not currently appear to expose deep as an available sleep mode.

I would like to know whether s2idle is the expected suspend mode for this HP laptop or whether the hardware should support another suspend state.

Lid Configuration

I checked /etc/systemd/logind.conf.

The relevant settings are currently commented out/default:

#HandleSuspendKey=suspend
#HandleSuspendKeyLongPress=hibernate
#HandleLidSwitch=suspend
#HandleLidSwitchExternalPower=suspend
#HandleLidSwitchDocked=ignore
#LidSwitchIgnoreInhibited=yes

I have not intentionally configured a custom HandleLidSwitch behavior in this file.

ACPI Wakeup Configuration

I checked:

cat /proc/acpi/wakeup

The output is:

Device  S-state  Status   Sysfs node
GPP1    S4       *disabled
GP17    S4       *enabled   pci:0000:00:08.1
GPP0    S4       *disabled

I have not manually changed these wakeup settings.

I would like to know whether the GP17 wakeup device being enabled is expected for this hardware and whether it could be related to the suspend/resume problem.

Current GRUB Configuration

During troubleshooting, I added the following AMDGPU-related kernel parameters:

GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.runpm=0 amdgpu.gpu_recovery=1 amdgpu.sg_display=0 quiet splash"

The parameters are:

amdgpu.runpm=0
amdgpu.gpu_recovery=1
amdgpu.sg_display=0

These parameters were added while investigating the suspend/resume issue.

I am not certain whether these parameters have any positive effect, and I would like support to determine whether they could themselves affect suspend/resume behavior.

I am willing to test the system with the default Ubuntu kernel command line if that would help isolate the problem.

Reboot / GNOME Session Behavior

At one point, when attempting to reboot, I received:

Operation inhibited by "saqeeb-ansari" (PID 3847 "gnome-session-s", user saqeeb-ansari), reason is "user session inhibited".
User saqeeb-ansari is logged in on tty2.
Please retry operation after closing inhibitors and logging out other users.
'systemd-inhibit' can be used to list active inhibitors.
Alternatively, ignore inhibitors and users with 'systemctl reboot -i'.

I would like to know whether this GNOME session inhibitor is normal behavior or potentially related to the suspend/resume issue.

Troubleshooting Already Performed

I have already checked the following:

  • Ubuntu version

  • Kernel version

  • GNOME/Wayland session

  • Hardware model

  • BIOS/firmware version

  • Suspend mode

  • Suspend statistics

  • systemd-logind lid configuration

  • ACPI wakeup devices

  • GRUB kernel parameters

  • Installed kernel configuration

I have also tested suspend behavior and experienced the same failure when attempting to resume after closing and reopening the laptop lid.

I have avoided making further random changes to /proc/acpi/wakeup, suspend modes, or kernel parameters because I would prefer to identify the root cause first.

Suspected Areas

I am not certain what is causing the problem, but the issue may involve one or more of the following:

  1. Linux kernel suspend/resume handling

  2. AMDGPU/DRM resume handling

  3. ACPI firmware/lid event handling

  4. HP BIOS/firmware

  5. s2idle support on this hardware

  6. GNOME/systemd lid handling

  7. Wayland/display restoration after resume

  8. A kernel regression in 7.0.0-30-generic

I would appreciate help determining which component is actually failing instead of applying unrelated configuration changes.

Information I Can Provide

I can provide additional diagnostic information including:

journalctl -b -1 -k
journalctl -b -1
lspci -nnk
lsusb
dmidecode
fwupdmgr get-devices
fwupdmgr get-updates
ACPI information
AMDGPU/DRM logs
suspend statistics
installed kernel information
systemd-inhibit output

I can also reproduce the suspend/resume failure and immediately collect the previous-boot kernel logs.

Help Requested

Could you please help me determine:

  1. Why does the laptop fail to resume after opening the lid?

  2. Is this a known issue with HP Laptop 15-fc0xxx?

  3. Is s2idle the correct suspend mode for this hardware?

  4. Does this hardware support deep sleep?

  5. Could the AMDGPU driver be responsible for the resume failure?

  6. Could amdgpu.runpm=0, amdgpu.gpu_recovery=1, or amdgpu.sg_display=0 be affecting suspend/resume?

  7. Is BIOS F.25 known to have suspend/resume problems?

  8. Is there a newer BIOS/firmware version recommended for this laptop?

  9. Is the ACPI lid event detected correctly?

  10. Could GP17 or another ACPI wakeup device be involved?

  11. Is this related to Ubuntu kernel 7.0.0-30-generic?

  12. Would testing another kernel be recommended?

  13. Could GNOME/Wayland be responsible for the display not returning after resume?

  14. What exact logs should I collect immediately after reproducing the failure?

I would prefer to diagnose the root cause before making additional changes to GRUB, ACPI wakeup configuration, suspend modes, or kernel parameters.

Thank you for your help.

2

Welcome to Ubuntu Discourse :slight_smile:

It looks like you may have entered the same/almost the same information at least 3 times.

Please go back and edit your post to remove duplicate information. It is very confusing for the volunteer users in its current state.

Thanks

1 Like
3

Sorry for the confusion. I accidentally pasted the same information multiple times while creating the post.

I have removed the duplicate content and cleaned up the post so that the issue and relevant system information are presented only once.

Thank you for pointing this out, and apologies for the inconvenience.

1 Like
4

Thanks, much appreciated.

1 Like