Panic - Watchdog Timeout: no checkins from watchdogd in 185 seconds

Were you by any chance also running Time Machine backup?

Someone at work thinks Time Machine maybe a common trigger for some users. I'm just trying to gather any supporting evidence, or refute the claim so time is not wasted looking explicitly at Time Machine, but maybe on the conditions running Time Machine creates, and then see if there are other apps that create similar conditions.

Someone else found the panics went away after removing a USB dongle for wireless mouse, so it is also possible that Time Machine was talking to a USB disk, and it is the USB device that is the common item.

Anyway, I would be interested in what information you can pass along.

I too have been having frequent panics on my MacBook Pro 16" 2019 so I am currently downloading the COMBO 10.15.5 to see whether that solves the problem.

I have a permanently connected USB hard drive for regular Time Machine backups. I also use an external screen.

Are there any tests that I could perform to help you, either before or after installing the COMBO update?

panic(cpu 10 caller 0xffffff7f94cf9ad5): userspace watchdog timeout: no

successful checkins from com.apple.WindowServer in 120 seconds

service: com.apple.logd, total successful checkins since load (50251

seconds ago): 5026, last successful checkin: 0 seconds ago

service: com.apple.WindowServer, total successful checkins since load

(50220 seconds ago): 4997, last successful checkin: 120 seconds ago

That is good to know, thanks, but not really surprising as no third party security apps have any role to play on any Mac, particularly after Catalina brought in more security.

Deadly embraces between two security systems can cause kernel panics.

Same here - I am running a 2017 MacBook Pro with 2 27" Apple Thunderbolt monitors and am not using Time Machine for backup. I did recently apply the Catalina 10.15.6 update and now am seeing a Kernal Panic from a watchdog timeout causing the machine to freeze and die.

perhaps this is common but when I look at the backtrace the issue appears in the AppleSMC driver.

Kernel Extensions in backtrace:

com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8c6f9000->0xffffff7f8c701fff

com.apple.driver.AppleSMC(3.1.9)[AB612149-B321-3B95-8741-B99E79274FCD]@0xffffff7f8c741000->0xffffff7f8c75ffff

dependency: com.apple.iokit.IOACPIFamily(1.4)[68557A36-4EE1-372A-983B-BB2769FDB8E0]@0xffffff7f8c6f0000

dependency: com.apple.driver.watchdog(1)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8c6f9000

dependency: com.apple.iokit.IOPCIFamily(2.9)[B130A8B7-967F-330E-942F-E0BB93C71C56]@0xffffff7f8c702000

I am not going to reinstall the OS because that will take way to long and will be tedious, so I just went into the Energy saver config and disabled the monitor and disks from going to sleep to see if that is the cause.

I'll try to keep you posted.

Thanks.

Same here - I am running a 2017 MacBook Pro with 2 27" Apple Thunderbolt monitors and am not using Time Machine for backup. I did recently apply the Catalina 10.15.6 update and now am seeing a Kernal Panic from a watchdog timeout causing the machine to freeze and die.

perhaps this is common but when I look at the backtrace the issue appears in the AppleSMC driver.

Kernel Extensions in backtrace:

com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8c6f9000->0xffffff7f8c701fff

com.apple.driver.AppleSMC(3.1.9)[AB612149-B321-3B95-8741-B99E79274FCD]@0xffffff7f8c741000->0xffffff7f8c75ffff

dependency: com.apple.iokit.IOACPIFamily(1.4)[68557A36-4EE1-372A-983B-BB2769FDB8E0]@0xffffff7f8c6f0000

dependency: com.apple.driver.watchdog(1)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f8c6f9000

dependency: com.apple.iokit.IOPCIFamily(2.9)[B130A8B7-967F-330E-942F-E0BB93C71C56]@0xffffff7f8c702000

I am not going to reinstall the OS because that will take way to long and will be tedious, so I just went into the Energy saver config and disabled the monitor and disks from going to sleep to see if that is the cause.

I'll try to keep you posted.

My current power setting are:

System Power Settings:

 AC Power:

 System Sleep Timer (Minutes): 0

 Disk Sleep Timer (Minutes): 0

 Display Sleep Timer (Minutes): 180

 Wake on AC Change: No

 Wake on Clamshell Open: Yes

 Wake on LAN: Yes

 AutoPowerOff Delay: 28800

 AutoPowerOff Enabled: 1

 Current Power Source: Yes

 DarkWakeBackgroundTasks: 1

 Display Sleep Uses Dim: Yes

 GPUSwitch: 2

 Hibernate Mode: 3

 High Standby Delay: 86400

 PrioritizeNetworkReachabilityOverSleep: 0

 ProximityDarkWake: 1

 Standby Battery Threshold: 50

 Standby Delay: 10800

 Standby Enabled: 1

 TCPKeepAlivePref: 1

 Battery Power:

 System Sleep Timer (Minutes): 30

 Disk Sleep Timer (Minutes): 0

 Display Sleep Timer (Minutes): 20

 Wake on AC Change: No

 Wake on Clamshell Open: Yes

 AutoPowerOff Delay: 28800

 AutoPowerOff Enabled: 1

 DarkWakeBackgroundTasks: 0

 Display Sleep Uses Dim: Yes

 GPUSwitch: 2

 Hibernate Mode: 3

 High Standby Delay: 86400

 ProximityDarkWake: 0

 Reduce Brightness: Yes

 Standby Battery Threshold: 50

 Standby Delay: 10800

 Standby Enabled: 1

TCPKeepAlivePref: 1

No dice - thought it may be related.

Error:

