2018 MacBook Pros crashing with "Bridge OS" error

mreg376 · Feb 7, 2019

elnbrg said:
My KP problem completely disappeared after upgrading to 10.14.3 and cleaning up the system.

MBP 15 2018/32GB/1TB

If "cleaning the system" is required to avoid these T2 crashes then you still have a problem.

duckrabbit · Feb 7, 2019

I've observed a reproducible crash that seems potentially T2/BridgeOS related--though it does not produce any notable log files.

It's happening whenever I quickly exit clamshell mode with MBP's display set to "Looks like 1440 x 900" rather than the Default.

1. Attach power adapter
2. Connect to external monitor (in my case Dell U2414H via HDMI, though I've reproduced the issue on another display as well)
3. Set MBP resolution to "Looks like 1440 x 900" and external display to native, non-mirrored
4. Close the lid on the MBP so it enters clamshell mode
5. Open the lid back up a few seconds after entering clamshell mode
6. At least 50% of the time, the machine will lock up with the external monitor in a "partially dimmed" state

I've tested this many times (50+ at this point) and have never gotten it to occur with the MBP display set to "Default for display".

Other notes:
- Occurs in clean install
- Does not occur in Safe Mode
- Does not occur on 2017 Macbook Pro

I'd be interested to see if anyone else can reproduce it--particularly other Vega 20 owners.

Plutonius · Feb 7, 2019

Howard2k said:
They must be working on a resolution and on a T3 I suppose, but nothing has been made public.

anaudiopro said:
If they release a T3 chip shortly after releasing the mini and it fixes everything people will completely lose their minds! Apple can’t have all these bad T2 chips (if that indeed is the cause) out in the world and then pull something like that. Talk about a colossal class action lawsuit!

The first thing would be that Apple needs to acknowledge the bridgeOS errors and T2 problems

.

Depending on how far along Apple is on an ARM based laptop, they mat not be putting too much effort into the next gen T2 chip. The functionality of the T2 would move into the new ARM eliminating the T2 (they will no longer need two processors (T2 and Intel)).

Howard2k · Feb 7, 2019

Plutonius said:
The first thing would be that Apple needs to acknowledge the bridgeOS errors and T2 problems .

Depending on how far along Apple is on an ARM based laptop, they mat not be putting too much effort into the next gen T2 chip. The functionality of the T2 would move into the new ARM eliminating the T2 (they will no longer need two processors (T2 and Intel)).

I don't think they would have to disclose the T2 issues to release T3, it's just a question of positioning the T3 as "new features" as opposed to "we replaced a screwed up one". Just try to quietly brush it under the carpet and hey, maybe 12 months down the road they can then say "Oh, and look, we increased overall reliability".

Total speculation on my part.

jeroenvisser101 · Feb 8, 2019

duckrabbit said:
I've observed a reproducible crash that seems potentially T2/BridgeOS related--though it does not produce any notable log files.

It's happening whenever I quickly exit clamshell mode with MBP's display set to "Looks like 1440 x 900" rather than the Default.

1. Attach power adapter
2. Connect to external monitor (in my case Dell U2414H via HDMI, though I've reproduced the issue on another display as well)
3. Set MBP resolution to "Looks like 1440 x 900" and external display to native, non-mirrored
4. Close the lid on the MBP so it enters clamshell mode
5. Open the lid back up a few seconds after entering clamshell mode
6. At least 50% of the time, the machine will lock up with the external monitor in a "partially dimmed" state

I've tested this many times (50+ at this point) and have never gotten it to occur with the MBP display set to "Default for display".

Other notes:
- Occurs in clean install
- Does not occur in Safe Mode
- Does not occur on 2017 Macbook Pro

I'd be interested to see if anyone else can reproduce it--particularly other Vega 20 owners.

If you look in Console.app, "System Reports", do you have files ending with .gpuRestart? Files ending in .panic? I'm having issues, specifically with Dell monitors and Vega 20 that have something to do with the GPU hanging and failing while trying to restart. When you say "lock up", is the mouse still working but the system (e.g. windowserver) completely unresponsive? Have you waited until something happened? (e.g. T2 chip panicking?)

armadiaz · Feb 8, 2019

right now im having a "bug_type" -> 115 and "os_version" -> Bridge OS on the ResetCounter.ips file

i wonder why i couldn't see any "Kernel Panics" or "System Popup Message" after my laptop has restarted, the only thing that logged was file called ResetCounter-2019-02-08-135732.ips (no other file are created / updated within that restart time period).

And if i check Shutdown Cause from my terminal, the logs said im having -20 shutdown, anyone has the same problem?

poorcody · Feb 8, 2019

jeroenvisser101 said:
I can report that my 1TB/Vega 20/32GB/i9 is still panicking with "Watchdog detected" on 10.14.3 (18D42). I wrote a bit about my personal journey researching it and here's an excerpt if anyone is interested:

Thanks, that is interesting... I'd be interested in reading more about your research. My group is developing an Electron app, and we are contemplating updating from 2016 MBP's... I'm wondering if this problem would preclude us using Electron... ?

jeroenvisser101 · Feb 8, 2019

poorcody said:
Thanks, that is interesting... I'd be interested in reading more about your research. My group is developing an Electron app, and we are contemplating updating from 2016 MBP's... I'm wondering if this problem would preclude us using Electron... ?

It really depends, is your app very graphic, does it use hardware acceleration (WebGL, Canvas or the like) to render it's UI? If so, I'd hold updating off (unless you have broken keyboards). I should also note that the issue happens mostly when a lot of apps are doing GPU-related stuff and the more displays, the more apps, the longer operations take, and the bigger the chance for deadlocks to hang the GPU.

Fishrrman · Feb 8, 2019

My opinion only (and what do I know?):
Scrap the t2 chip and "secure enclave" concept.
Go back to the "pre t2" design of, say, the 2015 MBPro.

That will take care of "t2-related crashes" across the entire Mac lineup.

duckrabbit · Feb 8, 2019

jeroenvisser101 said:
If you look in Console.app, "System Reports", do you have files ending with .gpuRestart? Files ending in .panic? I'm having issues, specifically with Dell monitors and Vega 20 that have something to do with the GPU hanging and failing while trying to restart. [

The only files I'm seeing created are ResetCounter-[Timestamp].ips inside /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge .
Contents look like this:
{"bug_type":"115","timestamp":"2019-02-07 08:42:44.42 +0000","name":"Reset count","os_version":"Bridge OS 3.3 (16P3133)","incident_id":"3AF6AEC5-2BFB-46D1-87B9-381F4C9A62A4"}
Incident Identifier: 3AF6AEC5-2BFB-46D1-87B9-381F4C9A62A4
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2019-02-07 08:42:44.38 +0000
Reset count: 0
Boot failure count: 1
Boot faults: force_off
Boot stage: 255
Boot app: 0

I've been assuming there are created because of the hard shutdown rather than the issue itself, but that's speculative on my part.

I've seen the issue on an Asus monitor as well, so it's not limited to Dell fwiw.

jeroenvisser101 said:
When you say "lock up", is the mouse still working but the system (e.g. windowserver) completely unresponsive? Have you waited until something happened? (e.g. T2 chip panicking?)

Yes, that's exactly what's happening. I've waited for a while without anything happening. Not sure if the machine would eventually restart itself (don't really have time to check at the moment).

Trey M · Feb 8, 2019

I have this same log...

{"bug_type":"115","timestamp":"2019-01-28 04:35:43.86 +0000","name":"Reset count","os_version":"Bridge OS 3.3 (16P3133)","incident_id":"46927EA0-7161-4A5B-8BDA-F79265104628"}
Incident Identifier: 46927EA0-7161-4A5B-8BDA-F79265104628
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2019-01-28 04:35:43.83 +0000
Reset count: 0
Boot failure count: 1
Boot faults: force_off
Boot stage: 255
Boot app: 0

Both times I have gotten this same log, I was utilizing the 'Screens' application to mirror my Mac desktop to my iPad. Upon disconnecting the connection from my iPad > Mac, this is where I've experienced the crash. It doesn't happen every time, just sometimes.

armadiaz · Feb 10, 2019

Trey M said:
I have this same log...

{"bug_type":"115","timestamp":"2019-01-28 04:35:43.86 +0000","name":"Reset count","os_version":"Bridge OS 3.3 (16P3133)","incident_id":"46927EA0-7161-4A5B-8BDA-F79265104628"}
Incident Identifier: 46927EA0-7161-4A5B-8BDA-F79265104628
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2019-01-28 04:35:43.83 +0000
Reset count: 0
Boot failure count: 1
Boot faults: force_off
Boot stage: 255
Boot app: 0

Both times I have gotten this same log, I was utilizing the 'Screens' application to mirror my Mac desktop to my iPad. Upon disconnecting the connection from my iPad > Mac, this is where I've experienced the crash. It doesn't happen every time, just sometimes.

well, funny thing is i do have this same log, but i never used any mirror screen with my mac. I only use it for light browsing. i wonder is this bug type 115 represent the issue or other thing that still ambiguous.

eyedee · Feb 11, 2019

I'm another to experience this issue. I bought a custom 2018 MacBook Pro (2.9GHz i9 32GB Ram Vega 20) some time around Black Friday which I received and started using in early January 2019. It's now completely frozen 4 times requiring a forced shutdown (hold down power button).

I've not been doing any intensive work yet or using power/ram hungry apps and the fans hardly ever spin up so that they are easily noticeable. I've been paying attention to Activity Monitor and my combined System and, so far, User CPU usage doesn't tend to stray much over 10% with 10-12GB's of the 32GB Ram being utilised.

Because it could potentially be connected to the error I wanted to say that I have two LG 27UK850 4K monitors attached via USB-C cables. Each monitor acts as a USB 3.0 hub and provides 2 x USB 3.0 ports. I have a Behringer UCA202 USB sound card (for the Fibre Optic TOS-Link) plugged into one of the monitors (necessary, because Apple chose to remove digital optical support from the newer MacBook Pro).

The error is the same each time. It always happens when 'waking' the Mac up after I've been away from if for a while and the display has been 'asleep'. When I press the spacebar or waggle the bluetooth mouse the MacBook Pro screen comes on as expedited and the 2 x LG monitors backlight turns on but no image is displayed. A couple of seconds later they both show a dialogue box saying 'No Signal' before they go back into standby mode. The touch bar is illuminated and shows 'ESC' on the left and the brightness, sound and Siri icons on the right, but it's utterly frozen and unresponsive to inputs, as is the case with all the physical keys, the touchpad and the mouse.

I leave my MacBook Pro on pretty much all the time (24 hours a day) and the error seems to happen every few days. I've attached the four logs incase its of any interest. The most recent three logs are all pretty much the same, but the first log (19th January) shows two boot failures and the boot sequence failed at a different stage. I assume it means boot from sleep as, like I mentioned, the Mac always freezes on waking up.

{"bug_type":"115","timestamp":"2019-02-11 13:35:57.66 +0000","name":"Reset count","os_version":"Bridge OS 3.2 (16P2542)","incident_id":"C6E28E4C-668A-487B-B66A-95E0BEEB6B05"}
Incident Identifier: C6E28E4C-668A-487B-B66A-95E0BEEB6B05
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2019-02-11 13:35:57.52 +0000
Reset count: 0
Boot failure count: 1
Boot faults: force_off
Boot stage: 255
Boot app: 0

{"bug_type":"115","timestamp":"2019-02-06 19:46:30.42 +0000","name":"Reset count","os_version":"Bridge OS 3.2 (16P2542)","incident_id":"7B50ADB2-AD37-4D5E-AC11-48676C50B091"}
Incident Identifier: 7B50ADB2-AD37-4D5E-AC11-48676C50B091
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2019-02-06 19:46:30.40 +0000
Reset count: 0
Boot failure count: 1
Boot faults: force_off
Boot stage: 255
Boot app: 0

{"bug_type":"115","timestamp":"2019-02-01 22:34:24.76 +0000","name":"Reset count","os_version":"Bridge OS 3.2 (16P2542)","incident_id":"7BC47048-155D-4CF2-A15C-4FD455985EDC"}
Incident Identifier: 7BC47048-155D-4CF2-A15C-4FD455985EDC
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2019-02-01 22:34:24.75 +0000
Reset count: 0
Boot failure count: 1
Boot faults: force_off
Boot stage: 255
Boot app: 0

{"bug_type":"115","timestamp":"2019-01-19 16:50:21.92 +0000","name":"Reset count","os_version":"Bridge OS 3.2 (16P2542)","incident_id":"FE9132E3-26A5-46DF-B22E-A35846108587"}
Incident Identifier: FE9132E3-26A5-46DF-B22E-A35846108587
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2019-01-19 16:50:21.86 +0000
Reset count: 0
Boot failure count: 2
Boot faults: btn1 force_off
Boot stage: 16
Boot app: 0

thedomus · Feb 12, 2019

My experience with MacBook Pro i9 32GB Ram connected to Apple Thunderbolt Display via Blackmagic eGPU.
The lockout/shutdown crash usually occurs when watching YouTube! Not every time, but when it does occur it's then.
I like playing Borderlands 2 (I know, old school!) it has never done it when playing that. I use Logic Pro X everyday and I can't remember the crash happening using that app.
I gonna try not using the eGPU and see if anything is better.

Marketh · Feb 12, 2019

This has probably already been asked & answered somewhere in the last 128 pages, but, is this also affecting 2018 13" models? My line of thought is this doesn't have a dedicated video card? I've never experienced this on my 13" which I've had from launch in Summer.

lankox · Feb 12, 2019

Marketh said:
This has probably already been asked & answered somewhere in the last 128 pages, but, is this also affecting 2018 13" models? My line of thought is this doesn't have a dedicated video card? I've never experienced this on my 13" which I've had from launch in Summer.

I have experienced the crash twice in the last month on my 2018 13" MBP

Gen4ig · Feb 12, 2019

MPB 13 2018
Today I get this
panic-full-2019-02-13-053317.538.ips

Code:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 3.4 (16P54085b)","timestamp":"2019-02-13 05:33:17.53 +0000","incident_id":"C3859E72-8807-435E-839C-3711C8858E0C"}
{
  "binaryImages" : [
    [
      "703c6593-cac3-294c-3bd8-4fccc35144cc",
      18446743936270598144,
      "U"
    ],
    [
      "00000000-0000-0000-0000-000000000000",
      0,
      "A"
    ],
    [
      "4f204902-6032-3d1f-86f9-4637b55006dd",
      6442450944,
      "S"
    ],
    [
      "f957203c-cb9a-34e8-bd46-16caf678db5f",
      4296130560,
      "P"
    ],
    [
      "deac47ba-c165-3a6e-8f69-ab70c95df06e",
      4296409088,
      "P"
    ],
    [
      "6df4d20f-f4de-36cf-ab0c-861339309a0f",
      4333748224,
      "P"
    ],
    [
      "c11934d2-60c8-3dd5-a0fc-7966891d9134",
      4334878720,
      "P"
    ],
    [
      "925b1273-af15-304f-8ccf-6f7ad5388bc2",
      4371939328,
      "P"
    ],
    [
      "f7ee9f96-23cf-3db8-9abe-488f8b45b298",
      4309729280,
      "P"
    ],
    [
      "2b1df330-2496-34a1-bc01-5728e0ffb6bd",
      4367745024,
      "P"
    ],
    [
      "fed13eda-82d8-3bdb-844a-9070e7d7fb2e",
      4338810880,
      "P"
    ],
    [
      "d02a9d5b-b7e9-3a6d-952b-259fbf3661f8",
      4303093760,
      "P"
    ],
    [
      "07df417d-4baf-3e56-9c03-7b8ce465f936",
      4309450752,
      "P"
    ],
    [
      "d3009fb2-9fd3-30e9-90e5-961469695997",
      4362092544,
      "P"
    ],
    [
      "e3bc6bd6-9c3d-3fa1-8c30-d6e867527235",
      4342448128,
      "P"
    ],
    [
      "c44eb885-b83e-385d-b0e0-dedb2659953b",
      4364173312,
      "P"
    ],
    [
      "4efe3195-e84f-3359-8e8b-b06f99a9ff92",
      4367089664,
      "P"
    ],
    [
      "8fb58184-ea6b-3ec5-a1b2-0decb0bf599f",
      4310482944,
      "P"
    ],
    [
      "35e3d348-a337-3459-9308-f5d46b527daf",
      4335681536,
      "P"
    ],
    [
      "124dbf6f-d71b-3cda-bab7-f9c11e08d088",
      4298522624,
      "P"
    ],
    [
      "ffa9a4cd-3ba3-3001-8494-4f36fc194f16",
      4330160128,
      "P"
    ],
    [
      "8cf7ca04-9bcc-3712-b714-8061cf01b3f3",
      4342005760,
      "P"
    ],
    [
      "8ea0eb4f-43f3-328f-87c7-ebcf41338fe9",
      4304666624,
      "P"
    ],
    [
      "bae1b312-ebaf-36f6-ab3c-329296524815",
      4367204352,
      "P"
    ]
  ],
  "build" : "Bridge OS 3.4 (16P54085b)",
  "crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
  "date" : "2019-02-13 05:33:17.06 +0000",
  "incident" : "C3859E72-8807-435E-839C-3711C8858E0C",
  "kernel" : "Darwin Kernel Version 18.5.0: Mon Jan 28 20:21:38 PST 2019; root:xnu-4903.250.319~17\/RELEASE_ARM64_T8010",
  "macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 574960 **\n",
  "macOSPanicFlags" : "0x4",
  "macOSPanicString" : "panic(cpu 2 caller 0xffffff80046c3b9f): UUID: 0A13A7AC-B044-4771-B550-E803FD2365B8\nStackshot Reason: Sleep transition timed out after 180 seconds while entering darkwake on way to sleep. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74.\nBacktracing specified thread\nBacktrace (CPU 2), Frame : Return Address\n0xffffff811fe63910 : 0xffffff80040d55a3 \n0xffffff9138a43a90 : 0xffffff8003fcb6f0 \n0xffffff9138a43b10 : 0xffffff8003fca3af \n0xffffff9138a43b60 : 0xffffff80040d2584 \n0xffffff9138a43bb0 : 0xffffff80040d1cb8 \n0xffffff9138a43be0 : 0xffffff7f87ba7975 \n0xffffff9138a43c00 : 0xffffff7f87bc0a97 \n0xffffff9138a43c10 : 0xffffff7f87bb066c \n0xffffff9138a43c60 : 0xffffff8004626074 \n0xffffff9138a43cd0 : 0xffffff80046407cf \n0xffffff9138a43d70 : 0xffffff8004626869 \n0xffffff9138a43db0 : 0xffffff800463d25c \n0xffffff9138a43e40 : 0xffffff800463947c \n0xffffff9138a43ea0 : 0xffffff80046362f3 \n0xffffff9138a43ef0 : 0xffffff8004636190 \n0xffffff9138a43f30 : 0xffffff8004655a32 \n0xffffff9138a43f70 : 0xffffff8004654fbc \n0xffffff9138a43fa0 : 0xffffff8003f5b0ce \n      Kernel Extensions in backtrace:\n         com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7f87b9f000->0xffffff7f87be9fff\n            dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f848eb000\n\nBSD process name correspondin

And

Code:

{"bug_type":"115","timestamp":"2019-02-13 05:33:17.21 +0000","name":"Reset count","os_version":"Bridge OS 3.4 (16P54085b)","incident_id":"D51AACDB-0685-423E-AAB7-CF5D5230A311"}
Incident Identifier: D51AACDB-0685-423E-AAB7-CF5D5230A311
CrashReporter Key:   c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Date: 2019-02-13 05:33:17.03 +0000
Reset count: 1
Boot failure count: 0
Boot faults:
Boot stage: 0
Boot app: 0

Yesterday
Kernel_2019-02-12-190036_MacBook-Pro-G.gpuRestart

Code:

Tue Feb 12 19:00:36 2019

Event:               GPU Reset
Date/Time:           Tue Feb 12 19:00:36 2019
Application:         Google Chrome He
Path:               
Tailspin:            /Library/Logs/DiagnosticReports/gpuRestart2019-02-12-190036.tailspin
GPUSubmission Trace ID: 0
OS Version:          Mac OS X Version 10.14.3 (Build 18D109)
Graphics Hardware:   Intel Iris Plus Graphics 655
Signature:           803

Report Data:


===========================================================================
                         Intel GPU Hang Summary
                              version 1.2.0
===========================================================================
  Schedule: Apple FirmwareMultiple channels per index

  Processing hang for hardware context ID[225]

-- Summary of Status for ALL Rings --
RCS Ring is:     - busy - in the ring    <--  Appears hung
VCS Ring is:     - NOT enabled - idle
BCS Ring is:     - NOT enabled - idle
VECS Ring is:     - NOT enabled - idle
VCS2 Ring is:     - NOT enabled - idle

===========================================================================
                     Hardware Ring Registers
===========================================================================

-- RCS Ring --
  RING_HEAD   = 0x08204ba4  (offset = 0x00004ba4, wrap count = 65, wait_for_cond = 0x0)
  RING_TAIL   = 0x00004bc0  (offset = 0x00004bc0)
  RING_START  = 0x466e7000  (offset = 0x466e7000)
  RING_CTRL   = 0x00007001  (enabled, auto report disabled (0x00), not waiting, semaphore not waiting, length = 0x008 4KB pages)

-- VCS Ring --
  RING_HEAD   = 0x00000fa0  (offset = 0x00000fa0, wrap count = 0, wait_for_cond = 0x0)
  RING_TAIL   = 0x00000fa0  (offset = 0x00000fa0)
  RING_START  = 0x40e25000  (offset = 0x40e25000)
  RING_CTRL   = 0x00007000  (disabled, auto report disabled (0x00), not waiting, semaphore not waiting, length = 0x008 4KB pages)

-- BCS Ring --
  RING_HEAD   = 0x1dc059a0  (offset = 0x000059a0, wrap count = 238, wait_for_cond = 0x0)
  RING_TAIL   = 0x000059a0  (offset = 0x000059a0)
  RING_START  = 0x4192c000  (offset = 0x4192c000)
  RING_CTRL   = 0x00007000  (disabled, auto report disabled (0x00), not waiting, semaphore not waiting, length = 0x008 4KB pages)

-- VECS Ring --
  RING_HEAD   = 0x00000000  (offset = 0x00000000, wrap count = 0, wait_for_cond = 0x0)
  RING_TAIL   = 0x00000000  (offset = 0x00000000)
  RING_START  = 0x00000000  (offset = 0x00000000)
  RING_CTRL   = 0x00000000  (disabled, auto report disabled (0x00), not waiting, semaphore not waiting, length = 0x001 4KB pages)

-- VCS2 Ring --
  RING_HEAD   = 0x00000000  (offset = 0x00000000, wrap count = 0, wait_for_cond = 0x0)
  RING_TAIL   = 0x00000000  (offset = 0x00000000)
  RING_START  = 0x00000000  (offset = 0x00000000)
  RING_CTRL   = 0x00000000  (disabled, auto report disabled (0x00), not waiting, semaphore not waiting, length = 0x001 4KB pages)

 - Other registers associated with guilty ring -
  BB_ADDR     = 0x40005294  (offset = 0x40005294, valid = 0x0)
  BB_STATE    = 0x00000020
  IPEIR       = 0x00000000
  ACTHD       = 0x08204ba4
  EIR         = 0x00000000
  EMR         = 0xfffffffa
  ESR         = 0x00000000
  INSTPM      = 0x00000000
  INSTPS      = 0x00008880

===========================================================================
                Stamp info for all indexes
===========================================================================
  Index  Submitted    Returned
    0:   0x0002f26d   0x0002f260 <- BUSY
    1:   0x0000135f   0x0000135f
    2:   0x00000000   0x00000000
    3:   0x00000000   0x00000000
    4:   0x00000533   0x00000533
    5:   0x00000604   0x00000604
    6:   0x00000d9c   0x00000d9c
    7:   0x00008b43   0x00008b43
    8:   0x00000035   0x00000035
    9:   0x00000032   0x00000032
   10:   0x0000006e   0x0000006e
   11:   0x0000004f   0x0000004f
   12:   0x00000082   0x00000082
   13:   0x00000782   0x00000782
   14:   0x0000001c   0x0000001c
   15:   0x0000003d   0x0000003d
   16:   0x00000229   0x00000229
   17:   0x0000006a   0x0000006a
   18:   0x00000032   0x00000032
   19:   0x00000121   0x00000121
   20:   0x00000005   0x00000005
   21:   0x0000000f   0x0000000f
   22:   0x00000200   0x00000200
   23:   0x001139a5   0x0011399d <- BUSY
   24:   0x00000000   0x00000000
   25:   0x00000000   0x00000000
   26:   0x00000000   0x00000000
   27:   0x00000000   0x00000000
   28:   0x00001eb7   0x00001eb7
   29:   0x00000dbf   0x00000dbf
   30:   0x000014eb   0x000014eb
   31:   0x000010d5   0x000010d5
   32:   0x0002c87f   0x0002c87f
   33:   0x00016b8d   0x00016b8d
   34:   0x00001cf7   0x00001cf7
   35:   0x0000002f   0x0000002f
   36:   0x00000003   0x00000003
   37:   0x00000003   0x00000003
   38:   0x00000003   0x00000003
   39:   0x00000003   0x00000003
   40:   0x000000f1   0x000000f1
   41:   0x00000023   0x00000023
   42:   0x00000002   0x00000002
   43:   0x00000002   0x00000002
   44:   0x00000002   0x00000002
   45:   0x00000018   0x00000018
   46:   0x00000002   0x00000002
   47:   0x00096618   0x00096618
   48:   0x00000000   0x00000000
   49:   0x00000000   0x00000000
   50:   0x00000000   0x00000000
   51:   0x00000000   0x00000000
   52:   0x00000000   0x00000000
   53:   0x00000000   0x00000000
   54:   0x00000000   0x00000000
   55:   0x00000000   0x00000000
   56:   0x00000000   0x00000000
   57:   0x00000000   0x00000000
   58:   0x00000000   0x00000000
   59:   0x00000000   0x00000000
   60:   0x00000000   0x0000cb89 <- BUSY
   61:   0x00000000   0x00011b2e <- BUSY
   62:   0x00000000   0x00000000
   63:   0x00000000   0x00000000

===========================================================================
                         Scheduler Status
===========================================================================
  Submitted Execlists:
     RCS: ctxt ID[225] | ctxt ID[0]
     VCS: [0/0]
     BCS: [0/0]
    VECS: [0/0]
    VCS2: [0/0]

  Blocked Channels:

  Work Queue Descriptors:
    [  0]: head 0x86, tail 0x93, refcount_a 5, refcount_u 1, storage_va 0xffffff8110e30000, storage_ga 0x41989000
    [  1]: head 0x3c, tail 0x3c, refcount_a 4, refcount_u 1, storage_va 0xffffff81112d1000, storage_ga 0x41a5a000
    [  6]: head 0x78, tail 0x78, refcount_a 4, refcount_u 1, storage_va 0xffffff8114828000, storage_ga 0x427f9000
    [  7]: head 0x126, tail 0x

my_mac_flickers_wtf_apple · Feb 14, 2019

MBP 2018 here since Dec. I just got initiated in the kernal panic club when my keyboard and mouse just froze for a minute! Also my mac flickers when connected to an external display! YAY APPLE!

afir93 · Feb 14, 2019

I may have had my first kernel panics in the 7 months of owning a 2018 MBP 15", though I'm not entirely sure about it. I believe that I just put my MBP to sleep last evening, as I usually do (rarely ever turn it off overnight if I use it the next day), but when I woke up today, it was completely off and started booting up. The only thing that was connected to it was the USB-C cable connected to the power outlet, no monitors or the like.

Again I'm not 100% sure, maybe I accidentally turned my MBP completely off last night instead of just putting it to sleep. Honestly if I didn't remember all the posts here on MacRumors, I wouldn't have thought twice about it. To those of you more familiar with the kernel panics, could this have been one, or does it sound like a characteristic scenario for a kernel panic to happen? Can I verify somewhere if it was indeed a kernel panic/related to the T2 chip (I heard with the console app but I'm not very familiar with it)? Again I had nothing connected but power, the only related thing I can think about is that I hadn't completely turned off my MBP for 2-3 weeks, so maybe it was running without a break for "too long"? Not sure, lol.

If it won't happen again then I won't worry about it, first time happening. Just thought it was a bit curious and that I'd point it out here.

vaugha · Feb 14, 2019

afir93 said:
I may have had my first kernel panics in the 7 months of owning a 2018 MBP 15", though I'm not entirely sure about it. I believe that I just put my MBP to sleep last evening, as I usually do (rarely ever turn it off overnight if I use it the next day), but when I woke up today, it was completely off and started booting up. The only thing that was connected to it was the USB-C cable connected to the power outlet, no monitors or the like.

Again I'm not 100% sure, maybe I accidentally turned my MBP completely off last night instead of just putting it to sleep. Honestly if I didn't remember all the posts here on MacRumors, I wouldn't have thought twice about it. To those of you more familiar with the kernel panics, could this have been one, or does it sound like a characteristic scenario for a kernel panic to happen? Can I verify somewhere if it was indeed a kernel panic/related to the T2 chip (I heard with the console app but I'm not very familiar with it)? Again I had nothing connected but power, the only related thing I can think about is that I hadn't completely turned off my MBP for 2-3 weeks, so maybe it was running without a break for "too long"? Not sure, lol.

