Bug 210867

Summary: I get a blank screen on boot
Product: Drivers Reporter: alex14641
Component: Video(Other)Assignee: drivers_video-other
Status: NEW ---    
Severity: blocking CC: ajb
Priority: P1    
Hardware: x86-64   
OS: Linux   
Kernel Version: 5.10.x Subsystem:
Regression: Yes Bisected commit-id:
Attachments: Kernel config file

Description alex14641 2020-12-23 03:33:07 UTC
Created attachment 294309 [details]
Kernel config file

After upgrading from 5.9.14 to 5.10.1, I get a black screen when I boot. The video card is an RX580. I bisected the issue to this commit:

commit 8353d30e747f4e5cdd867c6b054dbb85cdcc76a9
Author: Chiawen Huang <chiawen.huang@amd.com>
Date:   Fri Sep 25 10:54:55 2020 -0400

    drm/amd/display: disable stream if pixel clock changed with link active
    
    [Why]
    Vbios uses preferred timing to turn on edp but OS could use other
    timing.  If change pixel clock when link active, there is unexpected
    garbage on monitor.
    
    [How]
    Once pixel clock changed, the driver needs to disable stream.
    
    Signed-off-by: Chiawen Huang <chiawen.huang@amd.com>
    Reviewed-by: Tony Cheng <Tony.Cheng@amd.com>
    Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

diff --git a/drivers/gpu/drm/amd/display/dc/core/dc.c b/drivers/gpu/drm/amd/display/dc/core/dc.c
index 76946a7d47ca..2a725a5fba40 100644
--- a/drivers/gpu/drm/amd/display/dc/core/dc.c
+++ b/drivers/gpu/drm/amd/display/dc/core/dc.c
@@ -864,7 +864,6 @@ static void disable_vbios_mode_if_required(
                if (stream->link->local_sink &&
                        stream->link->local_sink->sink_signal == SIGNAL_TYPE_EDP) {
                        link = stream->link;
-                       break;
                }
 
                if (link != NULL) {


Reverting this commit allows my system to boot.
Comment 1 alex14641 2020-12-23 15:05:41 UTC
In addition to the blank screen, the system locks up: no ssh access.
Comment 2 alex14641 2020-12-30 20:24:33 UTC
As of 5.10.4, the issue is still present.
Comment 3 alex14641 2021-01-07 13:22:19 UTC
5.10.5 has resolved this issue.