Mac Mini crashing on sleep

Sorry, I haven’t read this whole thread, but it seems, these are the issues that are also discussed in this thread:

https://discussions.apple.com/thread/251244094?page=1

I’d like to sum up the results, we had collected so far:

• Troubles began with the installation of the Security Update 2020-002 and Safari 13.1
• Affected hardware: Mac mini 2018, iMac Pro and recent Mac Book Pro (hardware with Apple’s T2 Security Chip).
• Affected OS: High Sierra, Mojave, partly Catalina

Possible issues:

• no power supply on at least 1 Thunderbolt port (i.e. Mac mini ’18: TB-Bus 1, port next to HDMI)
• Kernel Panic through sleep or shut down commands, related to BridgeOS
• macOS crash when disconnecting an eGPU by the Disconnect command in the top bar eGPU menu
• some experience seemingly random restarts of their Macs with upcoming BridgeOS Kernel Panic Reports afterwards

The Security Update installed a Firmware Update for the T2 chip. This seems the reason, why the actual problems cannot be fixed by a re-installation of macOS: the new T2 firmware (build: 17P4263), located in a protected memory area of the T2 chip itself, will not be replaced with an older version during a fresh macOS installation.

The T2 chip holds the SMC, which is related to sleep and shut down.

The Security Update 2020-002 also installed changes to IOThunderboltFamily and Kernel, which might be the cause for the troubles with eGPU and failing power supply on 1 TB port.

Found solutions so far:

• To avoid the sleep and shut down BridgeOS Kernel Panics, it seems that not using (not even launching) Safari 13.1 is a reliable workaround. This new Safari version seems to trigger a bug which results in the aforementioned problems. Using a different browser, such as Firefox or Chrome does not trigger the bug.
• Failing power supply for TB port can be restored by a SMC reset (some had also success with NVRAM/PRAM reset).
• No solutions were found so far for the macOS crash while using the Disconnect command for an eGPU. Disconnecting without macOS crash can only be done when Mac is shut down.

We have send in lots of Kernel Panic Report and bug reports (via Apple Product Feedback).

So far nobody got any response by Apple. We’re actually waiting for a fix with upcoming updates, as this is clearly a software problem.

Expected solution:

Apple must release bug fixed versions of BridgeOS and Safari for High Sierra, Mojave and probably Catalina. (Catalina users encounter some other issues since the SecUpd that need to be addressed).

You might also want to have a look at:

https://apple.stackexchange.com/questions/386761/mac-mini-2018-kernel-panic-bug-type-210-after-security-update-2020-002

https://forums.macrumors.com/threads/mac-mini-2018-kernel-panic-bug_type-210-after-security-update-2020-002.2228812/

German: https://www.macgadget.de/Forum/T2-BridgeOS-crashes-durch-Security-Update-2020-002

Hope, this might help a bit.

Hello,

Try running the following tests:

How to reset the System Management Controller (SMC) on your Mac - Apple Support

Reset NVRAM or PRAM on your Mac - Apple Support

How to use Apple Hardware Test on your Mac - Apple Support

Here’s what Apple has to say about Sleep issues:

If your Mac doesn't sleep or wake when expected - Apple Support

FWIW, I gave up on the Sleep function years ago. Ever since the inception of OS X there have been Sleep related issues. And even more lately. I just use Display Sleep and keep it set for 15 minutes so I'm not burning the screen. No put hard disks to sleep (they should spin down on their own after about 10 minutes of inactivity), no wake for network access.That way your Mac uses very little power over Sleep and is ready to use at the touch of a key without any grogginess. UNIX based systems were made to be always on and they’ve been running busy servers 24/7 for decades.

My own 2010 iMac has been used daily and has never slept a day in its life. It's still going strong.

I sent the following message to https://www.apple.com/feedback/macos.html Please do the same to get Apple's attention.

"Previously a very stable Mac mini 2018 has now started to crash after going to sleep. Also after a cold boot there is a crash report. This started to happen after Security Update 2020-002 (Mojave). Resetting SMC or PRAM or safe-boot or checking with Disk First Aid does not help."

It seems that exluding boot from an external on T2 is a new feature (which leaves me scratching my head) but it can easily be allowed by booting in Recovery.

About Startup Security Utility - Apple Support

Ah... OK. Everything is on Mojave. I might already have a clone of the MBPro, for backup purposes.

In the olden times, I would put it into Firewire slave mode and then connect it to the Mini as a boot drive... I can't keep up with Apple's removal of features and addition of other features.

I finally did get a crash report. Can you glean anything from this?

After the reports about the beta builds, my expectations were already lowered.

(Will install anyways, but will wait a couple more days to gather some more information).

For those who are interested:

Apple's "About" page for the Security Update 2020-003:

https://support.apple.com/en-us/HT211170

and Safari 13.1.1:

https://support.apple.com/de-de/HT211177

There's only one "Solved" result on the discussions of this problem.

It is here; https://discussions.apple.com/thread/251168481

And Apple replaced his motherboard. It's clear they know what caused it, and that it would be a very expensive fix for them to replace ALL of the damaged motherboards. Perhaps they hope that AppleCare will run out for many of the Macs that were damaged by the security update - or that over time they may find a T-2 chip firmware fix to undo the previous buggy firmware update. Time will tell.

