Skip to main content ↑ ↓
Topic: Complete Sytem Freeze (Read 388 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Complete Sytem Freeze

MPV Freezes Whole System

I left computr running for the night. Nothing was running just a few tabs on Konsole with nothing using much CPU (no mining or compiling). Then in the morning I unlocked it, closed all tabs (they close very slow in KDE's Konsole, escaping too).

Opened Konsole (ctlr+alt+T - it should be, KDE doesn't use this shortcut by default) and played a video via mpv. After 10 min. I got TOTAL SYSTEM FREEZE. Pressed "f" to exit full screen and then "q" to quit. "F" exited full screen (one could see Konsole behind from which I had started mpv with video), but "q" got me TOTAL SYSTEM FREEZE. :(


Xorg
Intel Only
Vaapi was used.

Re: Complete Sytem Freeze

Reply #1 –
is this related to this post?

Re: Complete Sytem Freeze

Reply #2 –
Probably this post is more relevant, especially the advice from gripped from the mpv FAQ's:
https://forum.artixlinux.org/index.php/topic,5763.msg35996.html#msg35996

I tried vdpau (Nvidia equivalent) with VLC once, I got some weird multicolored blocks onscreen before the OS froze. It only ever worked with some hardware, not all. Work on it was never really completed and now I guess it is falling into disuse?
More info for VAAPI, which I haven't actually tried but is the Intel equivalent project
https://www.intel.com/content/www/us/en/developer/articles/technical/linuxmedia-vaapi.html
https://wiki.archlinux.org/title/Hardware_video_acceleration

If you start VLC on the command line there are some misleading messages about cannot find vdpau / vaapi which give the impression it should be installed:
Code: [Select]
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
[00007f40fc006a10] gl gl: Initialized libplacebo v5.264.1 (API v264)
[00007f40fc006a10] gl gl: Initialized libplacebo v5.264.1 (API v264)
[00007f40fc006a10] glconv_vaapi_x11 gl error: vaInitialize: unknown libva error
[00007f40fc006a10] glconv_vaapi_drm gl error: vaInitialize: unknown libva error
[00007f40fc006a10] glconv_vaapi_drm gl error: vaInitialize: unknown libva error

Edit:
If you look at the first link above, that has further links showing where vaapi and related software is developed and discussed, and there does seem to be continuing work on the project, so you might get more knowledgeable and helpful advice there, if you can provide them with full details of your problems and the hardware you are using. After all, me saying I tried vdpau once and it didn't work isn't really much use for you to fix vaapi if you are keen to try!  ;D

Re: Complete Sytem Freeze

Reply #4 –
Quote from: ####### – on
Probably this post is more relevant, especially the advice from gripped from the mpv FAQ's:
https://forum.artixlinux.org/index.php/topic,5763.msg35996.html#msg35996

I tried vdpau (Nvidia equivalent) with VLC once, I got some weird multicolored blocks onscreen before the OS froze. It only ever worked with some hardware, not all. Work on it was never really completed and now I guess it is falling into disuse?
More info for VAAPI, which I haven't actually tried but is the Intel equivalent project
https://www.intel.com/content/www/us/en/developer/articles/technical/linuxmedia-vaapi.html
https://wiki.archlinux.org/title/Hardware_video_acceleration

If you start VLC on the command line there are some misleading messages about cannot find vdpau / vaapi which give the impression it should be installed:
Code: [Select]
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
[00007f40fc006a10] gl gl: Initialized libplacebo v5.264.1 (API v264)
[00007f40fc006a10] gl gl: Initialized libplacebo v5.264.1 (API v264)
[00007f40fc006a10] glconv_vaapi_x11 gl error: vaInitialize: unknown libva error
[00007f40fc006a10] glconv_vaapi_drm gl error: vaInitialize: unknown libva error
[00007f40fc006a10] glconv_vaapi_drm gl error: vaInitialize: unknown libva error

Edit:
If you look at the first link above, that has further links showing where vaapi and related software is developed and discussed, and there does seem to be continuing work on the project, so you might get more knowledgeable and helpful advice there, if you can provide them with full details of your problems and the hardware you are using. After all, me saying I tried vdpau once and it didn't work isn't really much use for you to fix vaapi if you are keen to try!  ;D

That post was for scaling. New gpu-next is not quite ready for Intel. The new method doesn't use  hardware  for scaling and color scaling.

This is about system freeze, I do not know how it happened. I had to revert to reisuo and reisub. The only thing that comes to mind that somehow a few scripts in Konsole tabs may be related, but I doubt it, they use fzf and there had been some changes in fzf. I noticed it some time ago and it doesn't behave like it used to be in terms of spanning of multiple instances and using small amount of cpu. It wasen't like this  in one or two iterations before . It shuld search and turn off without staying on. I don't know what caused the system freeze, but as soon as I fired mpv (video from a hardrive that I always play) within 10 min. I got total system freeze. I hope this clarifies the issue.

Re: Complete Sytem Freeze

Reply #5 –
If a normal program segfaults, ie illegally accesses memory used elsewhere in a manner that causes unintentional damage to the operation of the program, it just stops with an error message, because it is running in userspace and the error is caught by the kernel and glibc or whatever. The OS continues. But with low level stuff like the kernel and graphics drivers, the OS freezes if something bad happens because there is no safety net to catch their errors. So most likely this is a graphics related freeze. To narrow down the cause, experiment by trying mpv without vaapi, and perhaps play the video in vlc and any other similar players, with and without vaapi if possible. These kinds of freezes often occur with a random element depending on if the bytes somewhere in the memory that get trashed were previously assigned for anything useful or not.

Re: Complete Sytem Freeze

Reply #6 –
I used to have a similar issue that was caused by a GPU crash which made the system unusable and even cut off the TTYs. The system may be still up and running but it cannot display anything.

First of all, can you reliably reproduce the issue?

If you can (and the system is not completely frozen), you may be able to access it via SSH (provided you configured it) and check both dmesg and /var/log/messages (or the equivalent in your system).

Hopefully this helps a bit!

Re: Complete Sytem Freeze

Reply #7 –
I finally figured out what is the culprit. Kernel and KDE is NOT compatible with f2fs and xfs. Since this is related to my other post and this not belong to Software, but now in kernel, I explain it here:

https://forum.artixlinux.org/index.php/topic,5886.0.html