My log:
{"bug_type":"210","timestamp":"2022-01-20 19:00:59.00 +0700","os_version":"iPhone OS 15.2.1 (19C63)","incident_id":"3AB7979E-9CC4-44FF-A37B-10C4C3382C5A"} { "build" : "iPhone OS 15.2.1 (19C63)", "product" : "iPhone14,3", "kernel" : "Darwin Kernel Version 21.2.0: Sun Nov 28 20:43:39 PST 2021; root:xnu-8019.62.2~1/RELEASE_ARM64_T8110", "incident" : "3AB7979E-9CC4-44FF-A37B-10C4C3382C5A", "crashReporterKey" : "5FB1098457e4e82a638cdf4335f0309c4323ce88", "date" : "2022-01-20 19:00:59.82 +0700", "panicString" : "panic(cpu 2 caller 0xfffffff02ba9d6ac): mbuf_watchdog: 1 waiters stuck for 11 secs\n3418/3424 mbufs in use:\n\t3418 mbufs allocated to data\n\t6 mbufs allocated to caches\n760/760 mbuf 2KB clusters in use\n591/592 mbuf 4KB clusters in use\n2048/2048 mbuf 16KB clusters in use
What I want to ask is, what is the condition that can trigger system rebooting?
iOS should not kernel panic. My advice:
-
This is Apple Developer Forums. If you’re not developing an app, you’re in the wrong place. You can discuss this issue in Apple Support Communities or contact Apple Support directly.
-
If you are developing an app, is this kernel panic related to your app? If not, follow the advice from my previous point.
-
If you’re developing an app and something in your app triggers a kernel panic, file a bug about that. Make sure to include a sysdiagnose log taken immediately after you reboot from the panic. And if you can attach a small test project that reproduces the problem, that’d be great!
Oh, and if you want to discuss your panic here, start a new thread and tag it with Kernel and any other tags relevant to the APIs you’re using. Make sure to include the number of the bug that you filed.
And on that note, I’m going to lock this thread because I don’t want it to become a monster thread that covers ever kernel panic ever (-:
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"