Hi Leonid,

One possible cause I can think of is the trigger type (level vs edge) of an interrupt is incorrect. The Linux device tree should have interrupt type for each interrupt source, so you can change the GIC init code to configure the interrupt types (GICD_ICFGR, assuming GICv2) accordingly and see if the messages disappear.

Regards,

Yanyan

From: Devel <devel-bounces@sel4.systems> on behalf of Leonid Meyerovich <lmeyerovich@i-a-i.com>
Date: Wednesday, 5 June 2019 at 4:28 am
To: "devel@sel4.systems" <devel@sel4.systems>
Subject: [seL4] xilinx ultrascale+: Spurious interrupt

Hello Everybody,

Petalinux is running on VM on the one of the core of Xilinx Ultrascale+ (A53)

From time to time I see Spurious Interrupt message from seL4 kernel (handleInterruptEntry)

<<seL4(CPU 1) [handleInterruptEntry/54 T0xff805da00400 "vm core" @ffffff80080fa414]: Spurious interrupt!>>

<<seL4(CPU 1) [handleInterruptEntry/54 T0xff805da00400 "vm core" @ffffff80083e64bc]: Spurious interrupt!>>

<<seL4(CPU 1) [handleInterruptEntry/54 T0xff805da00400 "vm core" @ffffff800894cc98]: Spurious interrupt!>>

Could somebody explain why it may happen? How to debug it?

Thank you,

Leonid

---

This message and all attachments are PRIVATE, and contain information that is PROPRIETARY to Intelligent Automation, Inc. You are not authorized to transmit or otherwise disclose this message or any attachments to any third party whatsoever without the express written consent of Intelligent Automation, Inc. If you received this message in error or you are not willing to view this message or any attachments on a confidential basis, please immediately delete this email and any attachments and notify Intelligent Automation, Inc.