From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 107518] polaris powerplay init fails: There must be 1 or more PCIE levels defined in PPTable Date: Sun, 26 Aug 2018 00:08:24 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1327936078==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 53AE06E039 for ; Sun, 26 Aug 2018 00:08:24 +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 --===============1327936078== Content-Type: multipart/alternative; boundary="15352421040.EF6F7.6741" Content-Transfer-Encoding: 7bit --15352421040.EF6F7.6741 Date: Sun, 26 Aug 2018 00:08:24 +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=3D107518 --- Comment #9 from Timothy Pearson --- (In reply to Timothy Pearson from comment #8) > Would it make sense to call amdgpu_asic_reset() as part of module load to > ensure that the GPU is in a known good state? This didn't fix the problem, but I did note that rmmod / modprobing the amd= gpu module from the host is a valid workaround. Something must happen on rmmod-based teardown aside from amdgpu_asic_reset(). --=20 You are receiving this mail because: You are the assignee for the bug.= --15352421040.EF6F7.6741 Date: Sun, 26 Aug 2018 00:08:24 +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 # 9 on bug 10751= 8 from Timothy Pearson 
(In reply to Timothy Pearson from comment #8)
> Would it make sense to call amdgpu_asic_reset() =
as part of module load to
> ensure that the GPU is in a known good state?

This didn't fix the problem, but I did note that rmmod / modprobing the amd=
gpu
module from the host is a valid workaround.  Something must happen on
rmmod-based teardown aside from amdgpu_asic_reset().

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