2018 MacBook Pros crashing with "Bridge OS" error

[shawndebnath]

Panicked task 0xffffffe0007c8b90: 2515 pages, 166 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000b6a540, backtrace: 0xffffffe016993530, tid: 332\n\t\t lr: 0xfffffff00aff88f0 fp: 0xffffffe016993670\n\t\t lr: 0xfffffff00aee15f4 fp: 0xffffffe016993680\n\t\t lr: 0xfffffff00af13a44 fp: 0xffffffe0169939f0\n\t\t lr: 0xfffffff00af13dd4 fp: 0xffffffe016993a50\n\t\t lr: 0xfffffff00af15914 fp: 0xffffffe016993a70\n\t\t lr: 0xfffffff00a6ab984 fp: 0xffffffe016993ae0\n\t\t lr: 0xfffffff00a6adbc8 fp: 0xffffffe016993b80\n\t\t lr: 0xfffffff00a6ab13c fp: 0xffffffe016993c00\n\t\t lr: 0xfffffff00a66aaa4 fp: 0xffffffe016993c30\n\t\t lr: 0xfffffff00b370764 fp: 0xffffffe016993c60\n\t\t lr: 0xfffffff00b3700bc fp: 0xffffffe016993c90\n\t\t lr: 0xfffffff00aeec500 fp: 0x0000000000000000\n\n",
"processByPid" : {

@StudioSanctum based on "tid: 332" can you search for 332 in your report which should bring you to a section like this:

          "332": {
            "userTime": 0.704289875,
            "systemTime": 0,
            "system_usec": 0,
            "id": 337,
            "basePriority": 81,
            "user_usec": 704289,
....         

            "schedPriority": 81,
            "name":
...

What does the name field say in your report?

 

[MBAir2010]

jeez louse, i just purchased a Macbook pro 2018 16 GB ram, 512 ssd, apple careless, and when i opened the lid, excessive cockroaches and locus started swarming and infested our entire neighborhood block, word!
the local news, government and pest control helicopters are hovering my apartment complex, its worse than Detroit!

Im gonna be on TV!
Im gonna be on TV!

 

[dspdoc]

@StudioSanctum based on "tid: 332" can you search for 332 in your report which should bring you to a section like this:

          "332": {
            "userTime": 0.704289875,
            "systemTime": 0,
            "system_usec": 0,
            "id": 337,
            "basePriority": 81,
            "user_usec": 704289,
....        

            "schedPriority": 81,
            "name":
...

What does the name field say in your report?

"332" : {
"basePriority" : 81,
"id" : 332,
"kernelFrames" : [
[
0,
68838046276
],
[
0,
68838047188
],
[
0,
68838054164
],
[
0,
68829231492
],
[
0,
68829240264
],
[
0,
68829229372
],
[
0,
68828965540
],
[
0,
68842620772
],
[
0,
68842619068
],
[
0,
68837885184
]
],
"name" : "AppleSMC",
"schedPriority" : 81,
"state" : [
"TH_RUN"
],
"system_usec" : 0,
"systemTime" : 0,
"user_usec" : 71593,
"userTime" : 0.071593875000000001
},

 

[Qaulity]

I have been studying the problems reported and have done some independent research.
I think the tell-tale aspect of the problem are the CATERR and Global Reset syndromes in the panic reports.

In my view, the problem is for Apple to update BridgeOS to handle the error signals (they have been updated) and provide extended diagnostic reporting.

Intel have a "Processor Reorder Buffer (ROB) Timeout Debug Guide". In there, they explain how a CATERR signal is sent instead of IERR or MCERR, and so system management code needs to be updated to match. They describe particular registers that characterise the nature of the problem; these should be provided to the panic code handler. They also list a good set of debug techniques for such scenarios.

My 2017 MBP has been crashing this past week due to those errors. Only when sleeping. Didn’t think much of it since I’m selling it but when i disabled all power saving features the problem went away. Obvious note, it does not contain the T2 chip.

 

[MasterStormcrow]

Do you put it to sleep (lid closed) without power, nothing connected to it, regularly? and open it before connecting anything to it? That's my daily routine and it crashes 90% of the time. The only thing I have not disabled is FileVault, and I won't disable due to the nature of the data on my drive.

Hello,

I leave the lid of my 2018 MacBook Pro i9/2tb/32gbram both up and closed while connected to power and while on battery with default settings while at both work and home. I have filevault enabled and firmware password enabled from within recovery (command R) with default firmware password security settings selected. The only peripherals I connect regularly to the mbp is the blackmagic design egpu with the LG 5k ultrafine display connected to the blackmagic design egpu's thunderbolt 3 port at both home and work.

Best,

W

 

[shawndebnath]

"332" : {
"basePriority" : 81,
"id" : 332,
"kernelFrames" : [
],
"name" : "AppleSMC",
},

Looks like in your case, its the SMC thread that's crashing as well. Seems like inside the firmware for T2, there's some interaction with SMC which is faulty/buggy. Pure guesses based on what I glean from the reports.

 

[dspdoc]

Looks like in your case, its the SMC thread that's crashing as well. Seems like inside the firmware for T2, there's some interaction with SMC which is faulty/buggy. Pure guesses based on what I glean from the reports.

So in your opinion is this hardware or software? Bear in mind this is the 2nd iMac Pro I have had.

 

[shawndebnath]

So in your opinion is this hardware or software? Bear in mind this is the 2nd iMac Pro I have had.

Take it with a grain of salt, but likely software/firmware. Given the number of people that have replaced their macbooks over the time period with different configurations and continue to see the issue, it's sure to rule out quality issues in certain batches of T2. I feel stronger about software glitch b/c it satisfies the case where incorrect state is built up over time as people plug in / remove different hardware to the macbook eventually leading to a kernel panic. Would be interesting to see after doing a SMC & NVRAM whether a macbook with no external accessories (USB or bluetooth) survives longer than one with accessories plugged in.

Or I could be very wrong and there is a fundamental defect in the chip that has gone unnoticed by Apple. Unlikely, but if that's the case, I am sure Apple will offer free replacements/fixes down the road. Keep in mind, certain hardware defects can be worked around in software too.

 

[dspdoc]

Take it with a grain of salt, but likely software/firmware. Given the number of people that have replaced their macbooks over the time period with different configurations and continue to see the issue, it's sure to rule out quality issues in certain batches of T2. I feel stronger about software glitch b/c it satisfies the case where incorrect state is built up over time as people plug in / remove different hardware to the macbook eventually leading to a kernel panic. Would be interesting to see after doing a SMC & NVRAM whether a macbook with no external accessories (USB or bluetooth) survives longer than one with accessories plugged in.

Or I could be very wrong and there is a fundamental defect in the chip that has gone unnoticed by Apple. Unlikely, but if that's the case, I am sure Apple will offer free replacements/fixes down the road. Keep in mind, certain hardware defects can be worked around in software too.

For as long as this has been going on Apple sure does seem tight lipped about it. You would think at this point they would at least publicly acknowledge this.

 

[Scythe]

Had my first BridgeOS crash today after leaving my 2018 MBP sleeping for 12hrs+ disconnected from power for the first time. System had rebooted and had my apps open when I got back to it, so I hadn't realised.

 

[shawndebnath]

For as long as this has been going on Apple sure does seem tight lipped about it. You would think at this point they would at least publicly acknowledge this.

Yeah true, but look at it from the business' point of view. The number of folks encountering and voicing their issue perhaps is in the minority and its hard to tell since we don't know how many units were shipped out. But as a company, I am sure there are folks looking into this issue before it blows up in their face in an uncontrolled manner (especially, if some people were reached out to by engineers).

What would help is if we could narrow it down to a set of consistently reproducible steps. Give this to an engineer and that will get brains ticking on how to correctly solve it - better yet, engineering managers can then jump in and do their part of "is it done yet?" :-D Otherwise, it typically results in the "we are trying and we don't have a root cause yet" loop.

 

[MacUser18095]

What would make you think it would be more or less of a problem? It’s a T2 problem. Not a screen size problem. If the machine has a T2 chip it has the issue. Even the iMP.

The only reason I asked because it seems most of the users here own 15 inch. There is nothing logical I know.

 

[dspdoc]

Had my first BridgeOS crash today after leaving my 2018 MBP sleeping for 12hrs+ disconnected from power for the first time. System had rebooted and had my apps open when I got back to it, so I hadn't realised.

Welcome to the party! *Here is your hat

 

[shawndebnath]

Had my first BridgeOS crash today after leaving my 2018 MBP sleeping for 12hrs+ disconnected from power for the first time. System had rebooted and had my apps open when I got back to it, so I hadn't realised.

Can you dig in and see if yours is AppleSMC as well? You can find how to look it up here:

https://forums.macrumors.com/thread...bridge-os-error.2128976/page-31#post-26358890

Welcome to the party! *Here is your hat

Hahaha. We should design and sell a hat / t-shirt on Cafe Press

 

[dspdoc]

Someone please tell me this is not true.

 

[CreeptoLoser]

View attachment 776468

Someone please tell me this is not true.

You would have to be in alternative facts territory to believe Mojave and Apple's desktop apps are built by a few part timers.

 

[dspdoc]

You would have to be in alternative facts territory to believe Mojave and Apple's desktop apps are built by a few part timers.

I hope you are correct, but with the current state of things I would not be surprised.

 

[AZhappyjack]

I hope you are correct, but with the current state of things I would not be surprised.

I would seriously suggest emailing Craig Federighi with your story. I had a problem with Mail several releases back (IIRC, it was Mavericks)... I fired off an angry email, and Federighi (or his admin) responded... but they did have a senior engineer contact me directly... and ultimately we managed to get the issue resolved... at this point, what do you have to lose?

federighi@apple.com

 

[dspdoc]

I would seriously suggest emailing Craig Federighi with your story. I had a problem with Mail several releases back (IIRC, it was Mavericks)... I fired off an angry email, and Federighi (or his admin) responded... but they did have a senior engineer contact me directly... and ultimately we managed to get the issue resolved... at this point, what do you have to lose?

federighi@apple.com

I am already in contact with a member of their executive relations team. I can't imagine that emailing Craig would do any more than put me right back in touch with the same department I am already dealing with. As I understand it, the engineers do not talk to people, ever... Are you sure you didn't mean a senior advisor? I have already spoken to many of them.

 

[bigcat]

Can you dig in and see if yours is AppleSMC as well? You can find how to look it up here:

https://forums.macrumors.com/thread...bridge-os-error.2128976/page-31#post-26358890

I have "name" : "RTBuddyV2" in my panicked threads. Not sure what that is.
[doublepost=1534530068][/doublepost]Is there a fast way to save the crash report before hitting the "Send to Apple" button? I've been doing the copy/paste to file thing but it takes a long time to complete the paste.

 

[shawndebnath]

I have "name" : "RTBuddyV2" in my panicked threads. Not sure what that is.
[doublepost=1534530068][/doublepost]Is there a fast way to save the crash report before hitting the "Send to Apple" button? I've been doing the copy/paste to file thing but it takes a long time to complete the paste.

It will be available in the Console app under System Reports > ProxiedDevice-Bridge as a panic.... report. I right click on it, Reveal in Finder and then copy that file to another folder so it isn't automatically deleted.

Also, do you have any accessories connected to the macbook?

 

[ricky1989]

432W out of an 87W power supply. Who said Apple can't innovate

389W from a 61w reporting here.

 

[bigcat]

Also, do you have any accessories connected to the macbook?

nothing is connected.

 

[CreeptoLoser]

I hope you are correct, but with the current state of things I would not be surprised.

Everything on iOS starts on macOS. Not just the app development, but everything from the kernel to the APIs.

 

[ricky1989]

I am already in contact with a member of their executive relations team. I can't imagine that emailing Craig would do any more than put me right back in touch with the same department I am already dealing with. As I understand it, the engineers do not talk to people, ever... Are you sure you didn't mean a senior advisor? I have already spoken to many of them.

Installing Mojave Public beta onto an external drive to force the BridgeOS to upgrade the to v3.0 (or newer) may be the solution? So far except from booting bootcamp on an external drive I have not yet encountered another kernel panic. Meaning I have had mine waking & sleeping and normal usage for 3-4 days without a reboot (plugging in dongles, charging etc).