Writing Good Bug Reports For Open-Source GPU Drivers
Written by Michael Larabel in Mesa on 15 October 2015 at 09:30 AM EDT. 9 Comments
While most Phoronix readers should be well aware of the bug reporting procedures for Mesa drivers, Ian Romanick of Intel has written a lengthy blog post about the process of writing a "good" bug report for the open-source graphics drivers.

Among the good bug report recommendations are submitting the bug report against the right product/component, correctly describing the software/hardware in the system, thoroughly describing the problem encountered, adding annotations to the bug summary, bisecting the regression and responding to the bug report.

If you want to read more about writing a good open-source driver bug report, visit Ian's blog.
Related News
About The Author
Author picture

Michael Larabel is the principal author of Phoronix.com and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated benchmarking software. He can be followed via Twitter or contacted via MichaelLarabel.com.

Popular News This Week