Help diagnosing freeze

Hello everyone.

Since a couple days, my Fedora installation (on an HP laptop with Intel graphics), while working sometimes freezes. No key combination seems to work, the mouse pointer does not move.

What seems strange to me is that twice out of three episodes, I pressed the power keys an it went to sleep, and worked after resume. This never happened to me before: freeze was freeze, with no response at all.

When it happened there wasn’t animation on screen nor sound (neither a blinking cursor), so I cannot tell if it’s a input problem or a real freeze.

Can somebody help me to diagnose the problem? Something I can check after the resume?

Thank you
Ignazio

I’m using Fedora 40 Workstation, fully updated, kernel 6.10.3-200.fc40.x86_64, on HP 250 G7 Notebook PC, Intel® UHD Graphics (ICL GT1).

I will share journalctl on next event, I cannot remember the exact time of other events.

This means the kernel hasn’t crashed, but there is a power management software issue or a hardware fault. Does the screen freeze or go black? Next time it happens, see if the or lights respond. Check for firmware updates – there has been a move away from vendor-specific power management towards more universal standards, but that can require firmware changes by vendors.

There are other ways to filter journalctl output. I would try to identify a boot “offset” where the problem occurred and see if the -p (priority) option identifies the issue. You can also try to find linux power management events with keywords like “power” and “sleep” with the -g (grep) option. Example:

% journalctl --no-hostname -b -1 -g sleep |cat
Aug 13 11:25:21 kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
Aug 13 11:25:21 kernel: ACPI: button: Sleep Button [SLPB]
Aug 13 11:25:22 kernel: ata1.00: Features: Trust Dev-Sleep NCQ-sndrcv
Aug 13 11:25:22 kernel: ahci 0000:00:17.0: port does not support device sleep
Aug 13 11:25:25 systemd-logind[900]: Watching system buttons on /dev/input/event0 (Sleep Button)

You should provide the output from running inxi -Fzxx in a terminal as pre-formatted text (use the </> button at the top of the text entry panel) to allow others with similar hardware and issues to find this topic.

Thank you.

I could not identify journalctl log for the events, I will wait for the next evento or try harder later.

This is the output of inxi -Fzxx:

System:
  Kernel: 6.10.3-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Console: pty pts/0 wm: gnome-shell DM: GDM Distro: Fedora Linux 40
    (Workstation Edition)
Machine:
  Type: Laptop System: HP product: HP 250 G7 Notebook PC
    v: Type1ProductConfigId serial: <filter> Chassis: type: 10 serial: <filter>
  Mobo: HP model: 86C1 v: 89.35 serial: <filter> part-nu: 1F3N0EA#ABZ
    UEFI: Insyde v: F.33 date: 07/31/2020
Battery:
  ID-1: BAT1 charge: 15.5 Wh (42.5%) condition: 36.5/41.0 Wh (89.0%)
    volts: 12.2 min: 11.3 model: COMPAL PABAS0241231 serial: <filter>
    status: charging
