https://bugs.freedesktop.org/show_bug.cgi?id=54002

--- Comment #2 from Thomas Rohloff v10lator@myway.de 2012-08-24 11:34:30 UTC --- Created attachment 66060 --> https://bugs.freedesktop.org/attachment.cgi?id=66060 radeontop

I just noticed that the GPU usage is very high (radeontop), so high that the desktop gets unusable in the LOW power profile. It spins between 20 and 80%

https://bugs.freedesktop.org/show_bug.cgi?id=54002

--- Comment #4 from Thomas Rohloff v10lator@myway.de 2012-08-24 12:11:38 UTC --- Created attachment 66062 --> https://bugs.freedesktop.org/attachment.cgi?id=66062 Xorg.0.log

(In reply to comment #3)

Can you isolate which update caused the problem?

I don't remember the version of mesa before and it's not in the emerge.log (gentoo). But I'll try my best to get it. If you have any ideas feel free to share them.

https://bugs.freedesktop.org/show_bug.cgi?id=54002

--- Comment #6 from Thomas Rohloff v10lator@myway.de 2012-08-24 12:44:33 UTC --- Okay, found a good commit and am bisecting. :)

https://bugs.freedesktop.org/show_bug.cgi?id=54002

--- Comment #8 from Thomas Rohloff v10lator@myway.de 2012-08-24 17:00:50 UTC --- If I set "pp_jimenezmlaa_color" to "0" everything is fine.

https://bugs.freedesktop.org/show_bug.cgi?id=54002

--- Comment #10 from Thomas Rohloff v10lator@myway.de 2012-08-24 17:39:49 UTC --- with both, ""pp_jimenezmlaa_color" and "pp_jimenezmlaa" setted to 0 it seems to be fixed completely. But I don't think activated MLAA should cause this.

https://bugs.freedesktop.org/show_bug.cgi?id=54002

--- Comment #11 from Vadim Girlin ptpzz@yandex.ru 2012-08-24 18:26:44 UTC --- (In reply to comment #7)

Created attachment 66074 [details] My .drirc

The bad commit is e7c177ec9e37d0c406c3b0ef8f228159d7ee5d69 ( st/dri: use driver name for driconf section lookup ) which sounds a bit weird. So I'm uploading my .drirc

That commit makes mesa use real driver name ("r600") when it selects the device section from drirc. Before that patch "dri" was used instead. As long as your drirc doesn't have "dri" section (there are "r600" and "dri2"), then I think it was not used at all, so defaults were used. And now the settings from the "r600" section were activated after that commit.

Probably you tried to enable MLAA earlier, that's why it was turned on in your drirc (but not active before that patch). I'm not sure how the MLAA should work, but your screenshot looks really antialiased, so probably it works now.

You might want to try removing/renaming '.drirc' to use default settings again, if you aren't sure how to restore correct settings manually. Also you might use 'driconf' utility that will create '.drirc' with default settings for you if it doesn't exist.

https://bugs.freedesktop.org/show_bug.cgi?id=54002

--- Comment #13 from Vadim Girlin ptpzz@yandex.ru 2012-08-24 19:24:25 UTC --- (In reply to comment #12)

(In reply to comment #11) I fully understand what the commit did. But I don't think MLAA should make the screen look like this, else nobody should enable it, so it's useless. Don't you agree?

I think it should be enabled for some graphical applications only (games etc), not for all applications by default. drirc allows to use different settings for specific apps based on the executable name.

https://bugs.freedesktop.org/show_bug.cgi?id=54002

Alex Deucher agd5f@yahoo.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NOTABUG

--- Comment #15 from Alex Deucher agd5f@yahoo.com 2012-08-25 13:09:46 UTC --- (In reply to comment #14)

MLAA seems to be doing exactly as under Windows. I saw the same thing with Catalyst on Windows 7 mostly in Messenger. See http://www.sevenforums.com/software/182520-msn-live-messenger-browser-proble..., http://www.sevenforums.com/software/182520-msn-live-messenger-browser-proble... and comments in http://www.sevenforums.com/graphic-cards/166423-text-looks-if-water-has-been...

So, for some reason, MLAA doesn't behave as expected with some applications (2D content where it "shouldn't")

When you turn on MLAA in your drirc, it applies to all 3D applications. If you are using a 3D compositor (compiz, gnome shell, kwin, etc.) as a window manager, it will also apply to X apps. If you want to enable MLAA you'll need to specify what apps you want it to apply to in your drirc.