Hardware video acceleration corrupts video
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 383
- Avg merge
- 8d 18h
- Merged PRs (30d)
- 4
Description
## System information
- CPU information: Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
- GPU information: Mesa Intel® Xe Graphics
- Display server if rendering to display: X
## Issue behavior
I have tried to open videos with different codecs and found that H264, H265 and VP9 videos when hardware-accelerated are corrupted while AV1 videos aren't.
How reproducible:
You can reproduce opening H264, H265 and VP9 videos on VLC using hardware accelerated decode by GPU.
Steps to Reproduce:
1. Open VLC (default settings) and open a H264, H265 or VP9 video
### Describe the current behavior
Actual results:
VLC playing a corrupted video.
### Describe the expected behavior
Expected results:
VLC playing the video stream right.
## Debug information
I have already reported this bug con bugzilla with number 1933143. See this link https://bugzilla.redhat.com/show_bug.cgi?id=1933143
## Debug information
- What's libva/libva-utils/gmmlib/media-driver version?
libva info: VA-API version 1.9.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_9
libva info: va_openDriver() returns 0
- Could you confirm whether GPU hardware exist or not by `ls /dev/dri`?
by-path card0 renderD128
- Could you provide vainfo log if possible by `vainfo >vainfo.log 2>&1`?
[vainfo.log](https://github.com/intel/media-driver/files/7075837/vainfo.log)
- Could you provide libva trace log if possible? Run cmd `export LIBVA_TRACE=/tmp/libva_trace.log` first then execute the case.
[libva_trace.log.093346.thd-0x000015d3.txt](https://github.com/intel/media-driver/files/7075825/libva_trace.log.093346.thd-0x000015d3.txt)
[libva_trace.log.094509.thd-0x000018aa.txt](https://github.com/intel/media-driver/files/7075826/libva_trace.log.094509.thd-0x000018aa.txt)
[libva_trace.log.094649.thd-0x000019c6.txt](https://github.com/intel/media-driver/files/7075827/libva_trace.log.094649.thd-0x000019c6.txt)
[libva_trace.log.094724.thd-0x00001a32.txt](https://github.com/intel/media-driver/files/7075828/libva_trace.log.094724.thd-0x00001a32.txt)
[libva_trace.log.094758.thd-0x00001a7c.txt](https://github.com/intel/media-driver/files/7075829/libva_trace.log.094758.thd-0x00001a7c.txt)
[libva_trace.log.094821.thd-0x00001a8d.txt](https://github.com/intel/media-driver/files/7075830/libva_trace.log.094821.thd-0x00001a8d.txt)
- Could you attach dmesg log if it's GPU hang by `dmesg >dmesg.log 2>&1`?
[dmesg.log](https://github.com/intel/media-driver/files/7075838/dmesg.log)
- Do you want to contribute a PR? (yes/no):
What is PR? If its meaning is to give other information, I am here to be asked for.
Contributor guide
Assessment
This issue has not been assessed yet.