Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It’s very concerning that keyboards can become problematic so early on. I’m very interested in their longevity after 5+ years. Between keyboards, kernel panics, and the absence of a heat sink, I’m holding off for now. Upgrading my old laptop in the meantime.
 
normally run bootcamp on my Macs - so this may be a silly question, and my apologies if so. Do I have anything to worry about on the Windows side with these bridge issues? debating on getting the new Air this weekend.
 
Okay, today I had my first Panic Reboot (actually a shut down) due to the T2 on this new MacBook Air. This was the beginning of the report:
{"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1 (16P1582)","timestamp":"2018-12-06 11:29:55.77 +0000","incident_id":"CDFDD6DC-2096-4C78-8E61-62AD8913D9F4"}
It was plugged to the power cord and completely charged when this happened.
Also, the Mac was unattended, I mean, It was idling because nobody was using it.

I already sent the report, we'll see if 10.14.2 solves this. I'm going to update soon.
 
I just came over to this forum to see if this was also happening on the new Air. I am now convinced that the T2 problem can happen with every model Apple has released with the T2, from the iMac Pro last year, the 2018 MacBook Pro, 2018 Macbook Air and 2018 Mac Mini. That's just the way it is, with Apple refusing to acknowledge the problem, apparently unable or unwilling to do anything about it, and they continue to ship these devices with the same issue. Anyone who wants more details can read the hundreds of pages of messages on the MacBook Pro and iMac forums. Buyers BEWARE, unless you want to spend your life at the "Genius" Bar.

I purchased a 2018 MacBook Pro, with i7, 16GB, 512GB SSD, received it last week. It froze five times just trying to update from macOS 10.14.1 to 10.14.2. Back it went.
 
  • Like
Reactions: Never mind and Wags
Really? Hmm, I beg to differ. I've been using Mac OS since my 12" iBook. As well as Windows and Linux.

Well if you had a machine which doesn't suck, seeing crashes these days is quite rare to the point you can go a year+ without seeing them (even on Windows). So when users start seeing it multiple times a week (sometimes a day), it is a big deal.

Actually recently saw a BSOD on a work issued Lenovo - haven't seen one in so long I had to take a picture to share it with people. Turns out IT did a dodgy update/roll-out which caused them for multiple users.
 
It’s very concerning that keyboards can become problematic so early on. I’m very interested in their longevity after 5+ years. Between keyboards, kernel panics, and the absence of a heat sink, I’m holding off for now. Upgrading my old laptop in the meantime.
What are you talking about? The MacBook Air has a heat sink.
 
I just came over to this forum to see if this was also happening on the new Air. I am now convinced that the T2 problem can happen with every model Apple has released with the T2, from the iMac Pro last year, the 2018 MacBook Pro, 2018 Macbook Air and 2018 Mac Mini. That's just the way it is, with Apple refusing to acknowledge the problem, apparently unable or unwilling to do anything about it, and they continue to ship these devices with the same issue. Anyone who wants more details can read the hundreds of pages of messages on the MacBook Pro and iMac forums. Buyers BEWARE, unless you want to spend your life at the "Genius" Bar.

I purchased a 2018 MacBook Pro, with i7, 16GB, 512GB SSD, received it last week. It froze five times just trying to update from macOS 10.14.1 to 10.14.2. Back it went.
They know about the problem since iMac Pro and then release on new Mac Mini. Seems like no real fix. So mini buyers have to deal with this for another 1475 days?
 
Really? Hmm, I beg to differ. I've been using Mac OS since my 12" iBook. As well as Windows and Linux.

I don't know what you have had or used, but if you believe that OSX/macOS regularly crashes and freezes (prior to these 2018 models) then you haven't been using Apple computers.
 
  • Like
Reactions: Never mind
OS's crash sometimes. It's not that big of a deal.


HS was a bag of poop in that regard, but under Sierra and Mojave crashes are very rare in my experience. Again, HS aside, I can't recall the last time I had one. In fact I don't think I've ever had a crash on Mojave.
 
Indeed, perhaps he meant an actively cooled heatsink? The fan in the Air is just a chassis fan, rather than a heat sink fan.
I wasn't responding to what he meant. I responded to what he said.
[doublepost=1545522456][/doublepost]
I don't know what you have had or used, but if you believe that OSX/macOS regularly crashes and freezes (prior to these 2018 models) then you haven't been using Apple computers.
I didn't say OS's regularly crash. I said OS's crash sometimes.
 
OS's crash sometimes. It's not that big of a deal.
I didn't say OS's regularly crash. I said OS's crash sometimes.
The point is that machines that don't use T2 with BridgeOS crash less.

