You are not logged in.

#1 2025-11-29 21:34:13

hyprcall
Member
Registered: 2025-11-29
Posts: 2

Issue with my Hyprland session crashing

Good afternoon, I am a new user of Arch Linux and have been so for a little under a month. I've had a few issues but I managed to resolved them thanks to the documentation and other fixes I found. I have spent over 6 hours on this issue and so far I haven't found anyone else with the exact same issue. I will provide my setup and pertinent information so that hopefully someone more experienced can figure out the issue.

Setup:
OS       Arch Linux x86_64
Kernel   Linux 6.17.9-arch1-1
WM       Hyprland 0.52.1 (Wayl)
CPU      AMD Ryzen 7 7700 (8C/)
GPU      AMD Raphael [Integrat]
GPU      NVIDIA GeForce RTX 50]

Here is my current hyprland.conf env section:

env = NVD_BACKEND,direct
env = XDG_CURRENT_DESKTOP,Hyprland
env = XDG_SESSION_TYPE,wayland
env = GDK_BACKEND,wayland,x11
env = ELECTRON_OZONE_PLATFORM_HINT,auto
env = XCURSOR_SIZE,24
env = HYPRCURSOR_SIZE,24
env = AQ_MGPU_NO_EXPLICIT,1
env = AQ_NO_MODIFIERS,1

I enabled the last two envs in order to hopefully fix the issue. At first I thought it was brave browser that caused the crash but it seems to be a problem with either of 2 things. The EGL driver or the amdgpu
Here is a piece of the crash report from Hyprland:

[ERR] [EGL] Command eglDupNativeFenceFDANDROID errored out with EGL_BAD_PARAMETER (0x12300): eglDupNativeFenceFDANDROID
[ERR] eglDupNativeFenceFDANDROID failed
[ERR] renderer: Explicit sync failed, releasing resources
...
[CRITICAL]
==========================================================================================
ASSERTION FAILED!

glGetError at Opengl::end() returned GL_CONTEXT_LOST. Cannot continue until proper GPU reset handling is implemented.

at: line 921 in OpenGL.cpp

Here is a piece of my dmesg:

[  382.943679] amdgpu 0000:13:00.0: amdgpu: ring gfx_0.1.0 timeout, signaled seq=39914, emitted seq=39916
[  382.943681] amdgpu 0000:13:00.0: amdgpu:  Process Hyprland pid 1319 thread Hyprland:cs0 pid 1384
[  382.943682] amdgpu 0000:13:00.0: amdgpu: Starting gfx_0.1.0 ring reset
[  383.091280] amdgpu 0000:13:00.0: amdgpu: Ring gfx_0.1.0 reset failed

I'm pretty sure both of these are related. The issue seems to occur more when I utilize brave browser. Especially when I stress test by resizing constantly. However, while trying to write this post it also occured even when all I had opened was firefox. It seems to occur no matter what I do. Lastly I'm not sure if this could be related but I also have these errors on dmesg:

[ 1772.994384] amdgpu 0000:13:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80.
[ 1772.994386] amdgpu 0000:13:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present.
[ 1773.025710] amdgpu 0000:13:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present.
[ 1773.026144] amdgpu 0000:13:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present.
...
[ 1773.108738] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[ 1775.014970] amdgpu 0000:13:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present.
[ 1775.015406] amdgpu 0000:13:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present.
[ 1782.836923] amdgpu 0000:13:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present.
[ 1782.837360] amdgpu 0000:13:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present.

Here is a full journalctl -b -1 output

https://0x0.st/K45O.txt

I give all this because I genuinely don't know what could be causing the issue.

Last edited by hyprcall (2025-11-29 22:33:58)

Offline

#2 2025-12-04 14:42:22

hyprcall
Member
Registered: 2025-11-29
Posts: 2

Re: Issue with my Hyprland session crashing

If for some reason anyone ever looks at this again, I just want to say that I think I managed to pinpoint this issue down the amdgpu driver itself. This issue stopped happening once I switched to my Nvidia GPU and disabled the iGPU from BIOS. So if anyone else gets a similar error and is lucky to have another GPU then here you go.

Offline

Board footer

Powered by FluxBB