POSTSCRIPT: I've been using Apple computers since the Apple ][ and I've received a number of invitations to join various class action lawsuits over that time. If they don't address this issue SOON, I expect I'll be invited to join another.

Definitively some piece of software that sits on some chip. Haven't read anything about anyone who could fix the issues by a clean install of High Sierra, Mojave or even Catalina. Don't even think that a firmware reset via Configurator would help, as it would most likely just install the newest (broken) version again.

…and there is just sooo much to choose from:

About the security content of macOS Catalina 10.15.4, Security Update 2020-002 Mojave, Security Update 2020-002 High Sierra - Apple Support

No wonder that Apple needs so much time to fix this. But they should, as many users are running High Sierra or Mojave for reasons.

The sleep and shutdown/cold-boot crash has persisted in Mojave (especially if Safari is used in the previous session) after the following five Mojave and Catalina firmware updates (that crash does not seem to happen in Catalina):

Security Update 2020-002 Mojave & macOS 10.15.4 update

Boot ROM Version: 1037.100.359.0.0 (iBridge: 17.16.14263.0.0,0)

macOS 10.15.4 Supplemental update

Boot ROM Version: 1037.100.362.0.0 (iBridge: 17.16.14281.0.0,0)

Security Update 2020-003 Mojave

Boot ROM Version: 1037.120.87.0.0 (iBridge: 17.16.15290.0.0,0)

macOS 10.15.5 update

Boot ROM Version: 1037.120.87.0.0 (iBridge: 17.16.15300.0.0,0)

Security Update 2020-004 Mojave and macOS 10.15.6 update

Boot ROM Version: 1037.147.1.0.0 (iBridge: 17.16.16065.0.0,0)

macOS 10.15.6 Supplemental update

Boot ROM Version: 1037.147.4.0.0 (iBridge: 17.16.16610.0.0,0)

A message a little earlier in this thread claims that Big Sur public beta 9.8.2020 might correct that Mojave sleep/shutdown crash. But I don't want to test beta software on my main Mac.

Boot ROM Version: 1554.0.0.141.1 (iBridge: 18.16.10347.5.3,0)

https://discussions.apple.com/thread/251226783?answerId=253212464022#253212464022

I filed this bug August 5, and updated it a number crashes with a new sysdiagnose.  Still: "Recent Similar Reports:None"

The sysdiagnose however is quite a large file, 140M, I'm getting a bit fe(e)d up with it without any feedback (ha!) from Apple..

Give it a go, make yourselves heard, file a bug at https://feedbackassistant.apple.com/.

And add a reference to this discussion? https://discussions.apple.com/thread/251226783

So far, my machine have run without any issue for 5days.

MagicQs-MacMini:~ MagicQ$ uptime

10:27 up 5 days, 1 hr, 4 users, load averages: 1.70 1.79 1.79

What I had done:

1. Apple replaced my motherboard, and that issue occurred once after restore all data from timeMachine.

{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.6 (18G103)","os_version":"Bridge OS 4.5 (17P5290)","macos_system_state":"sleep","incident_id":"0D2F7D05-3AE4-4653-9B88-EA3EB8068580","timestamp":"2020-05-28 18:11:28.00 +0000","bug_type":"210"}

Note, the T2-Chip's firmware version is 17P5290, that's being said, replace motherboard is not useful for me, and the issue might caused by software itself.

2 Install security update 2020-003, sounds good now.

Someone had posted that update 2020-003 doesn't make sense, so i doubt security 2020-002 made some hard hurt on the machine, mostly the T2-Chip.

Something I found this weekend: I had disabled (T2 chip related?) startup security, because I ran into problems trying out Catalina, some time ago, and disabling security was suggested as a solution. I have re-instated "full security, and did not experience crashes since. You may want to check what is configured for your mac, as following:

• reboot mac in safe mode (command-r while booting)
• from the utilities menu in the menu bar (not the pop-up window) choose the option Startup Security Utility
• I have selected full security

I chatted with Apple for a while yesterday.

First, I personally am sure this only affects two machines, one of the new laptops and the Mini 8, which have identical T2s and motherboards as far as I can tell.

Second, they are definitely aware of the problem.

Third, they still refuse to do data-gathering without Catalina on the internal drive.

Fourth, they will be issuing an update when they can.

My guess is that the update will be issued as a firmware update for both Mojave and Catalina. If it's issued for Catalina only, I would install Catalina on an external drive, then update that and hope the firmware update is the only issue.

I believe based on what I have heard so far that this is T2 related.

The support guy was unable to confirm any of what I just said, but he did say that there are other people with this issue who they have been able to get data from. Also, he looked briefly at the crash report and verified that the issue is not third party software.

I have tried booting in safe mode and on an untouched external drive system, and I have tried having all USB devices disconnected before sleep, including keyboard, and with different mice.

I am positive this is a Mini-8-and-one-laptop-affecting firmware/T2 issue and that the only solution for the moment is not to sleep.

I have the same issue except no eGPU. I have tried removing all kernel extensions. It might be Chrome related. I reset SMC and ran hardware test. All shows up as good. I was planning to do PRAM next, but I think removing Google auto-update stuff via LaunchControl (an essential utility IMHO, esp if removing spyware) and making sure Chrome is not running during sleep may fix it. I will keep trying but so far that seems to work... but I also removed traces of VMWare, Malwarebytes, Vallum, and some other stuff.