iMac Pros suffer this problem. iMacs do not.
2018 MacBook Airs suffer this problem. 2017 MacBook Airs and 2017 MacBooks do not.

See below:
Okay, today I had my first Panic Reboot (actually a shut down) due to the T2 on this new MacBook Air. This was the beginning of the report:
Code:
{"caused_by":"bridgeos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.1 (16P1582)","timestamp":"2018-12-06 11:29:55.77 +0000","incident_id":"CDFDD6DC-2096-4C78-8E61-62AD8913D9F4"}

It was plugged to the power cord and completely charged when this happened.
Also, the Mac was unattended, I mean, It was idling because nobody was using it.

I already sent the report, we'll see if 10.14.2 solves this. I'm going to update soon.
 
I have to say, since I updated to 10.14.2 that same day, I haven't had a single crash on the new Air.

But yeah, the problem here is BridgeOS and the T2 chip integration on macOS. On my old MacBook pro I had to wait 2 years to see my first kernel panic or crash. The BridgeOS crash happened barely 3 weeks after the purchase of this new 2018 MacBook Air. So definitely there's something wrong with T2 chip software integration.
 
I have to say, since I updated to 10.14.2 that same day, I haven't had a single crash on the new Air.

But yeah, the problem here is BridgeOS and the T2 chip integration on macOS. On my old MacBook pro I had to wait 2 years to see my first kernel panic or crash. The BridgeOS crash happened barely 3 weeks after the purchase of this new 2018 MacBook Air. So definitely there's something wrong with T2 chip software integration.
Still going solid? I picked mine up today without even having known about this and updated to 10.14.2 immediately. No issues so far.
 
Still going solid? I picked mine up today without even having known about this and updated to 10.14.2 immediately. No issues so far.
Yep. Still rock solid.
Obviously that doesn't mean it cannot happen again, but so far, no T2 related BridgeOS crash since last update.
 
  • Like
Reactions: dpgx81
T1 comes with a faulty keyboard, not a great deal :)
Oh you fail to see the Silver Lining my friend making this the 15” 2017 MBP 7th gen i7 2.9GHZ 16GB LPDDR3 w/4GB Radeon Pro 560 the most reliable vs. powerful MacBook Pro 2016-2018.

#1 Watch Zone of Tech who eventually got a 15” 2017 given to him after he eventually had THREE 2016 15” MBPs before being handed a new 2017 for free for his troubles and exact words were “it fixed All his problems.” He said he didn’t even expect to KEEP the 2018 15” MBP i9 w/32GB DDR4 and Radeon RX560X but because of the unique 4K rendering and 4K file exports he does, the extra 2 cores and CPU only intensive tasks shaved a few minutes off those unique production jobs and realized they added up to enough time he decided to keep it, but admitted he has had near daily, and certainly admitted to “multiple crashes” on his new 2018 MBP 15” i9, his Mac Book Air AND his new Mac Mini 6 core or any T2 Chip device he used.

Meanwhile the actual NUMBER of reported keyboard issues is so minimal on the 2017 and yet it qualifies for the Keyboard (lets be honest) a NEW $700 TopCase job up to 4 years from purchase. That translates to NEW BATTERIES EVERY COUPLE YEARS FOR REPORTING A FEW STICKY KEYS (if you pester your Apple Store about every incident despite majority resolving itself and get new TopCases), meaning new backlit keyboards and new batteries and potentially new track pad every couple years just as you battery has now lost 20% capacity per year and is at 60% capacity.

THEN get a SECOND new TopCase around 4yr #4 before the program ends so you leave with a set of brand new keys with no darkened letters from finger oils and fresh clicking keys and another new battery, you end up never having to do a single battery replacement for 4 years while always enjoying a near 80-100% capacity battery and new keyboards?

No crashes from T1 only handling Touch ID and a pretty desireable and techincailly overclockable 7820HK 7th gen with a 2.9GHZ base clock and a really strong single core that handles most of everyday life. Then the low power ram that HAS to result in extra battery life considering 32 GB of volitale ram that always be powered, with no power savings, is just power and battery life WASTED on 85% of users not running Virtual Machines?

Then consider the KEYBOARD in the 2018s are still failing at 10% according to many companies invested heavily in the Apple ecosystem but NOT part of the keyboard program and cut cost you potential deductible repairs depending b/c on how AppleCare+ now reads on causes of the issues they could place on the user?

