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

[AndrésVP]

Hey fellows! I have a 16" MacBook Pro from October last year and I also have these kernel panics. I could observe that they only happen when the power plug is connected. I tried it hundreds of times with and without connected charger (also doesn't matter in which port), and it definitely only happens when the power cable is plugged in.

I had the following error when trying to wake up:

panic(cpu 2 caller 0xffffff7f8a1a1ad5): 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 load (1850 seconds ago): 186, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (1820 seconds ago): 170, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffff92307b3720 : 0xffffff800971f5cd
0xffffff92307b3770 : 0xffffff8009858b05
0xffffff92307b37b0 : 0xffffff800984a68e
0xffffff92307b3800 : 0xffffff80096c5a40
0xffffff92307b3820 : 0xffffff800971ec97
0xffffff92307b3920 : 0xffffff800971f087
0xffffff92307b3970 : 0xffffff8009ec2838
0xffffff92307b39e0 : 0xffffff7f8a1a1ad5
0xffffff92307b39f0 : 0xffffff7f8a1a17fa
0xffffff92307b3a10 : 0xffffff8009e54a8e
0xffffff92307b3a60 : 0xffffff7f8a1a0cfe
0xffffff92307b3b60 : 0xffffff8009e5dcb3
0xffffff92307b3ca0 : 0xffffff80098082b2
0xffffff92307b3db0 : 0xffffff8009725328
0xffffff92307b3e10 : 0xffffff80096fbcc5
0xffffff92307b3e70 : 0xffffff8009712aa2
0xffffff92307b3f00 : 0xffffff8009830d05
0xffffff92307b3fa0 : 0xffffff80096c6226
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[B435C72B-B311-3C67-8AA1-1D5CE0FAD429]@0xffffff7f8a1a0000->0xffffff7f8a1a8fff

and this one, trying to shut the Mac down after having the power cable plugged in and disconnected:

panic(cpu 0 caller 0xffffff8008cc3183): "PowerOff timed out in phase 'Notifying priority clients'. Total 30000 ms:
vfs_unmountall: 1195 ms
Blocked on priority client: 31394 ms @ 0x<ptr>, com.apple.iokit.IOStorageFamily(2.1)[E13E9C61-F1F5-3A81-B1EF-65669C3CBDBF]@0x<ptr>->0x<ptr>
"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.121.2/iokit/Kernel/IOPMrootDomain.cpp:5403
Backtrace (CPU 0), Frame : Return Address
0xffffff8207d03bc0 : 0xffffff800851f5cd
0xffffff8207d03c10 : 0xffffff8008658b05
0xffffff8207d03c50 : 0xffffff800864a68e
0xffffff8207d03ca0 : 0xffffff80084c5a40
0xffffff8207d03cc0 : 0xffffff800851ec97
0xffffff8207d03dc0 : 0xffffff800851f087
0xffffff8207d03e10 : 0xffffff8008cc27cc
0xffffff8207d03e80 : 0xffffff8008cc3183
0xffffff8207d03ea0 : 0xffffff8008c49f84
0xffffff8207d03ec0 : 0xffffff8008561565
0xffffff8207d03f40 : 0xffffff8008561091
0xffffff8207d03fa0 : 0xffffff80084c513e

BSD process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

I tried the 4k video loop thing, but no panic in sight. That worked totally fine.

My setup is the basic 6-core MacBook Pro 16" with external display (Dell U2515H) with original Apple AV-adapter and right now running on 10.15.5 (with supplemental update). I also use the USB Hub of the Dell Monitor.

So you say it wouldn't worth the effort to bring the Mac in to service, as this is an OS issue??

Cheers!
Andrés

 

[sclowbird]

Hey fellows! I have a 16" MacBook Pro from October last year and I also have these kernel panics. I could observe that they only happen when the power plug is connected. I tried it hundreds of times with and without connected charger (also doesn't matter in which port), and it definitely only happens when the power cable is plugged in.

I had the following error when trying to wake up:

panic(cpu 2 caller 0xffffff7f8a1a1ad5): 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 load (1850 seconds ago): 186, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (1820 seconds ago): 170, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffff92307b3720 : 0xffffff800971f5cd
0xffffff92307b3770 : 0xffffff8009858b05
0xffffff92307b37b0 : 0xffffff800984a68e
0xffffff92307b3800 : 0xffffff80096c5a40
0xffffff92307b3820 : 0xffffff800971ec97
0xffffff92307b3920 : 0xffffff800971f087
0xffffff92307b3970 : 0xffffff8009ec2838
0xffffff92307b39e0 : 0xffffff7f8a1a1ad5
0xffffff92307b39f0 : 0xffffff7f8a1a17fa
0xffffff92307b3a10 : 0xffffff8009e54a8e
0xffffff92307b3a60 : 0xffffff7f8a1a0cfe
0xffffff92307b3b60 : 0xffffff8009e5dcb3
0xffffff92307b3ca0 : 0xffffff80098082b2
0xffffff92307b3db0 : 0xffffff8009725328
0xffffff92307b3e10 : 0xffffff80096fbcc5
0xffffff92307b3e70 : 0xffffff8009712aa2
0xffffff92307b3f00 : 0xffffff8009830d05
0xffffff92307b3fa0 : 0xffffff80096c6226
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[B435C72B-B311-3C67-8AA1-1D5CE0FAD429]@0xffffff7f8a1a0000->0xffffff7f8a1a8fff

