Bug 69983 - [r600g, bisected] Screen corruption in Firefox, World of Warcraft and other apps
Summary: [r600g, bisected] Screen corruption in Firefox, World of Warcraft and other apps
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
: 70068 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-09-30 21:39 UTC by Chris Rankin
Modified: 2013-10-08 08:58 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
screenshot attempting to show problem (1.02 MB, image/png)
2013-09-30 21:48 UTC, Chris Rankin
Details
Xorg.log with errors (50.18 KB, text/plain)
2013-10-01 01:44 UTC, Jos van Wolput
Details

Description Chris Rankin 2013-09-30 21:39:38 UTC
This commit is causing a patchy line of tiny little squares across one of the main diagonals on the screen (bottom-left to top-right):

68f6dec32ed5eede361f76c8dbdf897652659baf is the first bad commit
commit 68f6dec32ed5eede361f76c8dbdf897652659baf
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Sun Sep 22 21:45:23 2013 +0200

    r600g: move aux_context and r600_screen_clear_buffer to drivers/radeon
    
    This will be used in the next commit.

:040000 040000 9aa99663b074853ed4d88a5229ff88dfe2e8a0c4 f55eac99d036675f814a0465bf4c8f1e368054bd M	src
Comment 1 Chris Rankin 2013-09-30 21:48:33 UTC
Created attachment 86877 [details]
screenshot attempting to show problem

The corruption is of a flickering nature, which has made it difficult to capture. But you can hopefully see at least two little black squares which are definitely not supposed to be there.
Comment 2 Chris Rankin 2013-09-30 21:51:14 UTC
This is with a HD4890 (RV790).
Comment 3 Jos van Wolput 2013-10-01 01:42:22 UTC
Startng icedove/firefox with
OpenGL renderer string: Gallium 0.4 on AMD RS780
OpenGL version string: 2.1 Mesa 9.3.0-devel
commit mesa-68f6dec32ed5eede361f76c8dbdf897652659baf (bisected)
is causing a completely corrupted screen and xorg errors,
making mesa unusable.
Comment 4 Jos van Wolput 2013-10-01 01:44:16 UTC
Created attachment 86888 [details]
Xorg.log with errors
Comment 5 Jos van Wolput 2013-10-01 02:25:43 UTC
(In reply to comment #3)
> Startng icedove/firefox with...

This should be read 'Startng iceweasel' (Debian's Firefox), not icedove (Debian's Thunderbird).
Comment 6 Michel Dänzer 2013-10-01 10:15:41 UTC
Have you tried a clean build, i.e. after at least make clean?
Comment 7 Chris Rankin 2013-10-01 10:39:16 UTC
(In reply to comment #6)
> Have you tried a clean build, i.e. after at least make clean?

When I bisected this, I was performing "make distclean" each time.
Comment 8 Jos van Wolput 2013-10-01 11:17:51 UTC
(In reply to comment #6)
> Have you tried a clean build, i.e. after at least make clean?

Yes, I did make clean to get a clean build.
Comment 9 Jos van Wolput 2013-10-03 04:01:47 UTC
Same corrupted screen issue running /demos/cuberender, cubemap and dinoshade using mesa-68f6dec32ed5eede361f76c8dbdf897652659baf
Comment 10 Alex Deucher 2013-10-03 12:58:02 UTC
*** Bug 70068 has been marked as a duplicate of this bug. ***
Comment 11 Chris Rankin 2013-10-03 21:14:56 UTC
This issue is now fixed for me, presumably by:

commit b893bbf438e1924d5f47370b29421642e79b0221
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Thu Oct 3 16:39:50 2013 +0200

    r600g,radeonsi: create aux_context last
    
    This fixes a regression caused by 68f6dec32ed5eede361f76c8dbdf897652659baf.
Comment 12 Marek Olšák 2013-10-03 21:28:33 UTC
Ok, I'm closing this bug.
Comment 13 Jos van Wolput 2013-10-04 01:40:52 UTC


(In reply to comment #12)
> Ok, I'm closing this bug.

Thanks, demos running well, issue fixed!
Comment 14 Marc Dietrich 2013-10-04 08:53:51 UTC
confirmed fixed
Comment 15 Michel Dänzer 2013-10-08 08:58:53 UTC
*** Bug 70035 has been marked as a duplicate of this bug. ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.