dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216359] New: [amdgpu] ring gfx timeout after waking from suspend and exiting X
Date: Sun, 14 Aug 2022 05:55:52 +0000	[thread overview]
Message-ID: <bug-216359-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216359

            Bug ID: 216359
           Summary: [amdgpu] ring gfx timeout after waking from suspend
                    and exiting X
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.18.13, 5.19.1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: shlomo@fastmail.com
                CC: alexdeucher@gmail.com
        Regression: Yes

After waking up from suspend and exiting X (and trying to switch to a different
tty, but I think the bug happens before that), I get:

Aug 14 08:27:21 up kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, but soft recovered
Aug 14 08:27:31 up kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, but soft recovered
Aug 14 08:27:42 up kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, but soft recovered

The screen freezes, and I have to reboot to get a stable system.

Arch Linux 5.18.12.arch1-1 is good.
Arch Linux 5.18.14.arch1-1 is bad.
Arch Linux 5.18.15.arch1-1 is bad.
Arch Linux 5.18.16.arch1-1 is bad.
Arch Linux 5.19.1.arch2-1 is bad.

4ffcacab7145080187330accafae69e87a481eec is the first bad commit
commit 4ffcacab7145080187330accafae69e87a481eec
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Tue Jun 21 10:10:37 2022 -0400

    drm/amdgpu/display: disable prefer_shadow for generic fb helpers

    [ Upstream commit 3a4b1cc28fbdc2325b3e3ed7d8024995a75f9216 ]

    Seems to break hibernation.  Disable for now until we can root
    cause it.

    Fixes: 087451f372bf ("drm/amdgpu: use generic fb helpers instead of setting
up AMD own's.")
    Bug: https://bugzilla.kernel.org/show_bug.cgi?id=216119
    Acked-by: Evan Quan <evan.quan@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

 drivers/gpu/drm/amd/amdgpu/amdgpu_vkms.c          | 3 ++-
 drivers/gpu/drm/amd/amdgpu/dce_v10_0.c            | 3 ++-
 drivers/gpu/drm/amd/amdgpu/dce_v11_0.c            | 3 ++-
 drivers/gpu/drm/amd/amdgpu/dce_v6_0.c             | 3 ++-
 drivers/gpu/drm/amd/amdgpu/dce_v8_0.c             | 3 ++-
 drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 3 ++-
 6 files changed, 12 insertions(+), 6 deletions(-)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-08-14  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14  5:55 bugzilla-daemon [this message]
2022-08-16  5:45 ` [Bug 216359] [amdgpu] ring gfx timeout after waking from suspend and exiting X bugzilla-daemon
2022-08-16 16:55 ` bugzilla-daemon

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=bug-216359-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=dri-devel@lists.freedesktop.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