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

NJRonbo

macrumors 68040
Jan 10, 2007
3,233
1,224
I wanted to follow-up on my post with some important additional information that I hope someone will find helpful. For the past few days I have been pointing the finger at CalDigit for the kernel panic issues I have been having.

I have been in conversation with the company's CEO and I am very pleased at the level of assistance he has provided me. I was told that Caldigit support was backlogged from the holidays and that is most likely the reason why they went silent about this issue. However, the CEO has been in constant contact with me to examine the kernel pack issue including looking at my crash log.

I believe he MAY have found the root cause of the problem. I say that tentatively because a kernel panic could happen in the next few minutes. However, one has not happened since I applied the fix that he recommended:


As far as your kernel panic,
A Few suggestions-

1. Have you checked with Adguard to see if they have newer driver release? If not, we suggest you remove that software temporarily from your system. They have some information on their site - https://adguard.com/en/removal.html
If you still run into panic issue, please send off the logs, we can help to investigate.

2. When you un-dock or re-dock, please make sure your Mac’s lid is open before undocking or redocking.

For example:
To Un-dock: With the lid open, unplug the Thunderbolt cable. Then close lid.
To Re-dock: Open lid first, then connect the Thunderbolt cable to re-dock.

Through our repetitive tests, we’ve found this habit of sequence would greatly reduce panic issues.
We believe it’s probably related to the GPU or Intel CPU. We need more time to investigate the issues and will submit our final findings to Apple.

It seems like ADGUARD could have been the culprit.

The issue also could have involved disconnecting the MBP while the lid was closed.

Will keep an eye on things and let all of you know how this workaround is progressing.
 
  • Like
Reactions: Guy Brush

thefriendshipmachine

macrumors 6502
Apr 14, 2017
308
215

lilith2014

macrumors newbie
Jun 7, 2011
19
0
I just wanted to add my two cents here.
For the ones using MPB: Some of them have trouble with one capacitor that overheats, and when the logicboard switches from internal to dynamic GPUs, crashes. You'll have to replace the capacitor for a bigger/stronger one, and it's a pain to find somebody qualified to do so. You could try downloading the GFXCARDSTATUS app and manually switch the GPUs, usually leaving it in the Nvidia one, stopping the GPU switching.

Now I'm having trouble with my late 2015 4k Imac (17,1). I'm having trouble with ghost restarts while the mac is sleeping. Not the same KP shows up each time, always displaying problems with the GPU and only happens when the computer goes to sleep by itself, If I send it to sleep, no trouble. I had Sierra, no problem, upgraded to High Sierra, KPs started to show up, I just upgraded to BIG SUR, same cow crap.

I really hope this ain't a hardware issue tho.


I can't believe that after almost 10 years of having issues similar to this one goddamn apple can't fix it. Having us to find workarounds is a waste of time. Since I bought a Huion Kamvas drawing tablet (now I have 3 displays), I suspect this is the culprit.

Good luck everybody
 

tommiy

macrumors 6502
Dec 11, 2015
412
127
Interesting where did you learn about the capacitor issue and can you provide details of the capacitor in concern in regards to the circuit board id? This sounds like a design flaw if it needs to be replaced with one of greater capacity.
 

IAMDAVE1969

macrumors member
Aug 14, 2017
38
35
I purchased my 2019 16" MacBook Pro on December 12, 2019. After three to four weeks of use I began experiencing Kernel Panic and Sleep- Wake issues.

I contacted Apple and was told that it was a know issue and to wait for the next Catalina update. The problem persisted for months.

In March of 2020 Apple asked me to bring in my computer for servicing. I visited my local Apple store and luckily the Kernel Panic occurred while at the Genius Bar.

They took my computer to run diagnostics and told me that they would call me the next business day after running some diagnostics to report there findings. The next day I was informed that no issues were found with the hardware and that they reinstalled Catalina with a fresh install.

A few day later the Kernel Panic/ Sleep-Wake Issues started again. I escalated the issue to Level 2 Support. I was asked to run some local diagnostics and send to Apple for their Lab Techs to review. I received a call back several days later informing me that the Kernel Panics were a known issue and that Apple believed the issue was related to a coding issue in Catalina. I was asked to wait for the next Catalina update, then to report report back if the issue persisted.

After several Catalina Software updates, and numerous calls with Level 2 Support the problem still persisted.