If it won't happen again then I won't worry about it, first time happening. Just thought it was a bit curious and that I'd point it out here.

Sounds like a kernel panic to me. There should be a log stored somewhere in your drive when it happened. If you search the forum, you will find it.

appelei · Feb 14, 2019

Sooo, they (the Apple guys and girls) didn't solve the problem? I visited this thread end of November for the last time.

Plutonius · Feb 15, 2019

appelei said:
Sooo, they (the Apple guys and girls) didn't solve the problem? I visited this thread end of November for the last time.

Apple has been aware of the bridgeOS fault for over a year (since the iMac Pro was released).

If it's a hardware issue with the T2, software updates can most likely only mitigate it (reduce the chance it will happen). I doubt we will see a hardware change until Apple comes out with the 2019 model.

I think that most people will put up with the bridgeOS fault if it rarely occurs.

iZeljko · Feb 15, 2019

Plutonius said:
Apple has been aware of the bridgeOS fault for over a year (since the iMac Pro was released).

If it's a hardware issue with the T2, software updates can most likely only mitigate it (reduce the chance it will happen). I doubt we will see a hardware change until Apple comes out with the 2019 model.

I think that most people will put up with the bridgeOS fault if it rarely occurs.

I am also waiting to see what Apple will release in MacBook Pro form in August this year. Till then I am thrusting the new MM with eGPU to do my stuff... But I won't be biting the bullet before the Mac is proven to be a solid machine again as I just do not want to afford myself such a trouble for premium price.

