From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 59089] [bisected, regression] flood of GPU fault detected in logs caused by 9af20... drm/radeon: fix fence locking in the pageflip callback Date: Mon, 14 Jan 2013 06:01:26 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1943526201==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 91408E5C00 for ; Sun, 13 Jan 2013 22:01:26 -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 --===============1943526201== Content-Type: multipart/alternative; boundary="1358143286.e4a1e8C0.5063"; charset="us-ascii" --1358143286.e4a1e8C0.5063 Date: Mon, 14 Jan 2013 06:01:26 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D59089 --- Comment #6 from Alexandre Demers --- (In reply to comment #5) > I get the GPU faults starting with mesa commit >=20 > 3e163a137be7f9a80ec720903c4bda028de5681f is the first bad commit > commit 3e163a137be7f9a80ec720903c4bda028de5681f > Author: Marek Ol=C3=85=C2=A1=C3=83=C2=A1k > Date: Thu Nov 29 02:55:01 2012 +0100 >=20 > gallium/postprocess: share pipe_context and cso_context with the state > tracker >=20=20=20=20=20 > Using one context instead of two is more efficient and > we can skip another context flush. >=20=20=20=20=20 > Reviewed-by: Brian Paul Is it a flood? Other commits may create GPU faults, but it shouldn't flood = your logs. I think it would be better to track different sources of GPU faults in different bugs. --=20 You are receiving this mail because: You are the assignee for the bug. --1358143286.e4a1e8C0.5063 Date: Mon, 14 Jan 2013 06:01:26 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comment= # 6 on bug 59089<= /a> from Alexandre Demers 
(In reply to comment #5=
)
> I get the GPU faults starting with mesa commit
>=20
> 3e163a137be7f9a80ec720903c4bda028de5681f is the first bad commit
> commit 3e163a137be7f9a80ec720903c4bda028de5681f
> Author: Marek Ol=C3=85=C2=A1=C3=83=C2=A1k <maraeo@gmail.com>
> Date:   Thu Nov 29 02:55:01 2012 +0100
>=20
>     gallium/postprocess: share pipe_context and cso_context with the s=
tate
> tracker
>=20=20=20=20=20
>     Using one context instead of two is more efficient and
>     we can skip another context flush.
>=20=20=20=20=20
>     Reviewed-by: Brian Paul <brianp@vmware.com>

Is it a flood? Other commits may create GPU faults, but it shouldn't flood =
your
logs. I think it would be better to track different sources of GPU faults in
different bugs.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1358143286.e4a1e8C0.5063-- --===============1943526201== 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 --===============1943526201==--