2018 MacBook Pros crashing with "Bridge OS" error

[dspdoc]

reposting here from https://discussions.apple.com/message/33766089#33766089, to solicit more feedback.

I received my brand new Macbook Pro yesterday and after letting it sleep overnight, I unfortunately ran into the same BridgeOS error when I opened it this morning. Specs: i7/32GB RAM/1TB SSD. No accessories connected via USB or Bluetooth except for USB-C power chord. Computer lid was shut overnight. This is a clean re-install with option command R combo and formatted with APFS (case sensitive, encrypted).

After a bit of digging, I believe in this particular case, the blame falls to AppleSMC. How? If you look at the panic string, you will observe:

"Panicked thread: 0xffffffe0009706e0, backtrace: 0xffffffe016b3b530, tid: 337"
ref: https://gist.github.com/sdebnath/fab15b864c09fb70312f9c13c06e03c3#file-gistfile1-txt-L38


tid: 337 in this case refers to thread ID 337. The stack frame right below it is unfortunately undecipherable as I don't have the symbols to match the addresses to function names, however, the full report does list out the processes and associated threads under "processByPid" and "threadById" respectively. You can search for the tid and in my case:

"name": "AppleSMC"
ref: https://gist.github.com/sdebnath/fab15b864c09fb70312f9c13c06e03c3#file-gistfile1-txt-L2009

I will try to reset the SMC using the instructions at https://support.apple.com/en-us/HT201295 and see if that improves anything. Very curios if others are observing failures with AppleSMC as well. Would help narrow down this issue for sure!


Full panic report: https://gist.github.com/sdebnath/fab15b864c09fb70312f9c13c06e03c3

SMC reset will not fix this.
[doublepost=1534473699][/doublepost]

Man...that is so not good. How many this past week alone between your two T2 devices??

I’ve lost count. I’m just sick over it. I really don’t know what to do anymore. Strongly considering leaving Apple once and for all and I’m heartbroken over it.

 

[shawndebnath]

Just giving it a try - curious though - do you see AppleSMC in your reports that's actually causing the panic?

 

[dspdoc]

Just giving it a try - curious though - do you see AppleSMC in your reports that's actually causing the panic?

I’ve done PRAM resets, SMC resets, total wipes and reinstalls of the OS. Nothing touches this mess.

6th kernel panic of the evening. They seem to be getting worse at this point.

 

[claudio7ita]

The most irritating situation for me is the complete silence of Apple both for this serious problem and for that of the speakers issue. if they announced that they are analyzing problems and getting to know the developments, whether it is software or hardware, it would be a professional attitude worthy of the Apple name, but I do not feel like buying a MacBook Pro that I consider should be almost perfect, as long as I have reassurance.

 

[MacUser18095]

I am currently on Macbook pro 15 - 2018 and experiencing KPs. what about 13 inch?
I know this is the issue with T2 - Just want to check if its less or more on 13.

 

[MasterStormcrow]

I’ve done PRAM resets, SMC resets, total wipes and reinstalls of the OS. Nothing touches this mess.

6th kernel panic of the evening. They seem to be getting worse at this point.

Hello,

I'm new here. Reading this forum post had me scared, however my 15 day old 2018 MacBook pro i9/2tb/32gbram/ hasn't had this occur once. It sits at my desk at work and at home plugged in, goes to sleep with all default settings and haven't seen this occur once. I'm using the latest mojave dev beta 8.

When it was delivered I created a dummy user account and then used migration assistant from target disk mode to transfer my information from my old 2016 mbp to this computer. I then did a time machine backup to be safe. Then upgraded to mojave. then rebooted into restore mode (command R) and reinstalled mojave to be safe. Not once have I had this occur and I use my mbp all day and night. The only time I perform a shutdown is in the morning and evening when i'm leaving home to head to work and vise versa.

I hope this helps others gain hope, because reading this forum had me scared for the past week thinking that my close to $5000 computer was going to be problematic.

Best,

W

 

[bigcat]

A little update on this topic.



Of course, that 24 hours are not an indicator, but anyway it worth to try.
Go to Settings->Energy Saver.
1. UNCHECK automatical switching between the GPUs (if exists of course)
2. CHECK prevent computer from sleeping automatically...
3. UNCHECK put hard disk to sleep

4. UNCHECK Power Nap (regarding)
5. Turn display off after: - NEVER



I will update this topic if everything is fine.
https://discussions.apple.com/message/33764061#message33764061

This did not help. As usual, crashed this morning again.

 

[randolorian]

I will try to reset the SMC using the instructions at https://support.apple.com/en-us/HT201295 and see if that improves anything. Very curios if others are observing failures with AppleSMC as well. Would help narrow down this issue for sure!

The problem I have with resetting the SMC on these MBPs is that the Mac will power on while holding down the keys, using either of the two reset methods. This makes me wonder if it the reset actually occurs.

 

[dspdoc]

I am currently on Macbook pro 15 - 2018 and experiencing KPs. what about 13 inch?
I know this is the issue with T2 - Just want to check if its less or more on 13.

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.
[doublepost=1534511168][/doublepost]

