From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 104736] Kernel panic with agd5's drm-next-4.17-wip & GFX8/Polaris10/Ellesmere/Rx-480-8GiB Date: Wed, 24 Jan 2018 02:52:01 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1395447208==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 0B7766E4E9 for ; Wed, 24 Jan 2018 02:52:01 +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 --===============1395447208== Content-Type: multipart/alternative; boundary="15167623200.E7eB6d.7658" Content-Transfer-Encoding: 7bit --15167623200.E7eB6d.7658 Date: Wed, 24 Jan 2018 02:52:00 +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=3D104736 --- Comment #3 from Robin Kauffman --- (In reply to Alex Deucher from comment #2) > does manually loading gpu_sched before amdgpu fix the issue? Can try to do so, but unsure as to how given that pretty much the entire graphics stack is compiled into the kernel image. Reverting commit 4983e48c8539282be15f660bdd2c4260467b1190 ('drm/sched: move fence slab handling to module init/exit') fixes the issue, and thus this bug may be a duplicate of bug #104756. If so, this bug can be closed as a duplicate, or I can experiment with trying to force gpu_sched up first. --=20 You are receiving this mail because: You are the assignee for the bug.= --15167623200.E7eB6d.7658 Date: Wed, 24 Jan 2018 02:52:00 +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

Commen= t # 3 on bug 10473= 6 from Robin Kauffman 
(In reply to Alex Deucher from comment #2)
> does manually loading gpu_sched before amdgpu fi=
x the issue?

Can try to do so, but unsure as to how given that pretty much the entire
graphics stack is compiled into the kernel image.
Reverting commit 4983e48c8539282be15f660bdd2c4260467b1190 ('drm/sched: move
fence slab handling to module init/exit') fixes the issue, and thus this bug
may be a duplicate of bug #104756.  If so, this bug can =
be closed as a
duplicate, or I can experiment with trying to force gpu_sched up first.

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