Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-id: <33cf5071-3157-a3c2-3252-3a8ab926c60d@augustwikerfors.se>
Date:   Thu, 22 Sep 2022 20:13:39 +0200
MIME-version: 1.0
From:   August Wikerfors <git@augustwikerfors.se>
Subject: Re: [REGRESSION] Graphical issues on Lenovo Yoga 7 14ARB7 laptop since
 v6.0-rc1 (bisected)
To:     Alex Deucher <alexdeucher@gmail.com>
Cc:     Thorsten Leemhuis <regressions@leemhuis.info>,
        Harry Wentland <harry.wentland@amd.com>,
        Leo Li <sunpeng.li@amd.com>,
        Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
        Alex Deucher <alexander.deucher@amd.com>,
        linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
        regressions@lists.linux.dev
References: <c1f8886a-5624-8f49-31b1-e42b6d20dcf5@augustwikerfors.se>
 <eee82fb8-0fc5-98cb-e630-f86891574f21@leemhuis.info>
 <CADnq5_PRP3ekHPLhdXALxt9GL3aHHZQUw5TNAwm4t+ggimUq7g@mail.gmail.com>
Content-language: en-US
In-reply-to: <CADnq5_PRP3ekHPLhdXALxt9GL3aHHZQUw5TNAwm4t+ggimUq7g@mail.gmail.com>
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7bit
Reporting-Meta: AAHbDiOyw7PQ+YvQ6Tk2wL3boCy4Gse2rKd/OctvMwiREQdSmCjJhUzxDqPn50D4
 b2YL7+qFbADcEhF5v3aqKRWdW4C9GDLg1v0zCEesheVk5teTuP6L8+iQb/0tJ+8U
 hSKxQbyGrmunmbaqIpqk888yeTIIG1XuqLgGOgo1hLQ4JKpxXdv648D8QhO6JrXj
 qGi3zL33B0po4WwwwET92YCnHHv7IY9sg9LhVsKWXOrv5JabLgvcwABGXkiHmn0D
 qY51KM40XdVwdpCLYQ34SNxVaY3AqDVbW/4Cb4dd9NX7qyzSXjV7/fZ7whyGdCJ6
 YS6K7g/7sSeguYNl5E5Vs0cMDDPigKSnzscBzb/bDyfhFnmGl0oskLJCVmZ9uPym
 JMjHTpp99aEWw5fIT2v4E56iaQu/WEsxY68RPfyGoCdWM6vHTbbhrfpVdfckjwaN ERYMvB4=
Precedence: bulk

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://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=66f99628eb24409cb8feb5061f78283c8b65f820
Yes, the issue still happens with that patch, and also with the current 
git master (dc164f4fb00a0abebdfff132f8bc7291a28f5401).

Regards,
August Wikerfors