Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Constant Kernel Panics – userspace watchdog timeout: no successful checkins from com.apple.WindowServer

I am having the same issue. I have reinstalled Catalina from scratch, reset PRAM/NVRAM etc and it I get the same crash fairly regularly.

I can reproduce fairly regularly by sharing my screen on a Slack call with multiple external monitors connected.

I think it is related to having more than one external display, as mine wakes from sleep just fine with a single one, but fails with more than one.

I do not see the crash at all with a single screen.

To boot my laptops backlight broke a couple weeks ago. This is making WFH fairly difficult for me. I called Apple support and they have no other options to fix my screen than mail repair (estimated at month) and waiting for the stores to open again.

I have the 2019 Macbook Pro 15 with the i9 32GB of ram and the Vega 20. So much for Apple having the best and most stable laptops. Also amazing support options during such a challenging time when people are relying on their hardware to keep some of the economy running.
 
Seems new Supplemental update is out with fixes to hanging USB-C port. I might try and start hooking up things again to see if it crashes still.

running 3 days without UltraFine nor Caldigit TS3+ I haven’t seen any crashes at all.
 
Got the supplemental update and had a kernel panic within an hour. Apple support wants me to reinstall the operating system.
 
10.15.4 was relatively stable for me. The supplemental was not. Upon installation I got:

Code: 
panic(cpu 2 caller 0xffffff7f961a0aae): watchdog timeout: no checkins from watchdogd in 308 seconds (118534 totalcheckins since monitoring last enabled), shutdown in progress
 
hifismith said:
Got the supplemental update and had a kernel panic within an hour. Apple support wants me to reinstall the operating system.
Click to expand...

Wow, this is disappointing...I'm getting panics 2-3x a day. Jeez.. I want to go back to 10.15.3 now. 0 issues there
 
StolenPhone said:
10.15.4 was relatively stable for me. The supplemental was not. Upon installation I got:

Code: 
panic(cpu 2 caller 0xffffff7f961a0aae): watchdog timeout: no checkins from watchdogd in 308 seconds (118534 totalcheckins since monitoring last enabled), shutdown in progress
Click to expand...

I see two kinds of panics in this thread. The ones that just happen once you are shut down your computer and it just doesn't cleanly tear everything down and then there are some that just happen while you are using the computer.

Is this assumption correct? Which one is yours?
 
cinaplenrek said:
I see two kinds of panics in this thread. The ones that just happen once you are shut down your computer and it just doesn't cleanly tear everything down and then there are some that just happen while you are using the computer.

Is this assumption correct? Which one is yours?
Click to expand...

To add in to this I have seen both. The most disruptive for me is the freeze while using the computer. I disconnect all but one external display before sleeping the laptop and it doesn't crash while sleeping or waking.
 
fel10 said:
Yeah, I think you guys were right. I exchanged the computer at Best Buy and the new one hasn't giving me any issues.
Click to expand...

Good! But be aware that a lot points to (this thread for example) there being a software issue with current releases of Catalina that can trigger Kernel Panics too. Hopefully 10.15.5 takes care of it. Haven't heard anyone with 10.15.5 beta say they have been able to reproduce yet, so that's good.
 
star-affinity said:
Good! But be aware that a lot points to (this thread for example) there being a software issue with current releases of Catalina that can trigger Kernel Panics too. Hopefully 10.15.5 takes care of it. Haven't heard anyone with 10.15.5 beta say they have been able to reproduce yet, so that's good.
Click to expand...

StolenPhone said the supplemental update was worse above.
 
Looks like I spoke too soon. My exchanged MBP just gave me one of this after waking up from sleep

Screen Shot 2020-04-10 at 8.06.15 PM.png
 
Does everyone experiencing the issue have external monitors connected? I'd be interested to see if there's anyone out there that strictly works off a MacBook with no peripherals and is not experiencing the issue.
 
  • Like