It DEFINTELY is like having one less year of AppleCare and without a keyboard program that was really made for 2016 machines and included 2017 machines more to keep any upgrades from leaving Apple should something on the 2017 upgraded keyboard happen. I have a new in-box, unopened 2017 15” 2.9GHz 512GB 16GB LPDDR3 4GB Radeon 560 with nearly 2 years of existing AppleCare and a 2015 & 2017 owner is BEGGING me to sell him mine having had MORE luck with his 2017 than his 2015 even!

Meanwhile I happened to get last minute brand new logic board AND 3rd TopCase for free on my Mid-2012 15” Retina w/NVidia 650m 1GB DDR5 that still benches within 10-20% of a 2017, right before they turned them Vintage on Dec 31st 2018. Having been fortunate to document every misbehavior, the inside of my Mid-2012 was cleaned nearly every other year getting free TopCases. Now a brandnew Logic board that has shiny new solder and black clean chips. New island chiclet keyboard, battery, trackpad and only thing not new is the 15” Retina Display that is pixel perfect.

I held off opening my 2017 15” MBP wanting to wait on opinions and performance but despite the small jealousy of the T2 chip taking over as SSD controller on virtually Identical NVME 3.0 x 4 lane SSDs (that finally allowed it to get those promised 3200MB/s speeds) the WiFi cards can’t manage those speeds and I’ll gladly take a 2500MB/s read and sub 2000MB/s writes and not have a T2 crash and potential lost data while HAVING a port to retrieve data unlike the 2018 board where it was removed!

A board where even a bad capacitor on the board will cost you everything on that laptop. The 2017 on the other had still HAS that data recovery port and the possibility is still open to recovery of the SSD contents if it’s not failed. Anything on 2018 logic board goes and it’s a done deal. Plus no new TopCase deductible free on way out at year #4 like if you owned a 2017 15” and just kept track and made a few visits to Apple Store to document misbehavior of your keyboards.

Meanwhile enjoy your weekly crashes! Hit me up if you decide you want my 2017, celephane and entire unboxing experience and AppleCare already paid for and accepting small loss because my Mid 2012 Retina 15” just too good to sell, now that it’s essentially brand new. (If wondering the logic board came from ANOTHER program Apple had that lasted 4 years from purchase and I happened to buy mine from Apple reburbished pretty late in 2014 and got it covered legitmately) You just have to look at the GOOD side to certain programs and “time” how you USE them. Speaking up every time you have an issue, however minor, helps as well! Nothing underhanded, just held Apple to their own words and accountability.
 
Last edited:
  • Like
Reactions: afir93
The Bridge OS kernel panic - that starts as follows - happens to my 2018 MBA with a clean OS install about once per day. Occasionally twice a day but some days it doesn't happen.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.3 (16P3133)","timestamp":"2019-02-12 15:22:56.51 +0000","incident_id":"DF83F908-CCC4-4715-B465-F2AE610E3EDB"}

In all cases the MBA has been streaming video/audio to an Apple tv using Airplay and always has been tethered to an iPhone.

The on-line Apple Support guy said that it was the first time he had come across the problem and they had not received any information from Apple about it. I said how can that be when there the T2/Bridge OS issue has been known for about a year and there is a thread of over 100 pages on MacRumours about it affecting the MBP...?

He just told me to do the basic checks... which not surprisingly turned up nothing .. disc first aid, using a different user account (get same prob), resetting SMC and NVRAM/PRAM, using Apple Diagnostics...

I wonder whether there is any point in taking the MBA back and getting a replacement - that may have the same issue - or to just hope/wait for a fix...
 
The Bridge OS kernel panic - that starts as follows - happens to my 2018 MBA with a clean OS install about once per day. Occasionally twice a day but some days it doesn't happen.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.3 (16P3133)","timestamp":"2019-02-12 15:22:56.51 +0000","incident_id":"DF83F908-CCC4-4715-B465-F2AE610E3EDB"}

In all cases the MBA has been streaming video/audio to an Apple tv using Airplay and always has been tethered to an iPhone.

The on-line Apple Support guy said that it was the first time he had come across the problem and they had not received any information from Apple about it. I said how can that be when there the T2/Bridge OS issue has been known for about a year and there is a thread of over 100 pages on MacRumours about it affecting the MBP...?

He just told me to do the basic checks... which not surprisingly turned up nothing .. disc first aid, using a different user account (get same prob), resetting SMC and NVRAM/PRAM, using Apple Diagnostics...

I wonder whether there is any point in taking the MBA back and getting a replacement - that may have the same issue - or to just hope/wait for a fix...

I've had my MBA 2018 for 2 months now and I have not experienced this bridge OS crash even once. I would take it to Apple for a replacement. Crashing once a day sounds extremely frustrating.
 
I would replace it for sure. The new one might have the same problem but it doesn’t seem to affect every unit.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.