From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 110674] Crashes / Resets From AMDGPU / Radeon VII
Date: Mon, 12 Aug 2019 16:38:54 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0893782449=="
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 541DE6E588
for ; Mon, 12 Aug 2019 16:38:54 +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
--===============0893782449==
Content-Type: multipart/alternative; boundary="15656279345.C8Cf5D5D.22451"
Content-Transfer-Encoding: 7bit
--15656279345.C8Cf5D5D.22451
Date: Mon, 12 Aug 2019 16:38:54 +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=3D110674
--- Comment #87 from Tom B ---
> Could be we've got a race condition between the powerplay setup and amdgpu
handing off the card to drm_dev_register to advertise it for normal use.
The question then becomes: Why doesn't the race condition happen with only =
one
screen? Perhaps it's a matter of speed. With a single display, the driver
detect the displays, read/parse the EDID data, initialize in time. But then
that doesn't explain why the crash still occurs if you boot with one
DisplayPort monitor and attach another after X is running.
One thing I've been trying to work out is the difference between vega21_ppt=
.c
and vega20_hwmgr.c is, as they both contain slightly different or identic=
al
versions of the same functions. It looks like the functions in vega20_hwmgr=
.c=20
take precedence but it's strange to see this duplication and both files are
worked on in the commit history.
Take a look at vega20_set_uclk_to_highest_dpm_level and
vega20_apply_clocks_adjust_rules in both for examples.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15656279345.C8Cf5D5D.22451
Date: Mon, 12 Aug 2019 16:38:54 +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 # 87
on bug 11067=
4
from Tom =
B
> Could be we've got a race condition=
between the powerplay setup and amdgpu
handing off the card to drm_dev_register to advertise it for normal use.
The question then becomes: Why doesn't the race condition happen with only =
one
screen? Perhaps it's a matter of speed. With a single display, the driver
detect the displays, read/parse the EDID data, initialize in time. But then
that doesn't explain why the crash still occurs if you boot with one
DisplayPort monitor and attach another after X is running.
One thing I've been trying to work out is the difference between vega21_ppt=
.c
and vega20_hwmgr.c is, as they both contain slightly different or identic=
al
versions of the same functions. It looks like the functions in vega20_hwmgr=
.c=20
take precedence but it's strange to see this duplication and both files are
worked on in the commit history.
Take a look at vega20_set_uclk_to_highest_dpm_level and
vega20_apply_clocks_adjust_rules in both for examples.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15656279345.C8Cf5D5D.22451--
--===============0893782449==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs
--===============0893782449==--