Decode and Encode Debug Tool and surface dump

Overview

There are some tools could help us to collect driver and hardware information to debug issues, like Codechal dump as below.

Driver version

It's required to use Media driver release-internal or debug version for Codechal dump. Release version driver can not support this debug tool for performance and efficiency.

Registry key

Media starts to switch to device-based and modularized user setting from media driver commit 3cd7bff.

You could use below command to add the registry key file for debug as below. The media drive reads [Config] section and reports debug information in [report] section. All items in registry key file following the format "registry keys name"="keyValue".

$vim /etc/igfx_user_feature_next.txt 

[config]
    registry key1 = value1
[report]
    report key2 = value2

How to use Codec dump?

1. Firstly create a codechal dump file folder as below. Please make sure this folder is writable. The logs will be dumped into this file folder.

   $mkdir -p /data/codechal_dump
   

2. Add below keys to /etc/igfx_user_feature_next.txt under "[config]".

   1. "preAll" means the input surface of video processing, "postAll" means the output surface of video processing.
   2. If the input surface "preAll" is correct, but the output surface "postAll" is corrupted, probably the issue is in video processing driver.
   3. If the input surface "preAll" is corrupted, please check the component of the pipeline before video processing.
   4. If the output surface "postAll" is correct, please check the component of the pipeline after video processing.

   [config]
   outfileLocation=/data/vp_dump/
   dumpLocations=preAll,postAll