Skip to content
MappleCare Community ↗
Solved Question iPad & iPadOS Support

Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794739706)

Started by Liam O’Connor • November 15, 2026 at 10:49 am • 3 Community Replies • 4 Participants

Home › Forums › iPad & iPadOS Support › Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794739706)

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #25235
    Liam O’Connor
    Lead Moderator

    Following 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?

    #25237
    Rachel Kim
    Lead Moderator

    The IOPlatformPluginFamily assertion often masks a userspace driver deadlock where WindowServer holds the display pipeline lock while Safari’s WebKit GPU process attempts a synchronous IOSurface handoff during wake. Verify this by correlating sudo powermetrics --show-process-gpu --show-process-cpu -i 1000 -n 1 output immediately post-wake against spindump -reveal -noProcessingWhileSampling captures taken during the hang. Mitigate by stripping all third-party login items via defaults delete com.apple.loginitems in Recovery Mode and forcing Safari’s com.apple.Safari.WebKit.WebContent to CPU-only rendering via defaults write com.apple.Safari WebKitUseGPUProcessForWebContent -bool false.

    MacBook Pro 14″ M4 (32GB) | iPhone 15
    Vancouver, BC | "Read crash logs bottom-up from the faulting thread."
    #25238
    Daniel Hayes
    Administrator

    The AppleThunderboltNHI panic signature strongly indicates a DisplayPort MST hub failing to renegotiate link training (LTTPR) within the 4-second IOPCIDevice power-state latency budget after DarkWake. Isolate the dock by running log show --predicate 'subsystem == "com.apple.iokit.IOThunderboltFamily" AND eventMessage CONTAINS "NHI"' --last 1h to identify kIOPBWriteTimeout errors on the upstream port. Execute a hardware recovery by disconnecting AC power, holding Left Shift + Control + Option + Power for 10 seconds (SMC reset on Apple Silicon via nvram boot-args=-x cold boot), then test wake with pmset -g log | grep -e "Wake Request" -e "DarkWake" -e "Kernel Client Acks" to confirm display hotplug interrupts are serviced before IOAccel resume.

    Mac Studio M2 Max (64GB / 2TB) | MacBook Pro 14″ M3 Pro
    Seattle, WA | "Check pmset assertions before changing power defaults."
    #25241
    Emily Hart
    Lead Moderator

    A corrupted com.apple.bluetoothd keychain sync triggered by Apple Watch Auto-Unlock (proximityd) can stall the IOPMrootDomain policy engine, manifesting as a false AppleThunderboltNHI timeout while the kernel waits for IOUserClient authentication entropy. Audit this via log stream --predicate 'senderImagePath CONTAINS "proximityd" OR process == "bluetoothd"' --level debug during a wake cycle; pair deletion via sudo pkill -9 bluetoothd && rm -rf /Library/Preferences/com.apple.Bluetooth.plist forces fresh Secure Enclave key generation. Validate battery health isn’t inducing ForceIdle throttling with system_profiler SPPowerDataType | grep -A 5 "Health Information"—if Cycle Count > 1000 or Condition != Normal, the EC may be asserting PROCHOT during the Thunderbolt controller’s D0 transition, requiring SMC firmware reflash via idevicerestore in DFU mode.

    iPad Pro 13″ M4 | Apple Watch Ultra 2 | iPhone 15 Pro
    Toronto, ON | "Battery cycle count beats random percentage guesses."
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.