https://bugs.freedesktop.org/show_bug.cgi?id=42175
Bug #: 42175 Summary: RV730: Display errors in glxgears & WebGL Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: kdevel@vogtner.de
Since Mesa 7.11-rc2 the gallium driver is used on my machine and produces display errors. Find attached a glxgears screenshot and a screendump of http://learningwebgl.com/lessons/lesson03/index.html produced with the current Firefox.
Before and including 7.11-rc1 seemed to use the old driver which does not produce rendering errors but which crashes Firefox in http://learningwebgl.com/lessons/lesson16/index.html or in the Aquarium of http://code.google.com/p/webglsamples/.
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #1 from Stefan kdevel@vogtner.de 2011-10-24 14:06:39 PDT --- Created attachment 52710 --> https://bugs.freedesktop.org/attachment.cgi?id=52710 glxgears screenshot
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #2 from Stefan kdevel@vogtner.de 2011-10-24 14:07:44 PDT --- Created attachment 52713 --> https://bugs.freedesktop.org/attachment.cgi?id=52713 Lesson 3 screenshot
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #3 from Alex Deucher agd5f@yahoo.com 2011-10-24 14:44:38 PDT --- Can you bisect?
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #4 from Stefan kdevel@vogtner.de 2011-10-24 14:55:59 PDT --- (In reply to comment #3)
Can you bisect?
The change took place between 7.11-rc1 and -rc2:
a8907c6005d7935b4520255e12184c139471b5b9 is the first bad commit commit a8907c6005d7935b4520255e12184c139471b5b9 Author: Benjamin Franzke benjaminfranzke@googlemail.com Date: Sat Jul 2 13:41:35 2011 +0200
But: This is where the switch from the old driver to the Gallium takes place. The old driver got used in my configuration up to 7.11-rc1 because the udev-devel packet was not installed. Eventually after installing it 7.11-rc1 uses the new driver.
So currently I don't have a "good" reference for a bisection.
BTW: https://bugzilla.mozilla.org/show_bug.cgi?id=693056 (origin of the current problems).
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #5 from Stefan kdevel@vogtner.de 2011-10-24 17:32:00 PDT --- Mesa 7.12-devel (git-faa16dc) Works. No crash, no picture errors.
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #6 from Michel Dänzer michel@daenzer.net 2011-10-25 08:00:08 PDT --- (In reply to comment #5)
Mesa 7.12-devel (git-faa16dc) Works. No crash, no picture errors.
What about the current 7.11 branch? If that still shows the display errors, you should be able to bisect the change that fixed it on the master branch.
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #7 from Stefan kdevel@vogtner.de 2011-10-25 08:16:45 PDT --- (In reply to comment #6)
What about the current 7.11 branch? If that still shows the display errors, you should be able to bisect the change that fixed it on the master branch.
No bisection required. The bug was fixed by this commit:
"r600g: set correct tiling flags in depth info" http://cgit.freedesktop.org/mesa/mesa/commit/?id=faa16dc456f1f910eef24eaa238...
which I just verified by re-compiling mesa with the reversed patch applied.
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #8 from Michel Dänzer michel@daenzer.net 2011-10-26 01:47:13 PDT --- (In reply to comment #7)
No bisection required. The bug was fixed by this commit:
"r600g: set correct tiling flags in depth info" http://cgit.freedesktop.org/mesa/mesa/commit/?id=faa16dc456f1f910eef24eaa238...
Weird, as the commit log says, it's supposed to be a no-op ATM...
Marek, does this make sense to you? Should this change be backported to the 7.11 branch?
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #9 from Marek Olšák maraeo@gmail.com 2011-10-26 05:29:24 PDT --- No, it doesn't make sense. :) He might have an older, more buggy kernel than me. That would be the only explanation. I was working with the latest drm-fixes branch (3.1 rc10). Anyway I think the fix can safely go into 7.11.
https://bugs.freedesktop.org/show_bug.cgi?id=42175
--- Comment #10 from Stefan kdevel@vogtner.de 2011-10-26 05:38:41 PDT --- (In reply to comment #9)
He might have an older, more buggy kernel than me.
I'm using the longterm kernel 2.6.35.14.
https://bugs.freedesktop.org/show_bug.cgi?id=42175
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #11 from Michel Dänzer michel@daenzer.net 2011-10-26 06:07:50 PDT --- Marek backported the fix to the 7.11 branch, thanks.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org