iPhone 15 又自己重開了一次：這次是 SpringBoard 卡死 180 秒

📌 一句話結論

這次不是過熱。log 顯示是一次 userspace watchdog timeout：負責整個桌面與 UI 的 SpringBoard 行程卡住了，連續 180 秒沒向系統「回報還活著」。其他系統服務（藍牙、音訊、Wi-Fi、溫度監控…）全都正常運作，所以系統判定是 SpringBoard 自己鎖死，為了把畫面救回來，由軟體層的看門狗強制重開。簡單說：這是一次「桌面卡死 → 自動重啟」，不是手機壞掉。

📌 TL;DR

This time it wasn't heat. The log shows a userspace watchdog timeout: SpringBoard — the process behind the entire home screen and UI — got stuck and went 180 seconds without telling the system "I'm still alive." Every other system service (Bluetooth, audio, Wi-Fi, thermal monitor…) was working normally, so the system concluded SpringBoard itself was locked up and, to recover the UI, the software-level watchdog forced a reboot. In short: a "home screen froze → auto-restart," not a broken phone.

🕓 當時的情況

事發時間是 下午 16:27，手機已經開機運作約 15 小時（log 裡的 uptime 約 53,815 秒）。這次不是在大太陽下、也沒有滿載錄影——跟前一天那次「正午高溫熱當機」的情境完全不同。

體感上就是：畫面突然卡住、點什麼都沒反應，過了一段時間（約 3 分鐘）手機自己黑屏重開，重開後一切正常。

🕓 The Situation

It happened at 4:27 PM, after the phone had been running for about 15 hours (uptime in the log is ~53,815 seconds). This time it was not in direct sun and not under a heavy recording load — completely different from the previous day's noon heat shutdown.

What it felt like: the screen suddenly froze, taps did nothing, and after a few minutes (~3) the phone went black and rebooted on its own. Everything was fine afterward.

🔍 這份 log 在說什麼

① 關鍵那一行

userspace watchdog timeout: no successful checkins from SpringBoard (1 induced crashes) in 180 seconds

翻成白話：iOS 內部有個「看門狗」會要求每個重要服務定期「打卡報平安」。這行說的是——SpringBoard 已經 180 秒沒打卡了，看門狗認定它徹底卡死。後面那句 (1 induced crashes) 代表系統其實先試過「踹它一腳叫它重來」一次，沒救回來，最後才走到整機重開。

② 為什麼確定是 SpringBoard、不是別的

log 很貼心地列出所有受監控服務的「最後打卡時間」。除了 SpringBoard 是 180 秒前，其餘全部都是 0 秒前（剛剛才打卡）：

backboardd、audiomxd、logd、thermalmonitord、runningboardd、wifid、configd、CommCenter → 全部 0 秒前正常。

這代表系統的「地基」其實都活得好好的，唯獨最上層的桌面（SpringBoard）卡住。問題集中在 UI 層，不是底層硬體或核心。

③ 這次跟「過熱」無關

負責監控溫度的 thermalmonitord 也是 0 秒前正常打卡，沒有任何過熱降頻的跡象。所以這次跟前一天那次「高溫熱當機」是兩種不同的當機：上次是硬體看門狗在關機過程被熱逼到極限，這次是軟體看門狗發現桌面卡死。

🔍 What the Log Actually Says

① The key line

userspace watchdog timeout: no successful checkins from SpringBoard (1 induced crashes) in 180 seconds

In plain terms: iOS has a "watchdog" that requires each important service to "check in" periodically. This line says SpringBoard went 180 seconds without checking in, so the watchdog ruled it fully hung. The (1 induced crashes) note means the system first tried to "kick it and make it restart" once, that didn't recover it, and only then did it escalate to a full reboot.

② Why we're sure it's SpringBoard and nothing else

The log helpfully lists the "last check-in time" for every monitored service. Only SpringBoard is at 180 seconds ago; every other one is 0 seconds ago (just checked in):

backboardd, audiomxd, logd, thermalmonitord, runningboardd, wifid, configd, CommCenter → all normal, 0 seconds ago.

That means the "foundation" of the system was alive and well; only the top-level home screen (SpringBoard) was stuck. The problem is concentrated in the UI layer, not the low-level hardware or kernel.

③ This one has nothing to do with heat

thermalmonitord, which watches temperature, also checked in 0 seconds ago with no sign of thermal throttling. So this is a different kind of crash from the previous day's heat shutdown: last time a hardware watchdog was pushed past its limit by heat during shutdown; this time a software watchdog detected a frozen home screen.

🤔 SpringBoard 為什麼會卡死

SpringBoard 是 iOS 的「桌面大腦」——主畫面、App 切換、通知、鎖定畫面、狀態列全都歸它管。它一旦卡住，整支手機看起來就像「死當」。常見的卡死原因有幾類：

