2018 MacBook Pros crashing with "Bridge OS" error

[RossoNunzio]

Both were 2018 15" core i9 MBPs CTO for USA. Since I no longer have these two 2018 MBPs (as I am still waiting, since Oct 10th, on a replacement - my 3rd 2018 MBP), I don't know the modifications. By the way, where do you find the modifications? Thanks.

were KPs present during normal use?Strange that from October 10 you are still waiting.Sure, there are machines that have gone bankrupt if it were common to everyone, I think something would have happened.I hope you'll be lucky now with the new one.Update your experience

 

[solouki]

were KPs present during normal use?Strange that from October 10 you are still waiting.Sure, there are machines that have gone bankrupt if it were common to everyone, I think something would have happened.I hope you'll be lucky now with the new one.Update your experience

On Page 95 of this thread I have several posts detailing my issues/problems with the 2018 MBPs. One of these posts, #2360, discusses the KPs that I had:
https://forums.macrumors.com/thread...bridge-os-error.2128976/page-95#post-26681158

In summary, I had KPs both when waking the MBPs from sleep as well as KPs occurring during normal usage of the MBPs.

 

[Trillion]

It is not country or software configuration specific (happens on an Israeli version with encryption turned off, siri off and no touchID)

 

[vanillamac]

Just adding to the party here....iMac Pro suffering from this issue since I got it last week.

I was using a LG Ultrafine 4k display (which is now disconnected as I trouble shoot)
I had Chrome/Google Backup and Sync/Dropbox/Magnet as login items, these have been disabled

Still getting errors...

So now I'm playing the "have to unplug USB devices when I leave my desk in case the mac goes to sleep" to help apple further isolate the issue.

Glad I kept the 2017 macbook pro around and didn't upgrade to 2018 model....would be frustrating to have the same issue on my main and backup machine lol

 

[Marketh]

For any prospective buyers of the new MBP or the new Air, just for the record this isn't affecting all machines - I got the new 13" MBP shortly after they were announced in the Summer, and haven't had one kernel panic. Hey Siri enabled, FileVault enabled.

Specs, for what it's worth: 13"/2.3 i5/16Gb/512Gb SSD

Edit: Just for the record I am obviously not saying that new buyers will never experience one, just aiming to provide some balance and show that many machines out there will be unaffected.

 

[iZeljko]

The rumour has it that new MBP with Vega GPU is coming...
What a great way to quietly solve the KP related issue!

Hats down Apple!
[doublepost=1541461274][/doublepost]

were KPs present during normal use?Strange that from October 10 you are still waiting.Sure, there are machines that have gone bankrupt if it were common to everyone, I think something would have happened.I hope you'll be lucky now with the new one.Update your experience

Maybe Apple want's to send a "new" new model to a user who has demonstrated supreme knowledge like Solouki did.

Can't wait to see what is going to unfold in next few weeks with MM and the NMBP.

 

[solouki]

The rumour has it that new MBP with Vega GPU is coming...
What a great way to quietly solve the KP related issue!

Hats down Apple!
[doublepost=1541461274][/doublepost]
Maybe Apple want's to send a "new" new model to a user who has demonstrated supreme knowledge like Solouki did.

Can't wait to see **** is going to unfold in next few weeks with MM and the NMBP.

You're too kind in your assessment -- but beyond that, I don't think I've had any effect on Apple even though I've uploaded reams of documented problems to Support. I'm not sure how much of my documentation even made it to the engineers. But, as a pipe dream, I'd love to get the "new" new machine for testing, but that is not going to happen. I'll post when I've received my third "old" new machine, I'm just hoping it doesn't suffer from the issues that I found with the first two. It seems that there are 2018 MBPs that do not have these problems, I'm just unlucky enough to not have gotten one in my first two machines. P.S. Thanks for the comment though.

 

[kryptticAZ]

Apple really **** the bed on this release. After getting its most loyal customers to spend north of $4K on a laptop and deal with KP problems for the initial ownership period, they then release an updated model with better graphics card that we can't exchange our unit for. Good lord...

 

[Chancha]

Apple really **** the bed on this release. After getting its most loyal customers to spend north of $4K on a laptop and deal with KP problems for the initial ownership period, they then release an updated model with better graphics card that we can't exchange our unit for. Good lord...

Are we sure that the T2 issue only affects early batch? Or that it is hardware related which must be solved by newer designed MBA and Mini?

 

[iZeljko]

Are we sure that the T2 issue only affects early batch? Or that it is hardware related which must be solved by newer designed MBA and Mini?

We should find out soon.
I’m surprised that there are no early release units of the Mac Mini sent to youtubers

 

[Man4ester]

