Userspace Watchdog Timeout 180 Sec Iphone Xs Max

Chosen Solution

Probably phone got a bit of water through the scratches in the screen, and i’ve got userspace watchdog timeout problem the log files is saying something like that {“bug_type”:“210”,“timestamp”:“2022-12-06 13:25:03.48 +0300”,“os_version”:“iPhone OS 13.3 (17C54)”,“incident_id”:“2CADE8A7-61C4-4F43-B8D4-BAA1BD14762F”} “build” : “iPhone OS 13.3 (17C54)”, “product” : “iPhone11,6”, “kernel” : “Darwin Kernel Version 19.2.0: Mon Nov 4 17:46:11 PST 2019; root:xnu-6153.60.66~39/RELEASE_ARM64_T8020”, “incident” : “2CADE8A7-61C4-4F43-B8D4-BAA1BD14762F”, “crashReporterKey” : “f3212b3e602ab2d373db1407d020ca8d52d6e226”, “date” : “2022-12-06 13:24:54.94 +0300”, “panicString” : “panic(cpu 3 caller 0xfffffff016b99bf8): userspace watchdog timeout: no successful checkins from com.apple.thermalmonitord since wake\nservice returned not alive with context : is_alive_func returned unhealthy : current ffc6ffffffffffff, mask 33ffffffffdff, expected 33ffffffffdff\nservice: com.apple.backboardd, total successful checkins since wake (180 seconds ago): 19, last successful checkin: 0 seconds was trying to connect another charging port but nothing changed :(

As was already mentioned, the panic you linked generally points to some thermal sensors that are failing to check in. But not always. If there are other panics, they may give us more data to go off of. Just like any other sort of mystery, or science experiment, more data is generally better. You can use paste bin to post the full panics and link them back here so we can get a look at them without it cluttering up the original post. Also, if you have not done a software update yet, or restore (via recovery mode is best since it will be less likely to restart in the middle) I would give that a go. You mention in your question that there may have been water that got in through scratches in the screen. Scratches? Or actual cracks? I will also mention that despite the water resistant rating of the phone, this resistance degrades over time so even if the screen was intact, it’s possible liquid got into the phone. If there is a chance that was the case, first thing I would do is look for any signs of liquids inside. Finding out where or if there was any liquid damage is going to give you the best clues. Also, when you’re testing, are you fully reassembling the phone? Connecting just certain components? The XS Max needs both a good power button cable and a good charge port assembly to avoid this problem.

@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.

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?

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?

I got this problem from 4days ago and my phone keeps restarting , pleaase some insight about the problem