2018 MacBook Pros crashing with "Bridge OS" error

[marina1984]

Plug the charger on the right side of the computer, not the left side.
Apparently solved for me, after months of trials

 

[MRrainer]

Really?
I only have one power-inlet for my MacMini

 

[filmak]

Really?
I only have one power-inlet for my MacMini

If you are jealous, you can always buy a MacBook Pro so you can use the right ports.

 

[hawkeye_a]

Well, happened again today. This was the second time, and about two and a half months since the first.

10.15.4, BridgeOS 4.4.

Woke from sleep, touchid to login, plugged in an external-portable-hdd, and it froze, fans spun up and it shutdown.

 

[me55]

Latest macOS update (10.15.5 19F96) includes a T2 firmware update: 17P5290.

EDIT: Supplemental Updates bumps it up to: 19F101, 17P5300.

 

[MRrainer]

I've now resorted to just shutdown my Mini every evening. That way, I also don't have to cover the blue LED of my TimeMachine backup drive and the white "Power On" LED of the Mini is also off (which is annoying, if you sleep in the same room).

 

[MRrainer]

{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.6 (18G5033)","os_version":"Bridge OS 4.5 (17P5290)","macos_system_state":"sleep","incident_id":"F58B253E-911E-46BB-A828-4CAA846FD073","timestamp":"2020-05-28 17:50:24.00 +0000","bug_type":"210"}

10.14.6 (18G5033)

It's not over, yet.

 

[RumorConsumer]

I take it by your lack of a witty response that you have tried to boot from your clone and found that you can't. Neither can you boot into your recovery partition to do a restore should something go wrong and that becomes necessary.

The T2 chip prevents this unless you disable some of its security settings. I've posted how in other threads.

Maybe you think that disabling security settings is a good idea. I don't.

BTW, Time Machine works every hour, not just when I'm asleep. APFS Snapshots will do a complete System Restore in a few minutes and requires TM. Yes, I know that the cloneware now "works with Time Machine" — it has to or certain APFS functionality cannot work. One more reason I can state that cloning is not necessary.

Yes, those horrible HDDs in old Time Capsules caused TM problems and there was that bug in OS 10.9.4. So what? Every time a major OS upgrade happens, the cloneware developers tell you not to use it till they figure out how to make their products work again.

I don't care if you and the other cloneware fan boy bullies around here want to pay for something that isn't needed by anyone but your constant insistence that it's necessary is you spreading nonsense. Stop it.

I have no problem with stating facts in the light of misinformation and I am most definitely Not going away.

Not for nothing but Cloneware is actually shockingly helpful in business production environments where legal is a factor and you may need to clone a computer that is about to be re-purposed and you want the exact state preserved for legal purposes. Nothing beats a read-only disk image and unfortunately disk utility is kind of a broke ass you know what at this point so carbon copy cloner it is

 

[groove-agent]

Plug the charger on the right side of the computer, not the left side.
Apparently solved for me, after months of trials

I'm going to try that. Thanks.

Yesterday when I hooked up my 2019 16" MBP, I couldn't get it to recognize the charger. I was a little concerned because I'm right in the middle of my last school assignment and didn't want to take it in and potentially lose use. I then found out that only the back two USB ports (on left and right side) were affected. I shut down the laptop, then turned it back on and everything was fine again.

My 16" has been crashing when waking up with an external monitor since I bought it last October. Fortunately I haven't lost any work ... yet.

 

[Dev Tyagi]

Hi,
can anyone read this log for me?
Catalina 10.15.4
macbook pro 2018 2.6ghz

panic(cpu 0 caller 0xfffffff00f0c24d4): "i2c1::_checkBusStatus SCL is stuck low; last write status 00010108 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-tas5770L-spkr-woofer-r"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleS5L8940X/AppleS5L8940X-169.0.1/AppleS5L8940XI2C.cpp:351
Debugger message: panic
Memory ID: 0xff
OS version: 17P4263
macOS version: 19E266
Kernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010
Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0xe
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xec
x86 Previous Power Transitions: 0x70604000200
PCIeUp link state: 0x94721614
Paniclog version: 13
Kernel slide: 0x0000000006e70000
Kernel text base: 0xfffffff00de74000
mach_absolute_time: 0x9b8ffb52
Epoch Time: sec usec
Boot : 0x5e933b4e 0x000ed480
Sleep : 0x5e933b95 0x00029a86
Wake : 0x5e933cb6 0x0002687c
Calendar: 0x5e933cd8 0x000923dc

Panicked task 0xffffffe0011f4600: 664 pages, 9 threads: pid 40: bridgeaudiod
Panicked thread: 0xffffffe00157b4d0, backtrace: 0xffffffe015ba2920, tid: 1203
lr: 0xfffffff00e738764 fp: 0xffffffe015ba2960
lr: 0xfffffff00e7385c0 fp: 0xffffffe015ba29d0
lr: 0xfffffff00e852e7c fp: 0xffffffe015ba2a80
lr: 0xfffffff00ed0162c fp: 0xffffffe015ba2a90
lr: 0xfffffff00e737f28 fp: 0xffffffe015ba2e00
lr: 0xfffffff00e738280 fp: 0xffffffe015ba2e50
lr: 0xfffffff00f56e8f8 fp: 0xffffffe015ba2e70
lr: 0xfffffff00f0c24d4 fp: 0xffffffe015ba2ef0
lr: 0xfffffff00f0c1d38 fp: 0xffffffe015ba2f80
lr: 0xfffffff00f0c18d4 fp: 0xffffffe015ba2fb0
lr: 0xfffffff00f0c1570 fp: 0xffffffe015ba2ff0
lr: 0xfffffff00ed78d04 fp: 0xffffffe015ba3010
lr: 0xfffffff00ed78b6c fp: 0xffffffe015ba3040
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba30b0
lr: 0xfffffff00ed79530 fp: 0xffffffe015ba3110
lr: 0xfffffff00f058898 fp: 0xffffffe015ba3190
lr: 0xfffffff00f058698 fp: 0xffffffe015ba3220
lr: 0xfffffff00f0596e8 fp: 0xffffffe015ba3250
lr: 0xfffffff00f536844 fp: 0xffffffe015ba3280
lr: 0xfffffff00f536998 fp: 0xffffffe015ba3290
lr: 0xfffffff00f06df4c fp: 0xffffffe015ba32c0
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba3330
lr: 0xfffffff00f04e158 fp: 0xffffffe015ba33d0
lr: 0xfffffff00f05307c fp: 0xffffffe015ba3480
lr: 0xfffffff00f052d40 fp: 0xffffffe015ba34d0
lr: 0xfffffff00f052a0c fp: 0xffffffe015ba3530
lr: 0xfffffff00ec6e970 fp: 0xffffffe015ba3580
lr: 0xfffffff00f07b6a8 fp: 0xffffffe015ba35e0
lr: 0xfffffff00ec70ec4 fp: 0xffffffe015ba3650
lr: 0xfffffff00f07b450 fp: 0xffffffe015ba36d0
lr: 0xfffffff00ec9f00c fp: 0xffffffe015ba3860
lr: 0xfffffff00e8228d0 fp: 0xffffffe015ba3980
lr: 0xfffffff00e73df24 fp: 0xffffffe015ba39e0
lr: 0xfffffff00e713cf0 fp: 0xffffffe015ba3a60
lr: 0xfffffff00e72bc7c fp: 0xffffffe015ba3b10
lr: 0xfffffff00e849760 fp: 0xffffffe015ba3bd0
lr: 0xfffffff00e852fd4 fp: 0xffffffe015ba3c80
lr: 0xfffffff00ed0162c fp: 0xffffffe015ba3c90
lr: 0x0000000192a27198 fp: 0x0000000000000000

Hey ! I'm having the EXACT same issue. I just figured out that the mac crashes whenever I try to play any kind of sound (Using the internal speakers). If I plug in my headphones, the macbook works perfectly fine! It didn't crash even once while using with the headphones! The problem only occurs whenever internal speakers are used.
If you find any solution for this please let me know, Till then I guess we have to use our systems with a headphone plugged in all the time

 

[stormseq]

Hi guys,
anyone else having this exact same crash log? So far me and the above user Dev Tyagi above are having exact same panics, he mentioned it is due to the built in speakers, for example when you copy a file there is a notification sound, or when you plug in a charger, this could be the reason my mbp would crash after me trying to copy files, play youtube and the third problem is when i put it to sleep and wake up it crashes.

Dev has found a workaround, he keeps his headphones plugged in and like that it wont crash, also he charges when laptop is switched off?? This could be the reason why my mbp works completely fine in safe mode, because audio is disabled there. I can copy as many files i want and even browse.

I am going to do further testing with this new info.
If anyone else is having exact same problem this could be a workaround, also kindly comment and discuss. thanks.






panic(cpu 0 caller 0xfffffff0101564d4): "i2c1::_checkBusStatus SCL is stuck low; last write status 00010108 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-tas5770L-spkr-woofer-r"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleS5L8940X/AppleS5L8940X-169.0.1/AppleS5L8940XI2C.cpp:351
Debugger message: panic
Memory ID: 0xff
OS version: 17P4281
macOS version: 19E287
Kernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010
Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xec
x86 Previous Power Transitions: 0x70707060400
PCIeUp link state: 0x1614
Paniclog version: 13
Kernel slide: 0x0000000007f04000
Kernel text base: 0xfffffff00ef08000
mach_absolute_time: 0x7a282030
Epoch Time: sec usec
Boot : 0x5ed152d3 0x000e3aa9
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x5ed15325 0x000367a9

Panicked task 0xffffffe0014f2600: 674 pages, 7 threads: pid 40: bridgeaudiod
Panicked thread: 0xffffffe00182d520, backtrace: 0xffffffe0167ca920, tid: 1029
lr: 0xfffffff00f7cc764 fp: 0xffffffe0167ca960
lr: 0xfffffff00f7cc5c0 fp: 0xffffffe0167ca9d0
lr: 0xfffffff00f8e6e7c fp: 0xffffffe0167caa80
lr: 0xfffffff00fd9562c fp: 0xffffffe0167caa90
lr: 0xfffffff00f7cbf28 fp: 0xffffffe0167cae00
lr: 0xfffffff00f7cc280 fp: 0xffffffe0167cae50
lr: 0xfffffff0106028f8 fp: 0xffffffe0167cae70
lr: 0xfffffff0101564d4 fp: 0xffffffe0167caef0
lr: 0xfffffff010155d38 fp: 0xffffffe0167caf80
lr: 0xfffffff0101558d4 fp: 0xffffffe0167cafb0
lr: 0xfffffff010155570 fp: 0xffffffe0167caff0
lr: 0xfffffff00fe0cd04 fp: 0xffffffe0167cb010
lr: 0xfffffff00fe0cb6c fp: 0xffffffe0167cb040
lr: 0xfffffff00fd04ec4 fp: 0xffffffe0167cb0b0
lr: 0xfffffff00fe0d530 fp: 0xffffffe0167cb110
lr: 0xfffffff0100ec898 fp: 0xffffffe0167cb190
lr: 0xfffffff0100ec698 fp: 0xffffffe0167cb220
lr: 0xfffffff0100ed6e8 fp: 0xffffffe0167cb250
lr: 0xfffffff0105ca844 fp: 0xffffffe0167cb280
lr: 0xfffffff0105ca998 fp: 0xffffffe0167cb290
lr: 0xfffffff010101f4c fp: 0xffffffe0167cb2c0
lr: 0xfffffff00fd04ec4 fp: 0xffffffe0167cb330
lr: 0xfffffff0100e2158 fp: 0xffffffe0167cb3d0
lr: 0xfffffff0100e707c fp: 0xffffffe0167cb480
lr: 0xfffffff0100e6d40 fp: 0xffffffe0167cb4d0
lr: 0xfffffff0100e6a0c fp: 0xffffffe0167cb530
lr: 0xfffffff00fd02970 fp: 0xffffffe0167cb580
lr: 0xfffffff01010f6a8 fp: 0xffffffe0167cb5e0
lr: 0xfffffff00fd04ec4 fp: 0xffffffe0167cb650
lr: 0xfffffff01010f450 fp: 0xffffffe0167cb6d0
lr: 0xfffffff00fd3300c fp: 0xffffffe0167cb860
lr: 0xfffffff00f8b68d0 fp: 0xffffffe0167cb980
lr: 0xfffffff00f7d1f24 fp: 0xffffffe0167cb9e0
lr: 0xfffffff00f7a7cf0 fp: 0xffffffe0167cba60
lr: 0xfffffff00f7bfc7c fp: 0xffffffe0167cbb10
lr: 0xfffffff00f8dd760 fp: 0xffffffe0167cbbd0
lr: 0xfffffff00f8e6fd4 fp: 0xffffffe0167cbc80
lr: 0xfffffff00fd9562c fp: 0xffffffe0167cbc90
lr: 0x00000001cdf4f198 fp: 0x0000000000000000

 

[hometux]

I had also this Kernel Panics with my new Mac Mini 2018 (from February) after Mojave Security Update 2020-002 too, no changes also with 2020-003.

4 Weeks ago I talked three times with Apple Support remote assistance included without success.
Safe start, disable all 3rd party Kext's and some other tweaks but nothing helped to avoid the reproducible crashes 2 Minutes after entering sleep mode.

The Apple Support suggest upgrade to Catalina as last option to get further support (only for the actual macOS).
Two weeks ago I try it against my preferation for Mojave.

But finally I could hopefully say the cashes vanished with upgrade to Catalina 10.15.5. I didn't need any further call to Apple. Not a nice solution for anybody (who need 32Bit Software example) but my Mac Mini 2018 come back to normal behavior.

What I not understand, a MBP 2018 MBP (has a T2 Bridge OS like the Mini 2018 too) with completly the same Software, a MBP2017 and Macbook 2017 with similar installations working all like a charm without any crashes under Mojave 10.14.6. 2020-003

Strange.

 

[me55]

Haven't had any T2 crashes (or any crashes at all) in a looooooong time, so I'm happy. Mojave for me was craptastic anyways, Catalina runs so much better (2018 15" MBP).

macOS 10.15.6 19G73 includes another T2 update to 17P6065.

 

[MRrainer]

Still crashes here.

{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.6 (18G6020)","os_version":"Bridge OS 4.6 (17P6065)","macos_system_state":"sleep","incident_id":"F0BBAF11-6487-4A7C-9771-73C05744B291","timestamp":"2020-08-16 06:07:53.00 +0000","bug_type":"210"}

 

[matram]

Look for the panic string further down in the log, it may give you more useful information.

 

[Jazzrabbitslim]

Haven't had any T2 crashes (or any crashes at all) in a looooooong time, so I'm happy. Mojave for me was craptastic anyways, Catalina runs so much better (2018 15" MBP).

macOS 10.15.6 19G73 includes another T2 update to 17P6065.

mine is MacBook Pro 15 inch 2019, i7
I updated to 10.15.6,
Now I can plug in a small USB type-c hub to HDMI monitor like normal.Still I dare not to turn on to many T2 related functions...
However, it is weird that my screen goes dark after log in when it is connected with my USB C Samsung T5 SSD when on battery.
If it is plugged in or fully charged, no such issue. I tried not using direct usb type c to type c, switching to USB 3.0 A adapter then it seems better.
May be power issue?

 

[tommybanana]

Just upgraded by accident to 10.15.7.

Random T2 OSBridge Crash/Restarts are back! Hadn't had one for months......

 

[Iritscen]

I updated when 10.15.7 came out and immediately regretted it because my fans spun up to almost maximum and the computer was running hot 100% of the time. Turned out that I had stumbled into the notorious accountsd bug. After fiddling around trying to fix it, a simple restart seemed to do the trick.

Since then the computer has run fine and I haven't had any Bridge crashes. That being said, I turn my MBP off each night because it seems to me that leaving it running/asleep for days at a time increases the odds of a T2 hang on shutdown. It might be superstition, but I haven't had a hang in a while. Now that I've said this, I'll probably have one tonight when I shut down, but so far things have been solid since my update on 9/28.

 

[KDLM]

I'm coming back to this thread after a long time. I had bought a MBP that experienced the T2 chip panics. I exchanged it for another that had the same problems, and then bought an earlier MBP that did not have the T2 chip. I'd like to update my MBP now to the current MBP (I guess it would be a 2019 or 2020?). Before I do that, can anyone tell me if the 2020 MBP is subject to the same T2 chip problems?

 

[whg]

I'm coming back to this thread after a long time. I had bought a MBP that experienced the T2 chip panics. I exchanged it for another that had the same problems, and then bought an earlier MBP that did not have the T2 chip. I'd like to update my MBP now to the current MBP (I guess it would be a 2019 or 2020?). Before I do that, can anyone tell me if the 2020 MBP is subject to the same T2 chip problems?

I think that you should be save with T2 today. I have a Mac mini, MBP 13" and MBP 16" with T2 chips, all running the latest Catalina without any issues. I also used all of those with eGPU connected to an external 5k display without overheating (common complaint for 16").

 

[KDLM]

I think that you should be save with T2 today. I have a Mac mini, MBP 13" and MBP 16" with T2 chips, all running the latest Catalina without any issues. I also used all of those with eGPU connected to an external 5k display without overheating (common complaint for 16").

I did some more reading after I posted. I guess they are about to introduce a new 16" Macbook Pro before the end of this year. Maybe I should wait?

 

[Iritscen]

To be clear, there's no 16" 2020 MBP, only a 13" model released in May 2020, so if you're looking for a 16" model you should wait for a refresh. According to MacRumors, there's an average of 322 days between MBP refreshes, and it's been 347 days since the 2019 16" MBP came out.

To give an update on my last post, I do still occasionally have T2 freezes when shutting down my 16" 2019 MBP each night, but they seem rarer since the 10.15.7 update. I also now have a habit of waiting about ten seconds after choosing  > Shut Down…, letting the timer in the dialog count down from 1 minute to about 50 seconds before confirming that I want to shut down. The idea is to let the processes finish which run when you choose to shut down. I don't know what the OS does when you call up that dialog, but I can see disk and CPU activity using iStat Menus. Waiting several seconds at that point may be contributing to a more orderly and stable shutdown process.

 

[BevLA]

I've been having these same issues on my 2019 13" MacBook Air. At first it would just be black when I opened up the computer. Apple restored (not a complete wipe/restore) of Mojave for me. It was fine for a few weeks, now if I leave the Mac closed and unattended for a few hours, or overnight, it restarts due to an "error." First portion of Log report reads, "Log states- {"caused_by":"macos","macos_version":"Mac OS X 10.14.6 (18G6032)","os_version":"Bridge OS 4.6 (17P6610)","macos_system_state":"running","incident_id":"0AD3F42F-98D2-4739-855B-CDA7BDE41564","timestamp":"2020-12-15 02:17:06.00 +0000","bug_type":"210"}"

Seems as if I log out of my primary user, and sign in with the "Fix" user, then close up, I do not get an error log, but I do have to log in again in the morning. During my research, I've seen these same issues since 2018. I'm afraid to update to Catalina because it doesn't sound like it fixes the problem, and yet I would have to find replacement software for some of my 32bit apps. Would upgrading be worth it?

Any help is appreciated.

 

[RumorConsumer]

I've been having these same issues on my 2019 13" MacBook Air. At first it would just be black when I opened up the computer. Apple restored (not a complete wipe/restore) of Mojave for me. It was fine for a few weeks, now if I leave the Mac closed and unattended for a few hours, or overnight, it restarts due to an "error." First portion of Log report reads, "Log states- {"caused_by":"macos","macos_version":"Mac OS X 10.14.6 (18G6032)","os_version":"Bridge OS 4.6 (17P6610)","macos_system_state":"running","incident_id":"0AD3F42F-98D2-4739-855B-CDA7BDE41564","timestamp":"2020-12-15 02:17:06.00 +0000","bug_type":"210"}"

Seems as if I log out of my primary user, and sign in with the "Fix" user, then close up, I do not get an error log, but I do have to log in again in the morning. During my research, I've seen these same issues since 2018. I'm afraid to update to Catalina because it doesn't sound like it fixes the problem, and yet I would have to find replacement software for some of my 32bit apps. Would upgrading be worth it?

Any help is appreciated.

Just because your BridgeOS is crashing doenst meant youre have the same issue as was contained in this thread. You might just have some funky issue that is simply triggering a Bridge OS crash. So, Im a little unclear, does this happen with your user only and not the "fix" user? That would imply some kind of software issue...

 

[BevLA]

I did not receive an error code during the 2 weeks that I logged out of my main user, & logged into my "fixit" user account before closing up. Within days of returning to my regular account, the restarting due to Bridge error started again. I would love to delete this Bridge thing, "Bridge OS 4.6 (17P6610)", but can’t find it.