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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 29EBDC4167B for ; Mon, 27 Nov 2023 23:25:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233685AbjK0XYu (ORCPT ); Mon, 27 Nov 2023 18:24:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47990 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229821AbjK0XYt (ORCPT ); Mon, 27 Nov 2023 18:24:49 -0500 Received: from vps.thesusis.net (vps.thesusis.net [34.202.238.73]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6BC841AA for ; Mon, 27 Nov 2023 15:24:54 -0800 (PST) Received: by vps.thesusis.net (Postfix, from userid 1000) id 64FAA14ACC1; Mon, 27 Nov 2023 18:24:53 -0500 (EST) From: Phillip Susi To: Alex Deucher , Christian =?utf-8?Q?K=C3=B6nig?= Cc: Christian =?utf-8?Q?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 Subject: Re: Radeon regression in 6.6 kernel In-Reply-To: References: <87edgv4x3i.fsf@vps.thesusis.net> <559d0fa5-953a-4a97-b03b-5eb1287c83d8@leemhuis.info> <96e2e13c-f01c-4baf-a9a3-cbaa48fb10c7@amd.com> Date: Mon, 27 Nov 2023 18:24:53 -0500 Message-ID: <87jzq2ixtm.fsf@vps.thesusis.net> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?