Reactions: monstermac77 and crouch
prdg.alex said:
Does everyone experiencing the issue have external monitors connected? I'd be interested to see if there's anyone out there that strictly works off a MacBook with no peripherals and is not experiencing the issue.
Click to expand...
That would be me. I don't have a single thing attached other than the power cord. Brand new base model i9 MBP 16", about three weeks old, on 10.15.4, getting constant kernel panics after waking the computer up from sleep. Resetting the PRAM, SMC, and reinstalling the operating system didn't help, nor has adjusting the settings in Energy Saver preferences (e.g. turning off Power Nap, automatic graphic switching, etc.)

No matter what I try, the kernel panics come crashing back.

EDIT: misread the last part of your sentence (you looking for someone with no peripherals AND no crashes) -- sorry.
 
Last edited:
  • Like
Reactions: monstermac77
prdg.alex said:
Does everyone experiencing the issue have external monitors connected? I'd be interested to see if there's anyone out there that strictly works off a MacBook with no peripherals and is not experiencing the issue.
Click to expand...

I have 2 2015 MacBook Pro which aren’t experiencing any crashes using 10.15.4. I have not installed the 10.15.4 supplemental update yet.
 
So i did some digging and I've noticed the underlying cause of the watchdog kicking in to cause kernel panic is due to the GPU locking up. macOS tries to restart it and sometimes it is successful, other times it is not and thats when the watchdog kicks in and reboots the machine.

If you get a kernel panic, can you open Console.app from spotlight search, then select system.log on the left. Search for DumpGPURestart. You should see lines like the following a couple of minutes before the kernel panic occurs:

Apr 11 11:56:59 lepton com.apple.xpc.launchd[1] (com.apple.DumpGPURestart): Service only ran for 9 seconds. Pushing respawn out by 1 seconds.
Apr 11 11:57:01 lepton com.apple.xpc.launchd[1] (com.apple.DumpGPURestart): Service only ran for 1 seconds. Pushing respawn out by 9 seconds.

DumpGPURestart drops a debug report in /Library/Logs/DiagnosticReports/ named as Kernel_[...].gpuRestart.

Theres tons of information in there, alot over my head. But at least its good to know Apple are logging these lockups and hopefully the reports contain enough diagnostic information for them to fix the underlying issues.
 
  • Like
Reactions: monstermac77 and star-affinity
I'm seeing the issue on 10.15.4 on a Mac Pro (late 2013) trash bin. I've seen it when it's coming out of sleep, when I'm just working and when it's idle while I'm on the potty. I'm trying the 'supplement' update now... Pandemic + mac freezing is just too much..Throw me a bone, Apple!
 
  • Like
Reactions: monstermac77
Also been having tons of kernel/CPU/GPU panic, and hibernate wake error etc since I moved from my old 2016 MBP 15 to 2019 MBP 16...
 
I applied the supplement update. I'm now at 10.15.4 (19E287). It's been 2 days without a freeze. Unfortunately, this is not an indicator of anything from my experience with these Mac Pro (late 2013) trash bins. I'll report back if I can get at least a month of uptime.
 
Same Crash here, 13" MBP mid-2012 with updated RAM. I'm having the same crash issues and here is the log for y'all to chew on. No External Monitor, external peripherals are a trackball and 10-key USB calculator.

