Bug 58658

Sorry for the wrong mime-type. The screenshot is image/png, not text/plain.

I suspect this is a mesa 3D driver issue rather than a kernel issue.  Was this working in the past?  Can you bisect?

I'm not sure if it's mesa or kernel. Yes, it was working before last update (updated mesa + kernel).

I might be able to bisect later but atm my time is limited and as I don't even know what to bisect (kernel or mesa) it may take some time.

Bisected mesa.

This is a mesa bug caused by http://cgit.freedesktop.org/mesa/mesa/commit/?id=6532eb17baff6e61b427f29e076883f8941ae664

Can anybody move this to the right place or do I have to re-create the report (and if so: Where) ?

I can confirm that 6532eb17baff6e61b427f29e076883f8941ae664 causes problems.
glxgears start with black screen for few secs and then run at 0.8 FPS.
kernel radeon says smth like this:

[ 2077.626229] radeon 0000:01:00.0: GPU fault detected: 146 0x00239514
[ 2077.632491] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000
[ 2077.639970] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000

(In reply to comment #4)
> Bisected mesa.
> 
> This is a mesa bug caused by
> http://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=6532eb17baff6e61b427f29e076883f8941ae664
> 
> Can anybody move this to the right place or do I have to re-create the
> report (and if so: Where) ?

Thomas, does glxgears work on your setup?
btw, what gpu exactly do you have this bug with?

> does glxgears work on your setup?

I didn't test glxgears and am actually before this commit. Will try glxgears at my next bisecting round (for another bug).

> what gpu exactly do you have this bug with?

Sapphire Radeon HD 6950 (the one with dual BIOS and dual fans) with unlocked shaders (factory BIOS, not modded by me) and most likely with the locked BIOS, too, but there I can't tell really tell cause the GPU crashes right after compiz starts.

> kernel radeon says smth like this

I reported that, too. In fact I reported a few other bugs that seem all to be caused by this (and other) commits:
https://bugs.freedesktop.org/show_bug.cgi?id=58660
https://bugs.freedesktop.org/show_bug.cgi?id=58661
https://bugs.freedesktop.org/show_bug.cgi?id=58667

Help with bisecting is always welcome. :)

> does glxgears work on your setup?

I tested it now and either it runs just fine or crashes the GPU instantly ( https://bugs.freedesktop.org/show_bug.cgi?id=58667 ).

6532eb17baff6e61b427f29e076883f8941ae664 is not the cause of this bug (or damaged the hardware, but let's think positive for now) as I just had the exact same thing with a older mesa version. Also this seems to be connected with all other bug reports I listed above, especially the "GPU fault detected" from here: https://bugs.freedesktop.org/show_bug.cgi?id=58667

I'm still pre-bisecting (searching for a good commit) but as this bug sometimes needs hours to get triggered this may take very long.

I did go back till http://cgit.freedesktop.org/mesa/mesa/commit/?id=6c99f2101fbd3edb7d5899c44ca9d984a3c0f8b6 and the bug is still there (not the crashes directly, at least I couldn't trigger them, but the error messages) so either this bug is really old or it's not a mesa bug (or, but that would be really bad: It damaged the hardware).

Whoops, copy & pasting... The error messages + rendering errors occurred with that old commit.

I didn#t use r600g for some time now (used fglrx instead) but now this finally seems to be fixed! :)