It's now April of 2020, and Apple finally agreed to repair my computer. I was informed that they would need to replace my Logic Board. This is shortly after COVID hit and everything shut down. I could not bring in my computer anywhere for repair in Canada.

Once things opened back I contacted Apple in late June of 2020, and I was finally was able to book an appointment to repair my computer. There was about a month delay to get an appointment. I was finally was able to coordinate this in late July of 2020.

The Logic Board was replaced. After the repairs, I had absolutely 'no issue' with Kernel Panics/Sleep-Wake issues. And please note that I reinstalled all the identical software from my Time machine backup, on the same version of Catalina 10.15.6.

'Thank God...Problem solved.'

But Wait...

Four days after my warranty expired in December 2020, and 5 months after the Logic Board replacement the Kernel Panic/Sleep Wake issues started again!!!

Apple approved a second repair and once again replace the Logic Board, and to be safe replaced the Touch Bar free of charge.

I picked up my computer 2 week later, due to a parts delayed. I received a call that the repairs were complete and a diagnostic was run showing no Hardware issue.

I drove home after picking up my computer, powered the unit on, and five minutes into testing the computer the and Kernel panics began occurring again!!!

I called Apple Support again, and was told that they I would have to bring my computer in for a THIRD repair. This time I was told that they would once again replace the Logic Board and Touch Bar, and to be safe replace the outer shell that has some hardware attached.

I asked politely asked the Apple Support Rep the one question...'Before I go away and started preparing a very long email to communicate my twelve plus month experience, is there anyone else I can talk too. I prefer not to go that route.' I was then transferred to a Senior Customer Service Rep who finally agreed to replace my computer.

It's now late January 2021, and I have had my replacement 16”MacBook Pro for 4-5 weeks. Not one Kernel Panic/Sleep-Wakw issue.

'Knock on Wood'.

Once again I am running the same software reinstalled from my Time Machine back-up.

'Total nightmare.' Although this was a 'Super Frustrating Experience,' Apple did take care of me in the end.

I can't count how many hours I spent online with Apple Support, not to mention not having use of my computer for 30+ days due to repairs and downtime.

I see a lot of people in various forums who have experienced the identical issue with the 2019 16" MacBook Pro.

I do have to note that everyone I dealt with at Apple over the last 12 months was friendly, supportive they and always wanted to do there upmost to help.

LONG story I know, but I could have written a novel detailing everything I went through trying to get this issue resolved.
 
Last edited:

IAMDAVE1969

macrumors member
Aug 14, 2017
38
35
I have Big Sur 11.1 running on a replacement M1, still has this issue.

So that's 4 machines I've owned:

* MBP 16inch i9
* MBP 13inch M1 x2
* MBP 15inch i7

Seen it in Catalina (introduced around 10.5.6), ****ing stunning that this is still a thing.
How is this not a glaringly obvious and urgent UX issue. IT NEEDS A FIX.
I purchased my 2019 16" MacBook Pro on December 12, 2019. After three to four weeks of use I began experiencing Kernel Panic and Sleep- Wake issues.

I contacted Apple and was told that it was a know issue and to wait for the next Catalina update. The problem persisted for months.

In March of 2020 Apple asked me to bring in my computer for servicing. I visited my local Apple store and luckily the Kernel Panic occurred while at the Genius Bar.

They took my computer to run diagnostics and told me that they would call me the next business day after running some diagnostics to report there findings. The next day I was informed that no issues were found with the hardware and that they reinstalled Catalina with a fresh install.

A few day later the Kernel Panic/ Sleep-Wake Issues started again. I escalated the issue to Level 2 Support. I was asked to run some local diagnostics and send to Apple for their Lab Techs to review. I received a call back several days later informing me that the Kernel Panics were a known issue and that Apple believed the issue was related to a coding issue in Catalina. I was asked to wait for the next Catalina update, then to report report back if the issue persisted.

After several Catalina Software updates, and numerous calls with Level 2 Support the problem still persisted.

It's now April of 2020, and Apple finally agreed to repair my computer. I was informed that they would need to replace my Logic Board. This is shortly after COVID hit and everything shut down. I could not bring in my computer anywhere for repair in Canada.

Once things opened back I contacted Apple in late June of 2020, and I was finally was able to book an appointment to repair my computer. There was about a month delay to get an appointment. I was finally was able to coordinate this in late July of 2020.

