MEMORY_USAGE_UNKNOWN
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 350 missions where this alarm fired in the last 90 days as of 2026-10-13
Frequently co-occurring alarms (% of the 350 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm fires when we can’t sample the state of the memory in linux. Without knowing how much memory we are using, its unsafe to fly.
This should never be set in production, if it is there has been a software regression.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
do-not-reboot-the-vehicle-something-ha["<small><b>Step 1</b></small><br/>Action: Do NOT reboot the vehicle, something ..."]
escalate-to-embedded-linux-on-call{{"<small><b>Step 2</b></small><br/>Escalation: Escalate to P2 Embedded Linux On Call."}}
do-not-reboot-the-vehicle-something-ha --> escalate-to-embedded-linux-on-call
style do-not-reboot-the-vehicle-something-ha fill:#dcfce7,stroke:#22c55e,color:#14532d
style escalate-to-embedded-linux-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f 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.