From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108521] RX 580 as eGPU amdgpu: gpu post error! Date: Thu, 25 Oct 2018 01:15:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0764271317==" 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 54B1D6E2E7 for ; Thu, 25 Oct 2018 01:15:41 +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 --===============0764271317== Content-Type: multipart/alternative; boundary="15404301410.f5ce23b0B.11518" Content-Transfer-Encoding: 7bit --15404301410.f5ce23b0B.11518 Date: Thu, 25 Oct 2018 01:15:41 +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=3D108521 --- Comment #7 from Robert Strube --- Thanks for the suggestions! I took your advice and commented out the Vega M device IDs located here: /drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c These are the lines of code that I commented out. /* VEGAM */ {0x1002, 0x694C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGAM}, {0x1002, 0x694E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGAM}, This did indeed cause my Vega M to not be initialized, *but* the problem I'm having with the eGPU remains. So it appears you were correct and my hunch t= hat the Vega M is interfering with the eGPU initialization was incorrect. I'm = back to square one... I uploaded a new dmesg log for this kernel, perhaps with the Vega M out of = the equation you might see something new? Thanks! Rob --=20 You are receiving this mail because: You are the assignee for the bug.= --15404301410.f5ce23b0B.11518 Date: Thu, 25 Oct 2018 01:15:41 +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 # 7 on bug 10852= 1 from Robert Strube
Thanks for the suggestions! I took your advice and commented o=
ut the Vega M
device IDs located here: /drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c

These are the lines of code that I commented out.
/* VEGAM */
{0x1002, 0x694C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGAM},
{0x1002, 0x694E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGAM},

This did indeed cause my Vega M to not be initialized, *but* the problem I'm
having with the eGPU remains. So it appears you were correct and my hunch t=
hat
the Vega M is interfering with the eGPU initialization was incorrect.  I'm =
back
to square one...

I uploaded a new dmesg log for this kernel, perhaps with the Vega M out of =
the
equation you might see something new?

Thanks!
Rob


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