Security Update 2020-002

Hello kuramnasmeh,

thank you for pointing to the relation with Safari (v13.1, I guess)!

I could verify that the sleep and shut down related crashes of BridgeOS are obviously triggered by launching Safari.app during a computer session!

So, not launching Safari seems a reliable workaround to avoid these crashes for the moment.

@swerdnase:

according to the timestamps of the Kernel Panic Reports, the BridgeOS crashes are triggered by the sleep and shut down commands (regardless how the commands are fired up, by menu bar or keyboard shortcut). But, as kuramnasmeh notes, the bug seems only triggered, when Safari.app was launched before.

However, I would still argue that the main problem lies within the Security Update 2020-002 (here: for Mojave), as it had {amongst others} changes for IOThunderboldFamily and Kernel and I still see macOS crashing, when disconnecting the eGPU by the menu bar command and, last but not least, as it all started here with a failing power supply for the innermost Thunderbolt port.

update...

ok confirm the Safari involvement in the kernel issue. Tried to reboot without using Safari and I had no problems. I used Chrome, reboot and no problems. 

then, after this last reboot, I used Safari again and:

A-used it a little bit. then closed all the pages. Clear History, Clear Coookies and clear the cache. Then I closed Safari.

B-then I run Onyx...a complete maintenance. After which, onyx usually automatically reboot the system. and no problem. 

Intrigued by what just happened, after this reboot I repeated just the "A" procedure. without using Onyx. After the reboot...no problems at all.

Could you try these passages and see if it works for you as well?

- Open safari. Navigate. Close all the open pages, clear history, clear cookies, clear cache, close Safari...shut down and reboot.

Reminder. I'm with Mojave 10.14.6, iMac pro.

By the way...something else strange happened.. last time I did the procedure described above. After the reboot I opened Safari. homepage is by Apple. I went directly here in this forum. then I close the page. Clear history and I went to clear the cookies.

Strangely, in the list of the cookies used, I found a long list of cookies from website I never visited in the last session. I checked each one of them...and some ..I maybe visited moths ago. Some websites are within my favorites (in case there might be a connection in opening safari...and load all, or some cookies, from the favorites list)...but others...not at all. Strange thing...did someone has an answer to that?...Security update as well maybe?

In the meantime cheers...

L

Hello geoffdot5,

yes, you are right in that this Security Update was a very unfortunate one. Though it seemed at the beginning that only users of Apple hardware which contains the T2-chip were affected, I have found several posts that indicate that this is not the case.

It seems that the Boot ROM was updated and introduced all sorts of issues, some of which you ran into.

As Apple actually works on the Catalina 15.5 update, which should come out most likely during the next 2 weeks, my hopes are that Apple will bring out updates for Mojave and High Sierra too, which will address all the troubles Apple introduced with this careless 2020-002.

