Messages in this thread | | | Date | Sun, 13 Nov 2022 10:28:13 +0100 | Subject | Re: Regression bisected: drm/display/dp_mst: Move all payload info into the atomic state #forregzbot | From | Thorsten Leemhuis <> |
| |
[Note: this mail is primarily send for documentation purposes and/or for regzbot, my Linux kernel regression tracking bot. That's why I removed most or all folks from the list of recipients, but left any that looked like a mailing lists. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter out.]
[TLDR: I'm adding this regression report to the list of tracked regressions; all text from me you find below is based on a few templates paragraphs you might have encountered already already in similar form.]
Hi, this is your Linux kernel regression tracker.
On 10.11.22 23:32, Dirk Gouders wrote: > > 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.
Thanks for the report. To be sure below issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking bot:
#regzbot introduced 4d07b0bc403403 ^ https://gitlab.freedesktop.org/drm/amd/-/issues/2171 #regzbot title drm: amdgpu: No payload for [MST PORT:0000000006da5d29] found in mst state 00000000b0e556d6" on system resume with TBT dock connected. #regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight.
| |