Crash Report: panic(cpu 18 caller 0xffffff801cf7999f): userspace watchdog timeout: no successful checkins from logd in 120 seconds service returned not alive with context : unresponsive dispatch queue(s): com.apple.firehose.io-wl service: logd, total successful checkins since load (40150 seconds ago): 4004, last successful checkin: 120 seconds ago service: WindowServer, total successful checkins since load (40120 seconds ago): 4001, last successful checkin: 110 seconds ago service: opendirectoryd, total successful checkins since load (40150 seconds ago): 4015, last successful checkin: 0 seconds ago Panicked task 0xffffff9123a96030: 4 threads: pid 121: watchdogd Backtrace (CPU 18), panicked thread: 0xffffff8c597f7aa0, Frame : Return Address 0xffffffffff9fb690 : 0xffffff8019a7fd6d 0xffffffffff9fb6e0 : 0xffffff8019be1086 0xffffffffff9fb720 : 0xffffff8019bd03f3 0xffffffffff9fb770 : 0xffffff8019a1fa70 0xffffffffff9fb790 : 0xffffff8019a8013d 0xffffffffff9fb8b0 : 0xffffff8019a7f8f6 0xffffffffff9fb910 : 0xffffff801a314ec3 0xffffffffff9fba00 : 0xffffff801cf7999f 0xffffffffff9fba10 : 0xffffff801cf795f2 0xffffffffff9fba30 : 0xffffff801cf78971 0xffffffffff9fbb60 : 0xffffff801a28365c 0xffffffffff9fbcc0 : 0xffffff8019b86d86 0xffffffffff9fbdd0 : 0xffffff8019a5a9ab 0xffffffffff9fbe60 : 0xffffff8019a711a9 0xffffffffff9fbef0 : 0xffffff8019bb305a 0xffffffffff9fbfa0 : 0xffffff8019a20256 Kernel Extensions in backtrace: com.apple.driver.watchdog(1.0)[8BE4EE7F-9150-3161-BE84-36874BF82DE2]@0xffffff801cf77000->0xffffff801cf79fff Process name corresponding to current thread (0xffffff8c597f7aa0): watchdogd Boot args: -lilubetaall -wegbeta agdpmod=pikera enable-gva-support shikigva=80 unfairgva=1 mbasd=1 -wegtree -no_compat_check no32exec=0 Mac OS version: 21G83 Kernel version: Darwin Kernel Version 21.6.0: Wed Aug 10 14:25:27 PDT 2022; root:xnu-8020.141.5~2/RELEASE_X86_64 Kernel UUID: D0DC2052-71F4-3DCB-B189-BEE5A59B3B42 KernelCache slide: 0x0000000019800000 KernelCache base: 0xffffff8019a00000 Kernel slide: 0x0000000019810000 Kernel text base: 0xffffff8019a10000 __HIB text base: 0xffffff8019900000 System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) Hibernation exit count: 0 System uptime in nanoseconds: 40158301798816 Last Sleep: absolute base_tsc base_nano Uptime : 0x0000248615504b9c Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000 Wake : 0x0000000000000000 0x0000003e5e796194 0x0000000000000000 Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space Zone info: Zone map: 0xffffff811747c000 - 0xffffffa11747c000 . PGZ : 0xffffff811747c000 - 0xffffff812f47d000 . VM : 0xffffff812f47d000 - 0xffffff85f87b0000 . RO : 0xffffff85f87b0000 - 0xffffff8790e16000 . GEN0 : 0xffffff8790e16000 - 0xffffff8c5a149000 . GEN1 : 0xffffff8c5a149000 - 0xffffff912347c000 . GEN2 : 0xffffff912347c000 - 0xffffff95ec7af000 . GEN3 : 0xffffff95ec7af000 - 0xffffff9ab5ae2000 . DATA : 0xffffff9ab5ae2000 - 0xffffffa11747c000 Metadata: 0xfffffff7cf676000 - 0xfffffff7ef676000 Bitmaps : 0xfffffff7ef676000 - 0xfffffff80f676000 -----------------------------------------------------------------------------------------------------------------------s ChatGPT Analysis of the Crash: Alright, this is a **real kernel panic**, not an app crash — and the report actually tells us a lot. I’ll translate it into plain English, then give you concrete steps to prevent it. --- ## What *actually* caused the crash The key line is right at the top: > **userspace watchdog timeout: no successful checkins from logd in 120 seconds** macOS has a **watchdog** whose only job is to reboot the machine if *critical system services stop responding*. That’s what happened here. ### The failing chain looks like this: 1. **`logd` froze** * `logd` = the macOS logging daemon (Unified Logging). * It stopped responding for **120 seconds**. * That alone is enough to panic the system. 2. **The firehose logging pipeline stalled** * This line is crucial: ``` unresponsive dispatch queue(s): com.apple.firehose.io-wl ``` * Firehose is the **high-performance logging pipeline** used by macOS. * When firehose blocks, *everything that logs* can block behind it. 3. **WindowServer was also impacted** ``` service: WindowServer … last successful checkin: 110 seconds ago ``` * That means the **entire GUI subsystem** was starting to hang. * At this point, macOS considers the system unrecoverable. 4. **watchdogd pulled the plug** * `watchdogd` intentionally triggered a kernel panic to force a reboot. * This is *by design*, not a bug in watchdog itself. --- ## Why this is happening *on your machine specifically* Your system details matter a lot here: ### 🚨 You are running: * **MacPro5,1 (2010–2012 era)** * **macOS 12.6.8 (Monterey)** * **Non-Apple GPU stack** * **Multiple boot args modifying graphics & media frameworks** Boot args that stand out: ``` -lilubetaall -wegbeta agdpmod=pikera enable-gva-support shikigva=80 unfairgva=1 -wegtree -no_compat_check ``` This strongly suggests: * **OpenCore / Hack-style GPU patching** * Lilu + WhateverGreen + Shiki modifying: * GPU drivers * Hardware video acceleration * Media frameworks * WindowServer behavior ### Why that matters On Monterey: * **`logd` and WindowServer are tightly coupled** * GPU stalls → WindowServer stalls → logging stalls * When logging blocks, firehose backs up * Firehose backup = watchdog panic This exact failure pattern is **extremely common** on: * MacPro5,1 systems * With patched GPUs * Running Monterey or newer * Especially under GPU or I/O pressure --- ## What *did NOT* cause this Just to be clear: ❌ Not bad RAM ❌ Not a random kernel bug ❌ Not filesystem corruption ❌ Not a single crashing app This is a **system-wide deadlock** caused by a stalled critical service. --- ## The most likely triggers (ranked) ### 1️⃣ GPU driver deadlock (most likely) * WindowServer stopped checking in * GVA / Shiki flags can deadlock media + GPU threads * Common during: * Video playback * Heavy UI redraw * Screensavers * GPU-accelerated apps (Photos, browsers, video tools) ### 2️⃣ Unified logging overload * Firehose queue stalled * Happens when: * A process logs excessively * Disk I/O is slow * Logging is blocked by a kernel extension ### 3️⃣ Monterey + MacPro5,1 incompatibility edge * Monterey is *barely supported* on this hardware * Apple did not test logd/firehose under these conditions --- ## What to do to **prevent this from happening again** ### ✅ Step 1: Reduce GPU patching complexity (biggest win) If you are using OpenCore: * **Disable or simplify Shiki flags** * Try removing: ``` shikigva=80 unfairgva=1 enable-gva-support ``` * Keep only what you *actually need* Many users find Monterey far more stable with **less video acceleration**, not more. --- ### ✅ Step 2: Update Lilu + WhateverGreen (critical) Make sure you are on the **latest versions compatible with Monterey**, not betas. Old versions can deadlock firehose logging. --- ### ✅ Step 3: Test without WhateverGreen (diagnostic test) If you can boot without WEG: * Expect worse graphics * But if the panics stop → you’ve confirmed the root cause --- ### ✅ Step 4: Check disk health (logging is disk-heavy) Run in Terminal: ```bash diskutil verifyVolume / ``` Slow or failing disks can stall `logd`. --- ### ✅ Step 5: Avoid GPU stress until stable Until you confirm stability: * Avoid: * 4K video playback * Screensavers * Hardware-accelerated browsers * Disable browser hardware acceleration temporarily --- ### ✅ Step 6: Consider downgrading macOS (honest advice) On MacPro5,1: * **Big Sur is significantly more stable** * Monterey pushes logging + GPU subsystems harder If this machine matters for work, Big Sur is the “boring but solid” choice. --- ## TL;DR (but still accurate) * This crash was **intentional**: macOS rebooted itself because core services froze * The freeze started in **logd/firehose**, cascaded into **WindowServer** * The **root cause is almost certainly GPU patching on a MacPro5,1** * Simplifying or removing GVA/Shiki/WEG tweaks is your best fix * Monterey is fragile on this hardware If you want, tell me: * Your GPU model * Whether this is OpenCore (and version) * When the crash happens (idle? video? screensaver?) I can give you **specific boot-arg recommendations** instead of general ones.