Both were 2018 15" core i9 MBPs CTO for USA. Since I no longer have these two 2018 MBPs (as I am still waiting, since Oct 10th, on a replacement - my 3rd 2018 MBP), I don't know the modifications. By the way, where do you find the modifications? Thanks.

Z0V80004K (its Custom from i5/8gb/512GB in Apple site)
http://prntscr.com/lexumx

Z0V7000RR (its Custom from i5/8gb/256GB in Apple site)
http://prntscr.com/lexv7c

 

[Chancha]

We should find out soon.
I’m surprised that there are no early release units of the Mac Mini sent to youtubers

There are, but these guys also signed NDA and have to abide to a set date embargo lift for simultaneous publish. AppleInsider apparently prepared an article / review for the Mini already and even had a Youtube video posted, but it was pulled within an hour.

 

[solouki]

Z0V80004K (its Custom from i5/8gb/512GB in Apple site)
http://prntscr.com/lexumx

Z0V7000RR (its Custom from i5/8gb/256GB in Apple site)
http://prntscr.com/lexv7c

Ah! Thanks Man4ester.

I had searched through the System Report.spx files that I had saved from my two machines, and didn't find the modification numbers. Now I see that this part number is on the exterior of the packing boxes, and since the boxes were returned with the MBPs I don't have access to them anymore. Is there any other way of finding the part numbers than from the packing boxes?

 

[iZeljko]

There are, but these guys also signed NDA and have to abide to a set date embargo lift for simultaneous publish. AppleInsider apparently prepared an article / review for the Mini already and even had a Youtube video posted, but it was pulled within an hour.

Hm, that is a good point. I never thought of the NDA.
What do you reckon, when is the release date for the reviews?

 

[drecc]

An update - I think for me this is monitor related. I had an LG 31MU97, and I had terrible problems getting the MBP to wake up the display each morning. And I'd get KPs sometimes.

Yesterday I got a new LG 34WK95U, and I've had no problems with getting the machine to wake the monitor up. I think this might be the end of my KP issues.

 

[doitdada]

Could you expand on the external display flickering for me? My 4k UltraFine started doing this very thing right after I updated to 14.1. It doesn't do it every time it's plugged in, and it really only seems to do it when you're typing and the screen is refreshing.

I have a video example her.

It looks like this and occurs when I do basic stuff like browsing. Especially when I watch videos. It can occur up to 40-50 times a day. Hav tried different cables, but no difference. Doesn't occur when using the internal Display or when I use Windows 10 through Boot Camp. It is reported to Apple Cares Engineers, will get a feedback tomorrow. I will try to share details when I have a response.

This is just an illustration, but it looks like this and it is a mix of black screen and artefacts flying over the external monitor for a brief second or so. It just distorts whatever is on the screen and flickers/blinks.

 

[johnmcd3]

Has this still not been resolved or a resolution identified??

I have a 15" MBP (MacBookPro13,3) and I can repro this kernel panic 100% with the computer going to sleep from low battery. Apple should have been treated as I high priority issue, as I always get data loss when I have open unsaved work when the computer goes to sleep.

The top of the panic report always looks like the below. You can tell it's the same stack trace each time as the lower bytes of the stack frame addresses are always the same:

Anonymous UUID: 951133BA-6837-4A2D-97F8-E916A4D54E53

Tue Nov 6 16:26:03 2018

*** Panic Report ***
panic(cpu 6 caller 0xffffff7f990c7cf9): "Failed to complete supporting devices sleep/wake\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleEmbeddedOSSupport/AppleEmbeddedOSSupport-135.200.4/Source/Drivers/AppleEmbeddedOSSupportHost/AppleEmbeddedOSSupportHost.cpp:460
Backtrace (CPU 6), Frame : Return Address
0xffffff922e26bbe0 : 0xffffff80169aca1d
0xffffff922e26bc30 : 0xffffff8016ae6b13
0xffffff922e26bc70 : 0xffffff8016ad859a
0xffffff922e26bce0 : 0xffffff8016959ca0
0xffffff922e26bd00 : 0xffffff80169ac437
0xffffff922e26be20 : 0xffffff80169ac283
0xffffff922e26be90 : 0xffffff7f990c7cf9
0xffffff922e26bec0 : 0xffffff80169e8865
0xffffff922e26bf40 : 0xffffff80169e8415
0xffffff922e26bfa0 : 0xffffff80169590ce
Kernel Extensions in backtrace:
com.apple.driver.AppleEmbeddedOSSupportHost(1.0)[56A202E7-2E3F-3766-920F-488FAC2E8C48]@0xffffff7f990c6000->0xffffff7f990cbfff
dependency: com.apple.iokit.IOACPIFamily(1.4)[8A2C5602-298A-3199-AED0-979018ECBE16]@0xffffff7f977d3000

 

