From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7B6F0C433E0 for ; Tue, 5 Jan 2021 16:33:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 259B822CA2 for ; Tue, 5 Jan 2021 16:33:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725868AbhAEQdK (ORCPT ); Tue, 5 Jan 2021 11:33:10 -0500 Received: from mail1.ugh.no ([178.79.162.34]:58008 "EHLO mail1.ugh.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728752AbhAEQdK (ORCPT ); Tue, 5 Jan 2021 11:33:10 -0500 Received: from localhost (localhost [127.0.0.1]) by mail1.ugh.no (Postfix) with ESMTP id EB58D253956; Tue, 5 Jan 2021 17:32:28 +0100 (CET) Received: from mail1.ugh.no ([127.0.0.1]) by localhost (catastrophix.ugh.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfSrOnDksqq7; Tue, 5 Jan 2021 17:32:28 +0100 (CET) Received: from [IPv6:2a0a:2780:4d57:40:54fd:5612:86a2:2c2f] (unknown [IPv6:2a0a:2780:4d57:40:54fd:5612:86a2:2c2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: andre@tomt.net) by mail.ugh.no (Postfix) with ESMTPSA id 439CA253954; Tue, 5 Jan 2021 17:32:28 +0100 (CET) Subject: Re: [PATCH 5.10 637/717] drm/amd/display: Fix memory leaks in S3 resume To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, Harry Wentland , Alex Deucher , Nicholas Kazlauskas , Stylon Wang References: <20201228125020.963311703@linuxfoundation.org> <20201228125051.444911072@linuxfoundation.org> From: Andre Tomt Message-ID: <8db47895-e7e4-ed9a-e996-c071b5c6f750@tomt.net> Date: Tue, 5 Jan 2021 17:32:27 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On 05.01.2021 07:54, Greg Kroah-Hartman wrote: > On Mon, Jan 04, 2021 at 08:04:08PM +0100, Andre Tomt wrote: >> On 28.12.2020 13:50, Greg Kroah-Hartman wrote: >>> From: Stylon Wang >>> >>> commit a135a1b4c4db1f3b8cbed9676a40ede39feb3362 upstream. >>> >>> EDID parsing in S3 resume pushes new display modes >>> to probed_modes list but doesn't consolidate to actual >>> mode list. This creates a race condition when >>> amdgpu_dm_connector_ddc_get_modes() re-initializes the >>> list head without walking the list and results in memory leak. >> >> This commit is causing me problems on 5.10.4: when I turn off the display (a >> LG TV in this case), and turn it back on again later there is no video >> output and I get the following in the kernel log: >> >> [ 8245.259628] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* >> Restoring old state failed with -12 >> >> I've found another report on this commit as well: >> https://bugzilla.kernel.org/show_bug.cgi?id=211033 >> >> And I suspect this is the same: >> https://bugs.archlinux.org/task/69202 >> >> Reverting it from 5.10.4 makes things behave again. >> >> Have not tested 5.4.86 or 5.11-rc. >> >> I'm using a RX570 Polaris based card. > > Can you test 5.11-rc to see if this issue is there as well? Just did, and have the same issue on 5.11-rc2. Reverting it also solves the problem on 5.11-rc2, as it does on 5.10.4 FWIW one easy way to reproduce seems to be unplugging and re-plugging the HDMI.