Kernel panic userspace watchdog timeout

Lindsay, with 40 pages of this issue reported here - https://forums.macrumors.com/threads/constant-kernel-panics-userspace-watchdog-timeout-no-successful-checkins-from-com-apple-windowserver.2222878/page-40 - surely Apple should take note and fix this issue? Contact Apple one gets nowhere and left to fend for themselves with constant crashes, freezes and restarts. All of which have happened for me personally since updating to 11.2 (and same with 11.2.1) on my MacBook Pro 16". No issues with Catalina and repeat no issues with 11.1 prior to updating. All apps are up to date, SMC and PRAM reset performed and yet... crash, unable to work and my calls with senior tech persons via Apple Care have led to response as pay for business support to get better help!

SO, what are you/Apple going to do to fix this issue for not only me but thousands of your customers with issue and those having spent as me over £4k on a MacBook Pro that does not work!?

Thanks!

panic(cpu 1 caller 0xffffff80129f9a25): userspace watchdog timeout: no successful checkins from com.apple.logd in 120 seconds

service returned not alive with context : unresponsive dispatch queue(s): com.apple.firehose.io-wl

service: com.apple.logd, total successful checkins since load (17990 seconds ago): 1788, last successful checkin: 120 seconds ago

service: com.apple.WindowServer, total successful checkins since load (17960 seconds ago): 1796, last successful checkin: 0 seconds ago

Same here: 4 times a day, now. Apple nop longer cares about software quality, just profits-

Thank you, you speak from my heart!

These unspeakable tips for a serious error in the operating software, which thousands of customers have already reported about it, is simply outrageous.

I'm curious whether Apple will remove this comment again, because criticism does not go down well with the most expensive company in the world.

The error has been known for 1 year, it has not been fixed.

Unfortunately, one wonders whether Apple will also become like Microsoft.

Because Kerne Panic is actually something that Apple users have seen very, very rarely.

Lately normality.

No wonder if there are programmers who do not forget to ask about the available hard disk space when updating a major release.

Unbeatable when it comes to embarrassment.

The internet is full of the problem, but thank god there are new emojis on the iPhone.

Hi, algowythm,

Welcome to the Apple Support Communities. We understand that your MacBook Air has been unexpectedly becoming unresponsive before restarting itself. We are happy to help!

Based on what you've described, we recommend using the information in the Apple Support articles If your Mac restarts and a message appears - Apple Support and If your Mac restarted because of a problem - Apple Support to troubleshoot your issue.

Should you still experience the computer becoming unresponsive and/or restarting unexpectedly, please get in touch with Apple Support directly: Get Support.

Have a lovely day.

Since I bought the iMAC (Retine 5K, 27Inch, 2020) I have crashes multiple times a day.

Always when I'm off the computer for 5 minutes I have a fresh restarted mac that tells me if I want to report the crash.

And I keep on reporting this issue for 7 months now and hoping, in vain, that eventually an update will resolve this.

I tried an experiment over the weekend to see if it was a specific app I leave open when the computer goes to sleep that is causing the crashes, so I quit out of everything. I also went into Energy Saver in system preferences and changed the computer to never sleep. I took a screenshot of all my energy saver settings for reference. The screensavers for my computer and monitors were on all weekend and one click got the computer instantly on and there wasn't one crash. I don't know if it was these two things or a combination of that and other things, but it hasn't crashed since last week after trying this out. It's still not a long term fix, but a relatively easy work around solution. I will come back with any updates. Hope this helps others who are as frustrated as me!

My M1 Mac Mini is crashing constantly because of this error.

panic(cpu 1 caller 0xfffffe0018939e58): watchdog timeout: no checkins from watchdogd in 92 seconds (8839 total checkins since monitoring last enabled)

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 20D91

Kernel version: Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101

Fileset Kernelcache UUID: F78A48EC84D7C3283E7C6C67D00889A7

Kernel UUID: 9FE8C0DA-8ED0-381C-9CEC-2A779F3E1503

iBoot version: iBoot-6723.81.1

secure boot?: YES

Paniclog version: 13

KernelCache slide: 0x000000000dec8000

KernelCache base: 0xfffffe0014ecc000

Kernel slide: 0x000000000e9fc000

Kernel text base: 0xfffffe0015a00000

Kernel text exec base: 0xfffffe0015ac8000

mach_absolute_time: 0x1ee7f7c548c

Epoch Time: sec usec

