From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oa1-f43.google.com (mail-oa1-f43.google.com [209.85.160.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BF21451C50 for ; Tue, 21 Nov 2023 14:05:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="bILNtLup" Received: by mail-oa1-f43.google.com with SMTP id 586e51a60fabf-1ea82246069so3123576fac.3 for ; Tue, 21 Nov 2023 06:05:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700575550; x=1701180350; darn=lists.linux.dev; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=JicfpEa3uNWDUz2NDkVsyh217wG6PJj7MozXv7sFA4w=; b=bILNtLupsf4CsYF0YnZ3uilJMuTIY/Ww4DSydkP/Y3/c0ArO4FgHz8niAIfEPLpqlR +RTHeXoQ0IIJG+ezheLByI6mAOjXYev9jX9YexYjsnZsNFW1g02pmh8QyvJvIr9X1y7+ 3kUTNNAm2gVI5nO5PXP4xJ8GT5SH+emqkujvi1xGZ55EXSRhWDBxqHkccPfpWBKxQa1u jIg9sILCXPj5pjgc7tZSWfhpqEmRLMGcP8Jn7Ivm8txqBvx7SA4OtGltmxqhzRHFML/I jwv2Wgc0LkekAP4KtHuYzOmCn2kPdZNYfmGgKxHM2jKjab4e5kJwCj/Fp6/7U3itPd5i OqVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700575550; x=1701180350; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=JicfpEa3uNWDUz2NDkVsyh217wG6PJj7MozXv7sFA4w=; b=VH+YrjdyDlfGicDqUYxJyabWOwx2o4bTd/HIr0abKIYI7+8vCKnzHymgIzNi6vtPLI CozXoZa1euPjASBvOP/GoNZ3rr6ocFwViRUFrkw8SfF31bGhN8BCroxNF8gzpYYEtMo6 oT/kFQdEBGkMMLD3ayDKOPKypZk+2SpYkIxqYxJRtCPIx7IC3KIaLIv3hCBEPRIYy8xc JPAkmzKw0FElQLCMzF7sIfmfxKRIIuLqY0ZUQ9FLrBGJ9/x/gNbO/jxidhOfBmlng+h6 K+fJjiEGMLt9x+Epg+KiEebovEVVH4RfPa+ar2K6S5KeI2O8QVMoEotKCYaiywGYTm2K VHYA== X-Gm-Message-State: AOJu0Yy3jd9btdKAqh90KVIjgMkxTj1toTURlUMrEk+tq9IJ7E3abXEx /OHsizApacH98YLmg8Y2DKE1x3vRSfeaPSfNiAM= X-Google-Smtp-Source: AGHT+IHKHQMKS3b1gLqqox30Lk4uUwKC52JYW8VCEcKNOaYp9uPK894sLiFLuA30J+s9SqYcbYaSE9jt5JVjnAUgiXE= X-Received: by 2002:a05:6871:7398:b0:1f5:994:9853 with SMTP id na24-20020a056871739800b001f509949853mr13022151oac.22.1700575550741; Tue, 21 Nov 2023 06:05:50 -0800 (PST) Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 References: <87edgv4x3i.fsf@vps.thesusis.net> <559d0fa5-953a-4a97-b03b-5eb1287c83d8@leemhuis.info> <96e2e13c-f01c-4baf-a9a3-cbaa48fb10c7@amd.com> <87bkbodp51.fsf@vps.thesusis.net> In-Reply-To: <87bkbodp51.fsf@vps.thesusis.net> From: Alex Deucher Date: Tue, 21 Nov 2023 09:05:39 -0500 Message-ID: Subject: Re: Radeon regression in 6.6 kernel To: Phillip Susi Cc: =?UTF-8?Q?Christian_K=C3=B6nig?= , =?UTF-8?Q?Christian_K=C3=B6nig?= , Dave Airlie , Linux regressions mailing list , linux-kernel@vger.kernel.org, "amd-gfx@lists.freedesktop.org" , Luben Tuikov , dri-devel@lists.freedesktop.org, Alex Deucher Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Nov 20, 2023 at 5:40=E2=80=AFPM Phillip Susi w= rote: > > Alex Deucher writes: > > > Yes. Those changes went into 6.7 though, not 6.6 AFAIK. Maybe I'm > > misunderstanding what the original report was actually testing. If it > > was 6.7, then try reverting: > > 56e449603f0ac580700621a356d35d5716a62ce5 > > b70438004a14f4d0f9890b3297cd66248728546c > > I had been running v6.6-rc5 before pulling. It looks like that got me > somewhere between v6.6 and v6.7-rc1. Reverting those two commits fixes > it. Does reverting 56e449603f0ac580700621a356d35d5716a62ce5 alone fix it? Can you also attach your full dmesg log for the failed suspend? Alex 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 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D8666C61D94 for ; Tue, 21 Nov 2023 14:05:56 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id F15E110E02C; Tue, 21 Nov 2023 14:05:53 +0000 (UTC) Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) by gabe.freedesktop.org (Postfix) with ESMTPS id 80DE610E02C; Tue, 21 Nov 2023 14:05:51 +0000 (UTC) Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-1f03d9ad89fso3134973fac.1; Tue, 21 Nov 2023 06:05:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700575550; x=1701180350; darn=lists.freedesktop.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=JicfpEa3uNWDUz2NDkVsyh217wG6PJj7MozXv7sFA4w=; b=VnqrX9hZzzlnkcVS0uLxllOAsddAh/mM/8gqRibK7Npe91cpe9o7LHuT6yehTedqB/ A1/6Fuzjq/5+rbZPMGrlhI9Kdwz7bFLUCfU+MtoPgLdTj3S8agyZVbqtabls+5lZtfPY 6q7Eb9jLSTm8oNTXDR5HFzEu6jDeTXe+LZzYJGCHi5RpOzPcBENIXgdEkqhPQXE/oxJ4 kpURjQ6bJLmdTrd2qyeJjRys1LajuCmRk+Rd71tbrF7lvQT6dEl9rh/cDOS300vzvgFg Yx/i6PQ7fCbZ7knQDSMgCQkdomF34BnmMXz2czseQlnGXnYjDhH76VDtoul5Zv2nejp7 DAnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700575550; x=1701180350; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=JicfpEa3uNWDUz2NDkVsyh217wG6PJj7MozXv7sFA4w=; b=U08pTa6BEzBoEoHeHrN5LF53LexUbhoHnmzS57qQDLdsSFXUsWEwOdn+Pv1UISsooE z4FkLGAqr3KyJhidLHQhOFn0jZ+IZlK11Dor+cSmptsEo3YjcIlf5h72fykXbGqGTNL7 miNYLfs7iMyE+mgSa8rMzPeULiSROW87fbcP8VGW2guFjBF8oARz+56cKp5X8T9JKPM/ 4V2YqrUM9AWu8yoIEQVmyStFXUMuZ+FGp562bYZB8FlLgAKclXXtPw6AB6C3Wn6ILAXk QSIPXBnbpG3cuDTlDYY3Tm22KpHwh1T/sPby7NClEugL2FGnnUuUSQwU4T1H6mDG/oHL avGw== X-Gm-Message-State: AOJu0YwhOGVIOhmqxbzjTBByqbQXkfh6x6vvTgjUXbz556MkB1PLSoWy JEvpDprkzam7imrGWPACVdVY4ZuTSGILgFxaht0= X-Google-Smtp-Source: AGHT+IHKHQMKS3b1gLqqox30Lk4uUwKC52JYW8VCEcKNOaYp9uPK894sLiFLuA30J+s9SqYcbYaSE9jt5JVjnAUgiXE= X-Received: by 2002:a05:6871:7398:b0:1f5:994:9853 with SMTP id na24-20020a056871739800b001f509949853mr13022151oac.22.1700575550741; Tue, 21 Nov 2023 06:05:50 -0800 (PST) MIME-Version: 1.0 References: <87edgv4x3i.fsf@vps.thesusis.net> <559d0fa5-953a-4a97-b03b-5eb1287c83d8@leemhuis.info> <96e2e13c-f01c-4baf-a9a3-cbaa48fb10c7@amd.com> <87bkbodp51.fsf@vps.thesusis.net> In-Reply-To: <87bkbodp51.fsf@vps.thesusis.net> From: Alex Deucher Date: Tue, 21 Nov 2023 09:05:39 -0500 Message-ID: Subject: Re: Radeon regression in 6.6 kernel To: Phillip Susi Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux regressions mailing list , =?UTF-8?Q?Christian_K=C3=B6nig?= , linux-kernel@vger.kernel.org, "amd-gfx@lists.freedesktop.org" , Luben Tuikov , dri-devel@lists.freedesktop.org, Alex Deucher , =?UTF-8?Q?Christian_K=C3=B6nig?= Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Mon, Nov 20, 2023 at 5:40=E2=80=AFPM Phillip Susi w= rote: > > Alex Deucher writes: > > > Yes. Those changes went into 6.7 though, not 6.6 AFAIK. Maybe I'm > > misunderstanding what the original report was actually testing. If it > > was 6.7, then try reverting: > > 56e449603f0ac580700621a356d35d5716a62ce5 > > b70438004a14f4d0f9890b3297cd66248728546c > > I had been running v6.6-rc5 before pulling. It looks like that got me > somewhere between v6.6 and v6.7-rc1. Reverting those two commits fixes > it. Does reverting 56e449603f0ac580700621a356d35d5716a62ce5 alone fix it? Can you also attach your full dmesg log for the failed suspend? Alex 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 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BA53CC61D92 for ; Tue, 21 Nov 2023 14:05:54 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 4379310E096; Tue, 21 Nov 2023 14:05:54 +0000 (UTC) Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) by gabe.freedesktop.org (Postfix) with ESMTPS id 80DE610E02C; Tue, 21 Nov 2023 14:05:51 +0000 (UTC) Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-1f03d9ad89fso3134973fac.1; Tue, 21 Nov 2023 06:05:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700575550; x=1701180350; darn=lists.freedesktop.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=JicfpEa3uNWDUz2NDkVsyh217wG6PJj7MozXv7sFA4w=; b=VnqrX9hZzzlnkcVS0uLxllOAsddAh/mM/8gqRibK7Npe91cpe9o7LHuT6yehTedqB/ A1/6Fuzjq/5+rbZPMGrlhI9Kdwz7bFLUCfU+MtoPgLdTj3S8agyZVbqtabls+5lZtfPY 6q7Eb9jLSTm8oNTXDR5HFzEu6jDeTXe+LZzYJGCHi5RpOzPcBENIXgdEkqhPQXE/oxJ4 kpURjQ6bJLmdTrd2qyeJjRys1LajuCmRk+Rd71tbrF7lvQT6dEl9rh/cDOS300vzvgFg Yx/i6PQ7fCbZ7knQDSMgCQkdomF34BnmMXz2czseQlnGXnYjDhH76VDtoul5Zv2nejp7 DAnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700575550; x=1701180350; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=JicfpEa3uNWDUz2NDkVsyh217wG6PJj7MozXv7sFA4w=; b=U08pTa6BEzBoEoHeHrN5LF53LexUbhoHnmzS57qQDLdsSFXUsWEwOdn+Pv1UISsooE z4FkLGAqr3KyJhidLHQhOFn0jZ+IZlK11Dor+cSmptsEo3YjcIlf5h72fykXbGqGTNL7 miNYLfs7iMyE+mgSa8rMzPeULiSROW87fbcP8VGW2guFjBF8oARz+56cKp5X8T9JKPM/ 4V2YqrUM9AWu8yoIEQVmyStFXUMuZ+FGp562bYZB8FlLgAKclXXtPw6AB6C3Wn6ILAXk QSIPXBnbpG3cuDTlDYY3Tm22KpHwh1T/sPby7NClEugL2FGnnUuUSQwU4T1H6mDG/oHL avGw== X-Gm-Message-State: AOJu0YwhOGVIOhmqxbzjTBByqbQXkfh6x6vvTgjUXbz556MkB1PLSoWy JEvpDprkzam7imrGWPACVdVY4ZuTSGILgFxaht0= X-Google-Smtp-Source: AGHT+IHKHQMKS3b1gLqqox30Lk4uUwKC52JYW8VCEcKNOaYp9uPK894sLiFLuA30J+s9SqYcbYaSE9jt5JVjnAUgiXE= X-Received: by 2002:a05:6871:7398:b0:1f5:994:9853 with SMTP id na24-20020a056871739800b001f509949853mr13022151oac.22.1700575550741; Tue, 21 Nov 2023 06:05:50 -0800 (PST) MIME-Version: 1.0 References: <87edgv4x3i.fsf@vps.thesusis.net> <559d0fa5-953a-4a97-b03b-5eb1287c83d8@leemhuis.info> <96e2e13c-f01c-4baf-a9a3-cbaa48fb10c7@amd.com> <87bkbodp51.fsf@vps.thesusis.net> In-Reply-To: <87bkbodp51.fsf@vps.thesusis.net> From: Alex Deucher Date: Tue, 21 Nov 2023 09:05:39 -0500 Message-ID: Subject: Re: Radeon regression in 6.6 kernel To: Phillip Susi Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: amd-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion list for AMD gfx List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux regressions mailing list , =?UTF-8?Q?Christian_K=C3=B6nig?= , linux-kernel@vger.kernel.org, "amd-gfx@lists.freedesktop.org" , Luben Tuikov , dri-devel@lists.freedesktop.org, Alex Deucher , Dave Airlie , =?UTF-8?Q?Christian_K=C3=B6nig?= Errors-To: amd-gfx-bounces@lists.freedesktop.org Sender: "amd-gfx" On Mon, Nov 20, 2023 at 5:40=E2=80=AFPM Phillip Susi w= rote: > > Alex Deucher writes: > > > Yes. Those changes went into 6.7 though, not 6.6 AFAIK. Maybe I'm > > misunderstanding what the original report was actually testing. If it > > was 6.7, then try reverting: > > 56e449603f0ac580700621a356d35d5716a62ce5 > > b70438004a14f4d0f9890b3297cd66248728546c > > I had been running v6.6-rc5 before pulling. It looks like that got me > somewhere between v6.6 and v6.7-rc1. Reverting those two commits fixes > it. Does reverting 56e449603f0ac580700621a356d35d5716a62ce5 alone fix it? Can you also attach your full dmesg log for the failed suspend? Alex