AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexey Klimov" <alexey.klimov@linaro.org>
To: "Fugang Duan" <fugang.duan@cixtech.com>,
	"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
	"frank.min@amd.com" <frank.min@amd.com>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"david.belanger@amd.com" <david.belanger@amd.com>,
	"christian.koenig@amd.com" <christian.koenig@amd.com>,
	"Peter Chen" <peter.chen@cixtech.com>,
	"cix-kernel-upstream" <cix-kernel-upstream@cixtech.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: 回复: [REGRESSION] amdgpu: async system error exception from hdp_v5_0_flush_hdp()
Date: Wed, 16 Apr 2025 12:25:30 +0100	[thread overview]
Message-ID: <D980Y4WDV662.L4S7QAU72GN2@linaro.org> (raw)
In-Reply-To: <SI2PR06MB5041FB15F8DBB44916FB6430F1BD2@SI2PR06MB5041.apcprd06.prod.outlook.com>

On Wed Apr 16, 2025 at 4:12 AM BST, Fugang Duan wrote:
> 发件人: Alexey Klimov <alexey.klimov@linaro.org> 发送时间: 2025年4月16日 2:28
>>#regzbot introduced: v6.12..v6.13

[..]

>>The only change related to hdp_v5_0_flush_hdp() was
>>cf424020e040 drm/amdgpu/hdp5.0: do a posting read when flushing HDP
>>
>>Reverting that commit ^^ did help and resolved that problem. Before sending
>>revert as-is I was interested to know if there supposed to be a proper fix for
>>this or maybe someone is interested to debug this or have any suggestions.
>>
> Can you revert the change and try again https://gitlab.com/linux-kernel/linux/-/commit/cf424020e040be35df05b682b546b255e74a420f

Please read my email in the first place.
Let me quote just in case:

>The only change related to hdp_v5_0_flush_hdp() was
>cf424020e040 drm/amdgpu/hdp5.0: do a posting read when flushing HDP

>Reverting that commit ^^ did help and resolved that problem.

Thanks,
Alexey


  reply	other threads:[~2025-04-16 13:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 18:28 [REGRESSION] amdgpu: async system error exception from hdp_v5_0_flush_hdp() Alexey Klimov
2025-04-16  3:12 ` 回复: " Fugang Duan
2025-04-16 11:25   ` Alexey Klimov [this message]
2025-04-16 14:49     ` Alex Deucher
2025-04-17  0:42       ` 回复: " Fugang Duan
2025-04-17 13:08         ` Alex Deucher
2025-04-18  0:30           ` 回复: " Fugang Duan
2025-04-18  1:10             ` Alex Deucher
2025-04-22  2:20           ` Alexey Klimov
2025-04-22 13:00             ` Alex Deucher
2025-04-22 15:59               ` Alexey Klimov
2025-04-23 14:32                 ` Christian König
2025-04-24 15:44                 ` Alex Deucher
2025-04-27  1:01                   ` Alexey Klimov
2025-04-30 16:55                     ` Alex Deucher
2025-05-11 23:24                       ` Alexey Klimov
2025-05-12 14:46                         ` Alex Deucher
2025-04-16 11:44 ` Christian König
2025-04-22  2:49   ` Alexey Klimov
2025-04-24 11:41     ` Peter Chen

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=D980Y4WDV662.L4S7QAU72GN2@linaro.org \
    --to=alexey.klimov@linaro.org \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=david.belanger@amd.com \
    --cc=frank.min@amd.com \
    --cc=fugang.duan@cixtech.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=peter.chen@cixtech.com \
    --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