Any T2-related crashes with 2018 Mini?

shinji

macrumors 65816
Original poster
Mar 18, 2007
1,322
1,514
  • Like
Reactions: g75d3

JakeTheSn4ke

macrumors newbie
Nov 8, 2018
12
23
It’s too early. We’ll wait. So far, people are reporting this “coil whine” problem.
My 2018 Mac Mini was delivered 12 hours ago. 8 kernel panics related to BridgeOS in that amount of time. Taking it back to Apple tomorrow.
 

Chancha

macrumors 6502a
Mar 19, 2014
941
830
My 2018 Mac Mini was delivered 12 hours ago. 8 kernel panics related to BridgeOS in that amount of time. Taking it back to Apple tomorrow.
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.
 

maflynn

Moderator
Staff member
May 3, 2009
66,803
33,773
Boston
It means Apple has not fixed T2 related issue
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
 

PJivan

macrumors 6502
Aug 19, 2015
449
452
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.
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.
 

Chancha

macrumors 6502a
Mar 19, 2014
941
830
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
I hope you are right, perhaps Apple feels confident a software/firmware fix can remove KPs altogether so it is safe to ship T2s as is in new minis and Airs.
[doublepost=1541679165][/doublepost]
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.
But the poster specifically said they are "8 kernel panics related to BridgeOS". Even if it is induced by certain combination of 3rd party software / settings, together with TM restoration of previous OS versions we don't know, but at least one user manage to have that happen without trying.

All in all this is just alarming if not dissuading me to consider any Macs with a T chip now.
 

maflynn

Moderator
Staff member
May 3, 2009
66,803
33,773
Boston
I hope you are right, perhaps Apple feels confident a software/firmware fix can remove KPs altogether so it is safe to ship T2s as is in new minis and Airs.
Here's the rub, this problem has existed in the iMac Pro since 2017, and the MBP since the summer. I have no idea if its hardware or software but if its software why doesn't this affect everyone?
 
  • Like
Reactions: Ploki and M.Rizk

PJivan

macrumors 6502
Aug 19, 2015
449
452
I hope you are right, perhaps Apple feels confident a software/firmware fix can remove KPs altogether so it is safe to ship T2s as is in new minis and Airs.
[doublepost=1541679165][/doublepost]
But the poster specifically said they are "8 kernel panics related to BridgeOS". Even if it is induced by certain combination of 3rd party software / settings, together with TM restoration of previous OS versions we don't know, but at least one user manage to have that happen without trying.

All in all this is just alarming if not dissuading me to consider any Macs with a T chip now.
I'm just saying one report from an unknown person on the internet is not enough for me to label an item not reliable.
I'm not saying he is lying or anything just not enough for me.

If that was the case then no product at all would be. name an item and I can find you threads with users experiencing issues. No one ask for the T2, it cost them more money to include it and it cost money to service it. So if this issue is on mac mini, it must be a very low percentage.
 

JakeTheSn4ke

macrumors newbie
Nov 8, 2018
12
23
I hope you are right, perhaps Apple feels confident a software/firmware fix can remove KPs altogether so it is safe to ship T2s as is in new minis and Airs.
[doublepost=1541679165][/doublepost]
But the poster specifically said they are "8 kernel panics related to BridgeOS". Even if it is induced by certain combination of 3rd party software / settings, together with TM restoration of previous OS versions we don't know, but at least one user manage to have that happen without trying.

All in all this is just alarming if not dissuading me to consider any Macs with a T chip now.
Couple notes to add:

1) Two of the kernel panics happened at login. Saw the crash report about BridgeOS on following login.

2) Only external peripherals are: a standard USB mouse, Bluetooth Apple keyboard, and a 27” dell ultra sharp connected via USB-C

3) I kid you not, I get a kernel panic every time I’m browsing the Mac Runors forum. It’s like there’s some sort of media that the T2 chip is wanting to offload that causes a panic. That said, I did have a few panics while Chrome wasn’t even open.

4) I did restore from Time Machine AND used FileVault to configure my machine. Thinking about erasing everything to a fresh OS install to see if the issue still exists.

As a software developer with ~13 years of experience, it is maddening to receive a brand new computer and have this happen over and over right off the bat. Until yesterday when I was searching for solutions to my problem, I didn’t even know issues with BridgeOS were a thing. Why Apple decided to release new machines without solving the underlying issue first (regardless of whether it’s software or hardware) is mind boggling to me.

2C7D26A4-B56F-4F38-B2C8-D2D75A88324A.png
 

