From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 110822] [Bisected]Booting with kernel version 5.1.0 or higher on RX 580 hangs Date: Wed, 12 Jun 2019 18:30:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0460116562==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CB66F8967F for ; Wed, 12 Jun 2019 18:30:44 +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 --===============0460116562== Content-Type: multipart/alternative; boundary="15603642441.96dDaE.10252" Content-Transfer-Encoding: 7bit --15603642441.96dDaE.10252 Date: Wed, 12 Jun 2019 18:30:44 +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=3D110822 --- Comment #19 from Alex Deucher --- (In reply to Gobinda Joy from comment #18) >=20 > What I don't get is why they are using 2 calls to get the bandwidth readi= ng. > Since both function walking the PCIe tree what's the point. Also it seems > like the call to pcie_bandwidth_available() function is casing the > freeze/hangs in my system. So that's counts for something. >=20 Can you try a drm-next kernel? This code was ultimately cleaned in this pa= tch: https://cgit.freedesktop.org/drm/drm/commit/?id=3Ddbaa922b5706b1aff4572c280= e15bbea2d04afe6 I don't know why pcie_bandwidth_available() is causing problems for you, it= 's just standard PCIE stuff. --=20 You are receiving this mail because: You are the assignee for the bug.= --15603642441.96dDaE.10252 Date: Wed, 12 Jun 2019 18:30:44 +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 # 19 on bug 11082= 2 from Alex Deucher 
(In reply to Gobinda Joy from comment #18)
>=20
> What I don't get is why they are using 2 calls to get the bandwidth re=
ading.
> Since both function walking the PCIe tree what's the point. Also it se=
ems
> like the call to pcie_bandwidth_available() function is casing the
> freeze/hangs in my system. So that's counts for something.
> 

Can you try a drm-next kernel?  This code was ultimately cleaned in this pa=
tch:
https://cgit.freedesktop.org/drm/drm/commit/?id=
=3Ddbaa922b5706b1aff4572c280e15bbea2d04afe6
I don't know why pcie_bandwidth_available() is causing problems for you, it=
's
just standard PCIE stuff.

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