stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Christian Casteyde <casteyde.christian@free.fr>, stable@vger.kernel.org
Cc: regressions@lists.linux.dev, kai.heng.feng@canonical.com,
	alexander.deucher@amd.com, gregkh@linuxfoundation.org
Subject: Re: [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3)
Date: Sat, 14 May 2022 17:12:33 +0200	[thread overview]
Message-ID: <eed25dd6-36ba-cd1c-1828-08a1535ce6c6@leemhuis.info> (raw)
In-Reply-To: <2584945.lGaqSPkdTl@geek500.localdomain>

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.

Recently a regression was reported where 887f75cfd0da was suspected as
the culprit:
https://gitlab.freedesktop.org/drm/amd/-/issues/2008

And a one related to it:
https://gitlab.freedesktop.org/drm/amd/-/issues/1982

You might want to take a look if what was discussed there might be
related to your problem (I'm not directly involved in any of this, I
don't know the details, it's just that 887f75cfd0da looked familiar to
me). If it is, a fix for these two bugs was committed to master earlier
this week:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a56f445f807b0276

It will likely be backported to 5.17.y, maybe already in the over-next
release. HTH.

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.

> Hello
> Since 5.17.4 my laptop doesn't resume from suspend anymore. At resume, 
> symptoms are variable:
> - either the laptop freezes;
> - either the screen keeps blank;
> - either the screen is OK but mouse is frozen;
> - either display lags with several logs in dmesg:
> [  228.275492] [drm] Fence fallback timer expired on ring gfx
> [  228.395466] [drm:amdgpu_dm_atomic_commit_tail] *ERROR* Waiting for fences 
> timed out!
> [  228.779490] [drm] Fence fallback timer expired on ring gfx
> [  229.283484] [drm] Fence fallback timer expired on ring sdma0
> [  229.283485] [drm] Fence fallback timer expired on ring gfx
> [  229.787487] [drm] Fence fallback timer expired on ring gfx
> ...
> 
> I've bisected the problem.
> 
> Please note this laptop has a strange behaviour on suspend:
> The first suspend request always fails (this point has never been fixed and 
> plagues us when trying to diagnose another regression on touchpad not resuming 
> in the past). The screen goes blank and I can get it OK when pressing the 
> power button, this seems to reset it. After that all suspend/resume works OK.
> 
> Since 5.17.4, it is not possible anymore to get the laptop working again after 
> the first suspend failure.
> 
> HW : HP Pavilion / Ryzen 4600H with AMD graphics integrated + NVidia 1650Ti 
> (turned off with ACPI call in order to get more battery, I'm not using NVidia 
> driver).
> 
> 
> 
> 
> 

  reply	other threads:[~2022-05-14 15:12 UTC|newest]

Thread overview: 29+ 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 [this message]
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

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=eed25dd6-36ba-cd1c-1828-08a1535ce6c6@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=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 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).