Bug 53632

Summary: Random rendering corruptions
Product: DRI Reporter: Thomas Rohloff <v10lator>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Good rendering
none
Bad rendering none

Description Thomas Rohloff 2012-08-17 07:43:36 UTC 
I get random rendering corruptions in Minecraft with a CAYMAN GPU (radeon HD 6950).
It seems like the wrong textures are selected, see:
Good: http://img713.imageshack.us/img713/492/mcgood.png
Bad: http://img96.imageshack.us/img96/6417/mcbad.png

Also water seems to (randomly) choose the wrong texture in it's animation, resulting in flashing water. Also the game screen flashes blue sometimes.

There are no error logs at all and this seems to be triggered by Michel Dänzers patches to fix bug #45018 (see comment #119 there) as it wasn't there before. Please note that this has nothing to do with GLAMOR acceleration (not used when the corruptions occur).
Comment 1 Michel Dänzer 2012-08-17 08:28:09 UTC 
(In reply to comment #1)
> Good: http://img713.imageshack.us/img713/492/mcgood.png
> Bad: http://img96.imageshack.us/img96/6417/mcbad.png

Please attach files here directly.


> There are no error logs at all and this seems to be triggered by Michel Dänzers
> patches to fix bug #45018 (see comment #119 there) as it wasn't there before.

Can you bisect which commit exactly triggered it?

Do you have Jerome's kernel fix referenced in that report?
Comment 2 Thomas Rohloff 2012-08-17 08:40:26 UTC 
Created attachment 65672 [details]
Good rendering
Comment 3 Thomas Rohloff 2012-08-17 08:40:54 UTC 
Created attachment 65673 [details]
Bad rendering
Comment 4 Thomas Rohloff 2012-08-17 08:43:23 UTC 
(In reply to comment #1)
> Please attach files here directly.
Sorry, done.

> Can you bisect which commit exactly triggered it?
I'm not that good at bisecting (never did it) but I could try to remove your patches one by one. Would that help, too?

> Do you have Jerome's kernel fix referenced in that report?
No. It's a 3.5 kernel without (DRI related) patches. Do I need the kernel patch, too?
Comment 5 Michel Dänzer 2012-08-17 08:47:30 UTC 
(In reply to comment #4)
> > Can you bisect which commit exactly triggered it?
> I'm not that good at bisecting (never did it) but I could try to remove your
> patches one by one. Would that help, too?

Yes, that would be the poor man's way to isolate the commit. But you should really learn to bisect. :)


> Do I need the kernel patch, too?

Yes.
Comment 6 Thomas Rohloff 2012-08-17 09:40:15 UTC 
(In reply to comment #5)
> > Do I need the kernel patch, too?
> 
> Yes.
The patch seems to fix my issue. Sorry for the trouble.

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.