From: "Alexey Klimov" <alexey.klimov@linaro.org>
To: "Christian König" <christian.koenig@amd.com>,
alexander.deucher@amd.com, frank.min@amd.com,
amd-gfx@lists.freedesktop.org
Cc: <stable@vger.kernel.org>, <david.belanger@amd.com>,
<peter.chen@cixtech.com>, <cix-kernel-upstream@cixtech.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [REGRESSION] amdgpu: async system error exception from hdp_v5_0_flush_hdp()
Date: Tue, 22 Apr 2025 03:49:17 +0100 [thread overview]
Message-ID: <D9CTQ5P0YSCF.2802I0W1M4AWM@linaro.org> (raw)
In-Reply-To: <1567c4e7-fd5c-42d4-8278-e1bba2ce46cc@amd.com>
On Wed Apr 16, 2025 at 12:44 PM BST, Christian König wrote:
> Am 15.04.25 um 20:28 schrieb Alexey Klimov:
>> #regzbot introduced: v6.12..v6.13
>>
>> I use RX6600 on arm64 Orion o6 board and it seems that amdgpu is broken on recent kernels, fails on boot:
>
> Well in general we already had tons of problems with low end ARM64 boards. So first question of all is that board SBSA certified?
Yeah, I can imagine.
I can't find any info about SBSA cartification for that board hence I'd say that
state is unknown, hence most likely "no". At least that's what I think.
It is a good question for cix or cixtech.com-based emails.
They have some updated potentially unstable UEFI firmwares to test though.
> If not then the chances of that board actually working correctly are very low unfortunately.
>
>> [drm] amdgpu: 7886M of GTT memory ready.
>> [drm] GART: num cpu pages 131072, num gpu pages 131072
>> SError Interrupt on CPU11, code 0x00000000be000011 -- SError
>
> Any idea what that error code means?
Well, current thinking process that it means:
-- bits 31:26 system error interrupt;
-- bit 25 indicates that it was 32-bit instruction;
-- 0x11 in lsb is probably implementation-defined which can
be anything like bus errors, parity, access violations, etc
That's probably not very helping here.
Best regards,
Alexey
next prev parent reply other threads:[~2025-04-22 8:15 UTC|newest]
Thread overview: 24+ 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 3:12 ` Fugang Duan
2025-04-16 11:25 ` Alexey Klimov
2025-04-16 14:49 ` Alex Deucher
2025-04-17 0:42 ` 回复: " Fugang Duan
2025-04-17 0:42 ` Fugang Duan
2025-04-17 13:08 ` Alex Deucher
2025-04-18 0:30 ` 回复: " Fugang Duan
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 [this message]
2025-04-24 11:41 ` Peter Chen
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=D9CTQ5P0YSCF.2802I0W1M4AWM@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=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 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.