[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 11 Nov 2022 23:00:34 +0100
From: Dirk Gouders <dirk@...ders.net>
To: Lyude Paul <lyude@...hat.com>
Cc: Linux Kernel <linux-kernel@...r.kernel.org>,
Wayne Lin <Wayne.Lin@....com>,
Ville Syrjälä <ville.syrjala@...ux.intel.com>,
Fangzhi Zuo <Jerry.Zuo@....com>,
Jani Nikula <jani.nikula@...el.com>,
Imre Deak <imre.deak@...el.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Sean Paul <sean@...rly.run>
Subject: Re: Regression bisected: drm/display/dp_mst: Move all payload info
into the atomic state
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@...hat.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
>>
Powered by blists - more mailing lists