regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3) #forregzbot
Date: Fri, 27 May 2022 11:51:05 +0200	[thread overview]
Message-ID: <26e75811-0663-bea4-b637-985091c70587@leemhuis.info> (raw)
In-Reply-To: <eed25dd6-36ba-cd1c-1828-08a1535ce6c6@leemhuis.info>

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.

On 14.05.22 17:12, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker. Thanks for the report.
> 
> On 14.05.22 16:41, Christian Casteyde wrote:
>> #regzbot introduced v5.17.3..v5.17.4
>> #regzbot introduced: 001828fb3084379f3c3e228b905223c50bc237f9
> 
> FWIW, that's commit 887f75cfd0da ("drm/amdgpu: Ensure HDA function is
> suspended before ASIC reset") upstream.

#regzbot invalid: tricky situation with other problems; the issue thus
not really qualifies as regression

For details see:
https://lore.kernel.org/stable/MN0PR12MB61011E787AAAA98597A3A9DDE2D49@MN0PR12MB6101.namprd12.prod.outlook.com/
https://lore.kernel.org/stable/2175827.vFx2qVVIhK@geek500.localdomain/

      parent reply	other threads:[~2022-05-27  9:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 14:41 [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3) Christian Casteyde
2022-05-14 15:12 ` Thorsten Leemhuis
2022-05-14 17:34   ` Christian Casteyde
2022-05-16  2:47     ` Kai-Heng Feng
2022-05-16  3:06       ` Mario Limonciello
2022-05-16 17:23       ` Christian Casteyde
2022-05-17  2:03         ` Kai-Heng Feng
2022-05-17  6:36           ` Christian Casteyde
2022-05-17  6:58             ` Kai-Heng Feng
2022-05-17 17:37               ` casteyde.christian
2022-05-18  5:52                 ` Thorsten Leemhuis
2022-05-18  5:54                   ` Kai-Heng Feng
2022-05-18  6:37                     ` Thorsten Leemhuis
2022-05-18 20:15                       ` Limonciello, Mario
2022-05-23 13:02                       ` Christian Casteyde
2022-05-23 14:00                         ` Limonciello, Mario
2022-05-23 17:03                         ` Christian Casteyde
2022-05-23 22:01                           ` Limonciello, Mario
2022-05-24 20:54                           ` Christian Casteyde
2022-05-25  7:29                             ` Thorsten Leemhuis
2022-05-17 17:38               ` casteyde.christian
2022-05-17 18:13                 ` Limonciello, Mario
2022-05-18 11:02                   ` casteyde.christian
2022-05-19 17:31                     ` Limonciello, Mario
2022-05-19 18:07                       ` Limonciello, Mario
2022-05-18  2:08                 ` Kai-Heng Feng
2022-05-18  2:19                   ` Mario Limonciello
2022-05-18  7:15                   ` Christian Casteyde
2022-05-18 10:53                     ` casteyde.christian
2022-05-27  9:51   ` Thorsten Leemhuis [this message]

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=26e75811-0663-bea4-b637-985091c70587@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).