· 主執行緒被卡住：某個動畫、某個畫面渲染、或等待某個系統回應時陷入鎖死（deadlock）或無限等待，導致 UI 執行緒動不了。

· 資源吃緊：長時間開機（這次約 15 小時）累積記憶體碎片、太多 App 在背景，瞬間的資源壓力讓 SpringBoard 反應不過來。

· iOS 本身的 bug：某些版本在特定情境（例如某個通知、某個外接裝置、某個 widget）會偶發讓 SpringBoard 卡住，屬於系統層級的偶發事件。

從這份 log 無法 100% 鎖定是哪一個，但可以確定：這是軟體層的偶發卡死，不是硬體損壞。

🤔 Why SpringBoard Hangs

SpringBoard is the "brain of the home screen" in iOS — the main screen, app switching, notifications, lock screen and status bar all run through it. When it hangs, the whole phone looks dead-frozen. Common causes fall into a few buckets:

· The main thread gets stuck: an animation, a screen render, or waiting on some system response falls into a deadlock or infinite wait, freezing the UI thread.

· Resource pressure: long uptime (about 15 hours here) builds up memory fragmentation and too many background apps; a burst of pressure leaves SpringBoard unable to keep up.

· An iOS bug: some versions, in specific situations (a particular notification, an accessory, a widget), can occasionally freeze SpringBoard — a system-level intermittent event.

This single log can't pin down which one with certainty, but one thing is clear: it's an intermittent software hang, not hardware damage.

🛠️ 該怎麼處理

✅ 三個建議

1. 偶發一次：當成正常自我修復。重開後一切正常，就代表 iOS 的看門狗成功把卡死的桌面救回來了，這正是它該做的事，不用焦慮。

2. 偶爾手動重開機。長時間不關機（這次 15 小時其實不算長，但習慣養成有幫助），偶爾重開可以清掉累積的記憶體與背景狀態，降低 SpringBoard 卡死的機率。

3. 若「頻繁」發生才需要進一步查。如果一天卡死好幾次，再依序排查：更新到最新 iOS、移除最近新裝/可疑的 App 或 widget、必要時備份後「重置所有設定」。單一一次不必走到這步。

🛠️ What To Do

✅ Three suggestions

1. A one-off: treat it as normal self-recovery. If everything works after the reboot, iOS's watchdog successfully rescued the frozen home screen — exactly what it's supposed to do. No need to worry.

2. Reboot manually now and then. Going a long time without a restart (15 hours isn't really long, but the habit helps) lets memory and background state pile up; an occasional reboot clears it and lowers the chance of a SpringBoard hang.

3. Only dig deeper if it's frequent. If it freezes several times a day, work through it in order: update to the latest iOS, remove recently installed or suspicious apps/widgets, and if needed back up and "Reset All Settings." A single occurrence doesn't warrant this.

📄 Crash log（關鍵段落 · 已遮蔽）

以下是這次 panic 的關鍵段落（panic header + 服務打卡清單）。為了隱私，已遮蔽 incident_id、crashReporterKey 與所有 UUID。後面上萬行的 thread dump 與本次原因無關，已省略。

Below is the key section of the panic (panic header + service check-in list). For privacy, incident_id, crashReporterKey and every UUID have been redacted. The tens of thousands of lines of thread dump that follow are unrelated to the cause and have been omitted.

{"bug_type":"210","timestamp":"2026-06-23 16:27:39.00 +0800","os_version":"iPhone OS 26.5 (23F77)","incident_id":"████████-████-████-████-████████████"}
{
  "crashReporterKey" : "████████████████████████████████████████",
  "product" : "iPhone15,5",
  "kernel" : "Darwin Kernel Version 25.5.0: ... RELEASE_ARM64_T8120",
  "panicString" : "panic(cpu 0 caller 0x...): userspace watchdog timeout: no successful checkins from SpringBoard (1 induced crashes) in 180 seconds
service: backboardd,       last successful checkin: 0 seconds ago
service: SpringBoard (1 induced crashes), last successful checkin: 180 seconds ago
service: audiomxd,         last successful checkin: 0 seconds ago
service: logd,             last successful checkin: 0 seconds ago
service: thermalmonitord,  last successful checkin: 0 seconds ago
service: runningboardd,    last successful checkin: 0 seconds ago
service: wifid,            last successful checkin: 0 seconds ago
service: configd,          last successful checkin: 0 seconds ago
service: CommCenter,       last successful checkin: 0 seconds ago
...
",
  "socId" : "8120",
  "build" : "iPhone OS 26.5 (23F77)",
  "bug_type" : "210"
  ... (processByPid 完整 thread dump 共上萬行，與本次原因無關，此處省略 / full thread dump omitted) ...
}