userspace watchdog timeout 180 sec

I dunno, guys; thermalmonitord is a 'daemon'; i.e., a task that runs in the background and, as the name implies, it's job is to keep an eye on the thermal sensors. However, in most cases where the direct communication with the sensor has failed, it will tell you which sensor it was that it can't talk to.

In this case, though, what I'm seeing is that trying to talk to the thermal monitor daemon failed; the call to ask it for information returned a status of "not alive" after it failed it's periodic check in. So in this case it's the software that checks the sensors that has failed, rather than one of the sensors it's supposed to be checking.

That is specifically a software problem, not a hardware one, so replacing hardware won't fix that problem except indirectly. The things is, we don't know why thermalmonitord crashed; it could be corrupted firmware, bad NAND memory, or some other hardware factor we don't know about.

So whenever you have something you know to be a software error such as this, the first thing to do is to do a restore or update of the operating system in order to replace any corrupted storage with a good copy. After that, you check the phone and see if it's working again; if not, then you have to start looking at hardware issues.

@flannelist Alisha, you're obviously experienced in iOS/Linux internals; what do you think?

@jakebravo Your Phone is saying it’s not getting any data back from thermalmonitord, which is a sensor on the charge port / flex assembly.

Did you try swapping to a replacement (3rd party) assembly? It was a little unclear in question. I know some of the 3rd party ones come without the sensors, which is why it can cause issues with replacement parts.

Guys please help,

{"bug_type":"210","timestamp":"2023-01-03 12:28:01.00 +0700","os_version":"iPhone OS 16.2 (20C65)","roots_installed":0,"incident_id":"7F3EBA60-B291-4701-8E9C-1507B21C37BF"}

