IRQ_AFFINITY_SETUP_INCOMPLETE
Applicable alarms (1)
Likely outcomes — click to expand
Based on 1,489 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 16 ZERP issues filed on these missions)
Frequently co-occurring alarms (% of the 1,489 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm should be set on boot and cleared after the irq affinity service has successfully configured the core that each hardware IRQ is allowed to run on. For example, we pin the IMU SPI IRQ to core 5, where the rest of our controls loop lives. There appears to be a race condition where very occasionally the IRQ ends up on a non-deterministic IRQ number in which case we require a reboot.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-aircraft-for-steps-see["<small><b>Step 1</b></small><br/>Action: Power cycle the Aircraft. For steps, ..."]
is-the-irq-affinity-setup-incomplete{"<small><b>Step 2</b></small><br/>Question: Is the IRQ_AFFINITY_SETUP_INCOMPLETE ..."}
escalate-to-embedded-linux-on-call{{"<small><b>Step 3</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
the-aircraft-can-be-cleared-for-service["<small><b>Step 4</b></small><br/>Action: The Aircraft can be cleared for service."]
power-cycle-the-aircraft-for-steps-see --> is-the-irq-affinity-setup-incomplete
is-the-irq-affinity-setup-incomplete -->|YES| escalate-to-embedded-linux-on-call
is-the-irq-affinity-setup-incomplete -->|NO| the-aircraft-can-be-cleared-for-service
style power-cycle-the-aircraft-for-steps-see fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-irq-affinity-setup-incomplete fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-embedded-linux-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style the-aircraft-can-be-cleared-for-service fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.