Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

autoshot

macrumors member
Original poster
Jul 11, 2015
44
7
Hello everyone,
this morning when I wanted to wake my new (two day old) Mac mini 2018 I was greeted with a message saying that my computer restarted because of a problem. The associated error log reads as follows:
Code:
{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.2 (16P2542)","timestamp":"2018-12-20 06:33:17.45 +0000","incident_id":"..."}
A quick Google search revealed that apparently this issue is related to a problem with the T2-chip and that anyone affected should try to return their Mac ASAP. What would you say?
Cheers,
Daniel
 
That's a "t2-related" crash report.
Numerous postings about t2 errors in the MacBook Pro and iMac Pro discussion areas.

Looks like it's gonna be a problem for owners of Macs with t2 chips inside, until Apple gets this all "figured out" ...
 
That's a "t2-related" crash report.
Numerous postings about t2 errors in the MacBook Pro and iMac Pro discussion areas.

Looks like it's gonna be a problem for owners of Macs with t2 chips inside, until Apple gets this all "figured out" ...

Any kernel panic will be handled by T2, and T2 isn't the culprit in itself. When I had my first kernel panic yesterday it seems to have been related to memory. That is the practical difference between regular memory and ECC, which I had in my Mac Pro.
 
  • Like
Reactions: Ploki
Any kernel panic will be handled by T2, and T2 isn't the culprit in itself. When I had my first kernel panic yesterday it seems to have been related to memory. That is the practical difference between regular memory and ECC, which I had in my Mac Pro.
that makes much more sense than T2 doomsday
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.