Apple - Mac Mini 2018 Kernel panic bug_type 210 after Security Update 2020-002
I can confirm similar issues post Security Update 2020-002 on a 2018 Mac Mini runnign 10.14.6.
- A few days later I power it down. On restart refuses to boot normally, taken to Internet restore, which ends in Error -1008F.
- After clearing NVRAM it boots normally.
- Left to sleep overnight
- In the morning, it had shutdown and on starting up normally I received an ‘Unexpected Shutdown message, the crash log showed a panic with iBridge.
Reported to Apple with Feedback Assistant
Update: Security Update 2020-003 has updated Bridge OS so hopefully fixes the issue....
I also have this after every reboot/restart after running the 2020-002 security update on my Mac Mini 2018. Odd thing is, I first ran the update on a Mac OS that was booted from my external SSD (which I occasionally boot from for music production) and after I did this I also got the error after booting from my internal SSD, which had not yet been updated. So I don't know what this install did to the T2 chip but it's apparently regardless of wether you're running on internal or external SSD, and it seems to have affected the hardware rather than the Mac OS installation.
In my case security update #3 fixed this issue. Can't reproduce it by opening Safari or putting the Mac to sleep. After a clean shutdown and startup the error shows. So no fix indeed. Shabby.
Can't comment, so just wanted to state that the workaround from @howdytom works (update April 24, 2020).
I'm going to use Chromium (brew cask install chromium) until a Safari update comes and fixes the issue.
Same here. Macmini8,1 since Security Update 2020-002 (Mojave).
In my case the first thing that happened was that I had no screen signal, the update "broke" the thunderbolt port where the screen is connected. The port came to life again after manually resetting the NVRAM.
After that, every time my Mac goes into a deep sleep it restarts. Not sure if it's when it goes to sleep or at the moment I wake it up. That is very annoying and critical since any work I have opened gets lost. After reading this thread tested that a shutdown results in the same error and report.
I'm reading carefully this how-to, although I only have this Mac right now so I can't try. I suppose downgrading as @howdytom did to 10.14.6 (18G3020) from late January and do not apply the #2 security update is the only workaround right now.
I've already filled a report using the Feedback Assistant on March 31. No reply yet, as expected. I'll update the report with this thread link. Please report it to Apple too, the more we are the faster they'll fix that. In case you do (or did) please link to my report ID: FB7646497