From: Dirk Gouders <dirk@gouders.net>
To: Lyude Paul <lyude@redhat.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
"Wayne Lin" <Wayne.Lin@amd.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Fangzhi Zuo" <Jerry.Zuo@amd.com>,
"Jani Nikula" <jani.nikula@intel.com>,
"Imre Deak" <imre.deak@intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Sean Paul" <sean@poorly.run>
Subject: Re: Regression bisected: drm/display/dp_mst: Move all payload info into the atomic state
Date: Fri, 11 Nov 2022 23:00:34 +0100 [thread overview]
Message-ID: <gh5yflw3r1.fsf@gouders.net> (raw)
In-Reply-To: <006064db584562c38ba75bff30d1b33f8995df62.camel@redhat.com> (Lyude Paul's message of "Fri, 11 Nov 2022 15:50:02 -0500")
Thank you for the pointer. I will see if I can produce some of the
wanted logs but at the earliest tomorrow, it's almost sleeping time,
here.
Dirk
Lyude Paul <lyude@redhat.com> writes:
> Thank for letting us know! Luckily I only have good news, as we've actually
> been looking into this issue for a bit now and have made a pretty good amount
> of progress. There's pretty much only one issue left for us to fix I'm fairly
> sure:
>
> https://gitlab.freedesktop.org/drm/amd/-/issues/2171
>
> If you'd like to help, there's some logs I could use someone getting to help
> me figure out the last remaining issue here.
>
> On Thu, 2022-11-10 at 23:32 +0100, Dirk Gouders wrote:
>> Hello,
>>
>> I noticed a regression with Linus' current tree and bisected it to
>> 4d07b0bc403403 (drm/display/dp_mst: Move all payload info into the atomic state):
>>
>> I have two monitors connected to my laptop's USB-C port and since this
>> patch, one of the monitors remains dark.
>>
>> Please let me know if I can provide additional information that could help
>> to investigate this problem.
>>
>> Dirk
>>
next prev parent reply other threads:[~2022-11-11 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 22:32 Regression bisected: drm/display/dp_mst: Move all payload info into the atomic state Dirk Gouders
2022-11-11 20:50 ` Lyude Paul
2022-11-11 22:00 ` Dirk Gouders [this message]
2022-11-13 9:28 ` Regression bisected: drm/display/dp_mst: Move all payload info into the atomic state #forregzbot Thorsten Leemhuis
2022-11-20 17:29 ` Thorsten Leemhuis
2022-11-23 15:43 ` Thorsten Leemhuis
2023-01-13 20:38 ` Salvatore Bonaccorso
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=gh5yflw3r1.fsf@gouders.net \
--to=dirk@gouders.net \
--cc=Jerry.Zuo@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=imre.deak@intel.com \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=sean@poorly.run \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox