Recently i upgraded to Big Sur and i leave the computer for some time and came back and see that the system was rebooted with kernel panic. any help would be appreciated to fix the issue.
Here is the log i get when the imac pro is started
panic(cpu 4 caller 0xffffff800e153a13): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
iMac Pro
AdGuard knows there is an issue but they claim they can't fix it from their side… yet the problem goes away when you uninstall their software:
https://github.com/AdguardTeam/AdguardForMac/issues/761
AdGuard was suspect because its extension was clearly mentioned in the backtrace:
Kernel Extensions in backtrace:
com.adguard.nfext(27.0)[4AF16C66-CBFC-369B-8F0A-6FB96F1D536E]@0xffffff7fb1185000->0xffffff7fb1188fff
NJ Ron wrote:
As you may have seen, same situation as you however it doesn't involve Parallels. I have Parallels but rarely use it.
The thing about kernel extensions like those installed by Parallels is you don't need to run it for them to affect system operation, they just need to be installed.
Unchecking the Enable Power Nap in Setting/EnergySaver it has been only a short term solution for me. After 5 days my MBP experienced another Kernel panic. As some mentioned earlier, I feel that Apple should take notice of the issue and realese a Big Sur update the soonest.
Unfortunately, this same issue was present for the entire life of Catalina. Many of us rolled back to Mojave to make it stop happening when Apple logic board swaps - basically new machines - and complete fresh OS installs didn't address it.
Is it time to start listing what software we use, as well as any peripherals like USB hubs or other third-party hardware?
It has been 8 days since I installed the 11.1 update, and I have had no kernel panics since then so far. With 11.01, I did not get them every day, though I once got two in a row. If I don't get one for another week or so, I'll consider this fixed, at least for me.
High fan speeds come with the way Intel CPUs and "Turbo Boost" are designed, where basically the CPU is overclocked on tasks until its heat generation is too high and the system has to throttle it.
If you could post a panic.log someone might be able to analyze it for you, but ultimately only Apple Support can work and ultimately solve the issue, so you should contact them directly.
I have not had any more kernel panics since I updated to 11.1. The two places that Apple support has told me that Apple's engineers look is in feedback and bug reporting. I used both. You give feedback at https://www.apple.com/feedback/ and you can log a bug at https://feedbackassistant.apple.com/. I logged this bug, https://feedbackassistant.apple.com/feedback/8919606. Others have said that they couldn't see it and comment in it. If so, you can log another bug. I don't know whether they read the crash reports. They should have at least noticed that those reports spiked after production Big Sur was first released a few weeks ago.
From the many reports I have seen, I suspect there is more than one cause for kernel panics. I think mine, which started with Big Sur 11.01 and stopped with the 11.1 update, may have been resolved. I had no kernel panics when I was in Catalina, but many people say they did. About all you can do is to give feedback to Apple with diagnostic files and as much detail as you can about what was going on when MacOS panicked. I used to be better at reading system log files in UNIX (it's almost 10 years since I retired) than I am now, but the answers should be in those log files.
The text above is an update as I received it from the Apple Support Desk team a few days ago.
I am very hasitant to take their explanation for a face value at the moment. The Support team and their engineers suggest that my Kernel Panic issue derives from external USB periphal like a display or a hard disc drive. It seems a rather reasonable explanation but for the record since I purchased the MBP on May 2020 I changed three different displays (the latest one -LG display 27UL850- was purchased a month ago), and I bought two brand new external hard disck drives.
If the issue derives from the operation system. as some users suggest, then this is beyond my remit.
Thank you for your post.
I am hoping that the fact you have been working with Apple for all this time means that their engineers are well aware that there are kernel panic issues out there for many, many owners and are working to resolve them.
The thing that concerns me is that it *seems* nobody has yet been able to nail it down to a specific issue.
I have been a good four days without a single kernel panic. I did two things: I removed ADGUARD which a CalDigit engineer found lurking in my kernel crash report.
I have also stopped disconnecting from my CalDigit dock while the lid on my Macbook Pro is closed. All connecting and disconnecting are done with the lid open. This was at the advice of the CalDigit engineer.
And you know what? No kernel panics for four days. That's HUGE. I was getting panics daily.
And one last thing. I re-installed Adguard this morning. I can't live without that software. So far, no kernel panics so I am keeping my fingers crossed that either I downloaded a newer refreshed version or the problem had everything to do with the way I was connecting/disconnecting from the CalDigit dock.
But getting back to my original statement...
The problem *seems* to be that everyone has a different situation. I am frustrated that Apple has not been able to fix these issues and I sure hope to **** they are AWARE and trying.
This shows logd went off into the weeds and hasn’t checked in with the kernel in two minutes.
Most frequently that’s due to an I/O error of some type, perhaps a failing disk or corrupted file system, or a USB dock that’s gone away.
I've been watching this thread closely, since I have been seeing the "com.apple.remoted" watchdog crashes daily since upgrading to Big Sur on my 2019 MacBook 16" (checkin with service: remoted returned not alive with context: unresponsive work processor(s): remoted heartbeat on bridge no successful checkins since wake (120 seconds ago), 60 seconds since last crashed by watchdog). This only occurred when I had an external monitor attached, it didn't matter if it was directly connected via HDMI, Displayport, through a dock, with either or both of my two Dell branded monitors. I tried all of the other voodoo mentioned in this thread and other forums, like removing any networking software that had kernel extensions, changing display color temperature, resetting SMC/NVRAM, disabling automatic graphics switching, etc.
With 12.2.1 the crashes were daily, sometimes hourly. I was hoping 11.2.2 would fix the issue, and after being up all day yesterday I thought the issue was finally fixed, but this morning I woke up my Mac and it did the same thing again.
The symptoms are always the same. It's working fine, and then suddenly the network stops responding. I then have 3 minutes to close all my applications gracefully and wait for the reboot while I quietly curse myself for upgrading to Big Sur.
Actually maybe turning off Wi-Fi has helped? It's been running all day without rebooting. It was powered off this morning, which makes me think it crashed after going to sleep, but during the day it's been fine. Going to try disabling sleep.
Where's the bad hardware, and why didn't it upset Mojave? Thanks.
There's no way to tell from the panic log. You have to take it to an Apple Store or Authorized Repair Center.
Mojave may not trigger the hardware with the problem.
Ash_Smith,
It is worth of mentioning that for the last (almost) 12 months and since my initial purchase of MacBook Pro (16-inch, 2019), the product has been experiencing, among others, Kernel Panics of the following nature:
The Mac Support team adviced to replace the MacBook Pro since it was falling within the first 30 days of warranty. The product was replaced twice but that it self did not resolve the Kernel issue.
I was also adviced to isolate the issue by doing manual back up in the light of a malicious software causing the Kernel issue - The mac was formatted and the data was tranfrerred mannually several times.
On a later correspondence with the support team, I was adviced to isolate all the external hardwares, on a one by one basis, that may be the source of the Kernel Panics.
Later, I was adviced that the external monitor shoud not have VGA type cables and buses but an up to date one like HDMI and/USB-C's. It is suffice to say that I replaced the extenal monitor with brand new one that connects with USB-C and HDMI (LG 27’’ UHD 4K Monitor). Of course, I replaced all the external hard disc drives within the last 3months and I keep updating the product with the last operating system update - currently is up to date with Big Sur 11.2.3 (the initial purchase was on Mojave).
After executing all those actions the product still experiences a Kernel Panics and particularly when an external drive has been connected and disconnected from the mac. Since May 2020 I have recorded approximately 40 Kernel Panics.
A couple of days ago, on the 13th of April 2021, I spoke with a senior Support team member after a thorough and documented email I had sent to the Support team the week before. I requested an explanation and the senior member confirmed that he would escalate the issue once again to the engineer's team and they will come back to me within the next five working days - so, I am on standby now.
My view is that as a users we should keep evidence and track of any issue with our mac product and provide the documentation to the support team. They are supposed to do their best and resolve the issue - this is what they are supposed to do.
If the issue comes from their own operating system/ software then they may have to take ownership of the issue and fix it - I trust.
Apple replaced my logic board and my machine has not crashed for 2 days
SafeBoot seems to have worked for me. (iMac 5k 2014) Kernel Panic appeared only while shutdown by purpose
Big Sur kernel panic
