From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 110674] Crashes / Resets From AMDGPU / Radeon VII Date: Sun, 19 May 2019 22:28:50 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1413076376==" 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 75EB38919B for ; Sun, 19 May 2019 22:28:50 +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 --===============1413076376== Content-Type: multipart/alternative; boundary="15583049301.bB1B7bD.18405" Content-Transfer-Encoding: 7bit --15583049301.bB1B7bD.18405 Date: Sun, 19 May 2019 22:28:50 +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=3D110674 --- Comment #23 from Chris Hodapp --- I've been building kernels like a fiend the last couple days. Making matters more difficult is the fact that most of the intermediate commits produce kernels that get stuck waiting for devices to come up (something that went = in the run-up to 5.1 disagrees with my machine but then got fixed for the actu= al 5.1 release). No conclusive results yet except that both 5.0 and 5.0.17 work (so I'm assuming the whole 5.0.X series works) but nothing in the 5.1 series has truly been stable for me. It's interesting that you both have two monitors. I am also trying to run t= wo monitors over displayport. For what it's worth, I'm also using KDE with sdd= m, though if KDE or sddm is making the GPU reset then that is on the graphics driver, not the userspace programs that are trying to use it. --=20 You are receiving this mail because: You are the assignee for the bug.= --15583049301.bB1B7bD.18405 Date: Sun, 19 May 2019 22:28:50 +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 # 23 on bug 11067= 4 from Chris Hodapp 
I've been building kernels like a fiend the last couple days. =
Making matters
more difficult is the fact that most of the intermediate commits produce
kernels that get stuck waiting for devices to come up (something that went =
in
the run-up to 5.1 disagrees with my machine but then got fixed for the actu=
al
5.1 release). No conclusive results yet except that both 5.0 and 5.0.17 work
(so I'm assuming the whole 5.0.X series works) but nothing in the 5.1 series
has truly been stable for me.

It's interesting that you both have two monitors. I am also trying to run t=
wo
monitors over displayport. For what it's worth, I'm also using KDE with sdd=
m,
though if KDE or sddm is making the GPU reset then that is on the graphics
driver, not the userspace programs that are trying to use it.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15583049301.bB1B7bD.18405-- --===============1413076376== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============1413076376==--