Writing Good Bug Reports For Open-Source GPU Drivers

[phoronix]

Phoronix: Writing Good Bug Reports For Open-Source GPU Drivers

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...

http://www.phoronix.com/scan.php?pag...er-Bug-Reports

[jf33]

It's generally useful to have such guides, but Ian Romanick is doing the same silly thing everybody else does: He recommends using
glxinfo | grep "OpenGL version string"
This leads to confusion since the output is *not* two lines, but only
OpenGL version string: 3.0 Mesa 11.0.3

We had this on the phoronix forum only two days ago. http://www.phoronix.com/forums/forum...885#post828885

[tomtomme]

It's generally useful to have such guides, but Ian Romanick is doing the same silly thing everybody else does: He recommends using
glxinfo | grep "OpenGL version string"
This leads to confusion since the output is *not* two lines, but only
OpenGL version string: 3.0 Mesa 11.0.3

We had this on the phoronix forum only two days ago. http://www.phoronix.com/forums/forum...885#post828885

I would recommend:

glxinfo | grep "esa"
client glx vendor string: Mesa Project and SGI
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.0.0
OpenGL version string: 3.0 Mesa 11.0.0
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.0

or

glxinfo | grep "le v"
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.0.0
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.0

[ssokolow]

...or you could just use `glxinfo | egrep 'vendor|version'` or `glxinfo | grep -A3 vendor` depending on what you're trying to accomplish.

[asdfblah]

$ glxinfo | egrep 'render(er |ing)| version ' 

:P

[Bjotn]

"While most Phoronix readers should be well aware of the bug reporting procedures for Mesa drivers..." really?! Talk about slim target audience in that case.

/Bj?rn

[b15hop]

I found this article helpful because I have reported bugs on same game mods only to be rejected for poor reporting. I like that there are regression bug tracks as well as bisected bugs. Nice article. :-)

[Licaon]

No idea how it's set up on FD but can't all these be presented as needed/obligatory fields on the bug report form?
Yes, some will write garbage there ( although why did you bother making an account in the first place? ), but that blog post won't be seen by that many, ok Phoronix users saw it but the rest are playing until they hit a bug.

And since I mentioned "making account", that rubs me even worse, the main bug reporting place for me in the last years was Github, having seen the FD site asking me for an account there now made me go "pffft no Github no post". Yes I know Github is commercial/not-free/evil/whatever but a lot of devs can be easily reached/bugged there.

[Sarvatt]

It's generally useful to have such guides, but Ian Romanick is doing the same silly thing everybody else does: He recommends using
glxinfo | grep "OpenGL version string"
This leads to confusion since the output is *not* two lines, but only
OpenGL version string: 3.0 Mesa 11.0.3

We had this on the phoronix forum only two days ago. http://www.phoronix.com/forums/forum...885#post828885

They only want the mesa version number, rest doesn't matter.

[Ansla]

I'm pretty sure the renderer string is at least as useful as the version string. Maybe not for Intel, but at least for radeonsi it would be. And the blog post sounds like it should be concerning all drivers, not Intel only.

This is from an r600 card:
OpenGL renderer string: Gallium 0.4 on AMD CEDAR (DRM 2.41.0, LLVM 3.5.0)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.3