panic(cpu 6 caller 0xffffff7f94efaad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds

service: com.apple.logd, total successful checkins since wake (25170 seconds ago): 2518, last successful checkin: 0 seconds ago

service: com.apple.WindowServer, total successful checkins since wake (25170 seconds ago): 2456, last successful checkin: 120 seconds ago

Kernel Extensions in backtrace:

com.apple.driver.watchdog(1.0)

I understand that everybody has different problems with the kernel panic situation. In my case it started to occur after I installed 10.15.6 and it only happened when I was away from my iMac 2017 for a while. Upon return, the iMac had restarted. I never had any resets or freezes happening "live".

For that reason, I have now tried to disable power nap and it looks like this has solved the problem for me. In addition, I already had disabled HDD sleep mode previously as otherwise Catalina would always dismount my external drives.

Continued running caffeinate again yesterday and NO crashes, however I did notice during past crashes that there was a sound stream error right before the issue would occur.

So yesterday, I did not use the Mac for any Mac based calls. Sound output is fine but thinking it may have to do with sound input, like using the Microphone.

I was using Gen 2 AirPods but switched to AirPods Pro’s yesterday.

I am going to try to reproduce today and see if I can pin down the cause of my issue.

macOS 10.15.6 introduced a bug in App Sandbox that literally kills virtualization software causing a memory leak followed by a watchdog timeout kernel panic once kexts are loaded into the system.

If you're using such apps like VMware Fusion and VirtualBox I strongly encourage you to avoid installation and wait for a supplemental update addressing the issue.

I’m having the same KP issue every other day or so since 10.15.6 on my Mac mini. No monitor, 2 USB hard drives connected, no 3rd party apps besides Backblaze, & isn’t actively used (it’s my file/time machine server)

Only thing I’ve tried is reinstalling the 10.15.6 combo update.

New Mac Pro connected only to Pro Display, updated to 10.15.6. Now it has these kernel panic shutdowns but the log shows nothing. However when I restart the shutdown cause log claims that it shutdown normally right after this same restart! There is McAfee running but this did not happen before 10.15.6.

Apple is working on a supplemental update containing a fix for the App Sandbox which caused a headache to many users because of a bug that killed virtualization apps.

Until the update arrives it's strongly recommended to stay away of virtualizers.

I have the same issue but it STARTED with 10.15.6.

2013 Mac Pro, kernel panic every night since 10.15.6. also happens during the day if the Mac Pro is idle long enough. I've reinstalled macOS from recovery, no luck.

Oddly, it also kills Messages, forcing me to log back in. Once it was unsuccessful, which is when I reinstalled macOS. That fixed Messages, but not the kernel panics.

anic(cpu 2 caller 0xffffff7f9ef67ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds

service: com.apple.logd, total successful checkins since load (17130 seconds ago): 1714, last successful checkin: 0 seconds ago

service: com.apple.WindowServer, total successful checkins since load (17100 seconds ago): 1698, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address

0xffffff820dce3720 : 0xffffff801dd1a65d

0xffffff820dce3770 : 0xffffff801de54a75

0xffffff820dce37b0 : 0xffffff801de465fe

0xffffff820dce3800 : 0xffffff801dcc0a40

0xffffff820dce3820 : 0xffffff801dd19d27

0xffffff820dce3920 : 0xffffff801dd1a117

0xffffff820dce3970 : 0xffffff801e4c1b28

0xffffff820dce39e0 : 0xffffff7f9ef67ad5

0xffffff820dce39f0 : 0xffffff7f9ef677fa

0xffffff820dce3a10 : 0xffffff801e4539ce

0xffffff820dce3a60 : 0xffffff7f9ef66cfe

0xffffff820dce3b60 : 0xffffff801e45cbf3

0xffffff820dce3ca0 : 0xffffff801de035e2

0xffffff820dce3db0 : 0xffffff801dd203c8

0xffffff820dce3e10 : 0xffffff801dcf6d15

0xffffff820dce3e70 : 0xffffff801dd0db22

0xffffff820dce3f00 : 0xffffff801de2c065

0xffffff820dce3fa0 : 0xffffff801dcc1226

Kernel Extensions in backtrace:

com.apple.driver.watchdog(1.0)[832CC890-EE61-33E0-8FD4-8D354BCD0921]@0xffffff7f9ef66000->0xffffff7f9ef6efff

BSD process name corresponding to current thread: watchdogd

Mac OS version:

19G73

Kernel version:

Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64

Kernel UUID: 783946EA-6F11-3647-BF90-787AEA14B954

Kernel slide: 0x000000001da00000

Kernel text base: 0xffffff801dc00000

__HIB text base: 0xffffff801db00000

System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)

System shutdown begun: NO

Panic diags file available: YES (0x0)

I too have been experiencing these CPU Panic's since the 10.15.6 update.

I have a MBP 2018, connected via USB C to a Dell Monitor, and a Graphics Accellerator.

Since the 10.15.6 update the USB-C behaviour has been very patchy and I often have to pull the cable to my monitor and re-attach it to get the MBP to wake up.

I can see the mouse moving on both screens but it does not allow me to log in, and I have to hard shutdown the MBP.

And for a week or more, overnight now, I get the same CPU panic that brought me to this thread.

panic(cpu 2 caller 0xffffff7f873baad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds

Any solutions to this ?

I have the same problem, but it is infrequent. I have an "always on" iMac running 10.15.6 (Retina 5K, 27-inch, 2019, 3.6 GHz 8-Core Intel Core i9).

It seems to shutdown sometime overnight when it is in a rather quiescent state.

This iMac spontaneously shuts down every ~48 hours.

I can't correlate this directly to upgrading to 10.15.6, but it is definitely running 10.15.6.

Prior to this episode, this iMac would run without shutting down or rebooting for ~20-40 days at a time.

So far, it has not shutdown while I was actively using it.