From: Alex Deucher <alexdeucher@gmail.com>
To: Phillip Susi <phill@thesusis.net>
Cc: "Christian König" <christian.koenig@amd.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Dave Airlie" <airlied@gmail.com>,
"Linux regressions mailing list" <regressions@lists.linux.dev>,
linux-kernel@vger.kernel.org,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Luben Tuikov" <luben.tuikov@amd.com>,
dri-devel@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>
Subject: Re: Radeon regression in 6.6 kernel
Date: Tue, 21 Nov 2023 09:05:39 -0500 [thread overview]
Message-ID: <CADnq5_Nh4wCFY10Ha9dTGWvehPCdY2zxfERtFuoeF5_xA+P=QA@mail.gmail.com> (raw)
In-Reply-To: <87bkbodp51.fsf@vps.thesusis.net>
On Mon, Nov 20, 2023 at 5:40 PM Phillip Susi <phill@thesusis.net> wrote:
>
> Alex Deucher <alexdeucher@gmail.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
WARNING: multiple messages have this Message-ID (diff)
From: Alex Deucher <alexdeucher@gmail.com>
To: Phillip Susi <phill@thesusis.net>
Cc: "Linux regressions mailing list" <regressions@lists.linux.dev>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
linux-kernel@vger.kernel.org,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Luben Tuikov" <luben.tuikov@amd.com>,
dri-devel@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: Radeon regression in 6.6 kernel
Date: Tue, 21 Nov 2023 09:05:39 -0500 [thread overview]
Message-ID: <CADnq5_Nh4wCFY10Ha9dTGWvehPCdY2zxfERtFuoeF5_xA+P=QA@mail.gmail.com> (raw)
In-Reply-To: <87bkbodp51.fsf@vps.thesusis.net>
On Mon, Nov 20, 2023 at 5:40 PM Phillip Susi <phill@thesusis.net> wrote:
>
> Alex Deucher <alexdeucher@gmail.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
WARNING: multiple messages have this Message-ID (diff)
From: Alex Deucher <alexdeucher@gmail.com>
To: Phillip Susi <phill@thesusis.net>
Cc: "Linux regressions mailing list" <regressions@lists.linux.dev>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
linux-kernel@vger.kernel.org,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Luben Tuikov" <luben.tuikov@amd.com>,
dri-devel@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Dave Airlie" <airlied@gmail.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: Radeon regression in 6.6 kernel
Date: Tue, 21 Nov 2023 09:05:39 -0500 [thread overview]
Message-ID: <CADnq5_Nh4wCFY10Ha9dTGWvehPCdY2zxfERtFuoeF5_xA+P=QA@mail.gmail.com> (raw)
In-Reply-To: <87bkbodp51.fsf@vps.thesusis.net>
On Mon, Nov 20, 2023 at 5:40 PM Phillip Susi <phill@thesusis.net> wrote:
>
> Alex Deucher <alexdeucher@gmail.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
next prev parent reply other threads:[~2023-11-21 14:05 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 0:46 Radeon regression in 6.6 kernel Phillip Susi
2023-11-12 0:46 ` Phillip Susi
2023-11-12 11:12 ` Bagas Sanjaya
2023-11-12 11:12 ` Bagas Sanjaya
2023-11-12 18:42 ` Phillip Susi
2023-11-12 18:42 ` Phillip Susi
2023-11-19 6:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 6:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 6:47 ` Dave Airlie
2023-11-19 6:47 ` Dave Airlie
2023-11-19 13:24 ` Bagas Sanjaya
2023-11-19 13:24 ` Bagas Sanjaya
2023-11-19 13:48 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 13:48 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 13:53 ` Bagas Sanjaya
2023-11-19 13:53 ` Bagas Sanjaya
2023-11-20 15:57 ` Christian König
2023-11-20 15:57 ` Christian König
2023-11-20 16:08 ` Alex Deucher
2023-11-20 16:08 ` Alex Deucher
2023-11-20 16:08 ` Alex Deucher
2023-11-20 16:24 ` Christian König
2023-11-20 16:24 ` Christian König
2023-11-20 16:24 ` Christian König
2023-11-20 17:31 ` Alex Deucher
2023-11-20 17:31 ` Alex Deucher
2023-11-20 17:31 ` Alex Deucher
2023-11-20 22:40 ` Phillip Susi
2023-11-20 22:40 ` Phillip Susi
2023-11-20 22:40 ` Phillip Susi
2023-11-21 14:05 ` Alex Deucher [this message]
2023-11-21 14:05 ` Alex Deucher
2023-11-21 14:05 ` Alex Deucher
2023-11-21 22:05 ` Phillip Susi
2023-11-21 22:05 ` Phillip Susi
2023-11-21 22:05 ` Phillip Susi
2023-11-23 1:34 ` Luben Tuikov
2023-11-23 1:34 ` Luben Tuikov
2023-11-27 23:24 ` Phillip Susi
2023-11-27 23:24 ` Phillip Susi
2023-11-27 23:24 ` Phillip Susi
2023-11-28 22:13 ` Alex Deucher
2023-11-28 22:13 ` Alex Deucher
2023-11-28 22:13 ` Alex Deucher
2023-11-29 4:44 ` Luben Tuikov
2023-11-29 4:44 ` Luben Tuikov
2023-11-29 13:50 ` Alex Deucher
2023-11-29 13:50 ` Alex Deucher
2023-11-29 15:22 ` Alex Deucher
2023-11-29 15:22 ` Alex Deucher
2023-11-29 16:41 ` Luben Tuikov
2023-11-29 16:41 ` Luben Tuikov
2023-11-29 18:52 ` Alex Deucher
2023-11-29 18:52 ` Alex Deucher
2023-11-29 20:10 ` Alex Deucher
2023-11-29 20:10 ` Alex Deucher
2023-11-29 20:49 ` Alex Deucher
2023-11-29 20:49 ` Alex Deucher
2023-11-30 3:36 ` Luben Tuikov
2023-11-30 3:36 ` Luben Tuikov
2023-11-30 3:47 ` Luben Tuikov
2023-11-30 3:47 ` Luben Tuikov
2023-11-30 23:28 ` Alex Deucher
2023-11-30 23:28 ` Alex Deucher
2023-11-30 21:29 ` Alex Deucher
2023-11-30 21:29 ` Alex Deucher
2023-12-01 16:55 ` Alex Deucher
2023-12-01 16:55 ` Alex Deucher
2023-12-03 20:40 ` Phillip Susi
2023-12-03 20:40 ` Phillip Susi
2023-12-04 14:14 ` Alex Deucher
2023-12-04 14:14 ` Alex Deucher
2023-12-11 23:50 ` Phillip Susi
2023-12-11 23:50 ` Phillip Susi
2023-12-12 0:28 ` Phillip Susi
2023-12-12 0:28 ` Phillip Susi
2023-12-12 14:55 ` Alex Deucher
2023-12-12 14:55 ` Alex Deucher
2023-11-29 16:20 ` Luben Tuikov
2023-11-29 16:20 ` Luben Tuikov
2023-11-29 18:45 ` Alex Deucher
2023-11-29 18:45 ` Alex Deucher
2023-11-29 20:24 ` Phillip Susi
2023-11-29 20:24 ` Phillip Susi
2023-11-20 22:08 ` Phillip Susi
2023-11-20 22:08 ` Phillip Susi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADnq5_Nh4wCFY10Ha9dTGWvehPCdY2zxfERtFuoeF5_xA+P=QA@mail.gmail.com' \
--to=alexdeucher@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=phill@thesusis.net \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.