You might try to download the update from your Mac Pro, or by using Safe Mode ( https://support.apple.com/en-us/HT201262 ) with your iMac. (It will be slow, but some users report that they did not encounter problems when in Safe Mode, so this might help you out. It might also be a possibility to download from the Mac Pro, then copy the update to an USB drive/stick, launch the iMac in Safe Mode to install from the USB drive/stick).

If Bluetooth problems still occur: you might try to reset the Bluetooth Module: Shift-alt click onto the Bluetooth-icon in the top menu bar, then -in the upcoming Debug-menu- choose Reset Bluetooth Module (probably not word-for-word, I'm not on a US/en OS).

If you have troubles with a cabled USB-2 mouse, you might try to reset SMC, which controls the USB-busses ( https://support.apple.com/en-us/HT201295 ). (I'm assuming that you already tried other USB-ports for the mouse. As I stated earlier, one of my issues after the SecUpd was a failing power support for one Thunderbolt/USB-C port, which I could fix with the SMC Reset).

Good luck for the moment,

cheers, Roger

I can confirm, as well, that the BridgeOS Kernel Panic remains after updating with Security Update 2020-004 for Mojave and the Safari update that popped with it. Running Safari 100% results in the KP from the subsequent cold start.

Since my last post I came across something quite informative. Someone who dealt with AppleCare in Australia was told the following:

"1. Apple is aware of this bug but Apple engineers are NOT actively doing anything about it.

2. Support person found an internal technical bulletin from some time back that basically said the solution was to upgrade to Catalina."

The poster was Lasthenia and you can find the full post here:

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

At the end of this thread, Kabaldan reports that installing the Big Sur beta performs a firmware update on the T2, taking it to BridgeOS 5.0. Kabaldan further reports that the BridgeOS KPs disappeared, which Nymunariya replicated. So perhaps lobbying for BridgeOS 5.0 for the rest of us might be a decent strategy.

Do you have a Time Machine backup to Restore to/from?

https://support.apple.com/guide/mac-help/revert-to-a-previous-macos-version-mh15216/mac

Same here (Mac Mini (2018) running MacOS 10.14.6 Mojave) - bug reports after 2020-002 security update . But it's interesting, that if you won't open Safari app, this bug not happening.

Hello everyone,

I too experience issues on a 2018 Mac mini running Mojave .14.6 since I ran the Security Update 2020-002.

First, I noticed a failing power support for one Thunderbolt port. To fix this, I did a SMC reset, which did cure the power supply issue but introduced an issue whenever I set the Mac to sleep or shut it down: on setting to sleep, it mostly restarts and presents me a Kernel Panic report. When I shut the computer down, I'm presented a similar report the next time I start the Mac up.

Reports are always related to "BridgeOS", which obviously is the firmware for the T2-chip.

I've tried several SMC resets with all peripherals disconnected (except screen, mouse, keyboard), the 10 sec reset, everything to no avail.

I've found other users with similar issues in a german user forum, so everything seems to strongly indicate that this Security Update introduced some severe issues for certain users.

So far, I'm holding back from installing the Mojave Combo Updater or even to do a clean install of Mojave .14.6, simply because I actually suspect that the firmware will not be reset to the BridgeOS version that originally came with 10.14.6.

Also, at least one user in the german forum already tried a Mojave install, but continues to have these Kernel Panics.

This actually leads me to the conclusion, that only Apple can fix this with a new update for the BridgeOS.

The Security Update 2020-002 had changes for Mojave for IOThunderboltFamily and Kernel, so it might be that Apple fixed some issues within these but introduced new ones for other users/setups.

I'm actually preparing a bug report and really hope that Apple already works on this frustrating issue.

Hello Stephen,

thank you for coming back to this thread and also for the link to the Macrumors forum!

I'm curious if your backup will fix this. But honestly, I'm a bit sceptic as I imagine that the BridgeOS is probably installed on a permanent memory area within the T2 chip. And I'm doubtful, if a backup will restore that memory area too. (It's i.e. often the case that installers don't overwrite pieces of software that are newer than the software the installer would install itself).

As a fresh Mojave install did not fix the issue for one user over at a german Mac forum, this seems an indication that the BridgeOS/T2 firmware is written directly into the chip and is not being replaced with a "simple" reinstallation of macOS.

But on the other side, it seems that a clean install had resolved the issue for one user at the Macrumors forum, when I'm interpreting a posting over there correctly. At least until he reinstalled the SecUpd.

The actual build number of BridgeOS (after the SecUpd 2020-002) reads 17P4263, according to the user who tried the re-installation, it was 17P2551 before. (Can be checked either in the Panic report itself, or by "System Informations > Hardware > Controller" {most likely different on non-english OS, it's "Steuerung" on german macOS}, but one will notice the mentioning of the T2 Secure chip anyway).

For me, the Mojave 10.14.4 update firstly introduced issues with the USB/Thunderbolt Bus. Apple fixed problems with USB-Audio Interfaces at that time, but effectively rendered a passive LMP USB-3 4-port hub useless for me, as this then introduced a repetitive mouse stuttering every few seconds. This issue still does apply as of today (when I check the hub out of curiosity), so I was forced to buy an active USB-2 hub instead.

Am using Macs for over 20 years now and also have the feeling that the overall quality has somewhat dropped. Or Apple feels pressed to release software with more and more features, even when it's not yet entirely tested.

At this time, I think I will still wait a while for a fix through Apple prior to doing a clean install…

All the best for your attempt, take your time. It's ready when it's ready.

Best regards,

Roger Simon

I am also running a 2018 Mac Mini and every time I boot up, I get the "Your computer was restarted because of a problem" message. I have been sending the details to Apple so they hopefully will address it.

I have not had the issue with my machine randomly restarting but that may be because I do not allow it to go to sleep on it's own. I have heard the restart issue is related to sleep mode. There is a way to turn that off, which I have done. Maybe you can try this setting on the Energy Saver control panel to see if it fixes it for you.

Hope this helps.

This is a shoutout to everyone who posted here for their efforts and communication. Much appreciated!

I purchased a refurbished 2020 (aka 2018) Mac Mini last week. Not wanting to deal with Catalina yet I downgraded to Mojave, performed the updates immediately and was greeted in short order with this BridgeOS Kernel Panic. Not knowing what was going on and fearing that there was something hidden in the TimeMachine backup from my old 2012 Mac Mini (High Sierra) that Mojave wasn't liking, I wasted time looking for some sort of software conflict, undertaking the usual solutions and experienced ongoing frustration until I found this discussion.

Not using Safari has done the trick for now. In spite, I removed Safari from the dock and replaced it with Microsoft Edge.

Again, many thanks!

After giving up on a solution by Apple for Mojave, I decided to upgrade to Catalina {macOS 10.15.6 (19G2021) - T2 firmware 17P6610}. It's now one week and I haven't had one single BridgeOS crash with sleep and shut down (after launching Safari once before) and it's possible again to disconnect the eGPU by the top bar menu command or turning it on while Mac is running without macOS crashing.

The downside: lost one application (needed to buy another) and am now paying subscription for another.

Got response about the Rebuild: Launch Services task in Onyx: it just seemed to have helped az the beginning. But the user is now „back to the problems he had before“. It’s not a big surprise, as Launch Services just resets the links between files and applications.

For a user bug report, I’m using Apples Product Feedback page:

https://www.apple.com/feedback/

in this case for macOS:

https://www.apple.com/feedback/macos.html

The „Comments“ section is limited and only allows for a pretty compressed description of what is happening, but Apple comes back to the user, if the bug is somewhat new to them or they already know it but are still gathering more input.

Meanwhile I do think that only Apple can provide a fix for all these issues, I don’t think that there is a way to resolve these with approaches based on i.e. software that does not even „know“ the changes that the SecUpd introduced in various areas. Especially when Firmware and the T2 is involved.

Most issues seem related to either sleep or shut down routines where the affected Mac simply crashes and restarts or comes up with Panic Reports on the next start up.

For me, these issues were obviously invoked by the SMC reset I did when I had noticed that the power supply for the most inward Thunderbolt port (the one next to HDMI) failed. As the Security Update was the only change between this port working and not working, it quickly felt related.

IOThunderboltFamily and Kernel have had changes within the SecUpd, the T2 holds the SMC controller, so I really think that only Apple can actually repair what they broke.

<OT>

in regard to the macOS UI, I do miss the "classic" coloured labels, as I find myself often to just ignore the coloured dots. They do not draw enough attention to themselves and just aren't that helpful anymore.

Other than that I wouldn't like to have more colours within the UI itself, as I tend to perceive them as too distractive. Nearly all of the pro apps I'm using come with dark interfaces, some are quite good, some not that good. macOS Dark Mode isn't my favourite on computers, but I prefer Dark Mode on iOS devices.

Overall it's a subjective opinion, Apple just can't fulfil the wishes of everyone. Personally, my top priority would be that they only release stable, highly performing software. Sadly, they fell short on this lately.

</OT>

A follow-up here on Friday 10 April 2020 -- I left my Mac "on" with the settings as you suggested (i.e. cannot go into "sleep" mode) -- overnight, actually for over 12 hours and this morning the Mac display came on and the Mac had not gone into "kernel panic restart"!!

So this is a lifesaver for now. I do believe that if I do a standard SHUTDOWN and then start my Mac, I will get the little notice that the Mac has a problem…… I'll test that later but for now with this working I'm just leaving it and crossing my fingers that Apple issues a full fix / new Security UpDate or whatever they need to do--- and soon.

Thanks again for your post and to everyone who is posting here.

Best regards,

Steve Schulte

Friday 10 April 2020

I am having a similar situation - but mine is a kernel panic (unwanted shutdown / restart by my Mac Mini) -- see this MacRumors link: https://forums.macrumors.com/threads/mac-mini-2018-kernel-panic-bug_type-210-after-security-update-2020-002.2228812/

It seems this security update 2020-002 went out 24 March 2020. I've noticed kernel panics since about that date. Mac Mini (2018) running MacOS 10.14.6 Mojave.

Are you noticing unwanted shutdowns or restarts on your Mac.

Perhaps some others can post here if they are seeing issues.

I've tried all the "cures" for kernel panics-- nothing works so I am really thinking these issues are directly related to the 2020-002 security update.

Looking for more feedback or reference to any other post(s) on this issue if there are any.

Best regards,

Steve Schulte

Monday 6 April 2020