Any T2-related crashes with 2018 Mini?

[M.Rizk]

It seems apple is under the impression that its a software problem.

I don't know if its software or hardware, but my MBP doesn't have this issue, while many other MBP owners do

Same here. I have had my 2018 15” MBP for about two months now and not a single issue (hands on wood) other than Safari choppiness streaming YouTube (flashing pixels before Mojave, now flickering screen).

I am not trying to invalidate other posts though. I’ve been following this topic since the launch of the 2018 MBP. Even before I got mine and I have to admit that I was extremely worried getting mine since I live in a country without an Apple Store so I am extremely happy mine is free of this bug.

I really hope Apple fixes it for everyone soon. Hopefully it is a software bug. I am extremely disappointed they decided to use the same exact tech in new devices too when they knew they had issues and replaced MBPs more than twice for each one complaining without a fix!

 

[M.Rizk]

I think one comment on a forum it's not enough to mean anything to be fair, reviewers didn't have 8 kernel panick in 12 hours...I saw failed machines having kernel panick even prior to T2 chips or intel processors for what is worth.

Not a single reviewer mentioned it happening to the 2018 MBP either. I am not aware of any reporting such issues on the iMac Pro either. Somehow they all got lucky with good units but that does not invalidate other users’ claims.

 

[M.Rizk]

How do you know it has anything to do with the T2 chip and not something else?

We are not certain it is the T2. We just assume it is the reason because:
1. The issue is reported by Bridge OS which is the firmware running on the T2 chip (it could be something else though and the T2 just happens to report all issues)
2. It seems to be only affecting devices sold with the T2 chip (since the iMac Pro 2017).

Unfortunately Apple is not exactly clear about it, not even to the users who had calls with engineers and sent tons of data from their devices got to know what is causing it.

 

[JakeTheSn4ke]

Apple is going to replace my Mac Mini and the existing one is going in to see what happened. I was told that I’d get a call when they come to a conclusion but who knows.

Here’s to hoping the next Mac Mini is a+

 

[harriska2]

Apple is going to replace my Mac Mini and the existing one is going in to see what happened. I was told that I’d get a call when they come to a conclusion but who knows.

Here’s to hoping the next Mac Mini is a+

I’d love an update on your new machine when you’ve checked it out and loaded it up.

 

[maflynn]

