Re: [REGRESSION] amdgpu: async system error exception from hdp_v5_0_flush_hdp()

[Peter Chen <peter.chen@cixtech.com>]

[-- Attachment #1: Type: text/plain, Size: 1660 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

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