After the recent security release for Mojave my Mac Mini (2018) crashes when it goes to sleep. Every time I have to restart it and Finder reports that my Mac crashed. I have an eGPU which has been working like a champ to date... but curious if other people are seeing this problem.
Thanks in advance.
Mac mini, macOS 10.14
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:
Possible issues:
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:
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:
German: https://www.macgadget.de/Forum/T2-BridgeOS-crashes-durch-Security-Update-2020-002
Hope, this might help a bit.
Now I don't even need to sleep, if I shut off the screen through software ... whammo. And it's not showing me the crash reports.
2020-04-06 09:15:02.115105-0400 0xc3 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5
2020-04-06 09:18:53.028162-0400 0xc3 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1
2020-04-06 13:08:31.182844-0400 0xc3 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5
2020-04-06 14:56:02.703935-0400 0xc3 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 1
2020-04-06 16:28:54.643033-0400 0xc3 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5
2020-04-06 18:07:05.521605-0400 0xc3 Default 0x0 0 0 kernel: (AppleSMC) Previous shutdown cause: 5
Same firmware you have. I didn't check it before the Catalina thing. I guess I'd better make sure Safari is quit before sleeping.
Addendum: it might nto have actually been sleeping, the light doesn't pulse...
Thanks Matti for sharing your troubleshooting! We share a number of similar peripherals and this saved me some time. I agree it is a system software/firmware issue that will hopefully get fixed before having to move to Catalina (which I hear is having some of its own problems with the most recent update).
You are correct in addition to the security update there was also a Safari update at the same time in March 2020. I'm not convinced that it isn't related to sleep, but I agree I am often prompted with an error upon cold boot after I shut down the computer from the Finder. From shutdown to reboot, there is no time to sleep. Thank you for adding to this thread!
I have the same problem - Imac 2018, sys 10.14.6 with latest security update - it didn't fix my problems. Mine shows a dialoge when I start that my Mac that it was restarted each time I boot up. Even though I haven't restarted the Mac.
One other very peculiar thing is that my monitor is black at start up now since this update. I manually have to pull out the HDMI cable and reinsert it to get the monitor to work.
I can't either update to Catlina since I need several 32-bit applications in my work.
I mean, a barely two year old, to me a quite expensive Mac - and now this. Apple can do better than this!!!
Apple fix it!
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:
I too have a same issue (Crash after sleep, bridgeos Error after reboot) with Mac Mini 2018 /Mojave.
I'm sure that this is a common issue that Apple should fix ASAP!
I'm using external SSD boot disk connected to USB-C 3.2, and does it matter?
Yes, there is a hack to get the chime back!
From The Eclectic Light Company (Feb 22 2020):
To turn on your missing startup chime, open Terminal and type
sudo nvram StartupMute=%00
then press Return. You’ll be prompted for your admin user password, which you should type in and press Return again. Then close Terminal, and try restarting your Mac.
You should now hear that warm, reassuring chord every time your Mac starts up, until you next reset your NVRAM, after which you’ll need to repeat the process of turning it back on.
Happiness is.
Postscript
To turn off the startup chime, open Terminal and type
sudo nvram StartupMute=%01
@noonn
no, mavots isn’t.
(It’s just a response to my side question {page 9 / Jun 14 / 9:39 AM})
@mavots
Thanks for coming back to this. I knew that there is a Terminal command, I was just wondering about your argumentation that you would not hear the startup chime in the morning when you considered your mini to be restarting. (Verifying that you're using the Terminal command).
Now, let's hope that Apple will finally publish a working solution for our main problems on Mojave and High Sierra when they come up with 10.15.6.
To be clear, this isn't on the main topic.
In the beginning... the chime told the user that their Mac had passed the startup hardware test. If it failed, a series of bongs would indicate what hardware had failed and your system would not boot up. Very useful, and the chime was a welcome and assuring greeting from our friendly Macs.
Does anyone know if the hack is connected in any way to a positive result of a hardware test?
<ot>
Does anyone know if the hack is connected in any way to a positive result of a hardware test?
The "hack" reenables the Mac Startup Chime. It then has the same function as it ever had.
Don't have any knowledge about why Apple decided to deactivate the Startup Chime, but it seems that the latest Macs (2019+) have a different Chime, which is also deactivated by default (but can also be activated via Terminal).
Btw, the Terminal command does not work for any Mac since 2016, i.e. some mini 2018 will not have a Chime, some have.
</ot>
All, I was replying to a question someone asked about my Mac Mini restarting after a crash and my hearing the old chime. They asked how I got that functionality back and I answered his question. Please let's keep to the topic at hand.
Cheers
The Mac Mini is a small blip on the Apple product sales list. It's simply not a big money maker.
I'm beginning to think that Apple is prioritizing bug fixes and support based on product sales statistics. Are the products with small markets not even important enough TO FIX BUGS?? BUGS THAT THEY INTRODUCED INTO OUR COMPUTERS?
I'm utterly disgusted with Apple at this point.
I installed SecUpd 2020-004 Mojave on my Mini 2018 last night, ran SMC and PRAM.
The Mini booted up at 8:00 am as scheduled.
I turned on my screen and there it was, the same crash report during startup as usual.
** Side note: I usually get to my Mini around 9am after breakfast. Most times it's booted and ready to go and sometimes (once a week?) it's not booted at all. Always with the crash report. Perhaps sometimes it actually does crash and other times not. But always with the note.
Oh my god.
FINALLY my MacMini 2018 has completely stopped working.
Sudden crash, then no more boot up.
Stuck at Apple Logo, No SMC reset, no PRAM reset, no Safeboot, nothing works.
I have been using Mac from 1990's, and THIS thing has NEVER happened to me.
I'm very angry now, seriously.
If someone has the same trouble, please report here.
Thank you,
Mac Mini crashing on sleep
