linux-kernel - Regression: no display with Vega 56 AMD GPU bisected to commit bfdec2340478

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <010001645c459a1a-7702e186-5985-4c02-9983-7205df8e3232-000000@email.amazonses.com>
Date:   Mon, 2 Jul 2018 18:33:42 +0000
From:   Jeremy Cline <jeremy@...ine.org>
To:     Harry Wentland <harry.wentland@....com>,
        Alex Deucher <alexander.deucher@....com>
Cc:     Christian König <christian.koenig@....com>,
        "David (ChunMing) Zhou" <David1.Zhou@....com>,
        David Airlie <airlied@...ux.ie>, amd-gfx@...ts.freedesktop.org,
        dri-devel@...ts.freedesktop.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        mikhail.v.gavrilov@...il.com, regressions@...mhuis.info
Subject: Regression: no display with Vega 56 AMD GPU bisected to commit
 bfdec2340478

Hi folks,

A Fedora user, Mikhail (CCed), reported[0] a regression with their Vega
56 AMD GPU introduced by bfdec2340478 ("drm/amd/display: Implement
dm_pp_get_clock_levels_by_type_with_latency"). The symptom is that
nothing is displayed and looking at the logs (attached to the Bugzilla),
I see gnome-shell is failing with "Failed to set CRTC mode 3840x2160:
Invalid argument". The problem persists through 4.18 RC2 so it's not
fixed by 10dd2b865393 ("drm/amd/display: Fix wrong latency assignment
for VEGA clock levels").

I see a couple "if (!dm_pp_get_clock_levels_by_type_with_latency)"
blocks which would no longer be unconditionally run, but I don't know
enough to even guess at the problem.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1592110

Regards,
Jeremy