From: August Wikerfors <git@augustwikerfors.se>
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
Subject: Re: [REGRESSION] Graphical issues on Lenovo Yoga 7 14ARB7 laptop since v6.0-rc1 (bisected)
Date: Fri, 23 Sep 2022 22:26:35 +0200 [thread overview]
Message-ID: <ea1f1d81-650b-768a-30ab-c9d7d9f9fa54@augustwikerfors.se> (raw)
In-Reply-To: <f4818fc3-7015-29ed-95c5-ab6a18da33d7@amd.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: August Wikerfors <git@augustwikerfors.se>
To: Leo Li <sunpeng.li@amd.com>, 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 22:26:35 +0200 [thread overview]
Message-ID: <ea1f1d81-650b-768a-30ab-c9d7d9f9fa54@augustwikerfors.se> (raw)
In-Reply-To: <f4818fc3-7015-29ed-95c5-ab6a18da33d7@amd.com>
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
next prev parent reply other threads:[~2022-09-23 20:31 UTC|newest]
Thread overview: 18+ 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-17 16:57 ` August Wikerfors
2022-09-22 11:26 ` Thorsten Leemhuis
2022-09-22 11:26 ` Thorsten Leemhuis
2022-09-22 13:59 ` Alex Deucher
2022-09-22 13:59 ` Alex Deucher
2022-09-22 18:13 ` August Wikerfors
2022-09-22 18:13 ` August Wikerfors
2022-09-23 18:41 ` Leo Li
2022-09-23 18:41 ` Leo Li
2022-09-23 20:26 ` August Wikerfors [this message]
2022-09-23 20:26 ` August Wikerfors
2022-09-26 22:29 ` Leo Li
2022-09-26 22:29 ` Leo Li
2022-09-27 14:22 ` August Wikerfors
2022-09-27 14:22 ` August Wikerfors
2022-09-27 23:18 ` Leo Li
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=ea1f1d81-650b-768a-30ab-c9d7d9f9fa54@augustwikerfors.se \
--to=git@augustwikerfors.se \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sunpeng.li@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.