Bug 33918

Created attachment 42945 [details]
result with 6.13.2

Created attachment 42949 [details]
result with 6.14.0

As you can see, there are differences mostly under test07 and test14 where the shadows are rendered on everything instead of being rendered under the objects. There is also a difference with test10, but I think that's either related or of no importance for now (since the test completly fail to render anyway with prior version).

I should also add that I'm using the latest libdrm from git (which is mostly like 2.4.23 for radeon).

Any chance you can bisect xf86-video-ati and track down what caused this?  Also, what chip and 3D driver are you using?  Can you attach your dmesg output and xorg logs?

Onboard chip, RS780, which means it's an HD3200. When testing, I used the r600g driver.

I'll attach dmesg and xorg.log in a few minutes.

For the bisect, is there a way I could test without having to remove my deb package? Maybe, compiling, installing in a different folder and changing a path somewhere? Any suggestion?

Created attachment 42950 [details]
dmesg

Created attachment 42951 [details]
xorg.log

What I do is copy the *_drv.so files I compiled over the system ones (without removing the .deb), and when I'm finished testing I simply reinstall the deb to have everything restored.

As commented in bug 33738 I had similar corruption with xterm and eog, caused by commit ef9bfb262db7004bef3704e5d914687e50d3fca4.

Hmmm, strange. I can't seem to reproduce it with git repository and it might be related to one of two other patches introduced by Ubuntu packaging. I used the debian folder from previous 6.13.2 to base my own packaging. There are two patches included. I'll try to disable them one at a time and I'll come back soon to let you know if that helped.

By the way, thanks for sharing your procedure for testing git versions. That's what I thought was the way to go and it works great.

I removed both patches since Ubuntu removed one of them for Natty and the other was ment to be used to select gallium VS classic driver. For some reason, that last patch was causing the problem.

So the problem doesn't come from the radeon driver. We can close this bug. Sorry for taking your time and thank you for your help.

Just out of curiosity, can you point me to what patch was causing the problem?

Of course. Patch named 101_select_between_classic_and_gallium_dri.patch. Maybe it just needs to be modified to work properly. I was using the specified option (ForceGallium) in my xorg.conf, so it shouldn't have had any impact on the rendering when I was testing the r600g driver from git. But in fact, it was playing with both the rendering and the performances (the tests were running choppy).

(In reply to comment #14)
> Of course. Patch named 101_select_between_classic_and_gallium_dri.patch.

Please report this to Ubuntu. They took this approach despite my recommendation against it, and they should know it's causing problems.

(In reply to comment #15)
> (In reply to comment #14)
> > Of course. Patch named 101_select_between_classic_and_gallium_dri.patch.
> 
> Please report this to Ubuntu. They took this approach despite my recommendation
> against it, and they should know it's causing problems.

(In reply to comment #15)
> (In reply to comment #14)
> > Of course. Patch named 101_select_between_classic_and_gallium_dri.patch.
> 
> Please report this to Ubuntu. They took this approach despite my recommendation
> against it, and they should know it's causing problems.

Reported: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/715939

Thanks for everything