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: Sun, 25 Aug 2019 20:46:19 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1344411365==" 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 127906E130 for ; Sun, 25 Aug 2019 20:46:20 +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 --===============1344411365== Content-Type: multipart/alternative; boundary="15667659800.C4A59.10396" Content-Transfer-Encoding: 7bit --15667659800.C4A59.10396 Date: Sun, 25 Aug 2019 20:46:20 +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 #116 from ReddestDream --- Created attachment 145153 --> https://bugs.freedesktop.org/attachment.cgi?id=3D145153&action=3Dedit dmesgAMD2Monitors I've been doing a few tests. I looked into and compiled 5.3-rc5 along with these patches, but nothing seemed to resolve our multimonitor issue. :/ https://phoronix.com/scan.php?page=3Dnews_item&px=3DAMDGPU-Multi-Monitor-vR= AM-Clock I've also gotten some dmesg output with 5.2.9 with amdgpu.dc_log=3D1 drm.debug=3D0x1e log_buf_len=3D2M. Turns out that amdgpu.dc_log=3D1 does no= thing on this kernel, but I didn't know this when I ran the tests. The interesting a= dded data appears to be coming from drm.debug=3D0x1e. I have two (physically) identical LG 24UD58-B 4K60 monitors connected via D= P. One test was done with both monitors connected to Radeon VII, and the other= was done using my stable Intel+Radeon VII setup where one monitor is connected = to Radeon VII and the other is connected to the Intel iGPU (HD 630, also via D= P at 4K60). These dmesg dumps were taken with all DMs/DEs/Graphics disabled in order to limit interference. The system was booted to a text commandline at native resolution. Since 5.3 isn't changing anything, I plan to do a recompile of 5.2.9 (or 5.= 2.10 if it's out for Arch) with the smum_send_msg_to_smc_with_parameter patch suggested by Tom B. --=20 You are receiving this mail because: You are the assignee for the bug.= --15667659800.C4A59.10396 Date: Sun, 25 Aug 2019 20:46:20 +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

Comm= ent # 116 on bug 11067= 4 from ReddestDream 
Created attachment 145153 =
[details]
dmesgAMD2Monitors

I've been doing a few tests. I looked into and compiled 5.3-rc5 along with
these patches, but nothing seemed to resolve our multimonitor issue. :/

https://phoronix.com/scan.php?page=3Dnews_item&=
;px=3DAMDGPU-Multi-Monitor-vRAM-Clock

I've also gotten some dmesg output with 5.2.9 with amdgpu.dc_log=3D1
drm.debug=3D0x1e log_buf_len=3D2M. Turns out that amdgpu.dc_log=3D1 does no=
thing on
this kernel, but I didn't know this when I ran the tests. The interesting a=
dded
data appears to be coming from drm.debug=3D0x1e.

I have two (physically) identical LG 24UD58-B 4K60 monitors connected via D=
P.
One test was done with both monitors connected to Radeon VII, and the other=
 was
done using my stable Intel+Radeon VII setup where one monitor is connected =
to
Radeon VII and the other is connected to the Intel iGPU (HD 630, also via D=
P at
4K60).

These dmesg dumps were taken with all DMs/DEs/Graphics disabled in order to
limit interference. The system was booted to a text commandline at native
resolution.

Since 5.3 isn't changing anything, I plan to do a recompile of 5.2.9 (or 5.=
2.10
if it's out for Arch) with the smum_send_msg_to_smc_with_parameter patch
suggested by Tom B.

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