and this one, trying to shut the Mac down after having the power cable plugged in and disconnected:

panic(cpu 0 caller 0xffffff8008cc3183): "PowerOff timed out in phase 'Notifying priority clients'. Total 30000 ms:
vfs_unmountall: 1195 ms
Blocked on priority client: 31394 ms @ 0x<ptr>, com.apple.iokit.IOStorageFamily(2.1)[E13E9C61-F1F5-3A81-B1EF-65669C3CBDBF]@0x<ptr>->0x<ptr>
"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.121.2/iokit/Kernel/IOPMrootDomain.cpp:5403
Backtrace (CPU 0), Frame : Return Address
0xffffff8207d03bc0 : 0xffffff800851f5cd
0xffffff8207d03c10 : 0xffffff8008658b05
0xffffff8207d03c50 : 0xffffff800864a68e
0xffffff8207d03ca0 : 0xffffff80084c5a40
0xffffff8207d03cc0 : 0xffffff800851ec97
0xffffff8207d03dc0 : 0xffffff800851f087
0xffffff8207d03e10 : 0xffffff8008cc27cc
0xffffff8207d03e80 : 0xffffff8008cc3183
0xffffff8207d03ea0 : 0xffffff8008c49f84
0xffffff8207d03ec0 : 0xffffff8008561565
0xffffff8207d03f40 : 0xffffff8008561091
0xffffff8207d03fa0 : 0xffffff80084c513e

BSD process name corresponding to current thread: kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

I tried the 4k video loop thing, but no panic in sight. That worked totally fine.

My setup is the basic 6-core MacBook Pro 16" and right now running on 10.15.5 (with supplemental update)

So you say it wouldn't worth the effort to bring the Mac in to service, as this is an OS issue??

Cheers!
Andrés

Don't worry - it is no hardware issue. If you operate the MBP without external display just disable power nap. If you do with one external display - also disable power nap and use mirror mode. (Disable power nap on battery & power).

 

[aihkas]

Also hitting this issue, and it drives me nuts. Anybody found any workaround for this madness?

Not sure whether that's sustainable for you, but you can run 1080p.

 

[wgr73]

So 10.15.5 didn't fix this?

 

[Blue Joker]

So 10.15.5 didn't fix this?

I installed 10.15.5 a couple of days ago on an affected 2019 Mac Pro we have and we are still having the issue.

 

[moondarkx]

This problem have just started to happen to my mbp 15'' 2019. :/

The only change I made was installing 10.15.5 and deselecting automatic graphics switching.
Maybe it is related to that.

Any workarounds?

 

[xsnaruto]

Same issue here, I just bought a MacBook Pro 16'' from a friend's friend. Hopefully, these just a software issue.

I've tried turning off the "power nap" and disabling "auto graphics switching", and none of those solutions works. I found that each time the problem occurred, I was connected to the power supply and also connected through type-c to DP An external monitor. While I was outside, there was no power connected, no external monitor, and the MacBook did not reboot.

So, my temporary solution is to set "turn display off after" to NEVER at "Power Adapter".

Hope apple could solve this sooner because it really makes me can not working and learning well, and this is the computer I only have.

 

[pingchp]

Same issue here, I just bought a MacBook Pro 16'' from a friend's friend. Hopefully, these just a software issue.

I've tried turning off the "power nap" and disabling "auto graphics switching", and none of those solutions works. I found that each time the problem occurred, I was connected to the power supply and also connected through type-c to DP An external monitor. While I was outside, there was no power connected, no external monitor, and the MacBook did not reboot.

So, my temporary solution is to set "turn display off after" to NEVER at "Power Adapter".

Hope apple could solve this sooner because it really makes me can not working and learning well, and this is the computer I only have.

try install 'amphetamine' works for me. Set trigger only when power adapter is connected, so it won't bother when you're on battery.

 

[xsnaruto]

try install 'amphetamine' works for me. Set trigger only when power adapter is connected, so it won't bother when you're on battery.

Thank you for your suggestion, I tried this app and it works great to me.

A further question, have you check "Allow display sleep" function? I tried to check it, and the "reboot issue" happened as before. Seems that issue no need to wait for system sleep, but happening after display off.

 

[pingchp]

Thank you for your suggestion, I tried this app and it works great to me.

A further question, have you check "Allow display sleep" function? I tried to check it, and the "reboot issue" happened as before. Seems that issue no need to wait for system sleep, but happening after display off.

Same here, When display off the system crash. No need to wait for sleep. So I uncheck "Allow display sleep" to prevent the problem.
Even though 'Allow system sleep when display is closed' is checked but mac still can waking up smoothly. So weird.

 

[moondarkx]

I notice that my mac only have this problem on 10.15.5 when I'm running Google Drive File Stream. Do any of you use this service and are experiencing this problem as well?

 

[gregorskii]

