FS#42221 - [libdrm] System freezes - VA API in VLC
Attached to Project:
Arch Linux
Opened by nfnty (nfnty) - Thursday, 02 October 2014, 20:51 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 08 October 2014, 12:44 GMT
Opened by nfnty (nfnty) - Thursday, 02 October 2014, 20:51 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 08 October 2014, 12:44 GMT
|
Details
System freezes when using VA API as hardware-accelerated
decoder in VLC. Sometimes only the pointer can be moved,
although stuttering heavily.
After downgrading to libdrm 2.4.56-1: No more system freezes. Video codec H264 - MPEG-4 AVC (part 10) (h264) displays fine. Video codec H264 - MPEG-4 AVC (part 10) (avc1) has severe artifacts and after terminating VLC 1 to 2 kernel threads called systemd-coredum each have 100% load. These threads linger for several minutes. Package versions: linux 3.16.3-1 vlc 2.1.5-3 libva 1.4.0-1 libva-intel-driver 1.4.0-1 libdrm 2.4.58-1 xf86-video-intel 2.99.916-3 Running on i3-2348M. |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 08 October 2014, 12:44 GMT
Reason for closing: Fixed
Additional comments about closing: kernel 3.17
Wednesday, 08 October 2014, 12:44 GMT
Reason for closing: Fixed
Additional comments about closing: kernel 3.17
Comment by Andreas Radke (AndyRTR) -
Friday, 03 October 2014, 06:52 GMT
Comment by nfnty (nfnty) -
Saturday, 04 October 2014, 21:28 GMT
Comment by nfnty (nfnty) - Sunday,
05 October 2014, 14:31 GMT
Comment by nfnty (nfnty) - Sunday,
05 October 2014, 15:27 GMT
Comment by nfnty (nfnty) - Tuesday,
07 October 2014, 16:40 GMT
Comment by nfnty (nfnty) - Tuesday,
07 October 2014, 16:54 GMT
Report this upstream!
VA-API works great with mpv and XBMC with libdrm 2.4.58-1. No
freezes, artifacts or stuttering. Maybe this problem is specific
to VLC?
Might not be specific to VLC. XBMC randomly froze once last night
when trying to play a video with codec "H.264 / AVC / MPEG-4 AVC /
MPEG-4 part 10" and codec id 28 using VA-API.
Reported upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=84688
This bug should be fixed with kernel 3.17.
Can confirm; Kernel 3.17 solves the problem.