Now that a graphics-related issue has been identified, the following information needs to be collected for the next steps of the debug. The more complete this information is presented, the smoother the debug experience.

1. Symptoms: What are the symptoms seen at the system level? At the console output? Section 2 detailed many of the common symptoms, and some can happen at the same time.
2. Set up: How is the GPU used? Is the display a native Linux® display, or is this a remote display? Is this a vision processing pipeline in a RTOS plus Linux setup? What is the GPU driver and Software Development Kit (SDK) version used?
3. Scenario: In what situation did this issue occur? Where there other processors running? Is the processing part of a larger vision processing pipeline or similar? Does the issue occur immediately after starting the application or after some time?
4. Reproducibility: How easily can the issue be reproduced? Does the issue only happen on one board or does the issue happen on all boards? How long does the issue take to reproduce?
5. Recovery: Does the issue recover without any intervention, or does the system stay in a crashed state?
6. Logging: Please share all of the logs in the console and in the kernel (dmesg), or note that there are no logs when the failure happens.

This preliminary information is required throughout the debug and goes in tandem with the logs to identify the issue.