The Logic Board was replaced. After the repairs, I had absolutely 'no issue' with Kernel Panics/Sleep-Wake issues. And please note that I reinstalled all the identical software from my Time machine backup, on the same version of Catalina 10.15.6.

'Thank God...Problem solved.'

But Wait...

Four days after my warranty expired in December 2020, and 5 months after the Logic Board replacement the Kernel Panic/Sleep Wake issues started again!!!

Apple approved a second repair and once again replace the Logic Board, and to be safe replaced the Touch Bar free of charge.

I picked up my computer 2 week later, due to a parts delayed. I received a call that the repairs were complete and a diagnostic was run showing no Hardware issue.

I drove home after picking up my computer, powered the unit on, and five minutes into testing the computer the and Kernel panics began occurring again!!!

I called Apple Support again, and was told that they I would have to bring my computer in for a THIRD repair. This time I was told that they would once again replace the Logic Board and Touch Bar, and to be safe replace the outer shell that has some hardware attached.

I asked politely asked the Apple Support Rep the one question...'Before I go away and started preparing a very long email to communicate my twelve plus month experience, is there anyone else I can talk too. I prefer not to go that route.' I was then transferred to a Senior Customer Service Rep who finally agreed to replace my computer.

It's now late January 2021, and I have had my replacement 16”MacBook Pro for 4-5 weeks. Not one Kernel Panic/Sleep-Wakw issue.

'Knock on Wood'.

Once again I am running the same software reinstalled from my Time Machine back-up.

'Total nightmare.' Although this was a 'Super Frustrating Experience,' Apple did take care of me in the end.

I can't count how many hours I spent online with Apple Support, not to mention not having use of my computer for 30+ days due to repairs and downtime.

I see a lot of people in various forums who have experienced the identical issue with the 2019 16" MacBook Pro.

I do have to note that everyone I dealt with at Apple over the last 12 months was friendly, supportive they and always wanted to do there upmost to help.

LONG story I know, but I could have written a novel detailing everything I went through trying to get this issue resolved.
 
  • Like
Reactions: johnalan

star-affinity

macrumors 68000
Nov 14, 2007
1,996
1,333
@IAMDAVE1969

Thanks for telling your story!

It sure seems to me that this Kernel Panic can be both related to hardware and software, but (for most?) that the software problem should have been fixed by now and those still having problems in Big Sur probably has some kind of hardware problem.

Interesting that after two logic board exchanges you still saw the problem.

Like I've been saying in this thread I've never seen this watchdog Kernel Panic on a MacBook Pro 13" (2018) that I have for work – neither in Catalina nor in Big Sur. I used to see this watchdog related Kernel Panic on my by Catalina and Big Sur on my by Apple unsupported Mac Pro (still using it with the help of OpenCore) but since Big Sure I have no Kernel Panics on the Mac Pro upon wake from sleep, thus a software change fixed it in that case.
 

PowerMac84

macrumors member
Sep 16, 2016
33
21
Karlsruhe/Germany
This kind of error started happening to me yesterday on two Macs at the same time!
Can this be coincidence?

My MacBook Pro 15" (Retina from 2018) and my Mac Pro 5,1 (via OC), both running with Big Sur 11.1 started crashing with the same error report. Yesterday. No problems for years before.
The behaviour looks like this: suddenly the mouse is not moving anymore, sometimes I am able to still hear audio (from Skype) then the clock freezes. After a minute or two the Mac restarts.

After restarting the Mac slowly syncs Dropbox, open the usual demons and startup scripts. My Mac Pro and the Mac Pro would not stay running for more then five minutes until the crash happened again.

I figured it must have something to with interfering cloud sync processes or writes on the SSDs. Now I have narrowed it down to: Dropbox. Upon restart I have force quit Dropbox and it‘s helper apps. Everything is working fine now.

I tried reinstalling Dropbox but after a few hours it‘s happening again.

What do you think?
 

tipxbomb

