From: Leo Li <sunpeng.li@amd.com>
To: August Wikerfors <git@augustwikerfors.se>,
Alex Deucher <alexdeucher@gmail.com>
Cc: regressions@lists.linux.dev,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
Thorsten Leemhuis <regressions@leemhuis.info>,
Alex Deucher <alexander.deucher@amd.com>,
Harry Wentland <harry.wentland@amd.com>
Subject: Re: [REGRESSION] Graphical issues on Lenovo Yoga 7 14ARB7 laptop since v6.0-rc1 (bisected)
Date: Fri, 23 Sep 2022 14:41:37 -0400 [thread overview]
Message-ID: <f4818fc3-7015-29ed-95c5-ab6a18da33d7@amd.com> (raw)
In-Reply-To: <33cf5071-3157-a3c2-3252-3a8ab926c60d@augustwikerfors.se>
Hi August,
Can you provide a dmesg log with drm.debug=0x16 enabled in kernel cmdline?
I wasn't aware that there are currently psr su edp panel + rembrandt apu
systems out in the wild. In any case, psrsu + rmb should be working, and
there might something specific to your configuration that's hitting a
corner case. The dmesg will shed some light.
Thanks
Leo
On 2022-09-22 14:13, August Wikerfors wrote:
> Hi Alex,
>
> On 2022-09-22 15:59, Alex Deucher wrote:
>> On Thu, Sep 22, 2022 at 8:54 AM Thorsten Leemhuis
>> <regressions@leemhuis.info> wrote:
>>>
>>> Hi, this is your Linux kernel regression tracker. Top-posting for once,
>>> to make this easily accessible to everyone.
>>>
>>> @amdgpu developers, what up here? August afaics didn't even get a single
>>> reply for his report that even identifies the change that's causing the
>>> problem. We're already late in the development cycle, so it would be
>>> good if someone could take a closer look into this before it's too late
>>> for 6.0.
>>
>> Been a busy week. Haven't had a chance to look into this yet. Does
>> the issue still happen with this patch:
>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git%2Fcommit%2F%3Fid%3D66f99628eb24409cb8feb5061f78283c8b65f820&data=05%7C01%7Csunpeng.li%40amd.com%7Cb3457b7e83df4b2c7d4308da9cc63280%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637994672320000021%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=a0EMjX6L13FaQU0mqxp5vO9vRe0BEDBDJ5emOdCj8gY%3D&reserved=0
> Yes, the issue still happens with that patch, and also with the current
> git master (dc164f4fb00a0abebdfff132f8bc7291a28f5401).
>
> Regards,
> August Wikerfors
next prev parent reply other threads:[~2022-09-23 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 16:57 [REGRESSION] Graphical issues on Lenovo Yoga 7 14ARB7 laptop since v6.0-rc1 (bisected) August Wikerfors
2022-09-22 11:26 ` Thorsten Leemhuis
2022-09-22 13:59 ` Alex Deucher
2022-09-22 18:13 ` August Wikerfors
2022-09-23 18:41 ` Leo Li [this message]
2022-09-23 20:26 ` August Wikerfors
2022-09-26 22:29 ` Leo Li
2022-09-27 14:22 ` August Wikerfors
2022-09-27 23:18 ` Leo Li
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=f4818fc3-7015-29ed-95c5-ab6a18da33d7@amd.com \
--to=sunpeng.li@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=git@augustwikerfors.se \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--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