mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Alexander Deucher <Alexander.Deucher@amd.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Linux 6.1-rc1 drm/amdgpu regression
Date: Wed, 19 Oct 2022 14:00:13 -0600	[thread overview]
Message-ID: <efe5a0a4-775e-bc6b-27c2-aa506f5613fa@linuxfoundation.org> (raw)

Hi Alex,

I am seeing the same problem I sent reverts for on 5.10.147 on
Linux 6.1-rc1 on my laptop with AMD Ryzen 7 PRO 5850U with Radeon
Graphics.

commit e3163bc8ffdfdb405e10530b140135b2ee487f89
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Fri Sep 9 11:53:27 2022 -0400

     drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega

I see that the following has been reverted in Linux 6.1-rc1

commit 66f99628eb24409cb8feb5061f78283c8b65f820
Author: Hamza Mahfooz <hamza.mahfooz@amd.com>
Date:   Tue Sep 6 15:01:49 2022 -0400

     drm/amdgpu: use dirty framebuffer helper

However I still see the following filling dmesg and system is unusable.
For now I switched back to Linux 6.0 as this is my primary system.

[drm] Fence fallback timer expired on ring sdma0
[drm] Fence fallback timer expired on ring gfx
[drm] Fence fallback timer expired on ring sdma0
[drm] Fence fallback timer expired on ring gfx
[drm] Fence fallback timer expired on ring sdma0
[drm] Fence fallback timer expired on ring sdma0
[drm] Fence fallback timer expired on ring sdma0
[drm] Fence fallback timer expired on ring gfx

Please let me know if I should send revert for this for the mainline
as well.

thanks,
-- Shuah

             reply	other threads:[~2022-10-19 20:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 20:00 Shuah Khan [this message]
2022-10-19 20:27 ` Deucher, Alexander
2022-10-19 20:59   ` Shuah Khan
2022-10-19 21:24     ` Deucher, Alexander
2022-10-20  1:16       ` Shuah Khan

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=efe5a0a4-775e-bc6b-27c2-aa506f5613fa@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=Alexander.Deucher@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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
Powered by JetHome