Hello,

I'm new here. Reading this forum post had me scared, however my 15 day old 2018 MacBook pro i9/2tb/32gbram/ hasn't had this occur once. It sits at my desk at work and at home plugged in, goes to sleep with all default settings and haven't seen this occur once. I'm using the latest mojave dev beta 8.

When it was delivered I created a dummy user account and then used migration assistant from target disk mode to transfer my information from my old 2016 mbp to this computer. I then did a time machine backup to be safe. Then upgraded to mojave. then rebooted into restore mode (command R) and reinstalled mojave to be safe. Not once have I had this occur and I use my mbp all day and night. The only time I perform a shutdown is in the morning and evening when i'm leaving home to head to work and vise versa.

I hope this helps others gain hope, because reading this forum had me scared for the past week thinking that my close to $5000 computer was going to be problematic.

Best,

W

It provides no hope for professional users like myself that cannot and do not jump right on the latest OS. Those of us working in a critical environment hold out until like dot 5 of a release or even later. Besides, this only lets Apple off the hook on an issue that needs to be fixed NOW on the current OS. Mojave is not the answer.

 

[zargap]

The problem I have with resetting the SMC on these MBPs is that the Mac will power on while holding down the keys, using either of the two reset methods. This makes me wonder if it the reset actually occurs.

I also haven't gotten any successful boots after resetting NVRAM (assuming that that's what the second key combo on that instruction site does)

 

[dspdoc]

Wow Apple, just wow... You can call Apple and speak to a senior advisor and be told they have no knowledge of this issue over and over again. SMH

Well I got to about page 6 of the following search and deducted what I already knew. That this is a SERIOUS issue!!!

https://www.google.com/search?q=t2+kernal+panic&oq=t2+kernal+panic

 

[SDColorado]

Wow Apple, just wow... You can call Apple and speak to a senior advisor and be told they have no knowledge of this issue over and over again. SMH

Well I got to about page 6 of the following search and deducted what I already knew. That this is a SERIOUS issue!!!

https://www.google.com/search?q=t2+kernal+panic&oq=t2+kernal+panic

Hahaha. That in contrast to the one that has told me that they are closely following the discussions on Apples support forums and have been trying to gather data on things such as factory where they were built, time frame in which they were built, what peripherals that people have been using, etc.

You know... for that issue that they never heard about

Edit: Not to mention that they have already released a supplemental update to try to fix the issue that they aren't aware of

 

[dspdoc]

Hahaha. That in contrast to the one that has told me that they are closely following the discussions on Apples support forums and have been trying to gather data on things such as factory where they were built, time frame in which they were built, what peripherals that people have been using, etc.

You know... for that issue that they never heard about

It is pretty sad when the right hand doesn't know what the left hand is doing huh? And to make statements about which factory something is coming from would indicate hardware issues. That is NOT GOOD!!!

 

[SDColorado]

It is pretty sad when the right hand doesn't know what the left hand is doing huh?

More likely the left hand is well aware of what the right hand is doing, but likely have a more public policy that mums the word until it is resolved one way or the other. They never heard of the keyboard issue or antenna issues either... until they did.

 

[dspdoc]

More likely the left hand is well aware of what the right hand is doing, but likely have a more public policy that mums the word until it is resolved one way or the other. They never heard of the keyboard issue or antenna issues either... until they did.

LOL or the throttling issue.

 

[SDColorado]

LOL or the throttling issue.

Or the "stain gate" issues with the anti-reflective coating wearing off on some models, for which Apple has since authorized coverage within four years from the original purchase date of affected models

Edit: My 2013 MBP had the display replaced 3 times and each time they gave me the "Golly gee, we have never seen that before, but we will go ahead and replace it" routine.

I mean I am glad that they do fix it, but acknowledgement and ownership of the problem would go a long way toward customer trust.

 

[shawndebnath]

The problem I have with resetting the SMC on these MBPs is that the Mac will power on while holding down the keys, using either of the two reset methods. This makes me wonder if it the reset actually occurs.

Yeah, agreed. With the SMC reset, while holding the keys down and tapping the TouchID button, the system powers up but after a few seconds it shuts off in my case. I keep the key combo pressed for 10+ seconds. For the NVRAM reset, I keep it pressed for 20+ seconds and the system eventually restarts and then I let it go.

The fact that they respond to the key combinations likely means it is doing what it's supposed to. Since they don't have the light on the power connector anymore, delaying the restart has to be a sign of acknowledgement. Would be a lot better if they flash the touchbar or displayed a message in the touchbar to the fact.

I kept time using the stopwatch on my iPhone.

Also, after clearing SMC + NVRAM, this morning I didn't observe the kernel panic. Doesn't say much though.

 

[MasterStormcrow]

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.
[doublepost=1534511168][/doublepost]
It provides no hope for professional users like myself that cannot and do not jump right on the latest OS. Those of us working in a critical environment hold out until like dot 5 of a release or even later. Besides, this only lets Apple off the hook on an issue that needs to be fixed NOW on the current OS. Mojave is not the answer.

