PSTORE_WRITTEN_KERNEL_DEGRADED_REBOOT_REQUIRED
This alarm is covered by this guide. Applicable alarms (2)
Likely outcomes — click to expand
Based on 679 missions where this alarm fired in the last
90 days
(for PSTORE_WRITTEN_KERNEL_DEGRADED_REBOOT_REQUIRED) as of 2026-10-13
Grounding vs discrepancy (of 32 ZERP issues filed on these missions)
Frequently co-occurring alarms (% of the 679 missions above)
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm occurs when the Linux kernel on the Zip Compute has encountered an error, triggering a dump of debug data to the pstore (a persistent storage area designed for this purpose).
The Zip Compute may be in a degraded state and needs to be restarted.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
power-cycle-the-aircraft-refer-to-power["<small><b>Step 1</b></small><br/>Action: Power cycle the aircraft. Refer to P..."]
is-this-alarm-still-alerting-after-a-po{"<small><b>Step 2</b></small><br/>Question: Is this alarm still alerting after a ..."}
escalate-to-p2-embedded-linux-oncall{{"<small><b>Step 3</b></small><br/>Escalation: Escalate to **P2 Embedded Linux Oncal..."}}
return-aircraft-to-service("<small><b>Step 4</b></small><br/>Reference: Return aircraft to service.")
power-cycle-the-aircraft-refer-to-power --> is-this-alarm-still-alerting-after-a-po
is-this-alarm-still-alerting-after-a-po -->|Yes| escalate-to-p2-embedded-linux-oncall
is-this-alarm-still-alerting-after-a-po -->|No| return-aircraft-to-service
style power-cycle-the-aircraft-refer-to-power fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-this-alarm-still-alerting-after-a-po fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-p2-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.