socd-iboot — Unknown
Difference from “AP watchdog expired”: there, the main processor froze and the hardware watchdog restarted the device, with no text in the report. Here, the boot firmware itself (iBoot, called mBoot on recent iPhones) panicked; on the next boot, iOS only recovered the SOCD report (diagnostics kept across the restart) and displayed it as a panic. Unlike the watchdog case, the SOCDContainers block of an “iBoot panic” is readable: once decoded (base64), it contains iBoot's message in plain text. On an iPhone 14 Pro Max log (iOS 27.0): “iBoot Panic: ANS2 : Recoverable PANIC assert failed … MSP 0 asserted”; an ANS2 panic points to the NAND storage controller (iFixit). Without this decoding, the “iBoot panic” text does not say which component is at fault.
iPhone
Undetermined from the text alone — the detail is in the SOCDContainers block (case seen: ANS2 storage controller / NAND)
First check
Decode the SOCDContainers block (base64) and read iBoot's message.
Sources
- Apple XNU – socd_client.h (“soc diagnostics data pipeline”, XNU / WDT / SOC classes) ↗
- iFixit – iPhone Kernel Panics (wiki): “ANS2 Recoverable Panic” = NAND storage controller problem ↗
- Apple Community #254896533 – “SOCD report detected: (iBoot panic)” on MacBook Pro M1 (unresolved) ↗
- Rossmann Repair Group – MacBook Air M2: “SOCD report detected: (iBoot panic)” with pink screen (no confirmed repair) ↗