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
Question marked as Top-ranking reply

Aug 31, 2020 10:39 AM in response to wilko1702

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.

Sep 21, 2020 12:23 AM in response to isa56k

I spent a long time with Apple support looking at dumps from the panics on my machine - they found nothing useful.


However, their advice worked. I installed a completely new system on an external drive, and recreated the users - not copying them from previous backups. I've only copied over applications as I've needed them specifically.


I've now not had any panics for over two months. They were occurring twice a day. So, I don't know what third party was causing the problem, but that was what was the ætiology.



Sep 21, 2020 2:28 PM in response to instanton

instanton wrote:

On my Mac Pro, it was being caused by the McAfee kext mandated by my employer. Started in safe mode, rock solid for three weeks. Started with McAfee, crash within a few hours. Has been up continuously since I was allowed to get rid of McAFee going on three weeks now with pretty close to 100% CPU utilization during that time. Just FYI.

If you have McAfee 10.6.6, you can put it into kext-less mode, which has helped at my employer (same mandate for company Macs)

https://docs.mcafee.com/bundle/endpoint-security-10.6.0-installation-guide-macOS/page/GUID-74D9510B-A542-4811-AF36-78EA5949128A.html

Jun 20, 2020 4:47 AM in response to George Colpitts

Well, it really shouldn’t have worked, because a normal update should work. However, I have done this, and I have now not had a panic for some weeks, when they were happening every day:


Go to https://support.apple.com/downloads/macos and look for 10.15.4 COMBO update.


so, before you take your machine to be repaired, try the update with the COMBO, and it really might work.


This must mean that there’s a subtle error in the standard update process.


let’s hope Apple is reading this and fixes it.

Aug 3, 2020 6:34 AM in response to isa56k

Thanks to @dragontorc, he clued me in that "there are numerous reports from many users for kernel panics caused by a memory leak associated with a bug on the App Sandbox. VMWare and VirtualBox had already identified the issue."

and

"Apparently Apple is aware of the bug and I suppose a supplemental update containing a fix is currently in the works."


In my case I use VMWare Fusion...


https://discussions.apple.com/thread/251618187?answerId=253158745022#253158745022


Oct 4, 2020 8:02 AM in response to sheimbecher

I had lots of these kernel panic error in my iMac 21.5 inch 2017 running Catalina 10.15.7. So. So, I started a very long process: disconnect every peripheral; low level format of the internal disk; fresh OS (+update) and relevant apps installation from network; restore of only documents and data form TimeMachine backup; peripherals connected; all, with frequent shutdowns to check for the problem arising again. It didn´t show up.

Then, I got an error and decided to format the TimeMachine disk just in case. After a fresh full backup, the error showed up again; this time I noticed that the TimeMachine disk was "growling" a lot after the shutdown command and I got the restart and the kernel panic error.

My easy fix: I just eject the TimeMachine disk before shutdown, and everything goes well. I also have an external monitor that doen´t seem to matter to my process.

Hope it helps someone until Apple finds a way out.


Dec 5, 2020 2:29 PM in response to kbache7674

I posted in this thread earlier. My problem with this crash turned out to be hardware. It resolved after replacement of the logic board and solid state drive. The problem started while I was working in Lightroom CC Classic with a spinning beachball that I couldn't clear without a restart.


I don't know what LR could have done to break hardware and I would guess this is just coincidence.


But it's an odd coincidence...

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.