KERNEL_PSTORE_EXISTS_FROM_PRIOR_ERROR
This alarm is covered by this guide. Applicable alarms (1)
Likely outcomes — click to expand
Based on 10 missions where this alarm fired in the last 90 days as of 2026-10-13
Grounding vs discrepancy (of 2 ZERP issues filed on these missions)
Frequently co-occurring alarms (% of the 10 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm occurs if the Linux kernel on the Zip Compute previously encountered an error, leaving behind debug data in the pstore (a persistent storage area designed for this purpose).
This pstore data will be captured by the Zip’s logging system and offloaded appropriately. The alarm will clear once the data has been safely ingested into the logging system.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
wait-up-to-one-minute-for-the-alarm-to["<small><b>Step 1</b></small><br/>Action: Wait up to one minute for the alarm t..."]
is-this-alarm-still-alerting-after-one{"<small><b>Step 2</b></small><br/>Question: Is this alarm still alerting after on..."}
escalate-to-embedded-linux-oncall{{"<small><b>Step 3</b></small><br/>Escalation: Escalate to **Embedded Linux Oncall**."}}
return-aircraft-to-service("<small><b>Step 4</b></small><br/>Reference: Return aircraft to service.")
wait-up-to-one-minute-for-the-alarm-to --> is-this-alarm-still-alerting-after-one
is-this-alarm-still-alerting-after-one -->|Yes| escalate-to-embedded-linux-oncall
is-this-alarm-still-alerting-after-one -->|No| return-aircraft-to-service
style wait-up-to-one-minute-for-the-alarm-to fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-this-alarm-still-alerting-after-one fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-embedded-linux-oncall fill:#fef3c7,stroke:#f59e0b,color:#78350f
style return-aircraft-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87 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.