You are not logged in.

Pages: 1

#1 2026-08-24 06:36:49

Virtue
Member
Registered: 2026-08-24
Posts: 9

VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

GPU: AMD Radeon RX 580 (polaris10)
Kernel: linux-zen 7.1.9 (also tested on 7.1.6)
Mesa: 26.2.1 (also tested on 26.1.6)
Firmware: linux-firmware-amdgpu 20260810 (also tested on 20260622)
WM: Hyprland 0.56.2
So my problem is whenever I start recording through OBS, my monitor turns black for couple of seconds then turns on with huge artifacts. At this state i cannot interact with system at all. I can only reboot through power button. x264 works perfectly fine. I've tried downgrading mesa, kernel, firmware, ffmpeg, obs. None of it fixed the issue. I also tried other window manager (Niri) it didn't fixed the issue as well. The issue started happening after i update the system. Before that VAAPI worked perfectly fine.

Any ideas what else to check? Is it a known amdgpu regression?

Offline

#2 2026-08-24 14:12:29

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,879

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Do you get this w/ the zen kernel?

I can only reboot through power button.

Avoid that at all costs, see whether https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB works (this will ideally preserve the journal that are then ideally full of errors telling us what's going on)
nb. you'll have to explicitly enable that before the freeze!

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2026-08-24 18:32:01

Virtue
Member
Registered: 2026-08-24
Posts: 9

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Hey, i do get this with zen kernel and without it (normal linux kernel). I also wanna mention out that steam recordings with hardware acceleration doesn't entirely break the system. It only turns game black whenever I'm recording. I'm gonna try and see if freezing the system with obs and rebooting with REISUB will show the journal logs.

Offline

#4 2026-08-24 20:40:34

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,879

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Sorry my fingers betrayed my brain, I meant whether you get this w/ the LTS kernel, https://archlinux.org/packages/core/x86_64/linux-lts/

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2026-08-25 04:34:13

Virtue
Member
Registered: 2026-08-24
Posts: 9

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Hey, mate, it happens that when i booted through lts kernel and tried to record with obs my system didn't freeze with huge artifacts, infact my Hyprland booted me into save mode and now i think i got correct logs. About LTS kernel - yes i get same problem with it, but it happens that behavior changed a little bit. Let me send logs right here:

                                                     #1  0x00007f69dd711a57 ppoll (libc.so.6 + 0x111a57)
                                                     #2  0x00007f69dd500f59 n/a (libglib-2.0.so.0 + 0x63f59)
                                                     #3  0x00007f69dd501055 g_main_context_iteration (libglib-2.0.so.0 + 0x64055)
                                                     #4  0x00007f69de296f32 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x496f32)
                                                     #5  0x00007f69ddf8f664 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x18f664)
                                                     #6  0x00007f69de0b7ce2 _ZN7QThread4execEv (libQt6Core.so.6 + 0x2b7ce2)
                                                     #7  0x00007f69ddd6c951 n/a (libQt6DBus.so.6 + 0x39951)
                                                     #8  0x00007f69de1721eb n/a (libQt6Core.so.6 + 0x3721eb)
                                                     #9  0x00007f69dd6980a2 n/a (libc.so.6 + 0x980a2)
                                                     #10 0x00007f69dd72080c n/a (libc.so.6 + 0x12080c)
                                                     
                                                     Stack trace of thread 7947:
                                                     #0  0x00007f69dd71e4ed syscall (libc.so.6 + 0x11e4ed)
                                                     #1  0x00007f69dd52e15e g_cond_wait (libglib-2.0.so.0 + 0x9115e)
                                                     #2  0x00007f69dd4c352d n/a (libglib-2.0.so.0 + 0x2652d)
                                                     #3  0x00007f69dd538017 n/a (libglib-2.0.so.0 + 0x9b017)
                                                     #4  0x00007f69dd537b14 n/a (libglib-2.0.so.0 + 0x9ab14)
                                                     #5  0x00007f69dd6980a2 n/a (libc.so.6 + 0x980a2)
                                                     #6  0x00007f69dd72080c n/a (libc.so.6 + 0x12080c)
                                                     
                                                     Stack trace of thread 7948:
                                                     #0  0x00007f69dd6a0952 n/a (libc.so.6 + 0xa0952)
                                                     #1  0x00007f69dd711a57 ppoll (libc.so.6 + 0x111a57)
                                                     #2  0x00007f69dd500f59 n/a (libglib-2.0.so.0 + 0x63f59)
                                                     #3  0x00007f69dd501055 g_main_context_iteration (libglib-2.0.so.0 + 0x64055)
                                                     #4  0x00007f69dd5010a2 n/a (libglib-2.0.so.0 + 0x640a2)
                                                     #5  0x00007f69dd537b14 n/a (libglib-2.0.so.0 + 0x9ab14)
                                                     #6  0x00007f69dd6980a2 n/a (libc.so.6 + 0x980a2)
                                                     #7  0x00007f69dd72080c n/a (libc.so.6 + 0x12080c)
                                                     
                                                     Stack trace of thread 7949:
                                                     #0  0x00007f69dd6a0952 n/a (libc.so.6 + 0xa0952)
                                                     #1  0x00007f69dd711a57 ppoll (libc.so.6 + 0x111a57)
                                                     #2  0x00007f69dd500f59 n/a (libglib-2.0.so.0 + 0x63f59)
                                                     #3  0x00007f69dd501217 g_main_loop_run (libglib-2.0.so.0 + 0x64217)
                                                     #4  0x00007f69db65aed4 n/a (libgio-2.0.so.0 + 0x11fed4)
                                                     #5  0x00007f69dd537b14 n/a (libglib-2.0.so.0 + 0x9ab14)
                                                     #6  0x00007f69dd6980a2 n/a (libc.so.6 + 0x980a2)
                                                     #7  0x00007f69dd72080c n/a (libc.so.6 + 0x12080c)
                                                     ELF object binary architecture: AMD x86-64

Last edited by Virtue (2026-08-25 06:33:05)

Offline

#6 2026-08-25 04:38:01

Virtue
Member
Registered: 2026-08-24
Posts: 9

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Let me actually put it into paste.dev:
https://pastes.dev/wH61Fjf6iY
theres multiple errors i encountered in logs, but this one is for OBS

Offline

#7 2026-08-25 04:42:02

Virtue
Member
Registered: 2026-08-24
Posts: 9

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

I also wanna mention out that this issue does NOT occur on windows.

Offline

#8 2026-08-25 06:08:43

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,879

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Please use [code][/code] tags. Edit your post in this regard.
Also please don't bump, edit your previous post to mend it when nobody has replied so far.
Then, please, use a pastebin service that provides access to the raw text, see the 1st link below of a couple of options.

Process 7686 (obs) of user 1000 dumped core.

    Stack trace of thread 7714:
    #0  0x00007f7054a256ea abort (libc.so.6 + 0x256ea)
    #1  0x00007f70113ecd23 n/a (libgallium-26.2.1-arch1.1.so + 0xbecd23)
    #2  0x00007f70113f1fc5 n/a (libgallium-26.2.1-arch1.1.so + 0xbf1fc5)
    #3  0x00007f7010ddcd21 n/a (libgallium-26.2.1-arch1.1.so + 0x5dcd21)
    #4  0x00007f7010e2794d n/a (libgallium-26.2.1-arch1.1.so + 0x62794d)
    #5  0x00007f7054a980a2 n/a (libc.so.6 + 0x980a2)
    #6  0x00007f7054b2080c n/a (libc.so.6 + 0x12080c)

obs aborted, that's a controlled failure and typically comes w/ a message - check your system journal and/or try to run obs from an interactive shell.

Finally please post the output of 

vainfo

Can you encode w/ vaapi using ffmpeg?
https://wiki.archlinux.org/title/FFmpeg#VA-API (nb. on hybrid GPU systems you'll have to pay attention to the render device)

Edit

I also wanna mention out that this issue does NOT occur on windows.

Ceterum censeo: 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Last edited by seth (2026-08-25 06:09:16)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2026-08-25 07:03:48

Virtue
Member
Registered: 2026-08-24
Posts: 9

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Sorry! My bad, here's the output of vainfo:

Trying display: wayland
vainfo: VA-API version: 1.24 (libva 2.24.0)
vainfo: Driver version: Mesa Gallium driver 26.2.1-arch1.1 for AMD Radeon RX 580 Series (radeonsi, polaris10, ACO, DRM 3.64, 6.18.46-1-lts)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc

Yes, i can record with ffmpeg (on LTS kernel). And the file with video does create and plays perfectly fine. Here's the output of command if you need it

ffmpeg -threads 1 -f lavfi -i testsrc=duration=5:size=1920x1080:rate=30 -vaapi_device /dev/dri/renderD128 -vcodec h264_vaapi -vf format='nv12|vaapi,hwupload' output.mp4                                   ↵ 0

ffmpeg version n9.0.1 Copyright (c) 2000-2026 the FFmpeg developers
  built with gcc 16 (GCC)
  configuration: --prefix=/usr --disable-debug --disable-static --disable-stripping --enable-amf --enable-avisynth --enable-cuda-llvm --enable-lto --enable-fontconfig --enable-frei0r --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-lcms2 --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libdav1d --enable-libdrm --enable-libdvdnav --enable-libdvdread --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libharfbuzz --enable-libiec61883 --enable-libjack --enable-libjxl --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libplacebo --enable-libpulse --enable-librav1e --enable-librsvg --enable-librubberband --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpl --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-nvdec --enable-nvenc --enable-opencl --enable-opengl --enable-shared --enable-vapoursynth --enable-version3 --enable-vulkan --disable-decoder=magicyuv
  libavutil      61.  1.101 / 61.  1.101
  libavcodec     63.  1.101 / 63.  1.101
  libavformat    63.  1.101 / 63.  1.101
  libavdevice    63.  1.101 / 63.  1.101
  libavfilter    12.  1.101 / 12.  1.101
  libswscale     10.  1.101 / 10.  1.101
  libswresample   7.  1.101 /  7.  1.101
Input #0, lavfi, from 'testsrc=duration=5:size=1920x1080:rate=30':
  Duration: N/A, start: 0.000000, bitrate: N/A
  Stream #0:0: Video: wrapped_avframe, rgb24, 1920x1080 [SAR 1:1 DAR 16:9], 30 fps, 30 tbr, 30 tbn
Stream mapping:
  Stream #0:0 -> #0:0 (wrapped_avframe (native) -> h264 (h264_vaapi))
Press [q] to stop, [?] for help
[h264_vaapi @ 0x55beb1c61e80] No quality level set; using default (20).
Output #0, mp4, to 'output.mp4':
  Metadata:
    encoder         : Lavf63.1.101
  Stream #0:0: Video: h264 (High) (avc1 / 0x31637661), nv12(tv, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 30 fps, 15360 tbn
    Metadata:
      encoder         : Lavc63.1.101 h264_vaapi
[out#0/mp4 @ 0x55beb1c61440] video:283KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 0.505811%
frame=  150 fps= 82 q=-0.0 Lsize=     284KiB time=00:00:05.00 bitrate= 465.4kbits/s speed=2.73x elapsed=0:00:01.83

Here's the errors it gave before killing OBS

░░ Subject: Процесс 7476 (obs) сбросил дамп памяти
авг 25 12:04:57 archlinux xdg-desktop-portal-gtk[1073]: Error reading events from display: Обрыв канала
авг 25 12:04:57 archlinux hyprpolkitagent[1003]: The Wayland connection broke. Did the Wayland compositor die?
авг 25 12:04:57 archlinux kernel: xdg-desktop-por[1145]: segfault at 0 ip 0000562ea0275b87 sp 00007fff5c465290 error 4 in xdg-desktop-portal-hyprland[5cb87,562ea0221000+8b000] likely on CPU 15 (core 8, sock>
авг 25 12:04:57 archlinux systemd[881]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit UNIT has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
авг 25 12:04:57 archlinux kernel: Code: 62 48 8b 3b e8 2a a7 ff ff 48 8b 45 c8 64 48 2b 04 25 28 00 00 00 0f 85 b6 fe ff ff 48 8b 05 40 d4 05 00 48 8b 33 48 8b 40 08 <48> 8b 38 48 81 c4 c8 00 00 00 5b 41 5c>
авг 25 12:04:57 archlinux systemd-coredump[7853]: Process 998 (hyprpaper) of user 1000 terminated abnormally with signal 6/ABRT, processing...
авг 25 12:04:57 archlinux systemd[881]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'exit-code'.
авг 25 12:04:57 archlinux systemd-coredump[7859]: Process 1145 (xdg-desktop-por) of user 1000 terminated abnormally with signal 11/SEGV, processing...
авг 25 12:04:57 archlinux systemd[1]: Started Process Core Dump (PID 7853/UID 0).
░░ Subject: Запуск юнита systemd-coredump@3-4-7853_7854-0.service завершен
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Процесс запуска юнита systemd-coredump@3-4-7853_7854-0.service был завершен.
░░ 
░░ Результат: done.
авг 25 12:04:57 archlinux systemd[1]: Started Process Core Dump (PID 7859/UID 0).
░░ Subject: Запуск юнита systemd-coredump@4-5-7859_7860-0.service завершен
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ Процесс запуска юнита systemd-coredump@4-5-7859_7860-0.service был завершен.
░░ 
░░ Результат: done.
авг 25 12:04:57 archlinux systemd[881]: hyprpolkitagent.service: Main process exited, code=exited, status=255/EXCEPTION
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ An ExecStart= process belonging to unit UNIT has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 255.
авг 25 12:04:57 archlinux systemd[881]: hyprpolkitagent.service: Failed with result 'exit-code'.

Sorry for Russian language!
Also yes i disabled fast boot in windows (not bios) and rebooted 2 times.
Do you have any ideas what the issue could be?

Last edited by Virtue (2026-08-25 07:17:23)

Offline

#10 2026-08-25 07:25:33

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,879

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Do you have any ideas what the issue could be?

Do you have an abort message from OBS?
Do you enforce https://archlinux.org/packages/extra/x8 … an-radeon/ through https://wiki.archlinux.org/title/Hardwa … lkan_Video ?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2026-08-25 07:42:26

Virtue
Member
Registered: 2026-08-24
Posts: 9

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Doesn't seems like i have an abort message

12:04:04.271: Crash or unclean shutdown detected
12:04:05.607: [Safe Mode] Safe mode launch selected, loading third-party plugins is disabled
12:04:05.608: Platform: Wayland
12:04:05.608: CPU Name: Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz
12:04:05.608: CPU Speed: 3300.000MHz
12:04:05.609: Physical Cores: 10, Logical Cores: 20
12:04:05.609: Physical Memory: 32008MB Total, 26871MB Free
12:04:05.609: Kernel Version: Linux 6.18.46-1-lts
12:04:05.609: Distribution: "Arch Linux" Unknown
12:04:05.609: Desktop Environment: Hyprland (Hyprland)
12:04:05.609: Session Type: wayland
12:04:05.610: Current Date/Time: 2026-08-25, 12:04:05
12:04:05.610: Browser Hardware Acceleration: true
12:04:05.610: Qt Version: 6.11.2 (runtime), 6.11.1 (compiled)
12:04:05.610: Portable mode: false
12:04:05.610: Safe Mode enabled.
12:04:05.658: OBS 32.2.2 (linux)
12:04:05.658: ---------------------------------
12:04:05.660: ---------------------------------
12:04:05.660: audio settings reset:
12:04:05.660: 	samples per sec: 48000
12:04:05.660: 	speakers:        1
12:04:05.660: 	max buffering:   960 milliseconds
12:04:05.660: 	buffering type:  dynamically increasing
12:04:05.665: ---------------------------------
12:04:05.665: Initializing OpenGL...
12:04:05.665: Using EGL/Wayland
12:04:05.749: Initialized EGL 1.5
12:04:05.776: Loading up OpenGL on adapter AMD AMD Radeon RX 580 Series (radeonsi, polaris10, ACO, DRM 3.64, 6.18.46-1-lts)
12:04:05.776: OpenGL loaded successfully, version 4.6 (Core Profile) Mesa 26.2.1-arch1.1, shading language 4.60
12:04:05.827: ---------------------------------
12:04:05.827: video settings reset:
12:04:05.827: 	base resolution:   1920x1080
12:04:05.827: 	output resolution: 1920x1080
12:04:05.827: 	downscale filter:  Bicubic
12:04:05.827: 	fps:               60/1
12:04:05.827: 	format:            NV12
12:04:05.827: 	YUV mode:          Rec. 709/Partial
12:04:05.827: NV12 texture support enabled
12:04:05.827: P010 texture support not available
12:04:05.830: Audio monitoring device:
12:04:05.830: 	name: По умолчанию
12:04:05.830: 	id: default
12:04:05.833: ---------------------------------
12:04:05.836: Failed to load 'en-US' text for module: 'decklink-captions.so'
12:04:05.839: Failed to load 'en-US' text for module: 'decklink-output-ui.so'
12:04:05.843: A DeckLink iterator could not be created.  The DeckLink drivers may not be installed
12:04:05.843: Failed to initialize module 'decklink.so'
12:04:05.844: Skipping module 'frontend-tools', not on safe list
12:04:05.891: [pipewire] Available capture sources:
12:04:05.891: [pipewire]     - Monitor source
12:04:05.891: [pipewire]     - Window source
12:04:05.902: v4l2loopback not installed, virtual camera not registered
12:04:05.954: VAAPI: API version 1.24
12:04:05.954: FFmpeg VAAPI H264 encoding supported
12:04:05.962: FFmpeg VAAPI AV1 encoding not supported
12:04:05.969: FFmpeg VAAPI HEVC encoding supported
12:04:05.993: os_dlopen(libnvidia-encode.so.1->libnvidia-encode.so.1): libnvidia-encode.so.1: невозможно открыть разделяемый объектный файл: Нет такого файла или каталога
12:04:05.993: 
12:04:05.993: NVENC not supported
12:04:05.993: Failed to initialize module 'obs-nvenc.so'
12:04:06.055: Skipping module 'obs-websocket', not on safe list
12:04:06.066: ---------------------------------
12:04:06.066:   Loaded Modules:
12:04:06.066:     text-freetype2.so
12:04:06.066:     rtmp-services.so
12:04:06.066:     obs-x264.so
12:04:06.066:     obs-webrtc.so
12:04:06.066:     obs-vst.so
12:04:06.066:     obs-transitions.so
12:04:06.066:     obs-qsv11.so
12:04:06.066:     obs-outputs.so
12:04:06.066:     obs-libfdk.so
12:04:06.066:     obs-filters.so
12:04:06.066:     obs-ffmpeg.so
12:04:06.066:     linux-v4l2.so
12:04:06.066:     linux-pulseaudio.so
12:04:06.066:     linux-pipewire.so
12:04:06.066:     linux-jack.so
12:04:06.066:     linux-capture.so
12:04:06.066:     linux-alsa.so
12:04:06.066:     image-source.so
12:04:06.066:     decklink-output-ui.so
12:04:06.066:     decklink-captions.so
12:04:06.066: ---------------------------------
12:04:06.067: ---------------------------------
12:04:06.067: Available Encoders:
12:04:06.067:   Video Encoders:
12:04:06.067: 	- ffmpeg_svt_av1 (SVT-AV1)
12:04:06.067: 	- ffmpeg_aom_av1 (AOM AV1)
12:04:06.067: 	- ffmpeg_vaapi_tex (FFmpeg VAAPI H.264)
12:04:06.067: 	- hevc_ffmpeg_vaapi_tex (FFmpeg VAAPI HEVC)
12:04:06.067: 	- obs_x264 (x264)
12:04:06.067:   Audio Encoders:
12:04:06.067: 	- ffmpeg_aac (FFmpeg AAC)
12:04:06.067: 	- ffmpeg_opus (FFmpeg Opus)
12:04:06.067: 	- ffmpeg_pcm_s16le (FFmpeg PCM (16 бит))
12:04:06.067: 	- ffmpeg_pcm_s24le (FFmpeg PCM (24 бита))
12:04:06.067: 	- ffmpeg_pcm_f32le (FFmpeg PCM (32 бита с пл. тчк.))
12:04:06.067: 	- ffmpeg_alac (FFmpeg ALAC (24 бита))
12:04:06.067: 	- ffmpeg_flac (FFmpeg FLAC (16 бит))
12:04:06.067: 	- libfdk_aac (libfdk AAC)
12:04:06.067: ==== Startup complete ===============================================
12:04:06.130: All scene data cleared
12:04:06.130: ------------------------------------------------
12:04:06.136: Device for 'Audio Output Capture' source Звук раб. стола is also used for audio monitoring.
12:04:06.136: Deduplication logic is being applied to all monitored sources.
12:04:06.136: pulse-input: Server name: 'PulseAudio (on PipeWire 1.6.8) 15.0.0'
12:04:06.137: pulse-input: Audio format: s24le, 48000 Hz, 2 channels
12:04:06.137: pulse-input: Sample format s24le not supported by OBS,using float32le instead for recording
12:04:06.137: pulse-input: Started recording from 'alsa_output.usb-MSI_MSI_MAESTRO_300_Gaming_Headset_000000000000-00.analog-stereo.monitor' (default)
12:04:06.137: [Loaded global audio device]: 'Звук раб. стола'
12:04:06.137: pulse-input: Server name: 'PulseAudio (on PipeWire 1.6.8) 15.0.0'
12:04:06.138: pulse-input: Audio format: s16le, 48000 Hz, 1 channels
12:04:06.138: pulse-input: Started recording from 'alsa_input.usb-MSI_MSI_MAESTRO_300_Gaming_Headset_000000000000-00.mono-fallback' (default)
12:04:06.138: [Loaded global audio device]: 'Микр/доп'
12:04:06.138: PipeWire initialized
12:04:06.140: Switched to scene 'Сцена'
12:04:06.140: ------------------------------------------------
12:04:06.140: Loaded scenes:
12:04:06.140: - scene 'Сцена':
12:04:06.140:     - source: 'Захват экрана (PipeWire)' (pipewire-screen-capture-source)
12:04:06.140: ------------------------------------------------
12:04:06.152: Device for 'Audio Output Capture' source Звук раб. стола is also used for audio monitoring.
12:04:06.152: Deduplication logic is being applied to all monitored sources.
12:04:06.223: [pipewire] Screencast session created
12:04:06.684: adding 21 milliseconds of audio buffering, total audio buffering is now 21 milliseconds (source: Звук раб. стола)
12:04:06.684: 
12:04:06.748: adding 21 milliseconds of audio buffering, total audio buffering is now 42 milliseconds (source: Микр/доп)
12:04:06.748: 
12:04:07.097: [pipewire] Asking for monitor and window
12:04:07.101: [pipewire] source selected, setting up screencast
12:04:07.107: [pipewire] Server version: 1.6.8
12:04:07.107: [pipewire] Library version: 1.6.8
12:04:07.107: [pipewire] Header version: 1.6.8
12:04:07.108: [pipewire] Created stream 0x5592643f5730
12:04:07.108: [pipewire] Stream 0x5592643f5730 state: "connecting" (error: none)
12:04:07.108: [pipewire] Playing stream 0x5592643f5730
12:04:07.108: [pipewire] Stream 0x5592643f5730 state: "paused" (error: none)
12:04:07.133: [pipewire] Negotiated format:
12:04:07.133: [pipewire]     Format: 12 (Spa:Enum:VideoFormat:BGRA)
12:04:07.133: [pipewire]     Modifier: 0x0
12:04:07.133: [pipewire]     Size: 1920x1080
12:04:07.133: [pipewire]     Framerate: 0/1
12:04:07.136: [pipewire] Negotiated format:
12:04:07.136: [pipewire]     Format: 12 (Spa:Enum:VideoFormat:BGRA)
12:04:07.136: [pipewire]     Modifier: 0xffffffffffffff
12:04:07.136: [pipewire]     Size: 1920x1080
12:04:07.136: [pipewire]     Framerate: 0/1
12:04:07.189: [pipewire] Stream 0x5592643f5730 state: "streaming" (error: none)
12:04:39.968: ---------------------------------
12:04:39.968: [FFmpeg VAAPI encoder: 'advanced_video_recording'] settings:
12:04:39.968: 	device:       /dev/dri/by-path/pci-0000:03:00.0-render
12:04:39.968: 	rate_control: CBR
12:04:39.968: 	profile:      100
12:04:39.968: 	level:        -99
12:04:39.968: 	qp:           0
12:04:39.968: 	bitrate:      6000
12:04:39.968: 	maxrate:      6000
12:04:39.968: 	keyint:       120
12:04:39.968: 	width:        1920
12:04:39.968: 	height:       1080
12:04:39.968: 	b-frames:     0
12:04:39.968: 	ffmpeg opts:  
12:04:39.968: 
12:04:39.982: libfdk_aac encoder created
12:04:39.982: libfdk_aac bitrate: 160, channels: 1
12:04:39.987: ==== Recording Start ===============================================
12:04:39.987: [mp4 output: 'adv_file_output'] Writing Hybrid MP4/MOV file '/home/-----/2026-08-25_12-04-39.mp4'...

I censored my hostname here. Look what else i found.

авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: ring vce0 timeout, signaled seq=767, emitted seq=768
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu:  Process obs pid 7476 thread obs:cs0 pid 7497
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!. Source:  1
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: suspend of IP block <vce_v3_0> failed -22
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: BACO reset
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
авг 25 12:04:56 archlinux kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400200000).
авг 25 12:04:56 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: VRAM is lost due to GPU reset!
авг 25 12:04:56 archlinux kernel: [drm] UVD and UVD ENC initialized successfully.
авг 25 12:04:57 archlinux kernel: [drm] VCE initialized successfully.
авг 25 12:04:57 archlinux kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(1) succeeded!
авг 25 12:04:57 archlinux systemd-coredump[7815]: Process 7476 (obs) of user 1000 terminated abnormally with signal 6/ABRT, processing...
авг 25 12:04:57 archlinux systemd[1]: Created slice Slice /system/systemd-coredump.

Again, sorry for text being russian. This is the errors that caused the issue most likely. I found them in journal log
Concerning about vulkan question. I do have vulkan-radeon installed. Here's the package output:

 pacman -Qs vulkan-radeon
local/lib32-vulkan-radeon 1:26.2.1-1
    Open-source Vulkan driver for AMD GPUs - 32-bit
local/vulkan-radeon 1:26.2.1-1
    Open-source Vulkan driver for AMD GPUs

However, i dont enforce Vulkan Video via environment variables. Obs is targeting standard ffmpeg VA-API.

Last edited by Virtue (2026-08-25 07:49:00)

Offline

#12 2026-08-25 14:01:59

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,879

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

12:04:04.271: Crash or unclean shutdown detected

the log starts after the abort for a restart. But since it happens after a (successful) GPU reset the likely reason is that it cannot handle the lost GL context.

Is there more ahead of the kernel messages indicating the reset reason?
In doubt post your complete system journal for the boot after such crash 

sudo journalctl -b | nc termbin.com 9999

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2026-08-25 15:51:48

Virtue
Member
Registered: 2026-08-24
Posts: 9

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

Hey, here's the link: https://termbin.com/7laf (i redacted some things for privacy reasons)
Main reason I'm testing this on LTS kernel is because it the only way crash makes me enter Hyprland safe mode for further debugging.
and here's the amdgpu dump (hopefully this will help you)

 **** AMDGPU Device Coredump ****
version: 1
kernel: 6.18.46-1-lts
module: amdgpu
time: 283.373340932
process_name: obs PID: 3581

SOC Information
SOC Device id: 26591
SOC PCI Revision id: 231
SOC Family: 130
SOC Revision id: 1
SOC External Revision id: 81

SOC Memory Information
real vram size: 8589934592
visible vram size: 268435456
gtt size: 8338522112

GDS Config
gds: total size: 65536
gds: compute partition size: 65536
gds: gws per compute partition: 64
gds: os per compute partition: 16

HW IP Version Information

IP Firmwares
VCE feature version: 0, fw version: 0x351a0300
UVD feature version: 0, fw version: 0x01821000
GMC feature version: 0, fw version: 0x03b4dc40
ME feature version: 49, fw version: 0x000000a7
PFP feature version: 49, fw version: 0x000000fe
CE feature version: 49, fw version: 0x0000008c
RLC feature version: 1, fw version: 0x0000011e
RLC SRLC feature version: 0, fw version: 0x00000000
RLC SRLG feature version: 0, fw version: 0x00000000
RLC SRLS feature version: 0, fw version: 0x00000000
RLCP feature version: 0, fw version: 0x00000000
RLCV feature version: 0, fw version: 0x00000000
MEC feature version: 49, fw version: 0x000002da
MEC2 feature version: 49, fw version: 0x000002da
IMU feature version: 0, fw version: 0x00000000
PSP SOS feature version: 0, fw version: 0x00000000
PSP ASD feature version: 0, fw version: 0x00000000
TA XGMI feature version: 0x00000000, fw version: 0x00000000
TA RAS feature version: 0x00000000, fw version: 0x00000000
TA HDCP feature version: 0x00000000, fw version: 0x00000000
TA DTM feature version: 0x00000000, fw version: 0x00000000
TA RAP feature version: 0x00000000, fw version: 0x00000000
TA SECURE DISPLAY feature version: 0x00000000, fw version: 0x00000000
SMC feature version: 0, program: 0, fw version: 0x00171100 (23.17.0)
SDMA0 feature version: 31, firmware version: 0x0000003a
SDMA1 feature version: 0, firmware version: 0x0000003a
VCN feature version: 0, fw version: 0x00000000
DMCU feature version: 0, fw version: 0x00000000
DMCUB feature version: 0, fw version: 0x00000000
PSP TOC feature version: 0, fw version: 0x00000000
MES_KIQ feature version: 0, fw version: 0x00000000
MES feature version: 0, fw version: 0x00000000
VPE feature version: 0, fw version: 0x00000000

VBIOS Information
vbios name       : 113-MSITV341MH.970
vbios pn         : 113-V34122-X3
vbios version    : 254935553
vbios ver_str    : 015.050.002.001.000000
vbios date       : 2020/03/30 03:46

Ring timed out details
IP Type: 4 Ring Name: vce0

[gfxhub] Page fault observed
Faulty page starting at address: 0x0000000000000000
Protection fault status register: 0x0

IP Dump
Ring buffer information
ring name: gfx
Rptr: 0x100 Wptr: 0x100 RB mask: 7ff
Ring size in dwords: 2048
Ring contents
Offset 	Value
0x0 	0xc0032200
0x4 	0x401080
0x8 	0xff
0xc 	0x0
0x10 	0x2b
0x14 	0xc0053c00
0x18 	0x113
0x1c 	0x401040
0x20 	0xff
0x24 	0x1fafc
0x28 	0xffffffff
0x2c 	0x4
0x30 	0xc0033700
0x34 	0x40100000
0x38 	0x556
0x3c 	0x0
0x40 	0xf5fff00

Offline

#14 2026-08-25 16:56:09

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,879

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

The dump will be mostly interesting for https://gitlab.freedesktop.org/drm/amd/ … ge_size=20
There's a nullpointer resolution, it seems.
And the entire session goes down, but obs induces the GPU reset, so that checks out
https://gitlab.freedesktop.org/drm/amd/ … items/5595 looks related - assuming the offending patch might have been backported into LTS, can you try an older kernel from the https://wiki.archlinux.org/title/Arch_Linux_Archive ?

Also, does obs work on some simple Xorg session (eg. openbox will do) - or  sway?
(The screen recording on wayland requires an xdg-desktop-portal service, so that will matter, not sure whether weston provides such)

And just for the records: What is the hyper-frequent "u 1" shell script?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#15 2026-08-25 17:59:59

Virtue
Member
Registered: 2026-08-24
Posts: 9

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

So, i suppose its just a bug, huh. About the "u 1" shell script. Its a basically watches for tray items to appear. I fixed its being constantly sending messages now. I hope the patch will get merged soon. For now i'll just wait. Thank you very much for helping me. Is there anything i need to do to close this topic or make it officially solved?

Last edited by Virtue (2026-08-25 18:01:12)

Offline

#16 2026-08-25 19:02:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,879

Re: VAAPI hardware encoding hard-freeze system on kernel 7.19-zen

We don't know that yet - can/have you tried an older kernel (that is not the LTS kernel because I don't trust these bugs not being backported)?
Or alternatively the suggested patch?

Its a basically watches for tray items to appear.

Are you Looking for https://man.archlinux.org/man/udisksctl.1.en "monitor" ?
Or do you mean the systray?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB