All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: casteyde.christian@free.fr, Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
	alexander deucher <alexander.deucher@amd.com>,
	gregkh@linuxfoundation.org,
	Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3)
Date: Wed, 18 May 2022 07:52:36 +0200	[thread overview]
Message-ID: <4c8afdd6-3573-619d-d46c-e13a4fdd9ac7@leemhuis.info> (raw)
In-Reply-To: <941867856.547807110.1652809066335.JavaMail.root@zimbra40-e7.priv.proxad.net>

On 17.05.22 19:37, casteyde.christian@free.fr wrote:

> I've tryied to revert the offending commit on 5.18-rc7 (887f75cfd0da
> ("drm/amdgpu: Ensure HDA function is suspended before ASIC reset"), and
> the problem disappears so it's really this commit that breaks.

In that case I'll update the regzbot status to make sure it's visible as
regression introduced in the 5.18 cycle:

#regzbot introduced: 887f75cfd0da

BTW: obviously would be nice to get this fixed before 5.18 is released
(which might already happen on Sunday), especially as the culprit
apparently was already backported to stable, but I guess that won't be
easy...

Which made me wondering: is reverting the culprit temporarily in
mainline (and reapplying it later with a fix) a option here?

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.

  reply	other threads:[~2022-05-18  5:52 UTC|newest]

Thread overview: 32+ 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: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 [this message]
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  7:15                     ` Christian Casteyde
2022-05-18 10:53                     ` casteyde.christian
2022-05-27  9:51   ` [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3) #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=4c8afdd6-3573-619d-d46c-e13a4fdd9ac7@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=alexander.deucher@amd.com \
    --cc=casteyde.christian@free.fr \
    --cc=gregkh@linuxfoundation.org \
    --cc=kai.heng.feng@canonical.com \
    --cc=mario.limonciello@amd.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.