From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101946] Rebinding AMDGPU causes initialization errors [R9 290 / 4.10 kernel] Date: Fri, 28 Jul 2017 20:55:59 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1359996280==" 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 362086E1EC for ; Fri, 28 Jul 2017 20:55:59 +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 --===============1359996280== Content-Type: multipart/alternative; boundary="15012753590.409bf.15507"; charset="UTF-8" --15012753590.409bf.15507 Date: Fri, 28 Jul 2017 20:55:59 +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=3D101946 --- Comment #14 from Robin --- Created attachment 133108 --> https://bugs.freedesktop.org/attachment.cgi?id=3D133108&action=3Dedit case3.sh So, tinkering with the test script I've only been able to eliminate some suspicions and invalidate my observation the patch performed better. I've taken out vfio-pci binding from the loop. It's only used during boot to keep the GPU free to unbind. So it's not related to vfio-pci's having acces= s in between binds. I've made 3 methods for rebinding amdgpu. amdgpu rmmod > modprobe remove pci devices > rescan driver unbind > bind I've run each of these a few dozen times on each kernel and none of them re= ally stand out. All of them have a chance to work (as in, ring 1 test failure on= ly) or to fail. 4.13rc2, drm-next-4.14-wip, drm-next-4.14-wip + patch3 all have this behavi= our. So no I don't think they've helped after all. --=20 You are receiving this mail because: You are the assignee for the bug.= --15012753590.409bf.15507 Date: Fri, 28 Jul 2017 20:55:59 +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 # 14 on bug 10194= 6 from Robin 
Created attachment 133108 [detai=
ls]
case3.sh

So, tinkering with the test script I've only been able to eliminate some
suspicions and invalidate my observation the patch performed better.

I've taken out vfio-pci binding from the loop. It's only used during boot to
keep the GPU free to unbind. So it's not related to vfio-pci's having acces=
s in
between binds.

I've made 3 methods for rebinding amdgpu.
amdgpu rmmod > modprobe
remove pci devices > rescan
driver unbind > bind

I've run each of these a few dozen times on each kernel and none of them re=
ally
stand out. All of them have a chance to work (as in, ring 1 test failure on=
ly)
or to fail.

4.13rc2, drm-next-4.14-wip, drm-next-4.14-wip + patch3 all have this behavi=
our.
So no I don't think they've helped after all.

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