<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [Bisected]Booting with kernel version 5.1.0 or higher on RX 580 hangs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110822#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [Bisected]Booting with kernel version 5.1.0 or higher on RX 580 hangs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110822">bug 110822</a>
from <span class="vcard"><a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to Gobinda Joy from <a href="show_bug.cgi?id=110822#c18">comment #18</a>)
<span class="quote">>
> What I don't get is why they are using 2 calls to get the bandwidth reading.
> 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.
> </span >
Can you try a drm-next kernel? This code was ultimately cleaned in this patch:
<a href="https://cgit.freedesktop.org/drm/drm/commit/?id=dbaa922b5706b1aff4572c280e15bbea2d04afe6">https://cgit.freedesktop.org/drm/drm/commit/?id=dbaa922b5706b1aff4572c280e15bbea2d04afe6</a>
I don't know why pcie_bandwidth_available() is causing problems for you, it's
just standard PCIE stuff.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>