Had another black screen unresponsive
I still have this. No kernel panic reporting, but still hard reboots.
I still have this. No kernel panic reporting, but still hard reboots.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2018 MacBook Pros crashing with "Bridge OS" error
- Thread starter kryptticAZ
- Start date
- Sort by reaction score
Just had the exact same thing happen to me.
Black screen, no response, force restart and the system comes back up with no trouble report dialog window and no panic log where I expect to see it.
Had that too. But again, only when it went to sleep with my 4k connected. Freaked me out a bit as it took a bit to come back on after holding the power button.
Edit: every other time I close the lid without the 4k attached, it wakes up faster than I can open the lid all the way.
Feels like I'm taking crazy pills, but I'm glad I'm not alone I guess
Have you filed for a refund?
For the computer or the crazy pills? Pretty sure I'm out of the 2 weeks and frankly, too time constrained and/or lazy to deal with it, like i've said the restarts are more annoying than anything in practice (for now).
I get that it’s a pain but just know that if you asked for it you’d likely still get a refund or replacement. I just had a replacement ordered and I’m on day 16. They said something about it being possible up to 30 days in some situations.
I am sure that technically he *is* correct, but as mentioned it isn't really a solution. It treats a symptom, but doesn't address the underlying cause. Not to mention in the time that I tried it, the machine was constantly warm and I worry a little about image retention, even with the shifting screen saver. Maybe both of those are also unnecessary worries. But it still goes back to "it is not a reasonable solution."
That said, despite me having to explain to him that the T2 chip had a different procedure than the previous model, since we went through the SMC/NVRAM reset procedure, I have not had another BridgeOS crash. I am hesitant to call it "cured" since it has only been a few days, but keeping my fingers crossed.
HOWEVER... new symptom. My MBP occasionally reports ""Wireless signal is too weak to unlock with my Apple Watch" or something like that. Despite the fact that I am at the keyboard and the watch is obviously on my wrist. I am sure it isn't the watch, because I don't get that issue with my iMac ever.
It would be a stopgap measure, until such a time Apple could get a real fix out there - if it's a software patch, or maybe a product recall of the affected units if it's a deeper issue. But yeah, it wouldn't be ideal, for sure.
It's OK; quality LCD panels don't retain imagery.
Even those panels that are susceptible (I haven't seen one in years, and those were TN panels, not IPS) should be OK if you have a screen saver active (or a fully black - or white - screen.)I'm wishing you good luck!
Weird... Having just received my own MBP the other day, this is the first time I got to try out unlocking with the Watch. My old MBP was six months too old to get the BT4.0 functionality necessary to enable it. Meh. Now though, every time I wake my Mac it either unlocks before I have time to finish raising the screen, or within a second or two later. I literally don't have time to reach the touchid button; it's been super reliable so far. OG Watch Sport, by the way. Over 3 years now, and shows that even an old dog can have new tricks!
Weird... Having just received my own MBP the other day, this is the first time I got to try out unlocking with the Watch. My old MBP was six months too old to get the BT4.0 functionality necessary to enable it. Meh. Now though, every time I wake my Mac it either unlocks before I have time to finish raising the screen, or within a second or two later. I literally don't have time to reach the touchid button; it's been super reliable so far. OG Watch Sport, by the way. Over 3 years now, and shows that even an old dog can have new tricks!
It worked fine for 2 years on my 2016 MBP, which my wife now has. Works flawlessly on my iMac as well. It has worked up until a couple days ago fine on this one as well and still does 8 out of 10 times. More an annoyance than a real problem. But just another “feature”
Look in the folder just above "Retired." All of my Bridge OS panic logs are in the "ProxidedDevice-Bridge" folder.
I noticed in /Library/Logs/DiagnosticReports/ProxiedDevice-Bridge that I have multiple powerchimed-xxxxxxx.ips files tagged with a timestamp that are within milliseconds of the Bridge panic-full-xxxxxxx.ips file.
In the powerchimed files I have 2 types of exceptions:
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Do others that have the same files with exceptions ?
Wondering if its related to the bridge issue given the timing.
Example:
In the powerchimed files I have 2 types of exceptions:
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Do others that have the same files with exceptions ?
Wondering if its related to the bridge issue given the timing.
Example:
Code:
{"app_name":"powerchimed","app_version":"","bug_type":"109","timestamp":"2018-08-01 14:39:29.19 +0000","os_version":"Bridge OS 2.4.1 (15P6703)","incident_id":"17DBB8BD-7171-466F-9655-4AA7A8CFF7A0","slice_uuid":"d66a7abc-5aff-3702-a9db-aeb69571e492","build_version":"","is_first_party":true,"share_with_app_devs":false,"name":"powerchimed"}
Incident Identifier: 17DBB8BD-7171-466F-9655-4AA7A8CFF7A0
CrashReporter Key: c0dec0dec0dec0dec0dec0dec0dec0dec0de0001
Hardware Model: iBridge2,3
Process: powerchimed [48]
Path: /usr/libexec/powerchimed
Identifier: powerchimed
Version: ???
Code Type: ARM-64 (Native)
Role: Unspecified
Parent Process: launchd [1]
Coalition: com.apple.powerchimed [49]
Date/Time: 2018-08-01 14:39:29.0805 +0000
Launch Time: 2018-08-01 14:39:28.8558 +0000
OS Version: Bridge OS 2.4.1 (15P6703)
Baseband Version: n/a
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000020
VM Region Info: 0x20 is not in any region. Bytes before following region: 4305813472Thanks for the example.
I see the same thing with the same timestamp relationship to the panic ips file.
I checked there after my last restart and there was nothing, right now just some xml lookin stuff in there, I'll definitely report back if I get something there.
I've had two KPs followed by the BridgeOS error log. The first time was before the supplemental update while it was asleep and connected to my LG UltraFine 4K monitor.
The second one was after the supplemental update while it was asleep, but not connected to anything except power.
My MacBook Pro was asleep from Tuesday - Friday this week while I was traveling for work, and no KP at all. There seems to be no rhyme or reason to it.
The second one was after the supplemental update while it was asleep, but not connected to anything except power.
My MacBook Pro was asleep from Tuesday - Friday this week while I was traveling for work, and no KP at all. There seems to be no rhyme or reason to it.
My exact experience. Exact same screen. I’ve not had any issues if it is just power though. Only with something else connected, and again, never on battery power.
Seems like Apple is offering replacement units pretty much easily. Good to know they went for it even after 16 days of ownership.
Maybe we could have a poll to know how many person here had the Bridge OS KP and how many of them went for a replacement.
Strangely, I don't have these... Anyone nows what this process does ?
Maybe we should start a thread aside from this one on this matter.
Have you called Apple about it ? Since I already called for the KP and was offered a replacement, I didn't call them again about this issue. Will have mine in 10 days and maybe you should ask for one too...
Could you point me to other forums discussing this issue ?
When I start reading threads like this I think to myself, well it's just a couple of people with issues out of thousands of customers. But I have to say there are a lot of people with issues on this thread. Really makes me think twice about buying another MBP. Im going to wait.
It's a shame, on my 2016 MB the logic board broke - then they gave me the 2017 version and this is even worst. If they would just update the MB Air, I would definitely get it.
Maybe too add and don't change the keyboard on the MB Air... When I see my colleagues tipping on their ugly Dell notebooks I feel so jealous, it looks so comfortable.
Last edited:
I don't think so mate. It's a T2 chip related issue and T2 chip is only used on iMac Pro 2018 and mbp 2018. Perhaps some other factors are responsible for whatever happened on you 2017 mbp.
[doublepost=1533980390][/doublepost]
Despite the annoying reboot, I gotta say 2018 mbp is still a perfect machine. No need to wait from my perspective.
Apple has been dealing with the T2 crashing since last year. They've improved the stability so that many who are incurring it are incurring it less. There's still some who have a high occurrence of crashes it seems. Since Apple has a 14 day return period, try it out, and return it if you have issues.
I wouldn't say perfect, some folks seem to have the crackling, others have the T2. My machine has neither and I'm really happy with it.
It's good to hear there are still people in this thread that haven't had any issues. Up until yesterday I was right there with you as this 13" had been perfect. No crashes, no restarts, no crackling speakers, etc. I just happened to wake it yesterday afternoon, though, and I'd also been hit with the "Bridge OS" kernel panic and restart. Nothing had changed; it had the same monitor cable and I was doing the same stuff I'd been doing with it for 2 weeks. No idea what suddenly caused it to happen but seeing as they offered me a replacement (on day 16) and said I can keep this one until the new one arrives (in 2 weeks) I figured I'd give it a go, despite honestly thinking it's software-related. The best part was that the new one will come with its own 14 day refund/return period and she said that can actually be 30 days.
I will be honest, this T2 has me a bit spooked, and while I've yet to see a crash, I'm concerned it will happen at the most inopportune time. From what I've read (granted its not a lot), Apple believes its software related and so as time moves on, I think they'll improve things, but that doesn't answer why someone has the problem daily and I don't.
This is why Apple is #1 in customer support. I was able to exchange an iPad months after buying it, and they permitted that. I was not a little over the 14 day return period, but months and they allowed it.
Yeah, let's hope that's the case. It's still a bit worrying that people are having such crashes on their iMac Pros all these months later. Time will tell, I guess. I feel for the people who have these new MacBook Pros and are getting multiple crashes and restarts every day.
Exactly. I've always had good experiences with Apple support.