Bug 58491 - regression : r600g: work around ddx over alignment
Summary: regression : r600g: work around ddx over alignment
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-18 22:52 UTC by Bruno Jacquet (Xaapyks)
Modified: 2013-04-24 18:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Heroes of newerth corruption (155.93 KB, image/png)
2012-12-18 22:58 UTC, Bruno Jacquet (Xaapyks)
Details
Kernel log (81.25 KB, text/plain)
2012-12-18 23:03 UTC, Bruno Jacquet (Xaapyks)
Details

Description Bruno Jacquet (Xaapyks) 2012-12-18 22:52:41 UTC
Hi,

THis gives weird artifacts and my screen is not refreshed (need to alt tab several times to redraw it)

On HD 6870 and linux 3.7, 3c7d024c2671dac541b8f2daed55040f4fd5d62d radeon DDX.

d8287bac1fd4a77abc2db38de134f14176740d23 is the first bad commit
commit d8287bac1fd4a77abc2db38de134f14176740d23
Author: Jerome Glisse <jglisse@redhat.com>
Date:   Tue Dec 18 12:45:31 2012 -0500

    r600g: work around ddx over alignment
    
    This force surface allocated from ddx to be consider as height
    aligned on 8 and fix 1D->2D tiling transition that result from
    this.
    
    Signed-off-by: Jerome Glisse <jglisse@redhat.com>
    Reviewed-by: Marek Olšák <maraeo@gmail.com>

:040000 040000 9363ec48ccf6fdf72dd5500a25f89f987c66eb18 91abd9cb2eeab3d3324e4859776cf66e1934fa72 M      src
Comment 1 Bruno Jacquet (Xaapyks) 2012-12-18 22:58:08 UTC
Created attachment 71768 [details]
Heroes of newerth corruption
Comment 2 Jerome Glisse 2012-12-18 23:00:52 UTC
Kernel log please
Comment 3 Bruno Jacquet (Xaapyks) 2012-12-18 23:03:54 UTC
Created attachment 71772 [details]
Kernel log
Comment 4 Jerome Glisse 2012-12-18 23:08:43 UTC
YOu sure this is the kernel log after the issue show up ?
Comment 5 Bruno Jacquet (Xaapyks) 2012-12-18 23:15:09 UTC
Yes, I'm sure, I did another test to check, nothing gets added to my dmesg even after it shows up.
Comment 6 Jerome Glisse 2012-12-18 23:33:46 UTC
Can you try some other resolution than 1680x1040 and see if it has issue too. Specially something like 640x480
Comment 7 Bruno Jacquet (Xaapyks) 2012-12-18 23:39:03 UTC
Indeed, the resolution is the problem,

running any application in my system resolution (1680x1050) breaks rendering, something like 640x480 has no problems. It also corrupts things like glxgears while I resize them (from any resolution).
Comment 8 Bruno Jacquet (Xaapyks) 2012-12-18 23:45:07 UTC
(In reply to comment #7)
> Indeed, the resolution is the problem,
> 
> running any application in my system resolution (1680x1050) breaks
> rendering, something like 640x480 has no problems. It also corrupts things
> like glxgears while I resize them (from any resolution).

What I mean is, glxgears gets corrupted if I resize its window while it is running, it displays corrupted blocks
Comment 9 Andy Furniss 2012-12-19 11:03:56 UTC
(In reply to comment #8)
> (In reply to comment #7)
> > Indeed, the resolution is the problem,
> > 
> > running any application in my system resolution (1680x1050) breaks
> > rendering, something like 640x480 has no problems. It also corrupts things
> > like glxgears while I resize them (from any resolution).
> 
> What I mean is, glxgears gets corrupted if I resize its window while it is
> running, it displays corrupted blocks

I am also seeing this resize corruption on HD4890 (native res = 1920x1080).

Some demos seem to start corrupted - gearbox starts with band at top.

Projtex - less reliable, may need other demos run first, but may start totally corrupted then correct when a key is pressed.
Comment 10 Bruno Jacquet (Xaapyks) 2013-04-05 20:47:05 UTC
Should this stay open for reference?
Comment 11 Jerome Glisse 2013-04-24 18:59:26 UTC
Closing useless now


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.