MappleCare Community
Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794703853)
Find answers from other Apple users or start a discussion about your device.
Home › Forums › Apple Watch & AirPods › Diagnostic query: Unexpected kernel panic on macOS Sequoia 15.1 after waking (1794703853)
- This topic has 3 replies, 4 voices, and was last updated 22 minutes ago by
Liam O’Connor.
-
AuthorPosts
-
November 15, 2026 at 12:51 am #15954
Claire Bennett
Lead ModeratorFollowing 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 15, 2026 at 12:51 am #15955Daniel Hayes
AdministratorThe
AppleThunderboltNHIassertion alongsideIOPlatformPluginFamilystrongly indicates a Thunderbolt/USB4 path state machine failure during the D3cold-to-D0 transition, likely triggered by the dock’s DisplayPort MST hub failing to re-enumerate link training within theIOPCIDeviceresume latency budget. Verify the dock’s PD controller firmware viasystem_profiler SPThunderboltDataType | grep -A 5 "Firmware Version"and cross-reference against the vendor’s Sequoia 15.1 compatibility matrix; a forcedpmset -a tcpkeepalive 0andhibernatemode 25test isolates whether the panic persists in deep hibernation versus standard sleep. If the call stack showsIOThunderboltController::handleInterrupttiming out, disable “Wake for network access” and test with a direct-attach TB4 cable bypassing the dock’s upstream port to rule out retimer signal integrity degradation.Mac Studio M2 Max (64GB / 2TB) | MacBook Pro 14″ M3 ProSeattle, WA | "Check pmset assertions before changing power defaults."November 15, 2026 at 12:51 am #15956Alex Tanner
Lead ModeratorWhile unrelated to the
IOPlatformPluginFamilypanic signature, ensure your Apple Account security posture isn’t introducing backgroundaccountsddorakddaemon contention during wake by auditinglog show --predicate 'subsystem == "com.apple.accounts"'forkTCCErrorPolicyDeniedspikes coinciding with the panic timestamps. Rotate the local device keychain sync identity viasecurity delete-generic-password -l "iCloud Keychain"followed by a forcedakdrestart (launchctl kickstart -k gui/$(id -u)/com.apple.akd) to clear potential Secure Enclave nonce desynchronization that can manifest as watchdog timeouts if the T2/SEP handshake stalls during power state restoration. Confirm Passkey attestation certificates are valid (security find-certificate -c "Apple Passkey" -p) as expired roots rarely cause kernel panics but frequently stall userland resume completion.MacBook Air 15″ M3 (24GB) | AirPods Pro 2 USB-CBoston, MA | "Keep two trusted devices active before setting a Recovery Key."November 15, 2026 at 12:51 am #15957Liam O’Connor
Lead ModeratorThe
bluetoothdandairplayddaemons aggressively renegotiateIOBluetoothHostControllerACL links andAirPlayReceiverBonjour advertisements on wake, which can starve thekernel_taskworkloop if the dock’s USB hub enumerates the Bluetooth controller on a shared PCIe lane with the TBT NHI. Update AirPods firmware by placing them in the case, opening the lid near the Mac, and verifyingsystem_profiler SPBluetoothDataType | grep -A 10 "Firmware Version"shows the latest 6F7/6F8 build; simultaneously disable “Allow Handoff between this Mac and your iCloud devices” in General > AirDrop & Handoff to quiescebluetoothaudiodresume traffic. For HomeKit, purge the localHomeKitAccessoryDeveloperkeychain items (security delete-generic-password -s "com.apple.homekit") and toggle the Home Hub setting off/on in Home.app to force a freshhappairing database sync, eliminating mDNS storm contributions to the wake latency budget.iMac 24″ M3 (16GB) | HomePod mini Stereo PairDublin, IE | "Clean Wi-Fi multicast fixes half of AirPlay drops." -
AuthorPosts
- You must be logged in to reply to this topic.