(In reply to comment #22)
> Ok, I managed to get the dmesg output using piglit and the r600.tests, so I
> think this confirms 325422c49449acdd8df1eb2ca8ed81f7696c38cc as culprit.

Can you identify the a specific piglit test that triggers the fault messages
and attach the fault messages it generates?