If it has a Mac price tag and name, it needs to work like a Mac.

mdbradigan · Feb 15, 2019

Marketh said:
This has probably already been asked & answered somewhere in the last 128 pages, but, is this also affecting 2018 13" models? My line of thought is this doesn't have a dedicated video card? I've never experienced this on my 13" which I've had from launch in Summer.

I have this every single day on my 13" 2018 MBP. I have it plugged into a dock and eGPU and if the machine goes to sleep for more than ~20 minutes, it ain't waking up. I have to disconnect the TB3 ports, then either restart it or wait for it to resume after logging in (and touch ID does not work in these instances, so I always have to use password).

So - basically (since I keep my laptop in clamshell mode) - every. single. workday - I have to disconnect my computer, pull it out of stand, open it, log in, re-connect it, place it back in stand.

Is.... rather annoying.

advantechnica · Feb 16, 2019

Update 10.14.3 seems to have resolved the crashing for me. I don't use any peripherals and wasn't when I experienced the crashes prior. T2 firmware version: 16P3133

2018 MacBook Pros crashing with "Bridge OS" error

macrumors 65816

macrumors member

macrumors G3

macrumors 603

macrumors newbie

macrumors newbie

macrumors 65816

macrumors newbie

macrumors Penryn

macrumors member

macrumors 6502a

macrumors newbie

macrumors newbie

macrumors newbie

macrumors regular

macrumors 6502

macrumors newbie

macrumors newbie

macrumors 6502a

macrumors 6502a

macrumors newbie

macrumors G3

macrumors regular

macrumors regular

macrumors newbie

Our Staff