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

Most of the time I reboot my MBP 15-inch Mid 2014 with macOS Catalina 10.15.3 I get this... I tried PRAM and SCM reset but it comes back.


panic(cpu 2 caller 0xffffff7f88f3aaae): watchdog timeout: no checkins from watchdogd in 185 seconds (719 totalcheckins since monitoring last enabled), shutdown in progress

Backtrace (CPU 2), Frame : Return Address

0xffffff81e6debc40 : 0xffffff8007b3bb2b

0xffffff81e6debc90 : 0xffffff8007c734d5

0xffffff81e6debcd0 : 0xffffff8007c64f4e

0xffffff81e6debd20 : 0xffffff8007ae2a40

0xffffff81e6debd40 : 0xffffff8007b3b217

0xffffff81e6debe40 : 0xffffff8007b3b5fb

0xffffff81e6debe90 : 0xffffff80082d2b25

0xffffff81e6debf00 : 0xffffff7f88f3aaae

0xffffff81e6debf10 : 0xffffff7f88f3a472

0xffffff81e6debf50 : 0xffffff7f88f4fe76

0xffffff81e6debfa0 : 0xffffff8007ae213e

Kernel Extensions in backtrace:

com.apple.driver.watchdog(1.0)[053A5D15-51D4-3E61-978B-EB435FA4BD0A]@0xffffff7f88f39000->0xffffff7f88f41fff

com.apple.driver.AppleSMC(3.1.9)[8D698096-1F90-3679-8151-22A7665ED287]@0xffffff7f88f42000->0xffffff7f88f60fff

dependency: com.apple.iokit.IOACPIFamily(1.4)[3D78401B-5D2D-33BC-9E41-DD2164EA874D]@0xffffff7f88f30000

dependency: com.apple.driver.watchdog(1)[053A5D15-51D4-3E61-978B-EB435FA4BD0A]@0xffffff7f88f39000

dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f88651000


BSD process name corresponding to current thread: kernel_task


Mac OS version:

19D76


Kernel version:

Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64

Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE

Kernel slide: 0x0000000007800000

Kernel text base: 0xffffff8007a00000

__HIB text base: 0xffffff8007900000

System model name: MacBookPro11,2 (Mac-3CBD00234E554E41)

System shutdown begun: YES

Panic diags file available: YES (0x0)

Posted on Apr 1, 2020 2:34 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 31, 2020 10:39 AM

As a follow up, this was fixed for me with the August 12 10.15.6 supplemental update, as mentioned here https://www.macrumors.com/2020/08/12/apple-releases-macos-10-16-5-supplemental-update/. Note that this update is different from just '10.15.6'... it seems Apple doesn't like to increment minor numbers and is still calling this 10.15.6 supplement update.

Similar questions

96 replies

May 13, 2020 2:14 PM in response to iDeMi

It is a good way of installing incremental updates for any Mac that may have had a corrupt update process. It cannot do any harm and it may do good along with an occasional Safe Boot and resetting SMC and NVRAM

If the problem is incompatible apps or hardware it will probably not help.


Also remove all antivirus and cleaner apps.


If it was me I would revert to Mojave from the last TM backup in Mojave

Jun 26, 2020 1:03 PM in response to rosbif78

rosbif78 wrote:
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?

At this point in time I'm just trying to see if I can collect information that will point to a common cause.


But so far I have user environments all over the map, and nothing seems to be common.

I have system with no external devices, and no 3rd party kernel extensions. Those are the most baffling.


So I'm wondering if WatchDog timeout is a side effect of some other kernel change where the right kind of system load, causes the code responsible to telling the WatchDog timer to reset is not getting around to do the reset in a timely manor.


But it does not seem to be any specific identifiable subsystem. At first I was thinking USB bus, but when I started asking around, I found users with no external devices. Just the power cord.


However, a different use that ONLY have the watchdog timeout when using a specific USB device.


I wondered about IPv6, and I've asked some users if they would change System Preferences -> Network -> Select network interface in the left column -> Advanced -> Configure IPv6 -> "Link-local only" (that is change it away from "Automatic", and see if that helps. The theory being that everyone has a different home router, with different levels of firmware patching, and it is possible that the Catalina IPv6 stack does not like the response from a specific IPv6 implementation it has found on a home router.


And then there is the theory that 3rd party Bluetooth devices having a variety of different Bluetooth chips, with different qualities of Bluetooth implementations, which is yet another networking standard, and if I'm going to wonder about IPv6, it is only fair to wonder about Bluetooth (or at least non-Apple devices, as I'm sure Apple has been using Apple Bluetooth devices all over the place in-house).


But at the moment I have theories (LOUSY Theories), but nothing I can hang my hat on.


I'm as frustrated as the uses getting the watchdog timeouts.

Jul 28, 2020 2:48 AM in response to BobHarris

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.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.