(it could be something else though

What could it be? A new component introduced to the design of a computer which runs its operating system. Now all of a sudden that OS is crashing, causing problems for the computer itself. If its not the T2/Bridge OS what else could it be?
[doublepost=1541761880][/doublepost]

clearly a defective units then, believe it or not at work we have a loads of macbook 17/18 and never saw that happening.

The volume for which people are suffering this, makes that hard to believe. Its either Apple has some serious QC issues in the manufacturing process or its a software issue.

 

[PJivan]

What could it be? A new component introduced to the design of a computer which runs its operating system. Now all of a sudden that OS is crashing, causing problems for the computer itself. If its not the T2/Bridge OS what else could it be?
[doublepost=1541761880][/doublepost]
The volume for which people are suffering this, makes that hard to believe. Its either Apple has some serious QC issues in the manufacturing process or its a software issue.

The OP had the issue without any weird combination of software or unusual usage, and he can't even boot the machine, I really exclude his issue is software related.
Macrumors is followed WW so 100 pages discussion with 30-50-affected users can still be a small percentage, they sold millions of laptop.

I'm not denying there are issues, I'm just stating that we don't know how spread it is, we don't know if they are all related to the same hardware component or if Mac OS now group multiple issue under the same error code, a forum should help users and gather information but there is no use in jumping into clueless conclusion.

 

[Joestanxx]

Some Macbook Pro and iMac Pro users have been reporting kernel panics and other issues related to the T2 chip. https://www.macrumors.com/2018/07/26/apple-looking-into-t2-kernel-panic-reports/

Apple says a limited number of people are complaining, but we do have a long 100+ page thread about it https://forums.macrumors.com/thread...rashing-with-bridge-os-error.2128976/page-100

Anyone experiencing this with the 2018 Mini? Or any oddity related to bridgeOS?

My 17 is on its way back to apple , It started running very slow and the it would freeze up. The crash report showed that the error was caused by bridge OS. After a few freezes the machine would not reboot at all just power cycled. We will see how the replacement works that may also go back to apple if i have any problems I can always go back to my 2012 quad machine.

 

[JakeTheSn4ke]

My 17 is on its way back to apple , It started running very slow and the it would freeze up. The crash report showed that the error was caused by bridge OS. After a few freezes the machine would not reboot at all just power cycled. We will see how the replacement works that may also go back to apple if i have any problems I can always go back to my 2012 quad machine.

That’s the exact same thing I saw happen with my Mac Mini.

When you first got the machine and began configuring it, did you copy from Time Machine or something?

 

[Plutonius]

Its either Apple has some serious QC issues in the manufacturing process or its a software issue.

I think it's more likely a firmware issue related to the T2 hardware. I think that Apple would have had a fix by now with all the software updates if it was only a MacOS issue.

 

[Joestanxx]

That’s the exact same thing I saw happen with my Mac Mini.

When you first got the machine and began configuring it, did you copy from Time Machine or something?

I used the migration util. and copied from a backup of my 2012 mac mini
[doublepost=1541786299][/doublepost]

That’s the exact same thing I saw happen with my Mac Mini.

When you first got the machine and began configuring it, did you copy from Time Machine or something?

Did you apply the 10.14.1 update? My problems seemed to start after I did

 

[youslippin]

Same thing just happened to me a few minutes ago. I got the BridgeOS error as well. The Mac mini is only about 3 hours old. I upgraded the ram modules to 32gb as soon as I got it, fyi.

This was a completely clean install.

 

[trifid]

Ouch, I'm waiting for my order to arrive but I'm glad I'll be storing my user folder on a external drive and only put OS on the 128gb internal SSD, if I run into any issues I can just unplug external drive and RMA de the unit. This is another good reason for avoiding soldered SSDs.

 

[ktcifone]

Did not run migration assistant or time machine reconfigured from stock install. Didn't want issues since my 2012 mini was stuck with Sierra. No issues so far system is running quiet and fairly cool.

 

[dmsea1]

Just got my i7 last night - got it all setup, migrated over 500GB's of data - that took overnight. Hooked up to brand new LG 34 wide screen and a 60 inch 4k Vizio - no problems at all. No crashes, no glitches. Smooth as silk.

 

[JakeTheSn4ke]

I used the migration util. and copied from a backup of my 2012 mac mini
[doublepost=1541786299][/doublepost]
Did you apply the 10.14.1 update? My problems seemed to start after I did

I did the exact same thing. Restored from a 2012 Mac Mini back up the applied the 10.14.1
[doublepost=1541826488][/doublepost]

Same thing just happened to me a few minutes ago. I got the BridgeOS error as well. The Mac mini is only about 3 hours old. I upgraded the ram modules to 32gb as soon as I got it, fyi.

This was a completely clean install.

Did you copy over any files or apply the 10.14.1 update?

 

[youslippin]

edit

 

[Miat]

Same thing just happened to me a few minutes ago. I got the BridgeOS error as well. The Mac mini is only about 3 hours old. I upgraded the ram modules to 32gb as soon as I got it, fyi.

Sounds like it is a good idea for buyers to run the Mini first before making any mods.

 

[iZeljko]

Sounds like it is a good idea for buyers to run the Mini first before making any mods.

You are having a good point here! 16GB is not terribly expensive and it is more than enough for my needs.

I'd also add that it would be a good idea for Apple to release some information about the KP problems related to T2 equipped machines. This now is the 4th different machine that is suffering from internal problems. It is not convenient at all. (iMP, 13" MBP, 15" MPB, MM)

Mac used to be built like a tank. Now it seems it is built like a trash.
T2 almost sounds like a Trash 2. I'm disappointed.

Price of Macs in my home country is just insane and my only option is to buy it in some EU country with more down to earth prices (like Germany) and if the Mini ****'s the fan and I need to return it I need to take 2 days off work, buy plane tickets, drive to a 150 km away airport, take a flight to Frankfurt - all that just to return a Trash 2 product.

Thanks Apple - I've had enough.
I've never done it before but if I do not hear anything official about the Trash 2 problems I'm going Hackintosh.

I'm sick and tired of reading forums in order to find something that would help identify the "bad batch" ones.
Nothing.
You call Apple support to talk about KP problems and they tell you that it is caused only by the third party apps totally ignoring the fact that machines are KPing out of the box with nothing but Apple apps installed.

Poor Steve is turning in his grave now.

 

[Miat]

T2 almost sounds like a Trash 2.

When I see 'T2', I think Schwarzenegger in dark sunglasses.

 

[poorcody]

View attachment 802424

From the look of this crash report, it is being reported as "caused by" "macos", not the Bridge OS.

Note that all Kernal Panics are handled and reported by the Bridge OS now, so when the Mac OS has a KP, it is reported by the BridgeOS. I think there is some general confusion on this.

 

[Heat_Fan89]

From the look of this crash report, it is being reported as "caused by" "macos", not the Bridge OS.

Note that all Kernal Panics are handled and reported by the Bridge OS now, so when the Mac OS has a KP, it is reported by the BridgeOS. I think there is some general confusion on this.

If this is indeed an OS issue it really makes Apple look bad. Why? Because they design their own operating system to work with their designed hardware and they can't get that right. Meanwhile Microsoft and Linux can produce an operating system to work on millions if not billions of different configurations around the world.

High Sierra also had its share issues as well. Mojave so far has played nice on my 2012 Mini. I'm still debating whether to buy a 2018 Mini. Hopefully these gremlins will be squashed when it's time to make a decision.

 

[thingstoponder]

Sorry to hear that, but on the other hand, I don't mean it personally, this is somewhat illuminative to know. It means Apple has not fixed T2 related issues at all on hardware level, and proceeded to ship new Macs with it. I thought the mini must have been the safest bet among new Macs as it does not have a KB that can fail, a touch bar that you don't want, a thin chassis that has no room for heat dispensation, and no RAM that's permanently soldered. Yet Apple finds a way to brick it with forcing a premature T chip in it.

Yes they shipped a brick. Get real for a second, it's obviously gonna get fixed with an update and it's an isolated occurrence anyways seeing as no review has mentioned their machine crashing constantly.
[doublepost=1541901105][/doublepost]

If this is indeed an OS issue it really makes Apple look bad. Why? Because they design their own operating system to work with their designed hardware and they can't get that right. Meanwhile Microsoft and Linux can produce an operating system to work on millions if not billions of different configurations around the world.

High Sierra also had its share issues as well. Mojave so far has played nice on my 2012 Mini. I'm still debating whether to buy a 2018 Mini. Hopefully these gremlins will be squashed when it's time to make a decision.

Microsoft has had many many problems with their own OS on their own hardware. The Surface line isn't exactly rock solid. Also linux is a disaster when it comes to seamless compatibility.

Bugs happen, it's not the end of the world. No company is free of bugs.

 

[betadecay]

Note that all Kernal Panics are handled and reported by the Bridge OS now, so when the Mac OS has a KP, it is reported by the BridgeOS. I think there is some general confusion on this.

If this is true, i think most discussions about BridgeOS related KP have gone in a wrong direction. This would also explain the scatter in symptoms for some threads.

But at which place does the KP log point to/give a hint at the "real" issue of the crash?

 

[DVD9]

The volume for which people are suffering this, makes that hard to believe. Its either Apple has some serious QC issues in the manufacturing process or its a software issue.

Samsung wanted two dollars more for their SSD drive than some unknown Chinese manufacturer and Tim Cook chose the tiny tick up in profit margin.