CPU:
  Info: quad core model: Intel Core i5-1035G1 bits: 64 type: MT MCP
    arch: Ice Lake rev: 5 cache: L1: 320 KiB L2: 2 MiB L3: 6 MiB
  Speed (MHz): avg: 587 high: 1245 min/max: 400/3600 cores: 1: 1053 2: 1245
    3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 bogomips: 19046
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Iris Plus Graphics G1 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-11 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4,
    HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:8a56
  Device-2: Cheng Uei Precision Industry (Foxlink) HP TrueVision HD Camera
    driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-5:3
    chip-ID: 05c8:03d2
  Display: server: X.Org v: 24.1.2 with: Xwayland v: 24.1.2
    compositor: gnome-shell driver: dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96
  Monitor-1: eDP-1 model: BOE Display 0x095e res: 1366x768 dpi: 102
    diag: 395mm (15.5")
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.1.5 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel UHD Graphics (ICL GT1)
    device-ID: 8086:8a56
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:34c8
  API: ALSA v: k6.10.3-200.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.7 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: 4000 bus-ID: 01:00.0 chip-ID: 10ec:8168
  IF: eno1 state: down mac: <filter>
  Device-2: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
    vendor: Hewlett-Packard driver: rtw_8821ce v: N/A pcie: speed: 2.5 GT/s
    lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:c821
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth 4.2 Adapter driver: btusb v: 0.8 type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-10:4 chip-ID: 0bda:b00a
  Report: btmgmt ID: hci0 rfk-id: 7 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 4.2 lmp-v: 8
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
    v: 3.0 bus-ID: 00:17.0 chip-ID: 8086:282a
Drives:
  Local Storage: total: 238.47 GiB used: 80.56 GiB (33.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLQ256HAJD-000H1
    size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 33.9 C
Partition:
  ID-1: / size: 172.01 GiB used: 80.16 GiB (46.6%) fs: btrfs
    dev: /dev/nvme0n1p5
  ID-2: /boot size: 973.4 MiB used: 304.9 MiB (31.3%) fs: ext4
    dev: /dev/nvme0n1p4
  ID-3: /boot/efi size: 256 MiB used: 104.1 MiB (40.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 172.01 GiB used: 80.16 GiB (46.6%) fs: btrfs
    dev: /dev/nvme0n1p5
Swap:
  ID-1: swap-1 type: zram size: 7.54 GiB used: 393 MiB (5.1%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 54.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.54 GiB used: 4.55 GiB (60.3%) igpu: 60 MiB
  Processes: 363 Power: uptime: 1d 10m wakeups: 6 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: pm: flatpak pkgs: 13 Compilers: gcc: 14.2.1 Shell: Bash
    v: 5.2.26 running-in: gnome-terminal inxi: 3.3.34

BIOS updates are often resolve power management glitches.

There is a 2024 BIOS update. You should be able to install it using linux fwupdtool. Run sudo fwupdtool get-updates to list available updates.

Thank you very much. fwdupdtool does not update the firmware, and since the changelog only mentions security updates I don’t know if it’s worth to reinstall Windows to update the BIOS.

Also, my computer didn’t freeze in the meantime.

But maybe I discovered something: a “freeze” happened while using multitouch gesture on the touchpad: somehow, it didn’t register the release of a finger and seemed frozen until I put it back on and off. Maybe that’s what happened, with unwanted small touch?

If I have any news, I will report them here.

Thank you.

I can’t tell from this why fwupdtool “does not update the firmware”. Does it not find BIOS updates? Does it find updates but won’t install them? The installation fail? On my system, some firmware updates are held in a “prepared/waiting” statue until some other updates arrive, so there can be dependency issues.

Most vendors have ways to install firmware updates without windows, usually as a bootable image intended to be put on a USB stick. On vendor-specific sites I have seen workarounds such as booting a Windows installer to update firmware.
Many security issues stem from bugs that can affect normal operation, so you should not ignore them.

This sounds feasible. Sometimes there are settings that help with such problems – Allow the touchpad to keep working while a keyboard button is pressed, which can be changed using Gnome settings. Unfortunately, Gnome Settings may only show the most commonly used options, and some misbahaviour is only seen on certain hardware. If you don’t find a setting that helps with your issue, try Gnome and vendor-specific forums.

This is the output:

Loading…                 [*********                              ]12:01:44.806 FuUsbDevice          failed to parse platform BOS descriptor: failed to parse: no supported platform version: did not find magic
Loading…                 [************************************** ]
Devices with no available firmware updates: 
 • MZVLQ256HAJD-000H1
 • System Firmware
 • Unifying Receiver
Devices with the latest available firmware version:
 • UEFI dbx
No updates available for remaining devices

I will look for Windows-less way to install the BIOS; HP seems to only provide a Windows exe (for my previous PC there was a FreeDOS bootable image but I dont’ find it).

Thank you for the help with multitouch, I will look into it.

HP does participate in the Linux firmware project. You should probably contact HP Support in case they just need prompting to make the update available.