Bug 23902 - Blinking and artifacts in OpenGL
Summary: Blinking and artifacts in OpenGL
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-13 09:46 UTC by Maciej Piechotka
Modified: 2009-09-13 19:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Maciej Piechotka 2009-09-13 09:46:44 UTC
I have currently such problems:
- Blinking of whole screen in OpenGL 
- Drawing some parts of the window under it (only gnome-system-monitor applet black background) on top

They are present in (at least) ufo:ai and (was?) xmoto.

libdrm: 67e4172394a88d4922fb8d9c7c3d96ce7e02c5a
radeon driver: 917f2d7cd1815279710939edc27133ca6609460f
mesa: 970823978c2f7d2cf0757aa6ddbd6289b34c476f
xorg-server: 1.6
kernel: 2.6.31 vanilla

and earlier

KMS is not used.
Comment 1 Maciej Piechotka 2009-09-13 09:56:32 UTC
Ups.

Hardware: ATI XPress 200M RC410
Comment 2 Alex Deucher 2009-09-13 15:34:30 UTC
(In reply to comment #0)
> I have currently such problems:
> - Blinking of whole screen in OpenGL 

Graphical blinking or the monitor itself losing the signal temporarily?

> - Drawing some parts of the window under it (only gnome-system-monitor applet
> black background) on top
> 

Are you using a compositor like compiz or metacity or kwim?  3D and composite don't work well together with DRI1.  DRI2 fixes this, but requires KMS.

> They are present in (at least) ufo:ai and (was?) xmoto.
> 
> libdrm: 67e4172394a88d4922fb8d9c7c3d96ce7e02c5a
> radeon driver: 917f2d7cd1815279710939edc27133ca6609460f
> mesa: 970823978c2f7d2cf0757aa6ddbd6289b34c476f
> xorg-server: 1.6
> kernel: 2.6.31 vanilla
> 
> and earlier

Is this a regression and if so, when was the last time it worked correctly?
Comment 3 Maciej Piechotka 2009-09-13 15:41:57 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > I have currently such problems:
> > - Blinking of whole screen in OpenGL 
> 
> Graphical blinking or the monitor itself losing the signal temporarily?
> 

How to distinguish it? 

> > - Drawing some parts of the window under it (only gnome-system-monitor applet
> > black background) on top
> > 
> 
> Are you using a compositor like compiz or metacity or kwim?  3D and composite
> don't work well together with DRI1.  DRI2 fixes this, but requires KMS.
> 

I'm using metacity w/ /apps/metacity/general/compositing_manager. I'll try without.

> > They are present in (at least) ufo:ai and (was?) xmoto.
> > 
> > libdrm: 67e4172394a88d4922fb8d9c7c3d96ce7e02c5a
> > radeon driver: 917f2d7cd1815279710939edc27133ca6609460f
> > mesa: 970823978c2f7d2cf0757aa6ddbd6289b34c476f
> > xorg-server: 1.6
> > kernel: 2.6.31 vanilla
> > 
> > and earlier
> 
> Is this a regression and if so, when was the last time it worked correctly?

No. It is not a regression.

Comment 4 Alex Deucher 2009-09-13 15:49:34 UTC
(In reply to comment #3)
> 
> How to distinguish it? 

Are elements of the GUI blinking or is the entire monitor blinking (i.e., going in and out of powersave mode)?

> I'm using metacity w/ /apps/metacity/general/compositing_manager. I'll try
> without.

This is expected with 3D and compositing under DRI1.

Comment 5 Maciej Piechotka 2009-09-13 16:09:37 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > 
> > How to distinguish it? 
> 
> Are elements of the GUI blinking or is the entire monitor blinking (i.e., going
> in and out of powersave mode)?
> 

GUI blinking, In 'normal' work I have similar problems when I move laptop and I thought that connection cables started not to connect (if this is the case the 'normal work blinking' is a regression).

> > I'm using metacity w/ /apps/metacity/general/compositing_manager. I'll try
> > without.
> 
> This is expected with 3D and compositing under DRI1.
> 

Disabling compositing fixed the problem.
Comment 6 Alex Deucher 2009-09-13 16:19:43 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > 
> > > How to distinguish it? 
> > 
> > Are elements of the GUI blinking or is the entire monitor blinking (i.e., going
> > in and out of powersave mode)?
> > 
> 
> GUI blinking, In 'normal' work I have similar problems when I move laptop and I
> thought that connection cables started not to connect (if this is the case the
> 'normal work blinking' is a regression).

This sounds like the cable is coming loose if it only happens when you move the laptop.
Comment 7 Maciej Piechotka 2009-09-13 19:32:49 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #3)
> > > > 
> > > > How to distinguish it? 
> > > 
> > > Are elements of the GUI blinking or is the entire monitor blinking (i.e., going
> > > in and out of powersave mode)?
> > > 
> > 
> > GUI blinking, In 'normal' work I have similar problems when I move laptop and I
> > thought that connection cables started not to connect (if this is the case the
> > 'normal work blinking' is a regression).
> 
> This sounds like the cable is coming loose if it only happens when you move the
> laptop.
> 

You misunderstood me.
1. Such blinking occures when I move laptop and I assume somthing is loose. However it occured few times so it might be coincidence (I first observed it and after some time I observed 2) )
2. Such blinking started to occure when laptop is still which may be 1) or somehow 3)
3. Such blinking occures at specific moment (after loading ufo:ai). In this case it is rather not loose cable as laptop is still and it is reproducable. Also disabling composition fixs it. Laptop was still

So I can have:
1. Software bug which due to few correlations seemed to be hardware bug
2. Hardware bug which is turned on by some GPU commends. However it seems unlikely for me.
3. Software and hardware bug which looks the same, Hardware occures when laptop is moved and software when composition is enabled.


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.