AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@cixtech.com>
To: "Alexey Klimov" <alexey.klimov@linaro.org>
Cc: "Christian König" <christian.koenig@amd.com>,
	alexander.deucher@amd.com, frank.min@amd.com,
	amd-gfx@lists.freedesktop.org, stable@vger.kernel.org,
	david.belanger@amd.com, cix-kernel-upstream@cixtech.com,
	linux-arm-kernel@lists.infradead.org, bob.zhang@cixtech.com
Subject: Re: [REGRESSION] amdgpu: async system error exception from hdp_v5_0_flush_hdp()
Date: Thu, 24 Apr 2025 19:41:09 +0800	[thread overview]
Message-ID: <aAojVb48Vx1qY5LM@nchen-desktop> (raw)
In-Reply-To: <D9CTQ5P0YSCF.2802I0W1M4AWM@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 2655 bytes --]

On 25-04-22 03:49:17, Alexey Klimov wrote:
> EXTERNAL EMAIL
>
> 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.
>

Hi Alexey,

This board has just got Arm SystemReady SR v2.5 certificate, See
attachment. Arm is in the process of updating the list, so you may
can't find it in website now.

Peter
> 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

--

Best regards,
Peter


This email (including its attachments) is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Unauthorized use, dissemination, distribution or copying of this email or the information herein or taking any action in reliance on the contents of this email or the information herein, by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is strictly prohibited. If you are not the intended recipient, please do not read, copy, use or disclose any part of this e-mail to others. Please notify the sender immediately and permanently delete this e-mail and any attachments if you received it in error. Internet communications cannot be guaranteed to be timely, secure, error-free or virus-free. The sender does not accept liability for any errors or omissions.

[-- Attachment #2: Arm_SystemReady_SR_Certificate_Radxa_Computer_Shenzhen_Co_Ltd_Radxa_Orion_O6_1344.pdf --]
[-- Type: application/pdf, Size: 78685 bytes --]

      reply	other threads:[~2025-04-25  7:39 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
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 [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=aAojVb48Vx1qY5LM@nchen-desktop \
    --to=peter.chen@cixtech.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexey.klimov@linaro.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bob.zhang@cixtech.com \
    --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=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