From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108940] QHD bug? drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:1613 core_link_enable_stream+0xc14/0x1040 Date: Wed, 16 Jan 2019 13:52:49 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0701224272==" 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 3D41D6F097 for ; Wed, 16 Jan 2019 13:52:49 +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 --===============0701224272== Content-Type: multipart/alternative; boundary="15476467691.4BC57EfFB.20882" Content-Transfer-Encoding: 7bit --15476467691.4BC57EfFB.20882 Date: Wed, 16 Jan 2019 13:52:49 +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=3D108940 --- Comment #14 from H.Habighorst --- Can confirm.=20 But I'm a bit worried - there is a part before the "core_link_enable_stream" that seems wrong to me in initializing the device, which seems to occure in= all dmesg outputs. I've attached line numbers via less -N - maybe it helps. 837 [ 8.686299] [drm] BIOS signature incorrect 0 0 838 [ 8.686326] ATOM BIOS: 113-RAVEN-110 839 [ 8.686357] [drm] vm size is 262144 GB, 4 levels, block size is 9-bi= t, fragment size is 9-bit ... 854 [ 8.688113] [drm] Found VCN firmware Version: 1.73 Family ID: 18 ... 857 [ 8.797714] [drm] DM_PPLIB: values for Invalid clock 858 [ 8.797715] [drm] DM_PPLIB: 0 in kHz 859 [ 8.797715] [drm] DM_PPLIB: 400000 in kHz 860 [ 8.797716] [drm] DM_PPLIB: 933000 in kHz 861 [ 8.797716] [drm] DM_PPLIB: 1067000 in kHz 862 [ 8.797809] WARNING: CPU: 6 PID: 725 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1380 dcn_bw_update_from_pplib+0x16b/0x280 [amdgpu] This seems plain wrong to me - shouldn't it mention here the engine clock? This WARNING stems from not getting the clock values right - seems intended. The same warning occurs again, I wildly guess for the memory (?!). Line 862-1017 - only afterwards the mentioned "core_link_enable_stream" bug occurs. It seems to me - as a total layman - that the initialization fails = and afterwards bogus happens. --=20 You are receiving this mail because: You are the assignee for the bug.= --15476467691.4BC57EfFB.20882 Date: Wed, 16 Jan 2019 13:52:49 +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 # 14 on bug 10894= 0 from H.Habighorst 
Can confirm.=20

But I'm a bit worried - there is a part before the "core_link_enable_s=
tream"
that seems wrong to me in initializing the device, which seems to occure in=
 all
dmesg outputs.

I've attached line numbers via less -N - maybe it helps.

837 [    8.686299] [drm] BIOS signature incorrect 0 0
838 [    8.686326] ATOM BIOS: 113-RAVEN-110
839 [    8.686357] [drm] vm size is 262144 GB, 4 levels, block size is 9-bi=
t,
fragment size is 9-bit
...
854 [    8.688113] [drm] Found VCN firmware Version: 1.73 Family ID: 18
...
 857 [    8.797714] [drm] DM_PPLIB: values for Invalid clock
    858 [    8.797715] [drm] DM_PPLIB:   0 in kHz
    859 [    8.797715] [drm] DM_PPLIB:   400000 in kHz
    860 [    8.797716] [drm] DM_PPLIB:   933000 in kHz
    861 [    8.797716] [drm] DM_PPLIB:   1067000 in kHz
    862 [    8.797809] WARNING: CPU: 6 PID: 725 at
drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1380
dcn_bw_update_from_pplib+0x16b/0x280 [amdgpu]

This seems plain wrong to me - shouldn't it mention here the engine clock?

This WARNING stems from not getting the clock values right - seems intended.

The same warning occurs again, I wildly guess for the memory (?!).

Line 862-1017 - only afterwards the mentioned "core_link_enable_stream=
" bug
occurs. It seems to me - as a total layman - that the initialization fails =
and
afterwards bogus happens.

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