You are not logged in.
- Topics: Active | Unanswered
#1 2026-02-08 13:24:20
- 5hridhyan
- Member
- From: Asia
- Registered: 2025-12-25
- Posts: 217
[SOLVED]HP 247 G8 [AMD]: low battery actions fail [Workaround]
So yeah all I can say is It isn't "bad code" I am not an expert but I tried to read by understanding, how to read in the fp by other documents hopefully I was not all wrong and I did managed to get "workaround" from my understandings, so from my DSDT I see HP’s ACPI implementation has some "communication mismatch" with how the kernel identifies the OS. at least that is what I can say and from the understanding the logic I tried to fix by these Kernel parameters and make sure resume offset is correct.
And if you are a distro hopper make sure your old distro didn't gave you a unwanted gift about swap/hibernation image, trust me it survived two distro installs!!
my cmdline (do not blindly copy and paste everything!)
└─$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe rw rootflags=subvol=@ cryptdevice=UUID=63984f23-816d-48d8-9493-119bf15c9a26:root zswap.enabled=0 rootfstype=btrfs loglevel=3 amdgpu.dpm=1 lsm=landlock,lockdown,yama,apparmor,bpf apparmor=1 security=apparmor iommu=pt pcie_aspm=off amdgpu.noretry=0 amdgpu.gpu_recovery=1 "acpi_osi=Windows 2015" amdgpu.dcfeaturemask=0x8 resume=UUID=c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe resume_offset=17423426if you have time read it at least I got a time to vent my understandings about some parameters or just see cmd line and enter it in yours 
acpi_osi="Windows 2015": is because the DSDT's "OSFL" method checks for Windows strings to decide which power features to enable, and without this, the BIOS doesn't trigger the correct power-down sequence for modern AMD APUs, leading to that "zombie" state on resume. also it should be exactly like this in grub and after rendered it will be same as you see in my cmdline
acpi_osi=\"Windows 2015\"iommu=pt: It stops the IOMMU from re-mapping the GPU's memory space during wake, which was causing the driver hang.
pcie_aspm=off: fixed the TLB flush warnings and potential NVMe timeouts when writing the 16GB hibernation image to the encrypted swap.
well at least that is what I thought it did
also in Upower config keep the critical action above 7% for a "sweet spot" and set accordingly here is a example of mine
PercentageLow=18.0
PercentageCritical=15.0
PercentageAction=10.0the journal logs for successful "automatic" hibernation.
https://0x0.st/PA1F.txt
Hope you find this helpful
Good Luck!
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have been facing weird issue about hibernation, well I cannot confirm if it is regression by recent updates but since I installed ArchLinux I never hibernated not even manually and never let it to hit below 10%, but finally hit below %5 automatic hibernation leads to zombie like behavior [lock_screen=>no_input=>screen_black] yes manual hibernation too starts like that but in automatic hibernation it either wakes up directly and takes input else it same wakes up no input and in that case have to use Alt+printsc+REISUB.
Here is my journal https://0x0.st/PTT2.txt
my /etc/mkincipto
┌──(shridhyan@Aranya-Marjara)-[~]
└─$ grep ^HOOKS /etc/mkinitcpio.conf
HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block encrypt resume filesystems fsck)└─$ swapon --show
NAME TYPE SIZE USED PRIO
/swap/swapfile file 16G 0B -2
/dev/zram0 partition 2.8G 429.5M 100└─$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe rw rootflags=subvol=@ cryptdevice=UUID=63984f23-816d-48d8-9493-119bf15c9a26:root zswap.enabled=0 rootfstype=btrfs loglevel=3 amdgpu.dpm=1 lsm=landlock,lockdown,yama,apparmor,bpf apparmor=1 security=apparmor└─$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 swap 1 zram0 301b8baa-1e36-47d8-adcc-b425d552190a [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT32 38E3-7BAD 888.2M 13% /boot
└─nvme0n1p2 crypto_LUKS 2 63984f23-816d-48d8-9493-119bf15c9a26
└─root btrfs c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe 335.8G 29% /home
/var/log
/var/cache/pacman/pkg
/about my system
└─$ inxi -Fza
System:
Kernel: 6.18.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: hpet avail: acpi_pm parameters: BOOT_IMAGE=/vmlinuz-linux
root=UUID=c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe rw rootflags=subvol=@
cryptdevice=UUID=63984f23-816d-48d8-9493-119bf15c9a26:root
zswap.enabled=0 rootfstype=btrfs loglevel=3 amdgpu.dpm=1
lsm=landlock,lockdown,yama,apparmor,bpf apparmor=1 security=apparmor
Desktop: Hyprland v: 0.53.3 with: waybar tools: hypridle avail: hyprlock
vt: 1 dm: SDDM Distro: Aranya Marjara rolling
Machine:
Type: Laptop System: Hewlett-Packard product: HP 247 G8 Notebook PC v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Hewlett-Packard model: 85E0 v: 84.51 serial: <superuser required>
part-nu: 7J423PA#ACJ uuid: <superuser required> Firmware: UEFI vendor: AMI
v: F.68 date: 11/09/2022
Battery:
ID-1: BAT0 charge: 21.1 Wh (82.1%) condition: 25.7/25.7 Wh (100%)
volts: 12.12 min: 11.34 model: Hewlett-Packard Primary type: Li-ion
serial: <filter> charging: status: discharging cycles: N/A
CPU:
Info: model: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx bits: 64
type: MT MCP arch: Zen/Zen+ note: check gen: 1 level: v3 note: check
built: 2019 process: GF 12nm family: 0x17 (23) model-id: 0x18 (24)
stepping: 1 microcode: 0x8108109
Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB
desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1400 min/max: 1400/2100 boost: disabled scaling:
driver: acpi-cpufreq governor: schedutil cores: 1: 1400 2: 1400 3: 1400
4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 bogomips: 33535
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: ghostwrite status: Not affected
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: old_microcode status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; STIBP:
disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsa status: Not affected
Type: tsx_async_abort status: Not affected
Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega
Series / Radeon Mobile Series] vendor: Hewlett-Packard driver: amdgpu
v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie:
gen: 3 speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1
bus-ID: 04:00.0 chip-ID: 1002:15d8 class-ID: 0300 temp: 48.0 C
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
compositor: Hyprland v: 0.53.3 driver: X: loaded: modesetting
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: 1
Monitor-1: eDP-1 model: BOE Display 0x092c built: 2020 res: mode: 1366x768
hz: 60 scale: 100% (1) dpi: 112 gamma: 1.2 size: 310x170mm (12.17x6.85")
diag: 355mm (14") ratio: 16:9 modes: max: 1366x768 min: 640x480
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.4-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon Vega 8 Graphics
(radeonsi raven ACO DRM 3.64 6.18.7-arch1-1) device-ID: 1002:15d8
memory: 1.95 GiB unified: no
API: Vulkan v: 1.4.335 layers: 9 device: 0 type: integrated-gpu name: AMD
Radeon Vega 8 Graphics (RADV RAVEN) driver: mesa radv v: 25.3.4-arch1.1
device-ID: 1002:15d8 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-smi,radeontop
wl: nwg-displays,wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP
Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:15de class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Audio Coprocessor
vendor: Hewlett-Packard driver: snd_pci_acp3x v: kernel
alternate: snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci,
snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt,
snd_sof_amd_vangogh, snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel pcie: gen: 3
speed: 8 GT/s lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.18.7-arch1-1 status: kernel-api
tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.4.10 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: Hewlett-Packard driver: rtw88_8822ce v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:c822
class-ID: 0280
IF: wlp3s0 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-1:2 chip-ID: 0bda:b00c
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 3 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: yes pairing: yes
Drives:
Local Storage: total: 476.94 GiB used: 138.02 GiB (28.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 model: ABSSDNVMe512GB size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
tech: SSD serial: <filter> fw-rev: EDFB00.7 temp: 34.9 C scheme: GPT
Partition:
ID-1: / raw-size: 475.92 GiB size: 475.92 GiB (100.00%)
used: 137.89 GiB (29.0%) fs: btrfs dev: /dev/dm-0 maj-min: 253:0
mapped: root
ID-2: /boot raw-size: 1024 MiB size: 1022 MiB (99.80%)
used: 133.8 MiB (13.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 475.92 GiB size: 475.92 GiB (100.00%)
used: 137.89 GiB (29.0%) fs: btrfs dev: /dev/dm-0 maj-min: 253:0
mapped: root
ID-4: /var/log raw-size: 475.92 GiB size: 475.92 GiB (100.00%)
used: 137.89 GiB (29.0%) fs: btrfs dev: /dev/dm-0 maj-min: 253:0
mapped: root
Swap:
Kernel: swappiness: 100 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: file size: 16 GiB used: 0 KiB (0.0%) priority: -2
file: /swap/swapfile
ID-2: swap-2 type: zram size: 2.85 GiB used: 429.2 MiB (14.7%)
priority: 100 comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 49.0 C mobo: N/A gpu: amdgpu temp: 49.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 6 GiB note: est. available: 5.69 GiB used: 2.59 GiB (45.5%)
Processes: 298 Power: uptime: 1h 51m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 2.26 GiB services: upowerd Init: systemd
v: 259 default: graphical tool: systemctl
Packages: 1321 pm: nix-default pkgs: 0 pm: nix-sys pkgs: 0 pm: nix-usr
pkgs: 74 libs: 17 pm: pacman pkgs: 1226 libs: 302 tools: yay pm: flatpak
pkgs: 21 Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: kitty
inxi: 3.3.40some additional info:
-no Display manager
-Hyprland (starts with tty with the command "exec start-hyprland")
-haven't tried in LTS because in LTS brightness is other issue and, temps spike up etc, so never thought of trying it....
-no tlp, no power-profiles-daemon, no auto-cpufreq
-"Aranya-Marjara" (edited /etc/os/release and ntg else) is just a name. system is running Vanilla Arch with stock packages.
-I don't remember Hibernating while I was in Gentoo either
Edit
Re-wrote the post.
Last edited by 5hridhyan (Yesterday 18:46:55)
Offline
#2 2026-02-08 14:08:49
- 5hridhyan
- Member
- From: Asia
- Registered: 2025-12-25
- Posts: 217
Re: [SOLVED]HP 247 G8 [AMD]: low battery actions fail [Workaround]
Update, I added resume
┌──(shridhyan@Aranya-Marjara)-[~]
└─$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux root=UUID=c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe rw rootflags=subvol=@ cryptdevice=UUID=63984f23-816d-48d8-9493-119bf15c9a26:root zswap.enabled=0 rootfstype=btrfs loglevel=3 amdgpu.dpm=1 lsm=landlock,lockdown,yama,apparmor,bpf apparmor=1 security=apparmor resume=UUID=c0ae4a73-5088-4f7e-b497-ca1a4baa4dbe resume_offset=17159234https://0x0.st/PTA9.txt
I Got AMD TLB flush errors/warnings.
Manual Troubleshooting/results.
-I also tried this, even more weirder Hyprland crashed too, the Lesson, never "bruteforce" it!
echo disk | sudo tee /sys/power/state-tried manual hibernation for voodoo reason now, and it failed
└─$ systemctl hibernate
Call to Hibernate failed: Specified resume device is missing or is not an active swap deviceno wonder, offset was wrong, so ran this and I got exact offset for my BTRFS.
btrfs inspect-internal map-swapfile -r /swap/swapfileand replaced with matching offset, Manual Hibernation obviously works again.
-I did tried to disable zram and tried ntg changed, same behavior.
-also
└─$ cat /sys/power/resume
253:0-I Checked fwupdmgr. It reports "System Firmware" has no available updates on LVFS, so a native firmware fix via fwupd is out. I'm sticking with troubleshooting the kernel/driver side for now,
-After a long drama ntg changed, the working manual hibernation journal just a cross correction.
https://0x0.st/PTui.txt
-Edited Upower config and set it take action at 85 to rule out battery drops etc, kinda unexpected behavior I got confused if it hibernated or rebooted so which boot is mine now? anyways here are the both
https://0x0.st/PTS6.txt
https://0x0.st/PTSU.txt
-At this point Idk how to fix the "low battery hibernation" path correctly or anything wrong correctly, I also reverted Upower and I just kept resume and resume offset
-for my voodoo sanity check stressed so the battery could drain fast so I can test more, same behavior and at this point no matter 5% or 85%!!
-here we go again!
https://0x0.st/PTJu.txt
Edit
re-wrote the post for readibility
Last edited by 5hridhyan (Yesterday 10:08:26)
Offline
#3 2026-02-09 06:00:20
- 5hridhyan
- Member
- From: Asia
- Registered: 2025-12-25
- Posts: 217
Re: [SOLVED]HP 247 G8 [AMD]: low battery actions fail [Workaround]
I’ve stopped iterating on edits and switched the critical action to PowerOff instead of HybridSleep or Hibernate.
PowerOff completes, but consistently produces amdgpu TLB flush failed warnings:
logs: https://0x0.st/PTyI.txt
Edit
https://0x0.st/PTlX.txt
The cursed reality check: I just had a "natural" low-battery event while using Zen/YT/TOR-Browser, interestingly, the amdgpu TLB errors didn't appear in the logs this time. Instead, I got a massive stack trace involving libgallium and libxul (Firefox) getting stuck in a pthread_cond_wait.
the absurd theory: The GPU isn't always throwing a driver error; sometimes it just stops responding entirely. This leaves the software (Mesa/Firefox) hanging in a wait-loop while the system tries to kill the power.
who even imagined it would survive Gentoo and Arch installation!?
┌──(shridhyan@Aranya-Marjara)-[~]
└─$ sudo filefrag -v /swap/swapfile | grep -i extent
sudo hexdump -C /swap/swapfile | head
/swap/swapfile: 269 extents found
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000400 01 00 00 00 ff ff 3f 00 00 00 00 00 e0 08 b4 c8 |......?.........|
00000410 0a 54 48 9f 87 65 e4 aa ae 8a 89 9f 00 00 00 00 |.TH..e..........|
00000420 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000fd0 00 00 00 00 00 00 00 00 00 00 00 00 1c 96 fb 07 |................|
00000fe0 43 dc 09 01 00 00 00 00 04 00 00 00 53 57 41 50 |C...........SWAP|
00000ff0 53 50 41 43 45 32 53 57 41 50 53 50 41 43 45 32 |SPACE2SWAPSPACE2|
00001000 42 de 09 01 00 00 00 00 42 e0 09 01 00 00 00 00 |B.......B.......|┌──(shridhyan@Aranya-Marjara)-[~]
└─$ journalctl -b 2 | grep "hibernate"
Dec 04 20:44:36 archlinux systemd-hibernate-resume[784]: Reported hibernation image: ID=ubuntu VERSION_ID=24.04 kernel=6.14.0-36-generic UUID=1bab0b05-840b-4196-8456-9a231dc83918 offset=3360768
Dec 04 20:44:36 archlinux systemd-hibernate-resume[784]: HibernateLocation system identifier doesn't match currently running system, would not resume from it.
Dec 04 21:24:02 archlinux systemd[1]: systemd-hibernate-clear.service: Deactivated successfully.
┌──(shridhyan@Aranya-Marjara)-[~]
└─$ journalctl -b 3 | grep "hibernate"
Dec 04 21:24:34 archlinux systemd-hibernate-resume[784]: Reported hibernation image: ID=ubuntu VERSION_ID=24.04 kernel=6.14.0-36-generic UUID=1bab0b05-840b-4196-8456-9a231dc83918 offset=3360768
Dec 04 21:24:34 archlinux systemd-hibernate-resume[784]: HibernateLocation system identifier doesn't match currently running system, would not resume from it.
Dec 04 21:35:40 archlinux systemd[1]: systemd-hibernate-clear.service: Deactivated successfully.anyways created a fresh one!
the unfortunate summary
on this HP Ryzen platform, manual hibernation works reliably once resume and swap offsets are correct.
automatic low-battery actions (via upower [I tested with 85 as well as 5, same strange inconsistent behavior]) do not behave reliably ---- and the fact that the same TLB flush errors appear even during PowerOff!!
yeah I strongly suspect a firmware / ACPI issue, rather than a userspace configuration problem.
and the failures appear during power-state transitions when the kernel and drivers attempt to communicate with hardware that does not respond correctly.
Edit:
re-wrote post in order.
Last edited by 5hridhyan (Yesterday 18:53:37)
Offline