dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Gang.Ba@amd.com, "Christian König" <christian.koenig@amd.com>,
	"Deucher, Alexander" <alexander.deucher@amd.com>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"Linux List Kernel Mailing" <linux-kernel@vger.kernel.org>,
	"Linux regressions mailing list" <regressions@lists.linux.dev>
Subject: Re: REGRESSION drm/amdgpu: Radeon 7900 XTX hang & gpu_sched "Trying to push to a killed entity" since 1f02f2044bda (6.17-rc)
Date: Thu, 21 Aug 2025 01:05:00 +0500	[thread overview]
Message-ID: <CABXGCsMYpMXEFeycCXp6yJV8jUekOEtSpk0RV_==1x2bdJxVxQ@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_PdzYSzFL7KDsPV7zqX2avwn-NhSJqyVVPYF9LOMEyhWg@mail.gmail.com>

On Mon, Aug 18, 2025 at 7:41 PM Alex Deucher <alexdeucher@gmail.com> wrote:
> Should be fixed in:
> https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5fc4362fac9351557eb27c745579159a2e4520

Thanks.

Confirming the fix: v6.17-rc2 already includes aa5fc4362fac and the
hang is gone on my system with vanilla -rc2 (no local reverts).
My earlier test of -rc2 mistakenly kept a local revert of 1f02f2044bda
- sorry for the noise.

For the record:
v6.17-rc1 (d7ee5bdce789): regression present; cherry-picking
aa5fc4362fac fixes it.
v6.17-rc2: fixed as the commit is merged.

Introduced-by: 1f02f2044bda (“drm/amdgpu: Avoid extra evict-restore process”)
Fixed-by: aa5fc4362fac
Tested-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>

-- 
Best Regards,
Mike Gavrilov.

      reply	other threads:[~2025-08-20 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 14:32 REGRESSION drm/amdgpu: Radeon 7900 XTX hang & gpu_sched "Trying to push to a killed entity" since 1f02f2044bda (6.17-rc) Mikhail Gavrilov
2025-08-18 14:40 ` Alex Deucher
2025-08-20 20:05   ` Mikhail Gavrilov [this message]

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='CABXGCsMYpMXEFeycCXp6yJV8jUekOEtSpk0RV_==1x2bdJxVxQ@mail.gmail.com' \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=Gang.Ba@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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).