[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADnq5_Ou-MVVm0rdWDmDnJNLkWUayXzO26uCEtz3ucNa4Ghy2w@mail.gmail.com>
Date: Tue, 28 Nov 2023 17:13:03 -0500
From: Alex Deucher <alexdeucher@...il.com>
To: Phillip Susi <phill@...susis.net>
Cc: Christian König <christian.koenig@....com>,
Christian König <ckoenig.leichtzumerken@...il.com>,
Dave Airlie <airlied@...il.com>,
Linux regressions mailing list <regressions@...ts.linux.dev>,
linux-kernel@...r.kernel.org,
"amd-gfx@...ts.freedesktop.org" <amd-gfx@...ts.freedesktop.org>,
Luben Tuikov <luben.tuikov@....com>,
dri-devel@...ts.freedesktop.org,
Alex Deucher <alexander.deucher@....com>
Subject: Re: Radeon regression in 6.6 kernel
On Mon, Nov 27, 2023 at 6:24 PM Phillip Susi <phill@...susis.net> wrote:
>
> Alex Deucher <alexdeucher@...il.com> 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
Powered by blists - more mailing lists