SPRADI3 June   2024 AM625 , AM62P , AM67 , AM67A , AM68 , AM68A , AM69 , AM69A , DRA829J , DRA829J-Q1 , DRA829V , DRA829V-Q1 , TDA4AEN-Q1 , TDA4AH-Q1 , TDA4AL-Q1 , TDA4AP-Q1 , TDA4APE-Q1 , TDA4VE-Q1 , TDA4VEN-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VM , TDA4VM-Q1 , TDA4VP-Q1 , TDA4VPE-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Common Issues with Graphics Applications
    1. 2.1 System or Application Freeze
      1. 2.1.1 Typical Kernel Panic Logs
    2. 2.2 Screen Tearing
    3. 2.3 Artifacts or Corruption in the Screen
    4. 2.4 Blank Screen
    5. 2.5 Low Frame Rate
    6. 2.6 GPU Driver Logs and Hardware Recoveries
      1. 2.6.1 Typical GPU HWR Logs
  6. 3Support Flow for Graphics Issues
    1. 3.1 Submit Preliminary Description
    2. 3.2 Determine if the Issue Reproduces on TI EVM
    3. 3.3 Provide Follow-Up Testing and Logs
  7. 4Tools for GPU Driver Debug
    1. 4.1 Driver Status in Linux® DebugFS
    2. 4.2 Driver AppHints
    3. 4.3 PVR Log Dump Collection
    4. 4.4 Adding Log Groups to Firmware Traces
    5. 4.5 Disabling the Driver After Hardware Recovery
    6. 4.6 Disable Autoloading of the GPU Driver
  8. 5Integrating Patched GPU Drivers
    1. 5.1 UM Libraries Installation
    2. 5.2 KM Libraries Installation
    3. 5.3 Post-Installation Steps
  9. 6Summary

PVR Log Dump Collection

As mentioned in Section 2.6, the HWR logs contain logs for the GPU driver and firmware. To collect the logs from the GPU, a utility is available called pvrlogdump. pvrlogdump comes with the GPU driver installation. The utility saves the logs in the /tmp directory by default and output the names of the files so the files are easy to extract. Alongside the files generated by pvrlogdump, it is also useful to share the console of the execution of the app as this shows when the HWR happened. The following is an example of the pvrlogdump command output:​​

root@j721s2-evm:~# pvrlogdump
Checking driver state ............... initialised 
Checking for debugfs ................ found 
Checking for lockdep ................ not found 
Checking for ftrace ................. not found 
Checking for firmware log groups .... not found 
There are no AppHints enabled in /etc/powervr.ini or in debugfs for any of the firmware log groups. Unless 'pvrdebug' tool was used for that purpose there will be no information in firmware log. Please consider enabling some of the firmware log groups before the problem occurs. 
Dumping data ........................ 
[ 163.767302] PVR_K: 1005: User requested PVR debug info 
[ 163.772711] PVR_K: 1005: ------------[ PVR DBG: START (High) ]------------ 
… 
[ 164.363015] PVR_K: 1005: ------------[ PVR DBG: END ]------------ 
done
Archiving data ...................... done 
File /tmp/pvrlogdump_2402262237.txt.gz was created.