Boot : 0x608888d7 0x00034b78

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x6089e27d 0x000587ff

CORE 0 recently retired instr at 0xfffffe0015c32c0c

CORE 1 recently retired instr at 0xfffffe0015c31748

CORE 2 recently retired instr at 0xfffffe0015c32c0c

CORE 3 recently retired instr at 0xfffffe0015c32c0c

CORE 4 recently retired instr at 0xfffffe0015c32c10

CORE 5 recently retired instr at 0xfffffe0015c32c10

CORE 6 recently retired instr at 0xfffffe0015c32c10

CORE 7 recently retired instr at 0xfffffe0015c32c10

Total cpu_usage: 63955664

Thread task pri cpu_usage

0xfffffe166d25dfb8 kernel_task 0 4322000

0xfffffe166d3f7918 kernel_task 0 4871507

0xfffffe166d3f0658 kernel_task 0 4562788

0xfffffe166d4fc658 kernel_task 0 4656977

0xfffffe166d3f32c0 kernel_task 0 4721256

Panicked task 0xfffffe166d245f18: 261971 pages, 526 threads: pid 0: kernel_task

Panicked thread: 0xfffffe166d3f7918, backtrace: 0xfffffe304af0f8b0, tid: 433

lr: 0xfffffe0015b15fd0 fp: 0xfffffe304af0f920

lr: 0xfffffe0015b15d9c fp: 0xfffffe304af0f990

lr: 0xfffffe0015c37f0c fp: 0xfffffe304af0f9b0

lr: 0xfffffe0015c298b8 fp: 0xfffffe304af0fa60

lr: 0xfffffe0015acf7e8 fp: 0xfffffe304af0fa70

lr: 0xfffffe0015b15a2c fp: 0xfffffe304af0fe00

lr: 0xfffffe0015b15a2c fp: 0xfffffe304af0fe70

lr: 0xfffffe00162b06a0 fp: 0xfffffe304af0fe90

lr: 0xfffffe0018939e58 fp: 0xfffffe304af0fec0

lr: 0xfffffe0018939634 fp: 0xfffffe304af0ff00

lr: 0xfffffe0016e9d5d0 fp: 0xfffffe304af0ff20

lr: 0xfffffe0016c22808 fp: 0xfffffe304af0ffb0

lr: 0xfffffe001620d694 fp: 0xfffffe304af0ffc0

lr: 0xfffffe0015c2c1bc fp: 0xfffffe304af0ffe0

lr: 0xfffffe0015acf85c fp: 0xfffffe304af0fff0

lr: 0xfffffe0015b3ddac fp: 0xfffffe404cad3ee0

lr: 0xfffffe0015b3dfb8 fp: 0xfffffe404cad3f00

lr: 0xfffffe0015ad8c14 fp: 0x0000000000000000

** Stackshot Succeeded ** Bytes Traced 397167 (Uncompressed 1076944) **

Same iMac as me and same scenario. Been doing it for months under Catalina so I finally upgraded to Big Sur and nothing's changed. It's crazy to me that there is no solution for this after a year + of people posting about it. I'm trying to talk to a friend who might understand what these reports mean. It's another language to me. I will happily post back anything I find out from my IT department and friends at Apple!

I have a current fix for my setup, but mine was caused by thunderbolt connection to external monitors... So if you have an iMac Pro with 2 AOC 4K monitors plugged in via thunderbolt... Consistent Panic Watchdog Reboot shenanigans everyone else gets... My fix... With extended monitor plugged in... System Preferences... Display... Take your mouse to the display's preference box and click color... Go to bottom and select uncheck here to see blah blah blah... There will then be a huge list of all these devices... Scroll down till you see iMac or whatever your device is and select... Do this to EVERY account on the computer... Not a global setting... And wait and see if that helps... Cross those fingers...

I had the same problem on my MacBook Pro. Also, the Touch Bar was flickering horribly. Three weeks ago, the battery failed. I had the touch bar, keyboard and battery replaced (apparently they are all part of the same component). This seems to be a fairly common problem with MacBook Pro's since I received a no-questions-asked discount from the authorized repair store. After the computer came back from the store, voilá! no problems at all. So, in my case, it seems that flakey, failing hardware was at fault for the repeated kernel panic shutdowns.

11.2.2 update, still not fixed!

This has become and hourly experience for me. Trying to work out exactly what is causing it but it is happening under multiple different scenarios.

Log is below