PJivan

macrumors 6502
Aug 19, 2015
449
452
Perhaps not, but 101 pages in the MBP forum are enough to warrant concern given that the mini is using the same technology
clearly a defective units then, believe it or not at work we have a loads of macbook 17/18 and never saw that happening.
 
Last edited:
  • Like
Reactions: dpo and iZeljko

Chancha

macrumors 6502a
Mar 19, 2014
941
830
How do you know it has anything to do with the T2 chip and not something else?
When the error report involves "Bridge OS" then it surely is T2 chip related, as this is the OS that runs with / between the macOS.
 

JakeTheSn4ke

macrumors newbie
Nov 8, 2018
12
23
Woke up this morning to see if I could start to rule out certain variables and now the Mac Mini won’t even boot far enough for me to see the Apple logo.

Lights turn on, monitor recognizes a signal then the machine immediately power cycles.

This is, by far, the worst Apple experience I’ve ever had. :/
 

PJivan

macrumors 6502
Aug 19, 2015
449
452
Woke up this morning to see if I could start to rule out certain variables and now the Mac Mini won’t even boot far enough for me to see the Apple logo.

Lights turn on, monitor recognizes a signal then the machine immediately power cycles.

This is, by far, the worst Apple experience I’ve ever had. :/
In fairness you can't expect them to produce 200+ million device a year without issue, I still don't believe that T2 chipset is the issue, I can believe tho that some T2 chips are affected and there has been (maybe reduced but still there) a production issue from whoever build those silicons.

Just give it back and take a new one.
 
  • Like
Reactions: Cape Dave

JakeTheSn4ke

macrumors newbie
Nov 8, 2018
12
23
Just give it back and take a new one.
Appointment scheduled for 5pm.

Now my worry is how to safely remove all data from the machine since I’m not able to get it to boot. Lots of sensitive work-related data on the machine. :/
 

PJivan

macrumors 6502
Aug 19, 2015
449
452
Appointment scheduled for 5pm.

Now my worry is how to safely remove all data from the machine since I’m not able to get it to boot. Lots of sensitive work-related data on the machine. :/
well it's encrypted, one out of the many thousands encrypted machine they get back, I think you are pretty safe (thanks to T2 mandatory encryption let's praise this at least)
 

idark77

macrumors 6502
Dec 2, 2014
447
289
Couple notes to add:

1) Two of the kernel panics happened at login. Saw the crash report about BridgeOS on following login.

2) Only external peripherals are: a standard USB mouse, Bluetooth Apple keyboard, and a 27” dell ultra sharp connected via USB-C

3) I kid you not, I get a kernel panic every time I’m browsing the Mac Runors forum. It’s like there’s some sort of media that the T2 chip is wanting to offload that causes a panic. That said, I did have a few panics while Chrome wasn’t even open.

4) I did restore from Time Machine AND used FileVault to configure my machine. Thinking about erasing everything to a fresh OS install to see if the issue still exists.

As a software developer with ~13 years of experience, it is maddening to receive a brand new computer and have this happen over and over right off the bat. Until yesterday when I was searching for solutions to my problem, I didn’t even know issues with BridgeOS were a thing. Why Apple decided to release new machines without solving the underlying issue first (regardless of whether it’s software or hardware) is mind boggling to me.

View attachment 802424
Just a question:
did you update RAM modules?
 

Zarniwoop

macrumors 65816
Aug 12, 2009
1,019
728
West coast, Finland
Couple notes to add:

1) Two of the kernel panics happened at login. Saw the crash report about BridgeOS on following login.

2) Only external peripherals are: a standard USB mouse, Bluetooth Apple keyboard, and a 27” dell ultra sharp connected via USB-C

3) I kid you not, I get a kernel panic every time I’m browsing the Mac Runors forum. It’s like there’s some sort of media that the T2 chip is wanting to offload that causes a panic. That said, I did have a few panics while Chrome wasn’t even open.

4) I did restore from Time Machine AND used FileVault to configure my machine. Thinking about erasing everything to a fresh OS install to see if the issue still exists.

As a software developer with ~13 years of experience, it is maddening to receive a brand new computer and have this happen over and over right off the bat. Until yesterday when I was searching for solutions to my problem, I didn’t even know issues with BridgeOS were a thing. Why Apple decided to release new machines without solving the underlying issue first (regardless of whether it’s software or hardware) is mind boggling to me.

View attachment 802424
Sounds like a faulty SSD drive, and BridgeOS is unable to recover from it.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.