All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Wollrath <jwollrath@web.de>
To: dri-devel@lists.freedesktop.org
Cc: alexander.deucher@amd.com, tim.huang@amd.com
Subject: [Regression bisected] v6.3-rc4 Error scheduling IBs after resume from hibernate
Date: Thu, 30 Mar 2023 16:07:40 +0200	[thread overview]
Message-ID: <20230330160740.1dbff94b@schienar> (raw)

Hi,

on an AMD Ryzen 5 PRO 4650U / Renoir (amdgpu: added device
1002:1636) I the screen basically freezes and I get the
following errors with kernel v6.3-rc4

[   26.214541] amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx_low (-110).
[   26.379624] [drm] ring 0 timeout to preempt ib
[   27.387884] amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx_high (-110).
[   27.392945] [drm:process_one_work] *ERROR* ib ring test failed (-110).
[   27.400370] amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring <gfx_low>
[   27.400384] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling
IBs (-22)
[   44.440532] amdgpu 0000:03:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6
[   61.177118] amdgpu 0000:03:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
[   61.189275] amdgpu 0000:03:00.0: amdgpu: couldn't schedule ib on ring <gfx_low>
[   61.189286] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling
IBs (-22)

I bisected the issue, the first bad commit is
b589626674de94d977e81c99bf7905872b991197 reverting it on top
of v6.3-rc4 also fixes the issue.


Best regards,
Julian Wollrath

--
 ()  ascii ribbon campaign - against html e-mail
 /\                        - against proprietary attachments

             reply	other threads:[~2023-03-30 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 14:07 Julian Wollrath [this message]
2023-03-30 15:22 ` [Regression bisected] v6.3-rc4 Error scheduling IBs after resume from hibernate Deucher, Alexander
2023-03-30 16:18   ` Julian Wollrath

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=20230330160740.1dbff94b@schienar \
    --to=jwollrath@web.de \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tim.huang@amd.com \
    /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.