[solouki]

Has this still not been resolved or a resolution identified??

I have a 15" MBP (MacBookPro13,3) and I can repro this kernel panic 100% with the computer going to sleep from low battery. Apple should have been treated as I high priority issue, as I always get data loss when I have open unsaved work when the computer goes to sleep.

The top of the panic report always looks like the below. You can tell it's the same stack trace each time as the lower bytes of the stack frame addresses are always the same:

Anonymous UUID: 951133BA-6837-4A2D-97F8-E916A4D54E53

Tue Nov 6 16:26:03 2018

*** Panic Report ***
panic(cpu 6 caller 0xffffff7f990c7cf9): "Failed to complete supporting devices sleep/wake\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleEmbeddedOSSupport/AppleEmbeddedOSSupport-135.200.4/Source/Drivers/AppleEmbeddedOSSupportHost/AppleEmbeddedOSSupportHost.cpp:460
Backtrace (CPU 6), Frame : Return Address
0xffffff922e26bbe0 : 0xffffff80169aca1d
0xffffff922e26bc30 : 0xffffff8016ae6b13
0xffffff922e26bc70 : 0xffffff8016ad859a
0xffffff922e26bce0 : 0xffffff8016959ca0
0xffffff922e26bd00 : 0xffffff80169ac437
0xffffff922e26be20 : 0xffffff80169ac283
0xffffff922e26be90 : 0xffffff7f990c7cf9
0xffffff922e26bec0 : 0xffffff80169e8865
0xffffff922e26bf40 : 0xffffff80169e8415
0xffffff922e26bfa0 : 0xffffff80169590ce
Kernel Extensions in backtrace:
com.apple.driver.AppleEmbeddedOSSupportHost(1.0)[56A202E7-2E3F-3766-920F-488FAC2E8C48]@0xffffff7f990c6000->0xffffff7f990cbfff
dependency: com.apple.iokit.IOACPIFamily(1.4)[8A2C5602-298A-3199-AED0-979018ECBE16]@0xffffff7f977d3000

Hi johnmcd3,

If I'm not mistaken, the MacBookPro13,3 is from 2016 which has the T1 chip, not the T2 chip. This thread mainly concerns KPs on MacBookPro15,1 and MacBookPro15,2 models that have T2 processors, and the KPs result not from low battery sleeps but when waking from normal sleep mode as well as when the 2018 MBPs are running normally. I think you may have a different issue with your machine, but it is interesting. Did this behavior just start with 10.14.1, or did you have it under 10.13 and 10.12 also? Do you get KPs under other circumstances, say when waking from a normal sleep mode and not from a low battery induced sleep?

This is not something that I tested on the 2018 MBPs, i.e., low battery sleep mode waking causing KPs.

Thanks.

 

[Ael_MR]

I just wanted to add that as of last update the KP and reboots have not happened. Whatever was ailing my machine has disappeared. My faith in Apple is restored.

 

[FlushedNotRushed]

Is the KP / Bridge OS Crashing issue related to the macOS version I am on? I am currently on High Sierra and I haven't experienced any issues with crashing or the keyboard, but I kind of want to update to Mojave to utilize the "dark" mode.

 

[Maven1975]

I'm still getting them on my 2018 13" 2.3/1TB/16GB MacBook Pro on the latest software!

 

[mr.bee]

I too have the KP's on my MacBook Pro 15" bought in oktober.
Just by plugging in an external monitor I could reproduce the KP at the Genius Bar. I wasn't even logged into the system. A replacement is on it's way.

I hope this 'late' in the production line, the replacement unit is not bugged with this issue.

 

[Chancha]

Just as a heads up, a user receiving the new Mac mini today has already reported 8 times BridgeOS KP in the space of 12 hours.

Absolute joke of a tech company.

 

[Robotronic]

Just adding to the party here....iMac Pro suffering from this issue since I got it last week.

I was using a LG Ultrafine 4k display (which is now disconnected as I trouble shoot)

Just in case you didn't read all 100!!! pages of this thread to see my report of this previously: Same problem for me, been going on for months now. Can't use the LG UltraFine 4K with my iMac Pro, it will randomly crash. I can reliably reproduce the crash just by using Photos.app. Also had a 13" and a 15" 2018 MBP that had the same crashes, (though not with the LG display, I never connected it to those), both MBPs were returned. I have an open case with a senior advisor at Apple, nothing but crickets for weeks now, they stopped responding to my emails. I've decided enough is enough, built a Hackintosh which the LG displays work perfectly with, and I'm selling the iMac Pro. Really disappointing...

 

[maflynn]

.iMac Pro suffering from this issue since I got it last week.

If it were me, I'd return it.