X-Received: by 2002:a17:90b:4aca:b0:1b9:ed62:b917 with SMTP id mh10-20020a17090b4aca00b001b9ed62b917mr2399079pjb.237.1645507796067; Mon, 21 Feb 2022 21:29:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645507796; cv=none; d=google.com; s=arc-20160816; b=a6cq3HjiU4eQFPujUzVX1n5u7kLHKG4qJhcWvmwc/W4n0cvbuNsDIakroFxftOjgtF i85tsXl9njdnk35cX5FsUd0iAWoJ4iG7jLX7s7a8BSo26KNJ+cx8F9AVbwv9w1ay/d9b tT9Af01YuFCFeYtqNbLFNUNU9anr31Ezhe3wSREptYh/w6iCuutcJ/pypkRd4rfMtseM MVEpP7WbzC9DYqsa5FlQtSxWcDzcEwGcWQ4EPpHB0qz1epgk3eIH8+i0FYilsiD6pU9M aQamEF+eQmnsXvJ8oXsyYjej2CkPoXtqZLgXhRqiCskBcrUnxQFnwoYeO+SKk+Cr/R1M JAUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=pB155swSBk49PDT+eCV95gPkeDDn9OZawdG0rhDIJRE=; b=jXgDTBBhaxkhyktYzie8VDUYqYVoCr0sRX0QTQFh0SHC3LSQz77rj+pDAYWejUasDM msI6XYsQSYH0tpWGIMJytrymdY0puvzsUZQ41+XZH5s20Ozj5yYLZA3hpsqZjT46FkaW A3BMb/pHgczDyJYHENr2cpRxs8SrrMJ2yw6PZmTcD1C7TKhBNtYQSh5srLmwiHfcf0Pw Xd5TLbzCHvfumcSDOElpJwk7Wp6hbMBX3LuxIVD0H0VXi61VCoY1A4MSN1NLDTJK2l9t 16+GzPhZZtW/8zR4dxY8ochOWlX6+UD5EDyjLoyQE3TTceREL1auGcJlnA7rCvjv8rlU B/0A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="pTEm/Q5Z"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id k12si20864102pgt.445.2022.02.21.21.29.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 21 Feb 2022 21:29:56 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="pTEm/Q5Z"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 21CC410A7DD; Mon, 21 Feb 2022 20:58:44 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1377494AbiBUORU (ORCPT + 99 others); Mon, 21 Feb 2022 09:17:20 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:52502 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1377499AbiBUORR (ORCPT ); Mon, 21 Feb 2022 09:17:17 -0500 Received: from mail-oo1-xc29.google.com (mail-oo1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2F945E090 for ; Mon, 21 Feb 2022 06:16:54 -0800 (PST) Received: by mail-oo1-xc29.google.com with SMTP id i10-20020a4aab0a000000b002fccf890d5fso13346335oon.5 for ; Mon, 21 Feb 2022 06:16:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pB155swSBk49PDT+eCV95gPkeDDn9OZawdG0rhDIJRE=; b=pTEm/Q5ZcaImrNLul2uOOW3JIgCy8oOGT2jyBGg61wUnKrLHJQTr05kDrMDQgV695N 1te6tuy7pP04E4lnDUN9mOiIFJsZcHM4yPrnagdJJyeWQ3w9iYRLb9QiPeBjGcenXbhr lQgeSWXKjMHcGBBdrupKXsEi1ihBo0LY1BTVIWnM/bumbva0Poc/3R8uP8e1KmUPX2aZ Ztj6Tr4JjzBiycTk7ncfqLhVq6MM1XdPoQe0PMQ0Z5IoAFBRw2kN8FLLksCzy1OabSdM H4f4vw+p3WEOFEjUG3LaZaruVUYe78BU3dIWogDIMp5ISBHKnTXi0lrZuY66Pp7Cxphk THMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pB155swSBk49PDT+eCV95gPkeDDn9OZawdG0rhDIJRE=; b=Z2hIO4omo6i0O4OJahhJi67C645zcO6Ewe/Kvr0jJVWizI5G1Cw3FLlDNSiiZ2uogZ eIuFQM6xisDu+pvJ2hAj3ADBqnI9d96yIEtxzOCbX+5ft0dCchTXsa8xdT+AQ4qWjf3b T0HHZ9NSZJthsZVXakF9yXTy9a03dl00ATZ6ynem4Vf+Wl+/AMR82Jsk28Vj7d+fapcQ qG/6SqfCI+y2lgnHaSIPXStTX1G7+QD6+03F9CjRDTTV5cRAhWIDtYq9vnIEdsg4L7Yy IIjc2CiJ0q2GFqx/R9WuHiuDcl4qUjwNF8V1XB2OKBdTQN61KBkUj/0GYipjmBmVgOwJ yc0w== X-Gm-Message-State: AOAM530LE0wPZXdAwEjrty9W7tBiuhJemgNxcgfVkcjz50bRoJE7Dr+4 0swak1VgBSZRe5y6Xgox9rH6AiehZP7xsOH+IhM= X-Received: by 2002:a05:6870:3e0d:b0:d3:fe6d:57c3 with SMTP id lk13-20020a0568703e0d00b000d3fe6d57c3mr4707614oab.225.1645453013462; Mon, 21 Feb 2022 06:16:53 -0800 (PST) MIME-Version: 1.0 References: <5164225.DI6hChFYCN@ylum> In-Reply-To: From: Alex Deucher Date: Mon, 21 Feb 2022 09:16:42 -0500 Message-ID: Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend? To: Eric Valette Cc: Dominique Dumont , Salvatore Bonaccorso , Sasha Levin , amd-gfx list , David Airlie , "Pan, Xinhui" , LKML , Maling list - DRI developers , Luben Tuikov , 1005005@bugs.debian.org, Alex Deucher , Evan Quan , =?UTF-8?Q?Christian_K=C3=B6nig?= Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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 Mon, Feb 21, 2022 at 3:29 AM Eric Valette wrote: > > 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. It doesn't really matter what the platform is, it could still potentially help on your system, it depends on the bios implementation for your platform and how it handles suspend. You can try the patch, but I don't think you are hitting the same issue. I bisect would be helpful in your case. Alex