Bug 18328 - xterm contents cleared by glxgears window above
Summary: xterm contents cleared by glxgears window above
Status: RESOLVED DUPLICATE of bug 20037
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Acceleration/EXA (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-31 14:26 UTC by Andy Furniss
Modified: 2009-02-11 04:01 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg log (38.71 KB, text/plain)
2008-10-31 14:26 UTC, Andy Furniss
no flags Details

Description Andy Furniss 2008-10-31 14:26:29 UTC
Created attachment 19980 [details]
xorg log

Built  xorg/mesa/drm from git on 30/10/08 and have a rendering problem.

Using radeon driver from git, the problem does not happen with XAA.
Happens with metacity or twm - no desktop is installed.
X window dumps attached.

exa-gears3.xwd shows what happens to an xterm run below a glxgears window.
The contents of the window are OK until it gets focus.
If focus is then moved to another xterm, then that also has rendering problems as shown in exa-gears2.xwd

Last working tree was git from June, attempts to bisect back from current just hit build errors.

Xorg.0.log also attached.
Comment 1 Andy Furniss 2008-10-31 14:33:15 UTC
X window dumps were too big to attach you can see them here -

www.andyqos.ukfsn.org/screen/exa-gears3.xwd
www.andyqos.ukfsn.org/screen/exa-gears2.xwd
Comment 2 Michel Dänzer 2008-11-01 04:46:03 UTC
(In reply to comment #1)
> X window dumps were too big to attach you can see them here -

They can be trivially converted to e.g. .pngs of less than 50K.

I think this is more likely an issue in one of the drivers than in the EXA core, but let's see... Does Option "RenderAccel" "off" or "EXAOptimizeMigration" "off" help?

Comment 3 Andy Furniss 2008-11-01 07:00:42 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > X window dumps were too big to attach you can see them here -
> 
> They can be trivially converted to e.g. .pngs of less than 50K.
> 
> I think this is more likely an issue in one of the drivers than in the EXA
> core, but let's see... Does Option "RenderAccel" "off" or
> "EXAOptimizeMigration" "off" help?
> 

No, neither option helps.
Comment 4 Andy Furniss 2008-11-16 09:57:14 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > X window dumps were too big to attach you can see them here -
> > 
> > They can be trivially converted to e.g. .pngs of less than 50K.
> > 
> > I think this is more likely an issue in one of the drivers than in the EXA
> > core, but let's see... Does Option "RenderAccel" "off" or
> > "EXAOptimizeMigration" "off" help?
> > 
> 
> No, neither option helps.
> 

Does this implicate radeon then?

More info -  radeonhd suffers the same problem.

Before I updated to current xorg git, both radeon and radeonhd (current git versions but built in xorg git tree from June) were OK.
Comment 5 Andy Furniss 2008-11-16 11:43:50 UTC
(In reply to comment #4)

> Before I updated to current xorg git, both radeon and radeonhd (current git
> versions but built in xorg git tree from June) were OK.

Although mesa was an older version as well as xorg.

Comment 6 Michel Dänzer 2009-02-10 09:16:13 UTC
Bug 20037 could explain this, please try the fix referenced there.
Comment 7 Andy Furniss 2009-02-11 03:58:52 UTC
(In reply to comment #6)
> Bug 20037 could explain this, please try the fix referenced there.
> 

Thanks for the update.

Unfortunately I have a R600 card in the box now, so can't test until the Mesa/DRI work currently ongoing is available.
Comment 8 Michel Dänzer 2009-02-11 04:01:35 UTC
Assuming it's the same issue, please reopen if that turns out to be wrong.

*** This bug has been marked as a duplicate of bug 20037 ***


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.