From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 59899] Diagonal rendering artifacts on xbmc Date: Mon, 04 Feb 2013 09:57:20 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1565245113==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 047C1E5BFE for ; Mon, 4 Feb 2013 01:57:20 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1565245113== Content-Type: multipart/alternative; boundary="1359971839.07A2c60.18066"; charset="us-ascii" --1359971839.07A2c60.18066 Date: Mon, 4 Feb 2013 09:57:19 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=59899 --- Comment #6 from aeriksson@fastmail.fm --- Tried mesa git as of yesterday. No improvement. I've also tried to flip all USE flags on/off for mesa 9.0.1 with no improvement. Doing some surfing, I noticed the z buffer issues being a common problem, so I decided to try the car racing game "trigger". It does show the same effect as I've seen in screenshots on youtube (flickering triangular misrenderings on objects). The dynamic behavior seems to be the same. However, I see the same effect on the fist screen in Trigger, where the three helmets are shown. I'm not sure if they are supposed to be animated or static. The zbuffer issues I saw in other reports were all related to movements (Stuff move back/front, when I move a little). I also have zbuffer issues on the terrain once the game starts. If xbmc makes use of depth to paint its screen with a bunch of objects, I can see how this might be z related. However, xbmc should show a static screen (I think), whereas common z reports are all related to movement of the observer (I think). Any ideas how one could test this theory? Another crazy thing is that every once in a while it renders perfectly ok. While "bisecting" through the USEflags, I had a run of "good, good, good,..." and each test was a restart of Xserver, starting xbmc. After going back to the known bad set of USE flags (which now rendered good!!), I did some cursing and warm rebooted the box, and it suddenly rendered bad again :-(. This kind of suggests an uninitialized HW register to me... Any ideas how one can make xbmc not exercise the (gl?) related areas of the HW? I'm lacking a solid known-good state at the moment. -- You are receiving this mail because: You are the assignee for the bug. --1359971839.07A2c60.18066 Date: Mon, 4 Feb 2013 09:57:19 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 6 on bug 59899 from 
Tried mesa git as of yesterday. No improvement.
I've also tried to flip all USE flags on/off for mesa 9.0.1 with no
improvement.

Doing some surfing, I noticed the z buffer issues being a common problem, so I
decided to try the car racing game "trigger". It does show the same effect as
I've seen in screenshots on youtube (flickering triangular misrenderings on
objects). The dynamic behavior seems to be the same. However, I see the same
effect on the fist screen in Trigger, where the three helmets are shown. I'm
not sure if they are supposed to be animated or static. The zbuffer issues I
saw in other reports were all related to movements (Stuff move back/front, when
I move a little). I also have zbuffer issues on the terrain once the game
starts.

If xbmc makes use of depth to paint its screen with a bunch of objects, I can
see how this might be z related. However, xbmc should show a static screen (I
think), whereas common z reports are all related to movement of the observer (I
think).

Any ideas how one could test this theory?

Another crazy thing is that every once in a while it renders perfectly ok.
While "bisecting" through the USEflags, I had a run of "good, good, good,..."
and each test was a restart of Xserver, starting xbmc. After going back to the
known bad set of USE flags (which now rendered good!!), I did some cursing and
warm rebooted the box, and it suddenly rendered bad again :-(. This kind of
suggests an uninitialized HW register to me...

Any ideas how one can make xbmc not exercise the (gl?) related areas of the HW?
I'm lacking a solid known-good state at the moment.

You are receiving this mail because:
  • You are the assignee for the bug.
--1359971839.07A2c60.18066-- --===============1565245113== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1565245113==--