Hello,

My 2018 mbp i9/2tb/32gbram never experienced any problems even while on High Sierra 10.13.6 with the supplemental update during the 48 hours that it took to perform and finish the first time machine backup. I used it normally with all default settings at both home and work with final cut pro and all work related apps during that time. Maybe I just got lucky with my 2018 mbp.

Best,

W

 

[dspdoc]

 

[SDColorado]

View attachment 776445

That a lot nicer than what I would have written in the comments if it happened to me 7X in 24 hours hahaha

 

[faisalmemonuk]

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.

 

[dspdoc]

That a lot nicer than what I would have written in the comments if it happened to me 7X in 24 hours hahaha

This is enraging at this point.

 

[bigcat]

Hello,

My 2018 mbp i9/2tb/32gbram never experienced any problems even while on High Sierra 10.13.6 with the supplemental update during the 48 hours that it took to perform and finish the first time machine backup. I used it normally with all default settings at both home and work with final cut pro and all work related apps during that time. Maybe I just got lucky with my 2018 mbp.

Best,

W

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.

 

[SDColorado]

This is enraging at this point.

I feel for you! I have only had it happen a handful of times and even that is an annoyance. It shouldn’t be happening at all mind you, but for me it’s infrequent enough to be at annoyance level.

The frequency that you have been seeing it happen is way beyond that to where it is a serious loss of productivity and likely sanity

 

[dspdoc]

"panicString" : "panic(cpu 1 caller 0xfffffff00a6ab984): macOS panic detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 15P6059\nKernel version: Darwin Kernel Version 17.7.0: Fri Jun 15 23:12:25 PDT 2018; root:xnu-4570.71.1~3\/RELEASE_ARM64_T8010\nKernelCache UUID: EA400D2AE41F6E4E0B32A5E6010E1110\niBoot version: iBoot-4076.75.2\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide:     0x0000000003e00000\nKernel text base: 0xfffffff00ae04000\nEpoch Time:        sec       usec\n  Boot    : 0x5b765726 0x0008ae76\n  Sleep   : 0x5b765fe7 0x000b53fa\n  Wake    : 0x5b76cebd 0x0008d874\n  Calendar: 0x5b76e929 0x00099fd4\n\nPanicked 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" : {

"product" : "iBridge2,1"
}Model: iMacPro1,1, BootROM 15.16.6059.0.0,0, 8 processors, Intel Xeon W, 3.2 GHz, 64 GB, SMC
Graphics: Radeon Pro Vega 64, Radeon Pro Vega 64, PCIe
Memory Module: NODE 1/CPU1_DIMM_A0, 16 GB, DDR4, 2666 MHz, Hynix, HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK
Memory Module: NODE 1/CPU1_DIMM_B0, 16 GB, DDR4, 2666 MHz, Hynix, HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK
Memory Module: NODE 1/CPU1_DIMM_C0, 16 GB, DDR4, 2666 MHz, Hynix, HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK
Memory Module: NODE 1/CPU1_DIMM_D0, 16 GB, DDR4, 2666 MHz, Hynix, HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK HMA82GR7AFR4N-VK
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Apr  9 2018 19:30:51 version 9.130.18.10.32.3.0 FWID 01-ea787869
Bluetooth: Version 6.0.7f10, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
PCI Card: Universal Audio Apollo 8 - QUAD, Other Multimedia, Thunderbolt@63,0,0
PCI Card: UAD-2 Satellite Thunderbolt - OCTO, Other Multimedia, Thunderbolt@67,0,0
PCI Card: UAD-2 Satellite Thunderbolt - OCTO, Other Multimedia, Thunderbolt@71,0,0
USB Device: USB 3.0 Bus
USB Device: USB3.0 Hub
USB Device: USB3.0 Hub
USB Device: USB3.0 Hub
USB Device: SABRENT
USB Device: ASM1156-PM
USB Device: USB 2.0 BILLBOARD
USB Device: USB2.0 Hub
USB Device: USB2.0 Hub
USB Device: USB2.0 Hub
USB Device: USB Flash Drive
USB Device: iLok
USB Device: eLicenser
USB Device: A-Series Keyboard
USB Device: Maschine Mikro MK2
USB Device: HD Pro Webcam C920
USB Device: iBridge Bus
USB Device: Headset
USB Device: iBridge ALS
USB Device: iBridge FaceTime HD Camera (Built-in)
USB Device: iBridge
Thunderbolt Bus: iMac Pro, Apple Inc., 33.2
Thunderbolt Device: Thunderbolt 2 Option Card, Universal Audio, Inc., 3, 24.1
Thunderbolt Bus: iMac Pro, Apple Inc., 33.2

[doublepost=1534521532][/doublepost]

I feel for you! I have only had it happen a handful of times and even that is an annoyance. It shouldn’t be happening at all mind you, but for me it’s infrequent enough to be at annoyance level.

The frequency that you have been seeing it happen is way beyond that to where it is a serious loss of productivity and likely sanity

Yes, at this point it is a total liability to my business.