From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105251] [Vega10] GPU lockup on boot: VMC page fault Date: Thu, 13 Dec 2018 00:46:13 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0615610142==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id A8FCB6E8CA for ; Thu, 13 Dec 2018 00:46:14 +0000 (UTC) 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 --===============0615610142== Content-Type: multipart/alternative; boundary="15446619743.B4da.2259" Content-Transfer-Encoding: 7bit --15446619743.B4da.2259 Date: Thu, 13 Dec 2018 00:46:14 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105251 --- Comment #61 from Benjamin Hodgetts --- Created attachment 142797 --> https://bugs.freedesktop.org/attachment.cgi?id=3D142797&action=3Dedit New Error Since 4.19.X Ok, so some time between my last report and now (started happening since 4.19.something, I don't know which version specifically) this problem has changed in how it manifests itself. Previously you'd get the "[gfxhub] VMC = page fault" messages. Now it manifests itself in considerably more serious looki= ng errors (with none of the "VMC page faults" in sight). Log file attached. Once something triggers this, the card will become basically unresponsive a= nd anything that tries to use it will start throwing more of the errors seen in the attached log. It's not random though. For example I can run Unigine valley/superposition = or Elder Scrolls Online (via Wine+DXVK) for as long as I like, stress-testing = or benchmarking and it'll be fine. But as soon a I try one of the problem programs, it'll basically "break" the graphics card until I hard reset. --=20 You are receiving this mail because: You are the assignee for the bug.= --15446619743.B4da.2259 Date: Thu, 13 Dec 2018 00:46:14 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comme= nt # 61 on bug 10525= 1 from <= span class=3D"fn">Benjamin Hodgetts 
Created attachment 142797=
 [details]
New Error Since 4.19.X

Ok, so some time between my last report and now (started happening since
4.19.something, I don't know which version specifically) this problem has
changed in how it manifests itself. Previously you'd get the "[gfxhub]=
 VMC page
fault" messages. Now it manifests itself in considerably more serious =
looking
errors (with none of the "VMC page faults" in sight). Log file at=
tached.

Once something triggers this, the card will become basically unresponsive a=
nd
anything that tries to use it will start throwing more of the errors seen in
the attached log.

It's not random though. For example I can run Unigine valley/superposition =
or
Elder Scrolls Online (via Wine+DXVK) for as long as I like, stress-testing =
or
benchmarking and it'll be fine. But as soon a I try one of the problem
programs, it'll basically "break" the graphics card until I hard =
reset.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15446619743.B4da.2259-- --===============0615610142== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0615610142==--