{

"build" : "iPhone OS 16.2 (20C65)",

"product" : "iPhone11,8",

"socId" : "0x00008020",

"kernel" : "Darwin Kernel Version 22.2.0: Mon Nov 28 20:10:15 PST 2022; root:xnu-8792.62.2~1\/RELEASE_ARM64_T8020",

"incident" : "7F3EBA60-B291-4701-8E9C-1507B21C37BF",

"crashReporterKey" : "6af47c56c6da35c8301ff0a2d7ee9d8720802136",

"date" : "2023-01-03 12:28:01.88 +0700",

"panicString" : "panic(cpu 2 caller 0xfffffff0136abd38): userspace watchdog timeout: no successful checkins from logd in 180 seconds\nservice returned not alive with context : unresponsive dispatch queue(s): com.apple.firehose.io-wl \nlogd appears to not exist in launchd\nservice: backboardd, total successful checkins in 843 seconds: 82, last successful checkin: 0 seconds ago\nservice: SpringBoard, total successful checkins in 802 seconds: 65, last successful checkin: 150 seconds ago\nservice: mediaserverd, total successful checkins in 843 seconds: 65, last successful checkin: 160 seconds ago\nservice: logd, total successful checkins in 843 seconds: 64, last successful checkin: 180 seconds ago\nservice: thermalmonitord, total successful checkins in 843 seconds: 81, last successful checkin: 0 seconds ago\nservice: runningboardd, total successful checkins in 843 seconds: 76, last successful checkin: 0 seconds ago\nservice: wifid, total successful checkins in 843 seconds: 68, last successful checkin: 140 seconds ago\nservice: configd, total successful checkins in 843 seconds: 81, last successful checkin:\nDebugger message: panic\nMemory ID: 0xff\nOS release type: User\nOS version: 20C65\nKernel version: Darwin Kernel Version 22.2.0: Mon Nov 28 20:10:15 PST 2022; root:xnu-8792.62.2~1\/RELEASE_ARM64_T8020\nFileset Kernelcache UUID: 8631036BCCCF5DE9E3270CDB30F5633F\nKernel UUID: E162E369-A92E-3EB7-872F-862218FB860F\nBoot session UUID: 7F3EBA60-B291-4701-8E9C-1507B21C37BF\niBoot version: iBoot-8419.60.44\nsecure boot?: YES\nroots installed: 0\nPaniclog version: 14\nKernelCache slide: 0x000000000b0d8000\nKernelCache base: 0xfffffff0120dc000\nKernel slide: 0x000000000bcc0000\nKernel text base: 0xfffffff012cc4000\nKernel text exec slide: 0x000000000bd78000\nKernel text exec base: 0xfffffff012d7c000\nmach_absolute_time: 0x4b8046ecf\nEpoch Time: sec usec\n Boot : 0x63b3b90c 0x0002c5c5\n Sleep : 0x63b3ba1f 0x0002be32\n Wake : 0x63b3ba27 0x0006b16c\n Calendar: 0x63b3bcba 0x00081650\n\nZone info:\n Zone map: 0xffffffe0efcc0000 - 0xffffffe6efcc0000\n . VM : 0xffffffe0efcc0000 - 0xffffffe1d6324000\n . RO : 0xffffffe1d6324000 - 0xffffffe222ff0000\n . GEN0 : 0xffffffe222ff0000 - 0xffffffe309654000\n . GEN1 : 0xffffffe309654000 - 0xffffffe3efcb8000\n . GEN2 : 0xffffffe3efcb8000 - 0xffffffe4d6320000\n . GEN3 : 0xffffffe4d6320000 - 0xffffffe5bc988000\n . DATA : 0xffffffe5bc988000 - 0xffffffe6efcc0000\n Metadata: 0xffffffe00ebfc000 - 0xffffffe0103fc000\n Bitmaps : 0xffffffe0103fc000 - 0xffffffe0113f4000\n\nTPIDRx_ELy = {1: 0xffffffe4d6c26c08 0: 0x0000000000000002 0ro: 0x000000016ff770e0 }\nCORE 0: PC=0xfffffff012dfa9a8, LR=0xfffffff012dfa9a8, FP=0xffffffee79973f00\nCORE 1: PC=0xfffffff012dfa9a8, LR=0xfffffff012dfa9a8, FP=0xffffffee798b3f00\nCORE 2 is the one that panicked. Check the full backtrace for details.\nCORE 3: PC=0xfffffff012dfa9a8, LR=0xfffffff012dfa9a8, FP=0xffffffee796a3f00\nCORE 4: PC=0xfffffff012dfa9a8, LR=0xfffffff012dfa9a8, FP=0xffffffee796d3f00\nCORE 5: PC=0xfffffff012dfa9a8, LR=0xfffffff012dfa9a8, FP=0xffffffee79967f00\nCompressor Info: 42% of compressed pages limit (OK) and 16% of segments limit (OK) with 1 swapfiles and OK swap space\nTotal cpu_usage: 74102410\nThread task pri cpu_usage\n0xffffffe4d6c26c08 watchdogd 97 0\n0xffffffe4d66e9eb8 kernel_task 81 611313\n0xffffffe4d66c8418 kernel_task 0 5857151\n0xffffffe4d66c9810 kernel_task 0 5465907\n0xffffffe4d66c6978 kernel_task 0 3881542\n\nPanicked task 0xffffffe4d53fee78: 220 pages, 5 threads: pid 57: watchdogd\nPanicked thread: 0xffffffe4d6c26c08, backtrace: 0xffffffee7959f130, tid: 1502\n\t\t lr: 0xfffffff012dc6ba8 fp: 0xffffffee7959f170\n\t\t lr: 0xfffffff012dc697c fp: 0xffffffee7959f1e0\n\t\t lr: 0xfffffff012f0bdd4 fp: 0xffffffee7959f200\n\t\t lr: 0xfffffff012eff258 fp: 0xffffffee7959f270\n\t\t lr: 0xfffffff012efddf0 fp: 0xffffffee7959f300\n\t\t lr: 0xfffffff012d837b8 fp: 0xffffffee7959f310\n\t\t lr: 0xfffffff012dc6390 fp: 0xffffffee7959f6c0\n\t\t lr: 0xfffffff0134df108 fp: 0xffffffee7959f6e0\n\t\t lr: 0xfffffff0136abd38 fp: 0xffffffee7959f700\n\t\t lr: 0xfffffff0136ab5c0 fp: 0xffffffee7959f720\n\t\t lr: 0xfffffff0136aa474 fp: 0xffffffee7959f840\n\t\t lr: 0xfffffff013457cf0 fp: 0xffffffee7959f870\n\t\t lr: 0xfffffff013457fd8 fp: 0xffffffee7959fa00\n\t\t lr: 0xfffffff012ed0f6c fp: 0xffffffee7959fb20\n\t\t lr: 0xfffffff012dccc50 fp: 0xffffffee7959fbc0\n\t\t lr: 0xfffffff012d9fb68 fp: 0xffffffee7959fc20\n\t\t lr: 0xfffffff012db8874 fp: 0xffffffee7959fcc0\n\t\t lr: 0xfffffff012db8cec fp: 0xffffffee7959fdb0\n\t\t lr: 0xfffffff012ef484c fp: 0xffffffee7959fe80\n\t\t lr: 0xfffffff012efe08c fp: 0xffffffee7959ff10\n\t\t lr: 0xfffffff012d837b8 fp: 0xffffffee7959ff20\n Kernel Extensions in backtrace:\n com.apple.driver.AppleARMWatchdogTimer(1.0)[5133D809-B6E7-32DC-8177-6873F5C24635]@0xfffffff0136a7970->0xfffffff0136abd37\n dependency: com.apple.driver.AppleARMPlatform(1.0.2)[98A24B67-A443-3C7F-A0D6-F33C1BADF6D4]@0xfffffff01365a740->0xfffffff0136a796f\n\nlast started kext at 801246119: com.apple.plugin.IOgPTPPlugin\t1110.14 (addr 0xfffffff01267b180, size 111770)\nloaded kexts:

my iphone xr freeze and i have to force restart every 10-20 minutes, many says it’s the charging flex but can it be just software problem?

Please help me guyzzz

{"bug_type":"210","timestamp":"2024-06-15 22:27:48.00 +0530","os_version":"iPhone OS 15.8.2 (19H384)","incident_id":"C11A4D22-9E07-4862-814D-2330E590F639"}

{

"build" : "iPhone OS 15.8.2 (19H384)",

"product" : "iPhone9,4",

"socId" : "0x00008010",

"kernel" : "Darwin Kernel Version 21.6.0: Sun Oct 15 00:18:06 PDT 2023; root:xnu-8020.241.42~8\/RELEASE_ARM64_T8010",

"incident" : "C11A4D22-9E07-4862-814D-2330E590F639",

"crashReporterKey" : "a654e8b1c087337c9619a26b2cfdce52c7dd6e23",

"date" : "2024-06-15 22:27:48.46 +0530",

"panicString" : "panic(cpu 0 caller 0xfffffff01543bf58): userspace watchdog timeout: no successful checkins from logd in 180 seconds\nservice returned not alive with context : unresponsive dispatch queue(s): com.apple.firehose.io-wl \nservice: backboardd, total successful checkins since wake (410 seconds ago): 42, last successful checkin: 0 seconds ago\nservice: SpringBoard, total successful checkins since wake (410 seconds ago): 36, last successful checkin: 60 seconds ago\nservice: mediaserverd, total successful checkins since wake (410 seconds ago): 27, last successful checkin: 150 seconds ago\nservice: logd, total successful checkins since wake (410 seconds ago): 24, last successful checkin: 180 seconds ago\nservice: thermalmonitord, total successful checkins since wake (410 seconds ago): 42, last successful checkin: 0 seconds ago\nservice: runningboardd, total successful checkins since wake (410 seconds ago): 42, last successful checkin: 0 seconds ago\nservice: wifid, total successful checkins since wake (410 seconds ago): 36, last successful checkin: 60 seconds ago\n\nDebugger message: panic\nMemory ID: 0x1\nOS release type: User\nOS version: 19H384\nKernel version: Darwin Kernel Version 21.6.0: Sun Oct 15 00:18:06 PDT 2023; root:xnu-8020.241.42~8\/RELEASE_ARM64_T8010\nKernelCache UUID: CD36CE0B0356F65AFE5A8841F99CA9D2\nKernel UUID: D986A786-4953-350E-97CF-C0FCFF85FFCF\niBoot version: iBoot-7459.140.15\nsecure boot?: YES\nPaniclog version: 13\nKernel slide: 0x000000000e7d0000\nKernel text base: 0xfffffff0157d4000\nmach_absolute_time: 0x9f0f339ec\nEpoch Time: sec usec\n Boot : 0x666dbd8f 0x000d8cde\n Sleep : 0x666dc645 0x000dc51c\n Wake : 0x666dc64e 0x0003edbe\n Calendar: 0x666dc7e8 0x0007f92d\n\nZone info:\n Zone map: 0xffffffe00023c000 - 0xffffffe60023c000\n . VM : 0xffffffe00023c000 - 0xffffffe0e68a0000\n . RO : 0xffffffe0e68a0000 - 0xffffffe13356c000\n . GEN0 : 0xffffffe13356c000 - 0xffffffe219bd0000\n . GEN1 : 0xffffffe219bd0000 - 0xffffffe300234000\n . GEN2 : 0xffffffe300234000 - 0xffffffe3e689c000\n . GEN3 : 0xffffffe3e689c000 - 0xffffffe4ccf04000\n . DATA : 0xffffffe4ccf04000 - 0xffffffe60023c000\n Metadata: 0xffffffe6ea174000 - 0xffffffe6eb974000\n Bitmaps : 0xffffffe6eb974000 - 0xffffffe6eca70000\n\nCORE 0 is the one that panicked. Check the full backtrace for details.\nCORE 1: PC=0xfffffff015a413cc, LR=0xfffffff015a62c50, FP=0xffffffe6fac3a5d0\nCompressor Info: 20% of compressed pages limit (OK) and 9% of segments limit (OK) with 1 swapfiles and OK swap space\nTotal cpu_usage: 37484866\nThread task pri cpu_usage\n0xffffffe219094e10 watchdogd 97 0\n0xffffffe219066328 deleted_helper 46 1180175\n0xffffffe219062328 runningboardd 37 0\n0xffffffe218e10000 Zoom 31 3693\n0xffffffe218fd9c20 Zoom 31 2700\n\nPanicked task 0xffffffe21936a5b0: 205 pages, 4 threads: pid 57: watchdogd\nPanicked thread: 0xffffffe219094e10, backtrace: 0xffffffe6fb04b200, tid: 1452\n\t\t lr: 0xfffffff015995ea0 fp: 0xffffffe6fb04b240\n\t\t lr: 0xfffffff015995c28 fp: 0xffffffe6fb04b2b0\n\t\t lr: 0xfffffff015ab5324 fp: 0xffffffe6fb04b320\n\t\t lr: 0xfffffff015ab42c8 fp: 0xffffffe6fb04b3d0\n\t\t lr: 0xfffffff0159595fc fp: 0xffffffe6fb04b3e0\n\t\t lr: 0xfffffff015995944 fp: 0xffffffe6fb04b770\n\t\t lr: 0xfffffff015995944 fp: 0xffffffe6fb04b7d0\n\t\t lr: 0xfffffff015fd7000 fp: 0xffffffe6fb04b7f0\n\t\t lr: 0xfffffff01543bf58 fp: 0xffffffe6fb04b810\n\t\t lr: 0xfffffff01543b91c fp: 0xffffffe6fb04b830\n\t\t lr: 0xfffffff01543acac fp: 0xffffffe6fb04b950\n\t\t lr: 0xfffffff015f6d75c fp: 0xffffffe6fb04baf0\n\t\t lr: 0xfffffff015a82e40 fp: 0xffffffe6fb04bc10\n\t\t lr: 0xfffffff01599b528 fp: 0xffffffe6fb04bca0\n\t\t lr: 0xfffffff015974444 fp: 0xffffffe6fb04bd00\n\t\t lr: 0xfffffff015989cd8 fp: 0xffffffe6fb04bd90\n\t\t lr: 0xfffffff015aaa854 fp: 0xffffffe6fb04be60\n\t\t lr: 0xfffffff015ab4760 fp: 0xffffffe6fb04bf10\n\t\t lr: 0xfffffff0159595fc fp: 0xffffffe6fb04bf20\n\n",

"panicFlags" : "0x802",

"otherString" : "\n** Stackshot Succeeded Bytes Traced 205387 (Uncompressed 528336) \n",

In my opinion is a software issue because after these restarts started I replaced my battery and the charging flex, but this still happens. Please help. Will reset help?