From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Dave Airlie <airlied@gmail.com>,
Linux Regressions <regressions@lists.linux.dev>
Cc: "Phillip Susi" <phill@thesusis.net>,
"Luben Tuikov" <luben.tuikov@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Linux DRI Development" <dri-devel@lists.freedesktop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux AMDGPU" <amd-gfx@lists.freedesktop.org>
Subject: Re: Radeon regression in 6.6 kernel
Date: Sun, 19 Nov 2023 20:24:34 +0700 [thread overview]
Message-ID: <ZVoMklvIVClr_IIH@archie.me> (raw)
In-Reply-To: <CAPM=9tw-8pQWFso0zuLqpsqd5BSHWtc4As9ttdjY-DDr70EMqQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1770 bytes --]
On Sun, Nov 19, 2023 at 04:47:01PM +1000, Dave Airlie wrote:
> >
> > On 12.11.23 01:46, Phillip Susi wrote:
> > > I had been testing some things on a post 6.6-rc5 kernel for a week or
> > > two and then when I pulled to a post 6.6 release kernel, I found that
> > > system suspend was broken. It seems that the radeon driver failed to
> > > suspend, leaving the display dead, the wayland display server hung, and
> > > the system still running. I have been trying to bisect it for the last
> > > few days and have only been able to narrow it down to the following 3
> > > commits:
> > >
> > > There are only 'skip'ped commits left to test.
> > > The first bad commit could be any of:
> > > 56e449603f0ac580700621a356d35d5716a62ce5
> > > c07bf1636f0005f9eb7956404490672286ea59d3
> > > b70438004a14f4d0f9890b3297cd66248728546c
> > > We cannot bisect more!
> >
> > Hmm, not a single reply from the amdgpu folks. Wondering how we can
> > encourage them to look into this.
> >
> > Phillip, reporting issues by mail should still work, but you might have
> > more luck here, as that's where the amdgpu afaics prefer to track bugs:
> > https://gitlab.freedesktop.org/drm/amd/-/issues
> >
> > When you file an issue there, please mention it here.
> >
> > Furthermore it might help if you could verify if 6.7-rc1 (or rc2, which
> > comes out later today) or 6.6.2-rc1 improve things.
>
> It would also be good to test if reverting any of these is possible or not.
>
Hi Dave,
AFAIK commit c07bf1636f0005 ("MAINTAINERS: Update the GPU Scheduler email")
doesn't seem to do with this regression as it doesn't change any amdgpu code
that may introduce the regression.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-19 13:26 UTC|newest]
Thread overview: 39+ 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 11:12 ` Bagas Sanjaya
2023-11-12 18:42 ` Phillip Susi
2023-11-19 6:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 6:47 ` Dave Airlie
2023-11-19 13:24 ` Bagas Sanjaya [this message]
2023-11-19 13:48 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-19 13:53 ` Bagas Sanjaya
2023-11-20 15:57 ` Christian König
2023-11-20 16:08 ` Alex Deucher
2023-11-20 16:24 ` Christian König
2023-11-20 17:31 ` Alex Deucher
2023-11-20 22:40 ` Phillip Susi
2023-11-21 14:05 ` Alex Deucher
2023-11-21 22:05 ` Phillip Susi
2023-11-23 1:34 ` Luben Tuikov
2023-11-27 23:24 ` Phillip Susi
2023-11-28 22:13 ` Alex Deucher
2023-11-29 4:44 ` Luben Tuikov
2023-11-29 13:50 ` Alex Deucher
2023-11-29 15:22 ` Alex Deucher
2023-11-29 16:41 ` Luben Tuikov
2023-11-29 18:52 ` Alex Deucher
2023-11-29 20:10 ` Alex Deucher
2023-11-29 20:49 ` Alex Deucher
2023-11-30 3:36 ` Luben Tuikov
2023-11-30 3:47 ` Luben Tuikov
2023-11-30 23:28 ` Alex Deucher
2023-11-30 21:29 ` Alex Deucher
2023-12-01 16:55 ` Alex Deucher
2023-12-03 20:40 ` Phillip Susi
2023-12-04 14:14 ` Alex Deucher
2023-12-11 23:50 ` Phillip Susi
2023-12-12 0:28 ` Phillip Susi
2023-12-12 14:55 ` Alex Deucher
2023-11-29 16:20 ` Luben Tuikov
2023-11-29 18:45 ` Alex Deucher
2023-11-29 20:24 ` 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=ZVoMklvIVClr_IIH@archie.me \
--to=bagasdotme@gmail.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox