Since installing Catalina yesterday, multiple crashes from userspace watchdog timeout

Since I installed Catalina yesterday, I have had around five crashes with the error:


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


Any solutions. iMac Pro had been operating fine before update. Only apps running at the time were Chrome and TimeMachine backing up to a Drobo 5N2 (plus of course background apps like Google Backup and Sync, Dropbox, etc).

iMac Pro

Posted on Oct 8, 2019 9:20 AM

Reply
Question marked as Top-ranking reply

Posted on Apr 14, 2020 1:23 AM

I solved! it was enough to start the PC and press cmd+R and keep it pressed until a screen appears to reinstall the operating system. I chose to reinstall it, and it was the correct choice, I have not lost any data, simply reinstalled the OS from the beginning. After 45 minutes the OS is back to 100% operational, it restarts and shuts down regularly, I don't tell you how happy I feel! try it too. i follow this instruction:

<< (Restart, while holding Command-R)

If you can, run Disk Utility, and try a Repair Disk.

If that completes with no problems found, Quit Disk Utility, which will return you to the recovery menu.

Then, you will likely want to Reinstall OS X. It will use your internet

connection to download the system, then will continue with the

reinstall. You won't lose your own files and apps, but the reinstall

will simply reinstall the system in place.

Assuming your boot drive is still good, that should fix your kernel panic issue. >>


Link: https://forums.macrumors.com/threads/panic-cpu-2-caller-error.1961380/




Similar questions

577 replies

Aug 11, 2020 8:03 AM in response to star-affinity

star-affinity,

FWIW, I have encountered the watchdog timeouts sitting/working in my car with NO attached peripherals of any kind (Macbook Pro 2019, Catalina 10.15.5/6).


I did initially think that this might be tied to something like that (external monitors, docking station, etc.), but it now seems (at least to me) to be certain applications (VMWare Fusion, Virtualbox, Docker, Microsoft Teams, etc.) that trigger memory leaks in the o/s , and those leaks, in turn, cause kernel panics and these watchdog timeouts (and other such fun).


My experience this past week (after downgrading to 10.15.5) is that 10.15.5 *does* appear to be somewhat more stable than 10.15.6. But I use the term "stable" very loosely here... :)

Aug 22, 2020 1:55 PM in response to Jazzlady S

I've been following this thread since early April but this is my first post as I haven't felt that I had anything helpful to offer. Frankly I still don't but I wanted to share my experience and the path forward (hopefully) that I am going to try. I've been a Mac user since 1986 (with a brief break during the bad years post OS 7 until OS X and the switch to Intel). I've worked in IT in various capacities over the years (mostly help desk and sysadmin stuff) and I regularly use Mac, Linux, and Windows but I much prefer to live in the Mac world when possible. That said, the Catalina disaster that has beset us all has made me question that.


My affected machine is a late 2012 iMac with all the original apple ingredients--I haven't modified anything. I don't have external monitors on it and I do not have VM software installed. While this machine is getting old, it's always been rock-solid since day one. I ran Mojave on it until the end of December 2019 and never had a problem and typically only restarted the computer every couple months or so. Then at the end of 2012, I decided to upgrade to the new OS since it had been out a while. Typically, upgrading the OS with Apple has always been a good improvement: more stability, more features, quicker responsiveness... I've always been amazed how a new OS on apple always seems to make an older machine feel better as opposed to how those upgrades usually go in the Windows world. Initially, the Catalina upgrade seemed to be just that.


After a few months passed (mid-March), I deleted my bootable backup of my Mojave machine because my computer had run flawlessly in Catalina the whole time. Then on March 28, 2020 Apple pushed an update that effectively killed my computer. After that upgrade I would have constant kernel panics always due to the watchdogd counter hitting 0 without a checkin from the windows server. Sometimes my computer would have 10-20 kernel panics between pressing the power button and reaching the log-in screen. If I left it on all day, it would typically reboot 30-50 times a day! There was no way to even use the machine. Again, this was not caused by non-apple memory (it's all factory installed), or external monitors (I have none), or virtualization software (I'm not using it). Nor is it caused by any defective hardware--I've tested everything and it all checks out. Also, I should add, if I boot the computer into Linux it is completely stable and works great. In fact, that how I used my computer from March 28 until late June due to personal time constraints that prohibited me form working on the machine. This problem, it seems to me, is caused solely by Apple's negligence in their code. Problem is, as we all know, identifying the source of the problem from our end seems to be impossible.


So, since June, I gave up on Apple ever issuing a fix--they don't even seem willing to admit they created a problem. I wiped my computer and did a clean install of Mojave. It is stable for the most part but not at all as it was pre-Catalina. It runs okay about 70% of the time but often becomes completely unresponsive for a while requiring me to wait or even walk away until it comes back to life. It never kernel panics though so the endless reboot loops are gone which is at least a small, though somewhat pyrrhic, victory. The fact that this instability has carried back to Mojave even though I did a clean install leads me to believe that they altered code in the EFI that has caused this problem. That also would explain why none of us can find an actual cause let alone solution.


