From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ot1-f50.google.com (mail-ot1-f50.google.com [209.85.210.50]) (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 5CAF244390 for ; Tue, 28 Nov 2023 22:13:15 +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="NrscATeC" Received: by mail-ot1-f50.google.com with SMTP id 46e09a7af769-6d7e56f6845so3669756a34.0 for ; Tue, 28 Nov 2023 14:13:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701209594; x=1701814394; 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=bzkua+PtowZpetcv1vSwzhlAqYyVuNpPQqTrqldHUFg=; b=NrscATeCj86tcYq6IPYFj0UrplL4zIm+dsUiFG+ItOrhD/Pb1efGXA+Z0abc/xloqB 8cpEEKu8swNjiwAGlhC0dtkOTtimWrs5VdyG7C3dN7CdeJ0E9dIrvBWnUEM4XO0EBPcs gfI4ouA9wDT7IKGfVciCe+GpjBVOMCvxeJDHG4sBqOkBhTQsjQxRrkAeTDUMw5vNss46 BFX5FKiC8t6+9uNvLcWuz5NMA7bwGetPxakcb8qdMnv4Wr2yLaJ+uveAY4YgEAhTSuKT Hn56HEtbyKm+tFKBl5eEHCjCKsaDm+BOZqC4wcTyOZd2RASMknNn/vlVg0IOZlVgwZwJ S68Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701209594; x=1701814394; 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=bzkua+PtowZpetcv1vSwzhlAqYyVuNpPQqTrqldHUFg=; b=AAFDZOWMJpirEIOq21qoua6rsPq0dtr/T9mtyZqiOygAViKz+smVRH+wiyO2AJzYnJ JKmNStJUWmEDgvKZYzJzMC4oDU+Boe4Bod9M8y5emrlFRREla33SdRRjqpJ+vCoFp05v m4T2aeXZVDvohLnGrNPbwhjUsfCWlKSYjStwo6H0QGssEJIMV79rmRhUJ/cGK0VamY3r 9jLcd++1Q67nIvNgfj3uciOQy1Sp6WiVztdjRdpOYBabUpkUUeScm11RwKEnB1VzCq+S O28e3Mp0h3RB9lqxwI7kyYp/OaqRZAIAFQFL4pY7nWkmj+sCdf9Aa9DDW3s9Ng3pD70H 3agQ== X-Gm-Message-State: AOJu0YwjMQmSE4p/UtLrmH5ajqF+KFkGHRfuMcbVT/wAo4Jhws79M8ud oh4d1mK2bnoauo6/roYgguQ5M3rTZC3OUR0wuSw= X-Google-Smtp-Source: AGHT+IFbrCgwO30ksnJPK0vfsHqHO0Uot3qklNhA8h4Ae+35H6kZ7mEYmIQO0afjWRq/2USC0OYc3UiMQOZSlgVxD34= X-Received: by 2002:a05:6870:ebca:b0:1e9:9989:33a5 with SMTP id cr10-20020a056870ebca00b001e9998933a5mr23314739oab.5.1701209594307; Tue, 28 Nov 2023 14:13:14 -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> <87jzq2ixtm.fsf@vps.thesusis.net> In-Reply-To: <87jzq2ixtm.fsf@vps.thesusis.net> From: Alex Deucher Date: Tue, 28 Nov 2023 17:13:03 -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 27, 2023 at 6:24=E2=80=AFPM Phillip Susi w= rote: > > Alex Deucher writes: > > >> In that case those are the already known problems with the scheduler > >> changes, aren't they? > > > > 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 > > At some point it was suggested that I file a gitlab issue, but I took > this to mean it was already known and being worked on. -rc3 came out > today and still has the problem. Is there a known issue I could track? > At this point, unless there are any objections, I think we should just revert the two patches. 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 23398C4167B for ; Tue, 28 Nov 2023 22:13:17 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 884F410E193; Tue, 28 Nov 2023 22:13:16 +0000 (UTC) Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) by gabe.freedesktop.org (Postfix) with ESMTPS id 222FC10E193; Tue, 28 Nov 2023 22:13:15 +0000 (UTC) Received: by mail-ot1-x32b.google.com with SMTP id 46e09a7af769-6ce2988d62eso3659708a34.1; Tue, 28 Nov 2023 14:13:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701209594; x=1701814394; 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=bzkua+PtowZpetcv1vSwzhlAqYyVuNpPQqTrqldHUFg=; b=eKEH6jI+2YRKZHo6GkbT1bne1JxumQrvUPdv/rO/cJ1Xmlo++r+P5T5IDoOZTdIKii hSpGCrBZhyHez3M79gzeTP5er53HHFLdsqXpcwnnsmZHrb1Sx2kMtsmKcuX+go3EcKkA yJodKvJgk1c4jGJUtT2ezMEwt1+WvD229Iqk1NFtJ7QLZJesZUaIIxyWG19CRzW2grlo m6+8MmF67nAtngKRmO0fn3+Ey4p5Q1yKkG6+XIFHjBdNOoxyRBUhtcVEyZD6GVVKwv4h 8QBJU8M61YX3kxaat6JXTe+9545q5LxfeIRcHvSC9SZaXMmUR0dsHSmUWHC4VqqfTG4t EcQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701209594; x=1701814394; 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=bzkua+PtowZpetcv1vSwzhlAqYyVuNpPQqTrqldHUFg=; b=fUQmVJqv6qkZhZv5ATn6LBcLCQW2QRv0SlGleJEl3wWKido3TaEC6iegk/jxbWkw1a eVXPBpiw4qs62sBdBDGupFWnib6vN/ChcImZW+fSxSv/FardljHmsePYEiSfArgfjpAu EzfALPsxM8G7m1qdH9TlfiMJJnVt/ErwRvp9OreZ//Z7toqz3HvD0OCT1uwYFTZG8itN EPR0TmP4yx2utW+L5ZEGDIPWH/LgUgeWJuSA4bWw1m1mKR4+oRfO8n9KY7NxiA68Z4Yh 7X4N0wGrTR0/Vy0WK1v0SErYTIrwI72ALDHypEu11Bw5Llx4DYzLDC1SU4yy18SX9XpP 3r8w== X-Gm-Message-State: AOJu0YyPjoMCKe1SyiWRfFJ+Ig+CALsQjnLOomGeNIn+TnjDOYvdctRs LygeyEgHhCexUon1L7RwOt0oiPJM3RL4hS2PwV8= X-Google-Smtp-Source: AGHT+IFbrCgwO30ksnJPK0vfsHqHO0Uot3qklNhA8h4Ae+35H6kZ7mEYmIQO0afjWRq/2USC0OYc3UiMQOZSlgVxD34= X-Received: by 2002:a05:6870:ebca:b0:1e9:9989:33a5 with SMTP id cr10-20020a056870ebca00b001e9998933a5mr23314739oab.5.1701209594307; Tue, 28 Nov 2023 14:13:14 -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> <87jzq2ixtm.fsf@vps.thesusis.net> In-Reply-To: <87jzq2ixtm.fsf@vps.thesusis.net> From: Alex Deucher Date: Tue, 28 Nov 2023 17:13:03 -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 27, 2023 at 6:24=E2=80=AFPM Phillip Susi w= rote: > > Alex Deucher writes: > > >> In that case those are the already known problems with the scheduler > >> changes, aren't they? > > > > 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 > > At some point it was suggested that I file a gitlab issue, but I took > this to mean it was already known and being worked on. -rc3 came out > today and still has the problem. Is there a known issue I could track? > At this point, unless there are any objections, I think we should just revert the two patches. 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 B07F1C4167B for ; Tue, 28 Nov 2023 22:13:21 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 514B910E341; Tue, 28 Nov 2023 22:13:17 +0000 (UTC) Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) by gabe.freedesktop.org (Postfix) with ESMTPS id 222FC10E193; Tue, 28 Nov 2023 22:13:15 +0000 (UTC) Received: by mail-ot1-x32b.google.com with SMTP id 46e09a7af769-6ce2988d62eso3659708a34.1; Tue, 28 Nov 2023 14:13:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701209594; x=1701814394; 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=bzkua+PtowZpetcv1vSwzhlAqYyVuNpPQqTrqldHUFg=; b=eKEH6jI+2YRKZHo6GkbT1bne1JxumQrvUPdv/rO/cJ1Xmlo++r+P5T5IDoOZTdIKii hSpGCrBZhyHez3M79gzeTP5er53HHFLdsqXpcwnnsmZHrb1Sx2kMtsmKcuX+go3EcKkA yJodKvJgk1c4jGJUtT2ezMEwt1+WvD229Iqk1NFtJ7QLZJesZUaIIxyWG19CRzW2grlo m6+8MmF67nAtngKRmO0fn3+Ey4p5Q1yKkG6+XIFHjBdNOoxyRBUhtcVEyZD6GVVKwv4h 8QBJU8M61YX3kxaat6JXTe+9545q5LxfeIRcHvSC9SZaXMmUR0dsHSmUWHC4VqqfTG4t EcQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701209594; x=1701814394; 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=bzkua+PtowZpetcv1vSwzhlAqYyVuNpPQqTrqldHUFg=; b=fUQmVJqv6qkZhZv5ATn6LBcLCQW2QRv0SlGleJEl3wWKido3TaEC6iegk/jxbWkw1a eVXPBpiw4qs62sBdBDGupFWnib6vN/ChcImZW+fSxSv/FardljHmsePYEiSfArgfjpAu EzfALPsxM8G7m1qdH9TlfiMJJnVt/ErwRvp9OreZ//Z7toqz3HvD0OCT1uwYFTZG8itN EPR0TmP4yx2utW+L5ZEGDIPWH/LgUgeWJuSA4bWw1m1mKR4+oRfO8n9KY7NxiA68Z4Yh 7X4N0wGrTR0/Vy0WK1v0SErYTIrwI72ALDHypEu11Bw5Llx4DYzLDC1SU4yy18SX9XpP 3r8w== X-Gm-Message-State: AOJu0YyPjoMCKe1SyiWRfFJ+Ig+CALsQjnLOomGeNIn+TnjDOYvdctRs LygeyEgHhCexUon1L7RwOt0oiPJM3RL4hS2PwV8= X-Google-Smtp-Source: AGHT+IFbrCgwO30ksnJPK0vfsHqHO0Uot3qklNhA8h4Ae+35H6kZ7mEYmIQO0afjWRq/2USC0OYc3UiMQOZSlgVxD34= X-Received: by 2002:a05:6870:ebca:b0:1e9:9989:33a5 with SMTP id cr10-20020a056870ebca00b001e9998933a5mr23314739oab.5.1701209594307; Tue, 28 Nov 2023 14:13:14 -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> <87jzq2ixtm.fsf@vps.thesusis.net> In-Reply-To: <87jzq2ixtm.fsf@vps.thesusis.net> From: Alex Deucher Date: Tue, 28 Nov 2023 17:13:03 -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 27, 2023 at 6:24=E2=80=AFPM Phillip Susi w= rote: > > Alex Deucher writes: > > >> In that case those are the already known problems with the scheduler > >> changes, aren't they? > > > > 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 > > At some point it was suggested that I file a gitlab issue, but I took > this to mean it was already known and being worked on. -rc3 came out > today and still has the problem. Is there a known issue I could track? > At this point, unless there are any objections, I think we should just revert the two patches. Alex