From: Mark Boddington <lkml@badpenguin.co.uk>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: kernel 5.15.1: AMD RX 6700 XT - Fails to resume after screen blank
Date: Fri, 12 Nov 2021 17:24:58 +0000 [thread overview]
Message-ID: <ab370b30-3d01-6f7e-4e56-dd7b61251e25@badpenguin.co.uk> (raw)
In-Reply-To: <e0f6f173-95a6-3868-5cc1-44092acd9267@leemhuis.info>
Hi,
On 12/11/2021 16:04, Thorsten Leemhuis wrote:
> Hi Mark. Replying inline
> (https://en.wikipedia.org/wiki/Posting_style#Interleaved_style ), as
> that's the norm and kinda expected on Linux kernel mailing lists:
>
> On 11.11.21 00:11, Mark Boddington wrote:
>> And also
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c?h=linux-5.15.y&id=f02abeb0779700c308e661a412451b38962b8a0b
>>
>> Maybe if the function is called during resume() without being called
>> during init(), bad things happen???
> Have you tried to revert any of the patches you suspect to cause this
> and see if things improve? And BTW: did 5.15 (aka 5.15.0) work? Or was
> some process to resolve this made already somewhere else and I just
> missed it?
>
> Ciao, Thorsten (with his Linux kernel regression tracker hat on)
>
> #regzbot poke
I tried reverting both, but they didn't improve the situation.
I also had the deadlock happen on 5.15 yesterday, so the last stable
kernel I have used is 5.14.15. I can try the latest 5.14.x if that will
help?
Cheers,
Mark
next prev parent reply other threads:[~2021-11-12 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 16:27 kernel 5.15.1: AMD RX 6700 XT - Fails to resume after screen blank Mark Boddington
2021-11-10 17:38 ` Greg KH
2021-11-10 18:53 ` Mark Boddington
2021-11-10 23:02 ` Mark Boddington
2021-11-10 23:11 ` Mark Boddington
2021-11-12 16:04 ` Thorsten Leemhuis
2021-11-12 17:24 ` Mark Boddington [this message]
2021-11-13 8:15 ` Thorsten Leemhuis
2021-11-11 6:09 ` Thorsten Leemhuis
2021-11-25 11:11 ` Thorsten Leemhuis
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=ab370b30-3d01-6f7e-4e56-dd7b61251e25@badpenguin.co.uk \
--to=lkml@badpenguin.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).