I once had an issue like that that wasn't a KP, but the GPU hanging. Can you check your console for .gpuRestart files or alike (I believe those are Kernel*.gpuRestart messages, can't quite remember)? (Also WindowServer logs might give a hint)
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
I once had an issue like that that wasn't a KP, but the GPU hanging. Can you check your console for .gpuRestart files or alike (I believe those are Kernel*.gpuRestart messages, can't quite remember)? (Also WindowServer logs might give a hint)
Premal212
macrumors 6502
I believe it was a singular file that was over 20gigs https://discussions.apple.com/thread/8465477?page=10 scroll to horho77.
I was having KP at least 3 times a week on my 2016 Mac, they were all related to intel graphics, either it was illustrator causing it or finder, whenever I was doing something quite taxing on the machine with either of them.
On this replacement machine I'm clean so far.
drdaz
macrumors member
I've got a couple of VM's here that are > 20GB by themselves and I've copied around without issue.
EDIT: I have't tried it on the left hand ports... lol if that makes a difference.
[doublepost=1535542495][/doublepost]
I can't see any messages in the console matching gpuRestart, or files with that name (not sure which you meant or where I should check), but I've spotted some absolute madness in a couple of places.
There are WindowServer*.wakeups_resource.diag files indicating that WindowServer had '45001 wakeups over the last 208 seconds (216 wakeups per second average), exceeding limit of 150 wakeups per second over 300 seconds'. That said, I'm not sure if 'wakeups' mean what I think they mean in this context. And this was not around the time of the crash, so probably a red herring.
I have numerous similar reports about Docker doing *way* too many 'wakeups'.
Last edited:
afir93
macrumors 6502a
How do I check if I had a bridge run issue? Cause I had to restart but didn't get any weird report for diagnostics or anything.
[doublepost=1535544777][/doublepost]
[doublepost=1535544777][/doublepost]
What did you find out was be issue causing this?
drdaz
macrumors member
You're running the Mojave beta as far as I can tell from that trace (Darwin 18 and Bridge OS 3). That's not supposed to be stable.
macagain
macrumors 6502
drdaz, have you tried it w/o the TS3+?
I have a similar setup as you, and it was kp'ing on wake from sleep every single morning (yes, the dreaded bridgeOS error). As a test, I removed the TS3+ from the equation, and connected the 2 LG 4Ks directly to the mbp with dp->usbc cables. I'm going on 16 days now w/ no kp's or sleep/wake issues, with 1, 2, or no external monitors connected. I did do both a NVRAM and SMC reset after removing to TS3+.
There've been a number of posts coming to the defense of the TS3+, that it works great, good tech support etc. However, none of those posts explicitly said 2018 mbp with 2 4K monitors; most were using with 2017/16 models. You, on the other hand, seem to be experiencing exactly the same thing I was, with an almost exact same setup.
Not trying to nail Caldigit here... one day I will re-buy one of their products. I'm just wondering if there is something about an external hub that the 2018's don't like...
drdaz
macrumors member
That's very interesting. I believe (but I'm not 100% sure) that I experienced this once without the dock, and with just 1 screen attached via USB 3 adapter.
I'll be honest though, I feel like it doesn't matter. I feel like an external peripheral shouldn't *be able* to take a machine down like that. Keeping the product from falling on it's ass is very much Apple's responsibility.
EDIT: To answer your question (and not rant), no I haven't done that for an extended period. Could be fun to try.
EDIT: For what it's worth, I got hold of CalDigit at the same time as I got hold of Apple. They say they're running the new machines with the TS3+ without issue.
Last edited:
cwosigns
macrumors 68020
I've had it happen connected to one LG monitor. I've had it happen not connected to anything except power. I'm not sure peripherals have much to do with it.
drdaz
macrumors member
But which thing? The wake / sleep crash?
[doublepost=1535546768][/doublepost]Because there's a lot of stuff happening in this thread 😀
cwosigns
macrumors 68020
The KP on wake with the crash log referencing BridgeOS. But I agree...there is a lot of noise in this thread.
drdaz
macrumors member
There's a lot of noise from the machines, causing the noise in this thread :-/
If all kernel panics get reported like this now (and that seems to be the case), it's gonna be very hard to differentiate between errors for people who don't work intimately with the tech.
I opened the lid on my 15' 2.2/555x this morning and it had shut off and was completely rebooting (apple logo) and there was no error at all. The computer was not attached to anything when it happened. It was unplugged and sitting in it's sleeve in my briefcase all night.
I did not have this issue BEFORE yesterday's update and am now kicking myself for updating a computer that seemed to be working perfectly.
Only thing I can think of is that I may (stress the word "may") have closed the lid before the computer had completed the "back up now" from Time Machine. That's the only thing I can think of that was different (other than the update yesterday) that could account for the computer not waking from sleep properly.
Interestingly, like drdaz said, there was NO ERROR at all. So don't know if it was the Bridge OS error or not.
drdaz
macrumors member
That's the error I got this morning and I did have it before the update. Don't worry, it was coming anyway 😉
[doublepost=1535547741][/doublepost]
For what it's worth @macagain CalDigit did suggest turning off 'automatically switch off harddisks' in Power Saver. I'd forgotten about that til now since it seemed ridiculous. But since they're recommending it for their product it might be worth a bash.
Last edited:
Premal212
macrumors 6502
That’s the quote of this thread !! One way or another none of us are safe
I came into the office this morning to find the following crash on my 2018 13in MacBook Pro. I had installed the latest High Sierra update yesterday. The MacBook was in clamshell mode, connected to an external monitor with an Apple mouse and keyboard connected via Bluetooth. I found it interesting that after the reboot, the Apple mouse was no longer connected. I had to re-connect manually.
{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-08-29 05:49:20.10 +0000","incident_id":"4C06F0C3-F381-46A2-816B-2410EDA4A5C7"}
"build" : "Bridge OS 2.4.1 (15P6805)",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-29 05:49:19.60 +0000",
"incident" : "4C06F0C3-F381-46A2-816B-2410EDA4A5C7",
"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",
"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 566624 **\n",
"macOSPanicFlags" : "0x4",
"macOSPanicString" : "panic(cpu 0 caller 0xffffff80024fab10): \"Sleep\/Wake hang detected\"@\/BuildRoot\
{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6805)","timestamp":"2018-08-29 05:49:20.10 +0000","incident_id":"4C06F0C3-F381-46A2-816B-2410EDA4A5C7"}
"build" : "Bridge OS 2.4.1 (15P6805)",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-29 05:49:19.60 +0000",
"incident" : "4C06F0C3-F381-46A2-816B-2410EDA4A5C7",
"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",
"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 566624 **\n",
"macOSPanicFlags" : "0x4",
"macOSPanicString" : "panic(cpu 0 caller 0xffffff80024fab10): \"Sleep\/Wake hang detected\"@\/BuildRoot\
Ever since yesterday update my computer has been acting strange. Freezing and etc. Would a reset of SMC help?
So weird. I can use touch bar but mouse won't let me click anything
So weird. I can use touch bar but mouse won't let me click anything
Oof, sorry to report I just had a restart after this update but no error report apparently.
I then reset my SMC, no problem, and then tried resetting my NVRAM (assuming that's what ctrl+opt+right shift+power) does and it hangs on a load bar on booting. I left it overnight and it didn't boot. I've never successfully booted after this step, has anyone else had this?
I then reset my SMC, no problem, and then tried resetting my NVRAM (assuming that's what ctrl+opt+right shift+power) does and it hangs on a load bar on booting. I left it overnight and it didn't boot. I've never successfully booted after this step, has anyone else had this?
tjoab
macrumors newbie
The office release from Apple is on their security updates page.... but I can’t find what was actually changed
https://support.apple.com/en-us/HT201222
https://support.apple.com/en-us/HT201222
RumorConsumer
macrumors 68000
drdaz
macrumors member
Docks, external screens?
[doublepost=1535551607][/doublepost]
That means nothing changed; it says it offers the same security as the 10.13.6 release.
RumorConsumer
macrumors 68000
I'm on an i9 with 32 gb of ram and a 1 tb SSD. I use the machine daily in an office environment and have experienced the same BridgeOS kernel panic in a variety of situations, including:
These are just some of the scenarios, but wanted to point out that it's happening to me both when connected to accessories and when not. I'm hopeful yesterday's update will fix (no issues thus far - left machine connected to dock and engaged sleep through menu), but am not holding my breath at this point.
- left with lid open on desk at lock screen, connected to nothing (also when connected to power but nothing else)
- lid open at lock screen, connected to OWC Thunderbolt 3 dock with a few hard drives and LG 5K display connected
- lid open while working, machine sitting idle in lap while in a meeting
These are just some of the scenarios, but wanted to point out that it's happening to me both when connected to accessories and when not. I'm hopeful yesterday's update will fix (no issues thus far - left machine connected to dock and engaged sleep through menu), but am not holding my breath at this point.