From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 91278] Tonga GPU lock/reset fail with Unigine Valley Date: Mon, 28 Sep 2015 15:35:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1499115749==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B342F6EA04 for ; Mon, 28 Sep 2015 08:35:38 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1499115749== Content-Type: multipart/alternative; boundary="1443454538.e8371.14002"; charset="UTF-8" --1443454538.e8371.14002 Date: Mon, 28 Sep 2015 15:35:38 +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=3D91278 --- Comment #12 from Mathias Tillman --- (In reply to Michel D=C3=A4nzer from comment #10) > Mathias, so you can reliably reproduce the hang by replaying that apitrac= e? Okay, I have been able to replay the trace by compiling apitrace from sourc= e, and renaming glretrace to valley_x64. I can reproduce the hang by replaying, but not in a very useful way as the = hang happens on different frames on each replay, so I wouldn't really call it reproducible at this point. I will see what different options glretrace gives me, to see if I can find = some kind of common denominator between the hangs. --=20 You are receiving this mail because: You are the assignee for the bug. --1443454538.e8371.14002 Date: Mon, 28 Sep 2015 15:35:38 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 12 on bug 91278<= /a> from Mathias Tillman 
(In reply to Michel D=C3=A4nzer from comment #10)
> Mathias, so you can reliably reproduce the hang =
by replaying that apitrace?

Okay, I have been able to replay the trace by compiling apitrace from sourc=
e,
and renaming glretrace to valley_x64.
I can reproduce the hang by replaying, but not in a very useful way as the =
hang
happens on different frames on each replay, so I wouldn't really call it
reproducible at this point.
I will see what different options glretrace gives me, to see if I can find =
some
kind of common denominator between the hangs.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1443454538.e8371.14002-- --===============1499115749== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1499115749==--