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: <ea1f1d81-650b-768a-30ab-c9d7d9f9fa54@augustwikerfors.se>
Date:   Fri, 23 Sep 2022 22:26:35 +0200
MIME-version: 1.0
Subject: Re: [REGRESSION] Graphical issues on Lenovo Yoga 7 14ARB7 laptop since
 v6.0-rc1 (bisected)
Content-language: en-US
To:     Leo Li <sunpeng.li@amd.com>, Alex Deucher <alexdeucher@gmail.com>
Cc:     Thorsten Leemhuis <regressions@leemhuis.info>,
        Harry Wentland <harry.wentland@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>
 <33cf5071-3157-a3c2-3252-3a8ab926c60d@augustwikerfors.se>
 <f4818fc3-7015-29ed-95c5-ab6a18da33d7@amd.com>
From:   August Wikerfors <git@augustwikerfors.se>
In-reply-to: <f4818fc3-7015-29ed-95c5-ab6a18da33d7@amd.com>
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7bit
Reporting-Meta: AAEOL0javX7vJbTonMYC2eM4teWqEd60MX20U+3Im6izcE4iNa76d+RAkf65cWfX
 p514OTw7+zyMCBtIa6gcDTMiMR2v31KQAxK/xb203M4Vchq2Ym9DQL7zpleO+AGQ
 N3VGgds0agRl1XLhNoOsIFSgmp7P5JcoxlpuAQZtTYJgKon6aI3tww2L+Un8txzj
 h4eH1PwKLHLaiTzF2n+XWmdhywVrbZWsmlxla1L3zOWf8XWHbjrMlZt5KJdrLbwV
 E5QlRIljznw0VoRCjP2zlKQkYGQbvqeB4a5H/6tGCClP/IUvmnEIgwKkZ2qBQpWO
 up0NcE45yv6v7kKIK2zH1s3lIvpnn8JZuGNO/NvRxoyUi8usTMhRu0B0BaqcmIOH
 pnuL01jcFkSFirvCf7+BdInv2qtO1LgNUII8SwkLWQG6KKzf8Am0rrpKpQR86Zk2 1nl8uPEY
Precedence: bulk

Hi Leo,

On 2022-09-23 20:41, Leo Li wrote:
> Hi August,
> 
> Can you provide a dmesg log with drm.debug=0x16 enabled in kernel cmdline?
Log is available here: https://files.augustwikerfors.se/dmesg.2022-09-23.txt

This is what I did during that log:
1. Boot the system
2. Type into the password field in SDDM (this is when the problem occurs)
3. Switch to a TTY to save the log (the problem doesn't happen there)

Regards,
August Wikerfors