Mine is still crashing. It crashes when it's awake with the same error:

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

When it's under load connected to external monitors or more directly when sharing my screen on Google Meet / Slack etc.

I just recently had the laptop serviced due to the backlight breaking. When they did that they also replaced the logic board and touchbar. So this is basically a brand new machine and still crashes.

I do not think this is hardware. It is not only related to sleeping (although I have seen that). Mine crashes when using the computer.

I have power nap disabled, automatic graphics switching on, display never sleeps when on power. No luck.

2019 15 inch MBP Vega 20, 32GB ram, i9, currently running 10.15.4 but 10.15.5 was on it before and did not fix.

Seems like a lot of people saying it works, then reporting it back is due to it being intermittent.

 

[smmehta]

Same here, When display off the system crash. No need to wait for sleep. So I uncheck "Allow display sleep" to prevent the problem.
Even though 'Allow system sleep when display is closed' is checked but mac still can waking up smoothly. So weird.

Thank you pingchp. But it did not help. I have the same exact setup and it crashed after 3 hours. and crashed again an hour after. Wish Apple addresses this issue as the machine is almost impossible to use with frequent KP. Called Apple support and the front line person was of no value. I do not have google drive as moondarkx reports.

 

[Blue Joker]

I've opened a ticket with Apple Engineering.

 

[gregorskii]

I've opened a ticket with Apple Engineering.

"Radars are typically responded to in NaN"

I hope that isn't true and appreciate you doing that.

Also Destiny.

 

[smmehta]

I've opened a ticket with Apple Engineering.

Thanks. Can that be viewed and tracked publicly? If so, please share.

 

[Blue Joker]

Thanks. Can that be viewed and tracked publicly? If so, please share.

I opened it via our Enterprise Support contract with Apple. I will post their findings when and if they have any.

 

[caiofct]

Just to report that I am also having this issue. Happened to me 2 times so far on a brand new 2019 16" Macbook pro running macOS 10.15.5 while connected to an external monitor and plugged in the power source.

I will be using the Amphetamine app, thanks pingchp for the suggestion on that, and waiting for Apple to actually fix this annoying bug.

 

[Blue Joker]

Just to report that I am also having this issue. Happened to me 2 times so far on a brand new 2019 16" Macbook pro running macOS 10.15.5 while connected to an external monitor and plugged in the power source.

I will be using the Amphetamine app, thanks pingchp for the suggestion on that, and waiting for Apple to actually fix this annoying bug.

I would say this is a misnomer. We are experiencing this same issue only we are using 2019 Mac Pros.

 

[smmehta]

Just to report that I am also having this issue. Happened to me 2 times so far on a brand new 2019 16" Macbook pro running macOS 10.15.5 while connected to an external monitor and plugged in the power source.

I will be using the Amphetamine app, thanks pingchp for the suggestion on that, and waiting for Apple to actually fix this annoying bug.

Welcome to the party. there are many of us experiencing issue. Also, the problem is no option to go back to 10.14.6 if the MBP came with 10.15 pre-installed. Not sure what is Apple's thinking...

 

[donikatz]

Glad I found this thread, same problem on MBP 13" 2019. Even more frequently since 10.15.5 supplemental update: was weekly, now daily. Power adapter, power nap disabled, hard disk sleep disabled, external display + mirror mode with lid open... yet it persists.

Feels like Windows 95.

 

[smmehta]

I opened it via our Enterprise Support contract with Apple. I will post their findings when and if they have any.

I spend an hour with L2 engineer yesterday and they collected the logs and passed it to the engineering. So let's see what I get back from them. I suspect some driver issue and not sure why Apple cannot nail it. Ofcouse they are not watching this forum. Each of us has to log a ticket. It's painful but worth it.

 

[Blue Joker]

I spend an hour with L2 engineer yesterday and they collected the logs and passed it to the engineering. So let's see what I get back from them. I suspect some driver issue and not sure why Apple cannot nail it. Ofcouse they are not watching this forum. Each of us has to log a ticket. It's painful but worth it.

L2 just got back to me and they said it's an issue with WindowServer. They cannot pin where the issue is coming from. I disabled Metal in Adobe Premier and changed it to OpenCL, so we will see how that goes. Just spitballing now until they get back to me.

 

[aihkas]

I spend an hour with L2 engineer yesterday and they collected the logs and passed it to the engineering. So let's see what I get back from them. I suspect some driver issue and not sure why Apple cannot nail it. Ofcouse they are not watching this forum. Each of us has to log a ticket. It's painful but worth it.

They're not watching but they have the responsibility to do some vigorous testing, this should have been even caught with an automated test, it should never make it into alpha or beta releases, we're not even talking about production and here we are!
Worst-case scenario, the number of reports should trigger their alarm system and open an automatic issue showing that there's something wrong with their latest release on their top of the line laptop!

The conclusion of all this that the macOS engineering team is either understaffed or having some serious issues and they don't care! I'm reading that they're about to release the arm based Macbook, maybe they're busy with something bigger, no excuses though!

 

[Blue Joker]

Is anyone having this issue using an HDMI Display? Apple Engineering is asking.