Sorry this was so long. The length is reflective of my level of frustration with Apple. Remember when we all thought Vista was the worst OS upgrade ever? Vista is dead. Long live Catalina, destroyer of Macs!


[Edited by Moderator]

Oct 5, 2020 2:48 AM in response to ProfessorScott

For those with access to the Apple Feedback Assistant (Beta/Devs) are you submitting reports? I have been since back in May and am slightly concerned that the "Recent Similar Reports" has dropped from around 10 to "none". Maybe this is just a sign that they're not getting collated at Apples end?


I'm submitting with;


Description: System freezes and rebooted by watchdog due to WindowServer


Area: System Crashes/Unexpected Reboot


Type: Application Crash


How Long: It varies


Kind: Unexpected reboot (Restarted because of a problem)



This doesn't fit the problem exactly but was the best fit I could find in the options for the WindowServer issue;


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


Nov 26, 2020 3:12 AM in response to LD150

For me the problem didn't go away until Big Sur!

But I'm running a Mac Pro (Mid 2010) upgraded with RX 5700 XT graphics. This isn't supported to run Catalina nor Big Sur, (but it works with some tinkering…). Still, In Big Sur I haven't seen any of the Kernel Panics that I had in Catalina when waking from sleep, all the way from version 10.15.2 to 10.15.7.


So, this problem sure seem to have different causes; can seemingly be both hardware and software related.

”Watchdog timeout” kicking in seems like a symptom of the cause.


Sorry for all that still have problems. :(

Dec 25, 2020 12:27 AM in response to gnapier

I know what you mean, I am also running Ableton with a lot of plugins, Rme Ucx, Elektron ARmkII with Overbridge, 7 Behringer analog synths for which I started using midi just to rule out IO overloading, on top of that I am doing video editing and color grading in Davinci Resolve with Micro Panel and animation in AE and Cinema 4d. Also I have TB Dual Hdmi output to LG C9 and old Apple Cinema display... lots of things that could go wrong...


What first helped was disconnecting C9, but I needed that display for clients so I found out that if I dont use hidpi settings it would work for longer... I tried everything but it would just beachball and restart after a min... I just refused to think its a hardware problem, because all this shouldn't be a problem, I am running Macs for the last 15 years and I know this should be capable computers.


I noticed lots of time it crashed while editing clips in Resolve that had Neat Video OFX plugin so I removed it. Haven't crashed since then so thats something to think about.


My main problem now is with its P3 display and color management problems for color critical work. Its a huge mess...

Dec 27, 2020 5:30 AM in response to gnapier

Ok. Another update.


I replaced the problematic drive in the Thunderbay 8. I attached it back to the iMac. I also reattached my Drobo 5c so I could clone the content of the old drive on to the new one.


All of that proceeded without a hitch. So I decided to leave the set-up running to find out how long it would operate without a kernel panic.


Directly attached to the computer and operational is the Thunderbay 8 via TB3, a CalDigit TS3 Plus 15-Port TB3 Dock, a MOTU 1248 via TB2/TB3, an OWC TB3 dual HDMI mini Dock. There’s also a USB 3 hub and various USB devices (mostly synthesizers and modules) connected to the iMac. Essentially, the only thing NOT attached is the Sonnet Echo Express SE I.


So far this set up has remained up and operational with no reboots for over 12 hours.


I’ll leave the Sonnet box disconnected and see how long this lasts, but if it stays stable then my investment in UAD gear may be toast...


Oct 21, 2019 3:54 PM in response to Andrew Alderete

It may seem randomly, but most likely the error will point at whatever you were working on after a brief Mac idle (i.e. you left you computer to do some quick chores or, answer the door, etc.). Say if you were using Safari, it will surface in the crash report after the stall and reboot. Once my Mac crashed while I was using Activity Monitor, while checking for that unusual something… Another strange occurrence I had with my Mac is when it froze while I was accessing the USB-C to SD Card Reader for some 360 video files (nothing else extra was attached to the other USB-C ports, but the power cable). So, the mouse cursor turns into a spinning orb (you’ll get a total of 5 spin crashes, that’s 5 times the OS tried to recover), then the kernel panic pointing at the crash thread w/app name. Btw, I’ve checked the performance of USB-C to SD Card Reader and it’s ½ of what used to be. Before it was doing like 46-52 megabytes read/write per second, now is like 22-24 max megabytes/s.

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.

Since installing Catalina yesterday, multiple crashes from userspace watchdog timeout

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