[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADnq5_Nh4wCFY10Ha9dTGWvehPCdY2zxfERtFuoeF5_xA+P=QA@mail.gmail.com>
Date: Tue, 21 Nov 2023 09:05:39 -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 20, 2023 at 5:40 PM Phillip Susi <phill@...susis.net> wrote:
>
> Alex Deucher <alexdeucher@...il.com> 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
Powered by blists - more mailing lists