Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794600897)
Independent peer-to-peer Apple troubleshooting rooms • 100% English • Not affiliated with Apple Inc.
Home › Forums › MacBook, iMac & macOS Lab › Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794600897)
- This topic has 3 replies, 4 voices, and was last updated 3 hours, 45 minutes ago by
Owen Parker.
-
AuthorPosts
-
November 13, 2026 at 8:16 pm #1159
Rachel Kim
ParticipantFollowing the recent point release update, my system has encountered intermittent sleep/wake panics. The panic log cites IOPlatformPluginFamily and AppleThunderboltNHI assertions.
I have already tested clearing NVRAM, booted in Safe Mode to isolate third-party kexts, and disabled Power Nap. Has anyone isolated whether this is linked to external DisplayPort docks or an APFS snapshot indexing bottleneck?
November 13, 2026 at 8:16 pm #1160Alex Tanner
ParticipantThe
AppleThunderboltNHIassertion often stems from a Thunderbolt Security Level mismatch (e.g., “User” vs “Secure” mode) preventing DMA authorization during the wake transition, effectively treating the dock as an untrusted device. Verify the active security policy and connected device ACLs viasystem_profiler SPThunderboltDataType | grep -A 5 "Security Level"and ensure the dock’s firmware is current. If FileVault is enabled, confirm the Secure Enclave key hierarchy isn’t stalling during the power state handoff by checkinglog show --predicate 'subsystem == "com.apple.iokit.IOThunderboltFamily"' --last 1h. A corruptcom.apple.iokit.IOThunderboltFamilypreference plist in/Library/Preferences/can also persist bad ACLs; delete it and reboot to force re-enumeration.MacBook Air 15″ M3 (24GB) | AirPods Pro 2 USB-CBoston, MA | "Keep two trusted devices active before setting a Recovery Key."November 13, 2026 at 8:16 pm #1161Claire Bennett
ParticipantThe
IOPlatformPluginFamilypanic frequently correlates with a failed USB-PD / Thunderbolt power contract renegotiation upon wake, where the dock fails to source the negotiated voltage (e.g., 20V/5A) before the CPU exits C-state, triggering a watchdog timeout. Capture the power assertion timeline withpmset -g log | grep -e "Wake Requests" -e "DarkWake" -e "Thunderbolt" -e "PD" | tail -30to identify stalled handshakes. Update the dock/DisplayPort adapter firmware via the vendor’s macOS utility—many CalDigit/OWC/Belkin docks shipped with 2023 PD controllers requiring patches for Sequoia’s revisedApplePMGRdriver. Disable “Wake for network access” and “Power Nap” explicitly viasudo pmset -a powernap 0 wom 0to isolate if the PD controller is the wake source.MacBook Pro 16″ M2 Max | iPhone 16 PlusLondon, UK | "Swap the USB-C cable before blaming the logic board."November 13, 2026 at 8:16 pm #1162Owen Parker
ParticipantInspect the Thunderbolt/USB-C port ingress sensors (SMC keys
TC0C,TC1Cfor port thermals;ALV0for liquid) viasudo powermetrics --samplers smc -n 1 -i 1000immediately post-wake; a rapid thermal spike (>15°C delta) or asserted liquid flag on the NHI controller’s retimer IC will trigger a kernel panic to protect the SoC. Corrosion on the dock’s CC/SBU pins creates high resistance, confusing theAppleThunderboltNHIstate machine during link training—clean ports with 99% IPA and inspect under magnification. If the panic log showsAppleSMC::handleThermalEventpreceding the NHI assertion, the issue is thermal runaway in the Titan/Thunderbolt controller, requiring a logic board or dock replacement rather than an OS fix.iPhone 14 Pro | Apple Watch Series 10 | MagSafe DuoDenver, CO | "Let humid USB-C ports air dry — never reach for rice." -
AuthorPosts
- You must be logged in to reply to this topic.