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, 05 Oct 2015 22:51:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0183431337==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 72C8A6E022 for ; Mon, 5 Oct 2015 15:51:56 -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 --===============0183431337== Content-Type: multipart/alternative; boundary="1444085516.4Bf58dc1.14765"; charset="UTF-8" --1444085516.4Bf58dc1.14765 Date: Mon, 5 Oct 2015 22:51:56 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=91278 --- Comment #28 from Mathias Tillman --- (In reply to Andy Furniss from comment #27) > Created attachment 118665 [details] > valley vm fault dump > > Aha, here it is. I am getting similar results using check_vm. However, since the hang usually doesn't happen after the first vm fail (it did actually for me a few times, but most of the time it didn't) I modified the mesa code to disable closing the program once a vm fault happened. Unfortunately this doesn't really provide me with any interesting information - they have all complained about the paging fault happening in a VERTEX_BUFFER with an identical, or close to identical address. -- You are receiving this mail because: You are the assignee for the bug. --1444085516.4Bf58dc1.14765 Date: Mon, 5 Oct 2015 22:51:56 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 28 on bug 91278 from
(In reply to Andy Furniss from comment #27)
> Created attachment 118665 [details]
> valley vm fault dump
> 
> Aha, here it is.

I am getting similar results using check_vm. However, since the hang usually
doesn't happen after the first vm fail (it did actually for me a few times, but
most of the time it didn't) I modified the mesa code to disable closing the
program once a vm fault happened. Unfortunately this doesn't really provide me
with any interesting information - they have all complained about the paging
fault happening in a VERTEX_BUFFER with an identical, or close to identical
address.


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