Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp3537374pxb; Sun, 20 Feb 2022 23:33:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJyahcsVXYYcdzBe/3I6d3HAMKjNlylPwlr03jEjLRE8JouR0vnu3ZyO4v5+0FzVvlSlkfmJ X-Received: by 2002:a50:f69c:0:b0:410:8241:580c with SMTP id d28-20020a50f69c000000b004108241580cmr19545121edn.100.1645428805016; Sun, 20 Feb 2022 23:33:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645428805; cv=none; d=google.com; s=arc-20160816; b=whqTmk5i7Kyjtf6pEziSe3PFVVDgH0CRWpbm3jXEWAtK0sUS2roYkVtipVOsSIeWcQ vPign1pgBkBAIXezof8hHB4p/eE9jXGFjGrRhWxNDng56BfchBC8SwKZY8OGJ9FRPmlS swJUjMlmaNU8gQMbH6HliRaF3N8B/K5lMWeSWbBqYjufYMSG15or6795PtR8WpV1Q/Xt liq9aJyDjcdDx8gRQNzMwkVjuO8eFtpxmRycgr7/5DGfWJSES4bSNMIHO1GcHMo+2PnE dN9JwXbriOwF0AYL/1U0VQ4DlYQEooc5zzUIaWi07W+OScb2tMKWf3Ik61JlolQwxmjb nsrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :organization:from:references:cc:to:content-language:subject :reply-to:user-agent:mime-version:date:message-id:dkim-signature; bh=cHZBQIKok84oNba5CwWPt6fBomQ+GJa2KSKogtXqQrQ=; b=bIpsQUY9oM+/qtMQJtlIUguJ+tQppoPewugm96YAxu/vxXRAjNz2vE9MPh8qGirRkO sDDH8qE72GxLUmteCqFKw6HoXT10xhRtY08486Ro/BYbXJoTFfWQCBwMwT1JMdtveeqa zwxaR7mGgJSEnAgukE+o3vgoJixhXRYzOVuVi/6Qx1C4WDFzaqlicdcd7z6sGP9KTbZj EUXUI7M4l2MCz/m7Knva7RoIWNHTjb2KfCucvKt3A7EVavQF4NAWa3tJBiJcbMKeNN1U XFYGAuL6pWGmLX+pPGhdSIILWxgcf+GbQlLYAuCjjj70sskODufKHHmVTfPrvz1oTkRu IyjQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@free.fr header.s=smtp-20201208 header.b=rhWZ1j23; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=free.fr Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i22si9700049ejw.760.2022.02.20.23.33.02; Sun, 20 Feb 2022 23:33:25 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@free.fr header.s=smtp-20201208 header.b=rhWZ1j23; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=free.fr Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243346AbiBTSEB (ORCPT + 99 others); Sun, 20 Feb 2022 13:04:01 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:57474 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234727AbiBTSEA (ORCPT ); Sun, 20 Feb 2022 13:04:00 -0500 Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C1EAC41635 for ; Sun, 20 Feb 2022 10:03:38 -0800 (PST) Received: from [192.168.8.33] (unknown [90.19.9.37]) (Authenticated sender: eric.valette@free.fr) by smtp5-g21.free.fr (Postfix) with ESMTPSA id 7A5715FF33; Sun, 20 Feb 2022 19:03:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=free.fr; s=smtp-20201208; t=1645380216; bh=IukDJ5h4L2PHp9stLtKdlNNaLlvJkJUdojizUPTPeKM=; h=Date:Reply-To:Subject:To:Cc:References:From:In-Reply-To:From; b=rhWZ1j23EvxNsTknNLs/om+90oVmS28biKPyhdT0QbJKoeCDCPP/IkJNUAT/7Iiws nwFNm3+uHfm6F5dEPB+CiraRY8nhNVeGMhiNc1H4WmVJXdtxvKd11zFwtqbQYhrjB+ tP8jetzDa2dp08glWC1IjM63nqUJ7yWbxHXMCNkjt0C2NA8aMAIHMZx2zjTU6gE+D4 iRs3ese+SaeryZ7VV0NPAMLHjFcKoFVb/AtQybhKlngF7GnyrRPoQrIrQPIbJT7c3Q 9Pq4H0XINOZM9iesgyddmAcGAzy155Jrx9IYRprJG212qCesOH0Se9anppF4NwLiU0 44zHDMMtzfZwQ== Message-ID: Date: Sun, 20 Feb 2022 19:03:23 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Reply-To: eric.valette@free.fr Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend? Content-Language: en-US To: dod@debian.org, Salvatore Bonaccorso Cc: Alex Deucher , Sasha Levin , David Airlie , Maling list - DRI developers , "Pan, Xinhui" , LKML , 1005005@bugs.debian.org, Luben Tuikov , amd-gfx list , Evan Quan , =?UTF-8?Q?Christian_K=c3=b6nig?= References: <5164225.DI6hChFYCN@ylum> From: Eric Valette Organization: HOME In-Reply-To: <5164225.DI6hChFYCN@ylum> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/02/2022 16:48, Dominique Dumont wrote: > On Monday, 14 February 2022 22:52:27 CET Alex Deucher wrote: >> Does the system actually suspend? > > Not really. The screens looks like it's going to suspend, but it does come > back after 10s or so. The light mounted in the middle of the power button does > not switch off. As I have a very similar problem and also commented on the original debian bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005005), I will add some information here on another amd only laptop (renoir AMD Ryzen 7 4800H with Radeon Graphics + Radeon RX 5500/5500M / Pro 5500M). For me the suspend works once, but after the first resume (I do know know if it is in the suspend path or the resume path I see a RIP in the dmesg (see aditional info in debian bug)) and later suspend do not work: It only go to the kde login screen. I was unable due to network connectivity to do a full bisect but tested with the patch I had on my laptop: 5.10.101 works, 5.10 from debian works 5.11 works 5.12 works 5.13 suspend works but when resuming the PC is dead I have to reboot 5.14 seems to work but looking at dmesg it is full of RIP messages at various places. 5.15.24 is a described 5.15 from debian is behaving identically 5.16 from debian is behaving identically. >> Is this system S0i3 or regular S3? For me it is real S3. The proposed patch is intended for INTEl + intel gpu + amdgpu but I have dual amd GPU. --eric