macrumors newbie
Jan 28, 2021
2
0
I have been receiving these kernel panics multiple times a day (the computer freezes, followed by an eventual crash/restart if I don't do a hard shut down first). It occurs most frequently when waking the computer from sleep. Often I'll go to the bathroom and return to my computer, only to see my screensaver has frozen (at which point I'll be forced to do a hard shut down) or I'll come back and see my login screen (meaning the computer shut itself down). When logging back in, I receive the full kernel panic (attached below).

That said, certain applications seem to cause it while the computer is in use: Skype, Plex, iMovie, and occasionally while watching YouTube/Netflix. During a 45 minute Skype call, I'll get the freezing about 3 times. And as you can see from the embedded video, I can repeatedly produce the kernel panic using iMovie in just 2-3 minutes.


My guess is the issue stems from the Mac's use of the discrete GPU, probably the GPU driver because this issue began with a software (or potentially silent firmware) update and, according to others on the Apple Support Threads, is occurring on dozens of different models, meaning different GPUs. This is further evidenced by the fact that many of the applications I experience the crash while using require the discrete GPU to be used (and some especially tax it), as well as other users experiencing the crash when they plug their Mac into an external monitor, which likely triggers a switch to or more heavily involves the discrete GPU.

Here are steps you can do to reproduce the issue on your Mac running Catalina:
  1. (If you have a laptop) Open System Preferences, then go to Energy Saver, then deselect "Automatic Graphics Switching" at the top. This will make it so that your dedicated GPU is always in use.
  2. Go to this link and download the 4K video: https://www.videezy.com/urban/2820-aerial-footage-of-new-york-city-4k
  3. Open the video in Quicktime.
  4. In the menu bar, click "View" and then "Loop" so the video plays repeatedly.
  5. Play the video and wait.
Using this method I was able to cause my laptop to kernel panic with this error within 30 seconds of playing the video. I repeated the process 6 times just to be sure, and each time my computer kernel paniced with this error within 30 seconds every time.

Let's please figure this out. It's impossible to downgrade a 16-inch MBP to Mojave because it shipped with Catalina, so I'm stuck without any remedy here. I've tried a completely fresh install of Catalina, but that didn't resolve the issue.

Here's the panic:
Code:
panic(cpu 2 caller 0xffffff7f9cb9dad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (6130 seconds ago): 614, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (6100 seconds ago): 598, last successful checkin: 120 seconds agoBacktrace (CPU 2), Frame : Return Address
0xffffff924115b820 : 0xffffff801c13bb2b
0xffffff924115b870 : 0xffffff801c2734d5
0xffffff924115b8b0 : 0xffffff801c264f4e
0xffffff924115b900 : 0xffffff801c0e2a40
0xffffff924115b920 : 0xffffff801c13b217
0xffffff924115ba20 : 0xffffff801c13b5fb
0xffffff924115ba70 : 0xffffff801c8d2b25
0xffffff924115bae0 : 0xffffff7f9cb9dad5
0xffffff924115baf0 : 0xffffff7f9cb9d7e6
0xffffff924115bb10 : 0xffffff801c86739b
0xffffff924115bb60 : 0xffffff801c870443
0xffffff924115bca0 : 0xffffff801c222d12
0xffffff924115bdb0 : 0xffffff801c1419d8
0xffffff924115be10 : 0xffffff801c118635
0xffffff924115be70 : 0xffffff801c12f0e5
0xffffff924115bf00 : 0xffffff801c24b575
0xffffff924115bfa0 : 0xffffff801c0e3226
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[053A5D15-51D4-3E61-978B-EB435FA4BD0A]@0xffffff7f9cb9c000->0xffffff7f9cba4fffBSD process name corresponding to current thread: watchdogd
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-devMac OS version:
19D76Kernel 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:     0x000000001be00000
Kernel text base: 0xffffff801c000000
__HIB  text base: 0xffffff801bf00000
System model name: MacBookPro16,1 (Mac-E1008331FDC96864)
System shutdown begun: NO
I have been running this video for the past 3 hours, nothing happened.
This only happens randomly for me.


Every day / every 2 days I get it - in a random scenario, without doing anything.
Sometimes it will happen when I'm away from the computer, sometimes while I'm trying to click .

I coudlnt find any consistencies.

Considering an upgrade to big sur, overall Catalina is fine for me, I'm only considering it if it will improve the panic crashes.

Date/Time: 2021-01-28 14:26:06 +0200
End time: 2021-01-28 14:26:12 +0200
OS Version: Mac OS X 10.15.7 (Build 19H15)
Architecture: x86_64h
Report Version: 29

Data Source: Stackshots
Shared Cache: 0x1142000 F9F56FD2-0748-3B45-A14A-0DDA16E4701B
Reason: (1 monitored services unresponsive): remoted connection watchdog expired, 342 successful replies since wake, last successful checkin 80 seconds ago

Command: UserEventAgent
Path: /usr/libexec/UserEventAgent
Version: ??? (???)
PID: 123

Event: service process watchdog
Duration: 5.57s
Steps: 12

Hardware model: MacBookPro16,1
Active cpus: 16
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Time Awake Since Boot: 75000s



Process: UserEventAgent [123]
UUID: 93C3CCC8-5AD6-30E4-88A3-E18A92179FED
Path: /usr/libexec/UserEventAgent
Architecture: x86_64
Footprint: 7400 KB
Start time: 2021-01-28 14:26:06 +0200
End time: 2021-01-28 14:26:12 +0200
Num samples: 12 (1-12)
CPU Time: <0.001s
Note: 2 idle work queue threads omitted
 

johnalan

macrumors 6502a
Jul 15, 2009
868
1,023
Dublin, Ireland
I have the Kernel Panic on reboot issue on Big Sur 11.2...
but I've FINALLY been able to reliably reproduce this issue!!

  1. Install Ruby with Home-brew.
  2. Run "gem update".
  3. Reboot and you'll see the panic.

I don't think it's a ruby issue, but something that running the non-system ruby causes issues...

So weird.

I've rebooted say 75 times, and only on the 5/6 I ran gem, did I see the issue.
 
  • Wow
Reactions: star-affinity

star-affinity

macrumors 68000
Nov 14, 2007
1,996
1,333
I have the Kernel Panic on reboot issue on Big Sur 11.2...
but I've FINALLY been able to reliably reproduce this issue!!

  1. Install Ruby with Home-brew.
  2. Run "gem update".
  3. Reboot and you'll see the panic.

I don't think it's a ruby issue, but something that running the non-system ruby causes issues...

So weird.

I've rebooted say 75 times, and only on the 5/6 I ran gem, did I see the issue.
Still great to have a reliable way to reproduce it, since then it's easier to come up with a fix. :)
 
  • Like
Reactions: johnalan

gregorskii

macrumors newbie
Jun 26, 2017
17
5
Los Angeles
I have the Kernel Panic on reboot issue on Big Sur 11.2...
but I've FINALLY been able to reliably reproduce this issue!!

  1. Install Ruby with Home-brew.
  2. Run "gem update".
  3. Reboot and you'll see the panic.

I don't think it's a ruby issue, but something that running the non-system ruby causes issues...

So weird.

I've rebooted say 75 times, and only on the 5/6 I ran gem, did I see the issue.

I have ruby on my Mac, I use rbenv, I really doubt it's this. :/
 

johnalan

macrumors 6502a
Jul 15, 2009
868
1,023
Dublin, Ireland
I have ruby on my Mac, I use rbenv, I really doubt it's this. :/
It most certainly is this (for me).
I rebooted additionally about 40/50 times, and only on the times I ran gem (homebrew version) did I get the KP.

so out of 120+ reboots only the handful of times I ran gem ? I get the KP.

would you like a video to demo?

this is specifically for the watchdogd timeout kp on reboot.
 

gregorskii

macrumors newbie
Jun 26, 2017
17
5
Los Angeles
It most certainly is this (for me).
I rebooted additionally about 40/50 times, and only on the times I ran gem (homebrew version) did I get the KP.

so out of 120+ reboots only the handful of times I ran gem ? I get the KP.

would you like a video to demo?

this is specifically for the watchdogd timeout kp on reboot.
No don’t need a video. I think this thread has mixed issues for a while.

I reported mine crashes when connected to multiple monitors about a year ago. I get kernel panics only when connected to more than one external display since Catalina. No other issues otherwise.

they replaced my logic board when my lcd backlight died. I doubt it’s hardware.
 
  • Like
Reactions: johnalan

johnalan

macrumors 6502a
Jul 15, 2009
868
1,023
Dublin, Ireland
No don’t need a video. I think this thread has mixed issues for a while.

I reported mine crashes when connected to multiple monitors about a year ago. I get kernel panics only when connected to more than one external display since Catalina. No other issues otherwise.

they replaced my logic board when my lcd backlight died. I doubt it’s hardware.
Agreed. All this stuff is software.
I WISH they’d do a snow leopard release.
 

johnalan

macrumors 6502a
Jul 15, 2009
868
1,023
Dublin, Ireland
I've now found that anything calling into Ruby will cause this Kernel Panic, e.g. using home-brew to install anything from source, reboot after that, KP.
 
  • Like
Reactions: flitter

thefriendshipmachine

macrumors 6502
Apr 14, 2017
308
215
urgh, in addition to my entire screen just locking right up, I am STILL getting this issue!

userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds

every single day. What do I do :(
 

random-uk

macrumors member
Dec 29, 2011
56
19
I have the Kernel Panic on reboot issue on Big Sur 11.2...
but I've FINALLY been able to reliably reproduce this issue!!

  1. Install Ruby with Home-brew.
  2. Run "gem update".
  3. Reboot and you'll see the panic.

I don't think it's a ruby issue, but something that running the non-system ruby causes issues...

So weird.

I've rebooted say 75 times, and only on the 5/6 I ran gem, did I see the issue.
Seems like this homebrew user also had a similar result:

panic on shutdown

So might the panic on reboot actually be a homebrew issue?
 

thefriendshipmachine

macrumors 6502
Apr 14, 2017
308
215
Good find but its not home-brew directly, but as that post mentions, a few apps that have certain dependencies.
I panic every day randomly. I tried your steps to repro but they worked fine for me, probably we're on different versions of ruby, and also gem update depends on your ruby file. If you share your gemfile and version of ruby with me though I'd be happy to try and reproduce on my 2019 iMac.
 

random-uk

macrumors member
Dec 29, 2011
56
19
Good find but its not home-brew directly, but as that post mentions, a few apps that have certain dependencies.
@johnalan so I've experiment some more and tested removing homebrew entirely from my system and switching to MacPorts. Since doing this, I've not had any kernel panic on rebooting the system errors. I've been testing this way for about a week. So it's looking more and more like there is some weird interaction with macOS and homebrew.

Here are the packages I happened to have installed via homebrew - I don't know whether we have any ones in common or where to begin trying to track down the issue.
Code:
ffmpeg
flake8
fping
iperf3
jq
libjpeg
libtiff
libxml2
libxslt
little-cms2
media-info
nmap
pipenv
poetry
pyenv
python
rsync
tmux
webp
wget
youtube-dl
zsh-autosuggestions
zsh-completions
zsh-syntax-highlighting
 

johnalan

macrumors 6502a
Jul 15, 2009
868
1,023
Dublin, Ireland
@johnalan so I've experiment some more and tested removing homebrew entirely from my system and switching to MacPorts. Since doing this, I've not had any kernel panic on rebooting the system errors. I've been testing this way for about a week. So it's looking more and more like there is some weird interaction with macOS and homebrew.

Here are the packages I happened to have installed via homebrew - I don't know whether we have any ones in common or where to begin trying to track down the issue.
Code:
ffmpeg
flake8
fping
iperf3
jq
libjpeg
libtiff
libxml2
libxslt
little-cms2
media-info
nmap
pipenv
poetry
pyenv
python
rsync
tmux
webp
wget
youtube-dl
zsh-autosuggestions
zsh-completions
zsh-syntax-highlighting
Very interesting thanks!

I’ve been able to replicate now. I started a thread with instructions here:https://forums.macrumors.com/thread...-confirm.2284170/?post=29620148#post-29620148

can you take a look and see if you can?
 
  • Like
Reactions: star-affinity

johnalan

macrumors 6502a
Jul 15, 2009
868
1,023
Dublin, Ireland
I have the Kernel Panic on reboot issue on Big Sur 11.2...
but I've FINALLY been able to reliably reproduce this issue!!

  1. Install Ruby with Home-brew.
  2. Run "gem update".
  3. Reboot and you'll see the panic.

I don't think it's a ruby issue, but something that running the non-system ruby causes issues...

So weird.

I've rebooted say 75 times, and only on the 5/6 I ran gem, did I see the issue.
I posted here about how I can replicate.

I can now solve this (KP on reboot (Watchdogd)) :D

My replication steps only work when my terminal emulator (iTerm/Terminal) was in added in "Developer Tools" section of Security & Privacy settings in macOS.

Removed them and I could not longer replicate.

This looks to be a bug in codesign/watchdogd/adhoc signatures. Where you remove the terminal from dev tools, you can see the signature check is performed and all is well.

If you have terminal in the "developer tools" category, certain tools (like the ones I describe in my post, ruby/pip), cause the OS to panic on reboot, as something ends up hanging.

Amazing but now solved...

Described further here: https://sigpipe.macromates.com/2020/macos-catalina-slow-by-design/
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.