From: Thorsten Leemhuis <regressions@leemhuis.info> To: "regressions@lists.linux.dev" <regressions@lists.linux.dev> Subject: Re: [Bug Report] Desktop monitor sleep regression #forregzbot Date: Sat, 18 Dec 2021 08:02:31 +0100 [thread overview] Message-ID: <2f740617-29e4-2666-dc04-922357f96fda@leemhuis.info> (raw) In-Reply-To: <2f27c760-7679-c8d6-15f0-da1423ee9eb8@leemhuis.info> On 17.12.21 18:19, Thorsten Leemhuis wrote: > On 17.12.21 15:52, Imre Deak wrote: >> On Fri, Dec 17, 2021 at 03:46:21PM +0100, Thorsten Leemhuis wrote: >>> added some CCs Geert added in his reply >>> >>> On 07.12.21 08:20, Thorsten Leemhuis wrote: >>>> >>>> [TLDR: adding this regression to regzbot; most of this mail is compiled >>>> from a few templates paragraphs some of you might have seen already.] >>>> >>>> Hi, this is your Linux kernel regression tracker speaking. >>> >>> /me again >>> >>> What's up here? We are getting close to rc6, but there afaics wasn't any >>> reply of substance since the report ten days ago. Hence: >>> >>> Could anybody please comment on this? Imre Deak, the commit Brandon >>> found in the bisection contains a patch of yours, do you maybe have an >>> idea what's up here? >> >> Yes, >> https://bugzilla.kernel.org/show_bug.cgi?id=215203 >> >> based on which the problem is somehere in the AMD driver. > > Ha, sorry for the noise then, I really feel stupid: I have no idea why I > didn't check the bug report for an update, as I do normally do. Much > have slipped through. Ohh well, hopefully we one day have have a central > place to handle these things. For the record without anyone else in CC: Ha, now I know why I missed that, I forgot to tell regzbot about the bugzilla tickets. To fix this: #regzbot link: https://bugzilla.redhat.com/show_bug.cgi?id=2028613 #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215203 Ciao, Thorsten (wearing his 'Linux kernel regression tracker' hat). TWIMC: this mail is primarily send for documentation purposes and for regzbot, my Linux kernel regression tracking bot. These mails usually contain '#forregzbot' in the subject, to make them easy to spot and filter. >>> Ciao, Thorsten >>> >>> #regzbot poke >>> >>>> Adding the regression mailing list to the list of recipients, as it >>>> should be in the loop for all regressions, as explained here: >>>> https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html >>>> >>>> Also adding the authors and reviewers of the culprit and two appropriate >>>> mailing lists. >>>> >>>> On 07.12.21 01:21, Brandon Nielsen wrote: >>>>> Monitors no longer sleep properly on my system (dual monitor connected >>>>> via DP->DVI, amdgpu, x86_64). The monitors slept properly on 5.14, but >>>>> stopped during the 5.15 series. I have also filed this bug on the kernel >>>>> bugzilla[0] and downstream[1]. >>>>> >>>>> I have performed a bisect, first "bad" commit to master is >>>>> 55285e21f04517939480966164a33898c34b2af2[1], the same change made it >>>>> into the 5.15 branch as e3b39825ed0813f787cb3ebdc5ecaa5131623647. >>>> >>>> TWIMC: That was for 5.15.3 >>>> >>>>> I have >>>>> verified the issue exists in latest master >>>>> (a51e3ac43ddbad891c2b1a4f3aa52371d6939570). >>>>> >>>>> Steps to reproduce: >>>>> >>>>> 1. Boot system (Fedora Workstation 35 in this case) >>>>> 2. Log in >>>>> 3. Lock screen (after a few seconds, monitors will enter power save >>>>> "sleep" state with backlight off) >>>>> 4. Wait (usually no more than 30 seconds, sometimes up to a few minutes) >>>>> 5. Observe monitor leaving "sleep" state (backlight comes back on), >>>>> but nothing is displayed >>>>> >>>>> [0] - https://bugzilla.kernel.org/show_bug.cgi?id=215203 >>>>> [1] - https://bugzilla.redhat.com/show_bug.cgi?id=2028613 >>>> >>>> To be sure this issue doesn't fall through the cracks unnoticed, I'm >>>> adding it to regzbot, my Linux kernel regression tracking bot: >>>> >>>> #regzbot ^introduced 55285e21f04517939480966164a33898c34b2af2 >>>> #regzbot title fbdev/efifb: Monitors no longer sleep (amdgpu dual >>>> monitor setup) >>>> #regzbot ignore-activity >>>> >>>> Reminder: when fixing the issue, please add a 'Link:' tag with the URL >>>> to the report (the parent of this mail), then regzbot will automatically >>>> mark the regression as resolved once the fix lands in the appropriate >>>> tree. For more details about regzbot see footer. >>>> >>>> Sending this to everyone that got the initial report, to make all aware >>>> of the tracking. I also hope that messages like this motivate people to >>>> directly get at least the regression mailing list and ideally even >>>> regzbot involved when dealing with regressions, as messages like this >>>> wouldn't be needed then. >>>> >>>> Don't worry, I'll send further messages wrt to this regression just to >>>> the lists (with a tag in the subject so people can filter them away), as >>>> long as they are intended just for regzbot. With a bit of luck no such >>>> messages will be needed anyway. >>>> >>>> Ciao, Thorsten, your Linux kernel regression tracker. >>>> >>>> P.S.: As a Linux kernel regression tracker I'm getting a lot of reports >>>> on my table. I can only look briefly into most of them. Unfortunately >>>> therefore I sometimes will get things wrong or miss something important. >>>> I hope that's not the case here; if you think it is, don't hesitate to >>>> tell me about it in a public reply. That's in everyone's interest, as >>>> what I wrote above might be misleading to everyone reading this; any >>>> suggestion I gave they thus might sent someone reading this down the >>>> wrong rabbit hole, which none of us wants. >>>> >>>> BTW, I have no personal interest in this issue, which is tracked using >>>> regzbot, my Linux kernel regression tracking bot >>>> (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting >>>> this mail to get things rolling again and hence don't need to be CC on >>>> all further activities wrt to this regression. >>>> >>
next prev parent reply other threads:[~2021-12-18 7:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <8a27c986-4767-bd29-2073-6c4ffed49bba@jetfuse.net> 2021-12-07 7:20 ` [Bug Report] Desktop monitor sleep regression Thorsten Leemhuis 2021-12-17 14:46 ` Thorsten Leemhuis 2021-12-17 14:52 ` Imre Deak 2021-12-17 17:19 ` Thorsten Leemhuis 2021-12-18 7:02 ` Thorsten Leemhuis [this message] 2022-01-08 11:44 ` [Bug Report] Desktop monitor sleep regression #forregzbot Thorsten Leemhuis
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=2f740617-29e4-2666-dc04-922357f96fda@leemhuis.info \ --to=regressions@leemhuis.info \ --cc=regressions@lists.linux.dev \ --subject='Re: [Bug Report] Desktop monitor sleep regression #forregzbot' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).