panic(cpu 2 caller 0xffffff7f82ef9ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service returned not alive with context : is_alive_func returned unhealthy : WindowServer initialization not complete (post IOKitWaitQuiet)
service: com.apple.logd, total successful checkins since wake (2280 seconds ago): 229, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (2280 seconds ago): 191, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffff9202083720 : 0xffffff80023215cd
0xffffff9202083770 : 0xffffff800245a3c5
0xffffff92020837b0 : 0xffffff800244bf7e
0xffffff9202083800 : 0xffffff80022c7a40
0xffffff9202083820 : 0xffffff8002320c97
0xffffff9202083920 : 0xffffff8002321087
0xffffff9202083970 : 0xffffff8002ac2ce8
0xffffff92020839e0 : 0xffffff7f82ef9ad5
0xffffff92020839f0 : 0xffffff7f82ef97fa
0xffffff9202083a10 : 0xffffff8002a54f3e
0xffffff9202083a60 : 0xffffff7f82ef8cfe
0xffffff9202083b60 : 0xffffff8002a5e163
0xffffff9202083ca0 : 0xffffff8002409bb2
0xffffff9202083db0 : 0xffffff8002327328
0xffffff9202083e10 : 0xffffff80022fdcc5
0xffffff9202083e70 : 0xffffff8002314aa2
0xffffff9202083f00 : 0xffffff8002432605
0xffffff9202083fa0 : 0xffffff80022c8226
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[99A75EFF-7734-31A0-80BF-FF8288E30D9B]@0xffffff7f82ef8000->0xffffff7f82f00fff

BSD process name corresponding to current thread: watchdogd

Mac OS version:
19E287

Kernel version:
Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64
Kernel UUID: AB0AA7EE-3D03-3C21-91AD-5719D79D7AF6
Kernel slide: 0x0000000002000000
Kernel text base: 0xffffff8002200000
__HIB text base: 0xffffff8002100000
System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 44099712760185
last loaded kext at 334840938323: >AudioAUUC 1.70 (addr 0xffffff7f857f9000, size 28672)
last unloaded kext at 579262540541: >!AMuxControl 5.1.16 (addr 0xffffff7f848e8000, size 81920)
loaded kexts:
>AudioAUUC 1.70
>!AGraphicsDevicePolicy 5.1.16
@AGDCPluginDisplayMetrics 5.1.16
>!AHV 1
|IOUserEthernet 1.0.1
|IO!BSerialManager 7.0.4f6
>!AMikeyHIDDriver 131
>AGPM 111.4.4
>X86PlatformShim 1.0.0
>pmtelemetry 1
>!AUpstreamUserClient 3.6.8
>!AMikeyDriver 283.15
@Dont_Steal_Mac_OS_X 7.0.0
>!A!IHD4000Graphics 14.0.5
>!ABacklight 180.3
>!AHDA 283.15
>eficheck 1
>!AThunderboltIP 3.1.4
>AirPort.Brcm4360 1400.1.1
>!AMCCSControl 1.11
>!ASMCPDRC 1.0.0
>SMCMotionSensor 3.0.4d1
|!ABCM5701Ethernet 10.3.5
>!ASMCLMU 212
>!ALPC 3.1
>!AFWOHCI 5.6.2
>!A!ISlowAdaptiveClocking 4.0.0
>!A!IFramebufferCapri 14.0.5
@fileutil 20.036.15
@filesystems.autofs 3.0
>!AIR!C 360
>!UTCButtons 255
>!UTCKeyboard 255
>!AVirtIO 1.0
@filesystems.hfs.kext 522.100.5
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
|SCSITaskUserClient 422.101.1
@filesystems.apfs 1412.101.1
@private.KextAudit 1.0
>!ASDXC 1.7.7
>!AAHCIPort 341.0.2
>!AACPIButtons 6.1
>!ASmartBatteryManager 161.0.0
>!ARTC 2.0
>!AHPET 1.8
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
$!AImage4 1
@nke.applicationfirewall 303
$TMSafetyNet 8
@!ASystemPolicy 2.0.0
>!A!ICPUPowerManagement 222.0.0
|EndpointSecurity 1
|IOAVB!F 840.3
@plugin.IOgPTPPlugin 840.3
>!ASSE 1.0
>!ABacklightExpert 1.1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
|IOFireWireIP 2.3.0
@!AGPUWrangler 5.1.16
|IONDRVSupport 575.1
|IO80211!F 1200.12.2b1
|IOSkywalk!F 1
>corecapture 1.0.4
>!ASMBus!C 1.0.18d1
>!AHDA!C 283.15
|IOHDA!F 283.15
|IOEthernetAVB!C 1.1.0
>mDNSOffloadUserClient 1.0.1b8
>!ASMBusPCI 1.0.14d1
|IOFireWire!F 4.7.5
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
|IOSlowAdaptiveClocking!F 1.0.0
|IOAccelerator!F2 438.4.5
@!AGraphicsDeviceControl 5.1.16
|IOGraphics!F 575.1
>!AGraphicsControl 5.1.16
@kext.triggers 1.0
|Broadcom!BHost!CUSBTransport 7.0.4f6
|IO!BHost!CUSBTransport 7.0.4f6
|IO!BHost!CTransport 7.0.4f6
|IO!B!F 7.0.4f6
|IO!BPacketLogger 7.0.4f6
>!UMultitouch 264
>usb.IOUSBHostHIDDevice 1.2
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
|IOAudio!F 300.2
@vecLib.kext 1.2.0
|IOSerial!F 11
|IOSurface 269.11
@filesystems.hfs.encodings.kext 1
|IOSCSIMultimediaCommandsDevice 422.101.1
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
>!AThunderboltDPInAdapter 6.2.6
>!AThunderboltDPAdapter!F 6.2.6
>!AThunderboltPCIDownAdapter 2.5.4
|IOAHCISerialATAPI 268
|IOAHCIBlock!S 316.100.5
>!AThunderboltNHI 5.8.6
|IOThunderbolt!F 7.6.0
|IOAHCI!F 290.0.1
>usb.!UEHCIPCI 1.2
>usb.!UEHCI 1.2
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IOUSB!F 900.4.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
>DiskImages 493.0.0
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!AKeyStore 2
>!UTDM 489.101.1
|IOSCSIBlockCommandsDevice 422.101.1
>!ACredentialManager 1.0
>KernelRelayHost 1
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
|IOTimeSync!F 840.3
|IONetworking!F 3.4
|IOUSBMass!SDriver 157.101.3
|IOSCSIArchitectureModel!F 422.101.1
|IO!S!F 2.1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
|CoreAnalytics!F 1
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
|IOReport!F 47
>!AACPIPlatform 6.1
>!ASMC 3.1.9
>watchdog 1
|IOPCI!F 2.9
|IOACPI!F 1.4
@kec.pthread 1
@kec.Libm 1
@kec.corecrypto 1.0
 
  • Like
Reactions: MackyMcMac17
Hey, I have exactly the same issue.

It happens when the MBP wakes-up after sleep (some hours) using an external display.

I think it's software related, I made a NVRAM & SMC reset, reinstalled everything and it's the same. Some other users exchanged they MBP for a new one and the issue is showing after few days too.

I found a workaround for this, the idea is basically reduce the pressure on the NVRAM. I think due a firmware/GPU driver issue there is a memory leak.

The idea is under Energy Saver disable the Power Nap, that will reduce some pressure on the NVRAM.


Screen Shot 2020-04-13 at 16.42.38.png



This hide (the but is still there) the bug, but at least is a way to keep working up to they release the solution.
 
Andrés Natanael Soria said:
Hey, I have exactly the same issue.

It happens when the MBP wakes-up after sleep (some hours) using an external display.

I think it's software related, I made a NVRAM & SMC reset, reinstalled everything and it's the same. Some other users exchanged they MBP for a new one and the issue is showing after few days too.

I found a workaround for this, the idea is basically reduce the pressure on the NVRAM. I think due a firmware/GPU driver issue there is a memory leak.

The idea is under Energy Saver disable the Power Nap, that will reduce some pressure on the NVRAM.


Screen Shot 2020-04-13 at 16.42.38.png



This hide (the but is still there) the bug, but at least is a way to keep working up to they release the solution.
Click to expand...

Hi... So with your workaround, you don't see this issue anymore?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back