Laptop without nvidia hangs on reboot or shutdown

Hello, here are the logs:

https://pastebin.com/JbkRRyQ6 failed reboot

https://pastebin.com/J5TY8k6d failed shutdown

Here’s system info from inxi:

[yiyi@yiyi-hplaptop14dq2xxx ~]$ inxi -F
System:
  Host: yiyi-hplaptop14dq2xxx Kernel: 6.17.1-arch1-1 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.4.5 Distro: EndeavourOS
Machine:
  Type: Laptop System: HP product: HP Laptop 14-dq2xxx v: N/A
    serial: <superuser required>
  Mobo: HP model: 87FD v: 57.26 serial: <superuser required> UEFI: AMI
    v: F.33 date: 10/04/2023
Battery:
  ID-1: BAT0 charge: 34.5 Wh (90.9%) condition: 38/41 Wh (92.5%)
CPU:
  Info: dual core model: 11th Gen Intel Core i3-1115G4 bits: 64 type: MT MCP
    cache: L2: 2.5 MiB
  Speed (MHz): avg: 1034 min/max: 400/4100 cores: 1: 1034 2: 1034 3: 1034
    4: 1034
Graphics:
  Device-1: Intel Tiger Lake-LP GT2 [UHD Graphics G4] driver: i915 v: kernel
  Device-2: Chicony HP TrueVision HD Camera driver: uvcvideo type: USB
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: modesetting dri: iris gpu: i915
    resolution: 1366x768~60Hz
  API: EGL v: 1.5 drivers: iris,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.2.4-arch1.1
    renderer: Mesa Intel UHD Graphics (TGL GT2)
  API: Vulkan Message: No Vulkan data available.
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio
    driver: sof-audio-pci-intel-tgl
  API: ALSA v: k6.17.1-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.4.8 status: active
Network:
  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
    driver: rtw88_8821ce
  IF: wlan0 state: up mac: 74:97:79:99:64:9b
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb type: USB
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: N/A
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
Drives:
  Local Storage: total: 267.36 GiB used: 44.44 GiB (16.6%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: BC711 HFM256GD3JX013N
    size: 238.47 GiB
  ID-2: /dev/sda vendor: Kingston model: DataTraveler 3.0 size: 28.88 GiB
    type: USB
Partition:
  ID-1: / size: 45.82 GiB used: 19.05 GiB (41.6%) fs: ext4 dev: /dev/nvme0n1p5
  ID-2: /boot/efi size: 256 MiB used: 92.3 MiB (36.0%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A
  Fan Speeds (rpm): cpu: 0 fan-2: 0
Info:
  Memory: total: 8 GiB note: est. available: 7.4 GiB used: 2.82 GiB (38.1%)
  Processes: 209 Uptime: 25m Shell: Bash inxi: 3.3.39
[yiyi@yiyi-hplaptop14dq2xxx ~]$ 

I have KDE plasma installed and this is a freshly installed, fully updated system.

When i go to the start menu and click shutdown, or reboot, the computer has a 1/8 chance of getting stuck, hanging at the “reached target reboot” or “reached target shutdown” lines in the logs.

I do not have an Nvidia card, and I am running a laptop that only has integrated graphics. I cannot disable TPM, and the Bios does not let me change power settings. What can I do?

It also sometimes happens more often on reboot than shutdown. I have tried adding ACPI=force to the boot command line in grub, and I have also tried reinstalling the kernel with sudo pacman -S linux linux-headers, it also seems to happen in Cachyos.

Windows doesn’t do this and it runs fast enough but I can’t use it, and it also happens on fedora. Kubuntu does reboot and shutdown fine but it runs very slowly for some reason and Ubuntu sometimes does the same thing as endeavouros and also boots slowly with soft lockups during boot

It seems as if the logs end before what is shown on the poweroff screen is written to the logs, so i’m guessing the kernel? is hanging at shutdown or reboot? The poweroff screen does show “reached target shutdown” or “reached target poweroff” or something similar but apparently this is not written to the logs for some reason

It also seems to happen more often if I alternate between shutdown or reboot, like if I first shutdown then reboot then shutdown then reboot and so on

I do get kernel soft lockup messages at shutdown and reboot on debian on the power off screen when this happens so I guess the same thing is happening here.