2018 MacBook Pros crashing with "Bridge OS" error

[RumorConsumer]

Continuing where I left off; Nope, I just confirmed it, the KP does NOT happen on this 2017 5K iMac... So as expected the issue is absolutely T2 related as theorized.

Now the question is what will Apple do with this info? The answer, a resounding absolutely NOTHING! SMH

Yeah it does seem to be a problem. Apple does fix things like this. If getting wound up and convincing yourself that nobody is working on it is working for you, great. But unless Ive missed something you don't have any evidence that they are or are not. Maybe, just as an experiment, it would be easier on your mind to root for the engineers fixing the issue right now and visualizing and lending all your sureness to that instead of sending out all the negativity. It's a choice. Totally optional of course.

 

[dspdoc]

Yeah it does seem to be a problem. Apple does fix things like this. If getting wound up and convincing yourself that nobody is working on it is working for you, great. But unless Ive missed something you don't have any evidence that they are or are not. Maybe, just as an experiment, it would be easier on your mind to root for the engineers fixing the issue right now and visualizing and lending all your sureness to that instead of sending out all the negativity. It's a choice. Totally optional of course.

Here's my evidence that said engineers are not hard at work fixing this (at least not diligently); the issue has existed since December 14, 2017 and still remains to this date. Don't mistake my posts as negativity and then suggest I be more Zen. Namaste.

 

[ra004e]

Looks like I jinxed it... Just had my first kernel panic on 13" w/TB, 16/256gb.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-22 14:51:08.20 +0000","incident_id":"69D3CC97-C02A-473A-94E8-FC5BCCCA0F7C"}
{
"build" : "Bridge OS 2.4.1 (15P6703)",
"product" : "iBridge2,4",
"kernel" : "Darwin Kernel Version 17.7.0

Occurred whilst I was using Keynote (lost work, thanks Apple). No devices connected, only Wi-fi.

Bug 210 is just the gift that keeps on giving!

If this happens to you again could you post bit further down the panic report, I'm curious what in the stack trace is causing the issue. All my crashes so far seems to be Intel Graphics related.

I'm not sure this is really the error.

""caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-22 14:51:08.20 +0000","incident_id":"69D3CC97-C02A-473A-94E8-FC5BCCCA0F7C"}"

I think this might be the reporting mechanism the T2/Bridge OS is providing.

In my instance it's always crashing interacting with Chrome and all error/KP reports after reboot conclude with the stack trace failing on Intel Graphics Driver.

 

[Apple Knowledge Navigator]

If this happens to you again could you post bit further down the panic report, I'm curious what in the stack trace is causing the issue. All my crashes so far seems to be Intel Graphics related.

I'm not sure this is really the error.

""caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-22 14:51:08.20 +0000","incident_id":"69D3CC97-C02A-473A-94E8-FC5BCCCA0F7C"}"

I think this might be the reporting mechanism the T2/Bridge OS is providing.

In my instance it's always crashing interacting with Chrome and all error/KP reports after reboot conclude with the stack trace failing on Intel Graphics Driver.

Sure, I'm not sure how far down you want me to go but here's more:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-22 14:51:08.20 +0000","incident_id":"69D3CC97-C02A-473A-94E8-FC5BCCCA0F7C"}
{
"build" : "Bridge OS 2.4.1 (15P6703)",
"product" : "iBridge2,4",
"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",
"incident" : "69D3CC97-C02A-473A-94E8-FC5BCCCA0F7C",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-22 14:51:07.72 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff015d73984): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 15P6703\nKernel version: Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 26CB7FFEC7AA68DD8FCEC101101C7E4E\niBoot version: iBoot-4076.75.2\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x000000000f600000\nKernel text base: 0xfffffff016604000\nEpoch Time: sec usec\n Boot : 0x5b71ecd8 0x000074c7\n Sleep : 0x5b7d6b2b 0x0005956f\n Wake : 0x5b7d6b56 0x00034cf4\n Calendar: 0x5b7d7840 0x00061962\n\nPanicked task 0xffffffe000405ce8: 3386 pages, 205 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0007e5950, backtrace: 0xffffffe011ceb530, tid: 277\n\t\t lr: 0xfffffff0167f88f0 fp: 0xffffffe011ceb670\n\t\t lr: 0xfffffff0166e15f4 fp: 0xffffffe011ceb680\n\t\t lr: 0xfffffff016713a44 fp: 0xffffffe011ceb9f0\n\t\t lr: 0xfffffff016713dd4 fp: 0xffffffe011ceba50\n\t\t lr: 0xfffffff016715914 fp: 0xffffffe011ceba70\n\t\t lr: 0xfffffff015d73984 fp: 0xffffffe011cebae0\n\t\t lr: 0xfffffff015d75bc8 fp: 0xffffffe011cebb80\n\t\t lr: 0xfffffff015d7313c fp: 0xffffffe011cebc00\n\t\t lr: 0xfffffff015d32aa4 fp: 0xffffffe011cebc30\n\t\t lr: 0xfffffff016b70784 fp: 0xffffffe011cebc60\n\t\t lr: 0xfffffff016b700bc fp: 0xffffffe011cebc90\n\t\t lr: 0xfffffff0166ec500 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 95392 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pageSize":16384,"memoryPressure":false,"memoryPages":

(Sorry for the formatting - I'm not used to pasting code)

 

[zargap]

Here's my evidence that said engineers are not hard at work fixing this (at least not diligently); the issue has existed since December 14, 2017 and still remains to this date. Don't mistake my posts as negativity.

I don't think I'm mistaking anything for anything, now you're posting about a computer that doesn't even have the chip that is the obvious culprit in this issue and I'm confused about how that's helpful at all aside to say previous apple good new apple bad, arrrrrrrgh.

If this happens to you again could you post bit further down the panic report, I'm curious what in the stack trace is causing the issue. All my crashes so far seems to be Intel Graphics related.

I'm not sure this is really the error.

""caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-22 14:51:08.20 +0000","incident_id":"69D3CC97-C02A-473A-94E8-FC5BCCCA0F7C"}"

I think this might be the reporting mechanism the T2/Bridge OS is providing.

In my instance it's always crashing interacting with Chrome and all error/KP reports after reboot conclude with the stack trace failing on Intel Graphics Driver.

Could you check by PID like in my previous post? Also could you show how you're seeing the Intel Graphics Driver failing?

 

[ra004e]

Mate I disagree, see my error report below:
Mon Jul 23 15:18:24 2018

*** Panic Report ***
panic(cpu 2 caller 0xffffff7fa19c8cf5): "Failed to complete supporting devices sleep/wake\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleEmbeddedOSSupport/AppleEmbeddedOSSupport-135.50.3/Source/Drivers/AppleEmbeddedOSSupportHost/AppleEmbeddedOSSupportHost.cpp:460
Backtrace (CPU 2), Frame : Return Address
0xffffff921ba2bbf0 : 0xffffff801ec6c1c6
0xffffff921ba2bc40 : 0xffffff801ed95274
0xffffff921ba2bc80 : 0xffffff801ed87544
0xffffff921ba2bcf0 : 0xffffff801ec1e1e0
0xffffff921ba2bd10 : 0xffffff801ec6bc3c
0xffffff921ba2be40 : 0xffffff801ec6b9fc
0xffffff921ba2bea0 : 0xffffff7fa19c8cf5
0xffffff921ba2bed0 : 0xffffff801eca5844
0xffffff921ba2bf40 : 0xffffff801eca53a5
0xffffff921ba2bfa0 : 0xffffff801ec1d557
Kernel Extensions in backtrace:
com.apple.driver.AppleEmbeddedOSSupportHost(1.0)[CCE30882-1413-3FEB-ACDD-077C8D1DABE7]@0xffffff7fa19c7000->0xffffff7fa19ccfff
dependency: com.apple.iokit.IOACPIFamily(1.4)[95DA39BB-7C39-3742-A2E5-86C555E21D67]@0xffffff7f9f948000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
17G65

Kernel version:
Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
Kernel UUID: 1AE5ACFD-3B6F-3D74-AD52-31F1430DBC6F
Kernel slide: 0x000000001ea00000
Kernel text base: 0xffffff801ec00000
__HIB text base: 0xffffff801eb00000
System model name: MacBookPro14,2 (Mac-CAD6701F7CEA0921)

I think it is a kernel problem for all of us. So is this so different to your problem?

This post is reinforcing my assumption regarding the T2 . It seems like it's reporting these issues not necessarily the cause of them. As i look through this thread and look at any stack traces they seem kernel related. My understanding T2 is it's own OS running, so it would be available after the OS crashed thus able to report these type issues. Of course I don't know for sure, but have had a bit of time debugging linux kernel and most of these issues I'm seeing look like they're software/driver related. So Bridge OS errors may be something of a red herring of multiple issues effecting these new machines and unless we have a Apple kernel dev willing to comment I don't think we can just put the blame on Bridge OS just yet.

 

[M.Rizk]

I don't think I'm mistaking anything for anything, now you're posting about a computer that doesn't even have the chip that is the obvious culprit in this issue and I'm confused about how that's helpful at all aside to say previous apple good new apple bad, arrrrrrrgh.

He was talking about the iMac Pro, the first Mac with the T2 chip.

 

[ra004e]

I don't think I'm mistaking anything for anything, now you're posting about a computer that doesn't even have the chip that is the obvious culprit in this issue and I'm confused about how that's helpful at all aside to say previous apple good new apple bad, arrrrrrrgh.


Could you check by PID like in my previous post? Also could you show how you're seeing the Intel Graphics Driver failing?

I will as soon as it panics again, I've been using Safari instead of Chrome and no crashes yet, but only a few days don't so want to get optimistic too soon. I will go back to Chrome tomorrow and see if I can get it to crash again. It was crashing at least 2-3 times a day using Chrome with same Intel error in stack trace. Will let you know.

 

[michael31986]

Can software fix this?

 

[onelm]

This post is reinforcing my assumption regarding the T2 . It seems like it's reporting these issues not necessarily the cause of them. As i look through this thread and look at any stack traces they seem kernel related. My understanding T2 is it's own OS running, so it would be available after the OS crashed thus able to report these type issues. Of course I don't know for sure, but have had a bit of time debugging linux kernel and most of these issues I'm seeing look like they're software/driver related. So Bridge OS errors may be something of a red herring of multiple issues effecting these new machines and unless we have a Apple kernel dev willing to comment I don't think we can just put the blame on Bridge OS just yet.

I think you're absolutely correct on this one -- I posted earlier in the thread about having the sleep/wake KPs on my 2018 MBP but also having had them on a 2017 MBP. The crashing behaviour is exactly the same between the two machines, and only occurs when the MBP sleeps with external display(s) connected. It appears that some variant of the issue existed with 2016 MBPs as well:

https://discussions.apple.com/thread/8248092

I'm kicking myself for not hanging onto the crash logs from my 2017, but Intel Graphics / driver as suspects makes a lot more sense to me at this point than the T2 chip specifically.

 

[ra004e]

Sure, I'm not sure how far down you want me to go but here's more:

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-22 14:51:08.20 +0000","incident_id":"69D3CC97-C02A-473A-94E8-FC5BCCCA0F7C"}
{
"build" : "Bridge OS 2.4.1 (15P6703)",
"product" : "iBridge2,4",
"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",
"incident" : "69D3CC97-C02A-473A-94E8-FC5BCCCA0F7C",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-22 14:51:07.72 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff015d73984): macOS watchdog detected\nDebugger message: panic\nMemory ID: 0xff\nOS version: 15P6703\nKernel version: Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 26CB7FFEC7AA68DD8FCEC101101C7E4E\niBoot version: iBoot-4076.75.2\nsecure boot?: YES\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x000000000f600000\nKernel text base: 0xfffffff016604000\nEpoch Time: sec usec\n Boot : 0x5b71ecd8 0x000074c7\n Sleep : 0x5b7d6b2b 0x0005956f\n Wake : 0x5b7d6b56 0x00034cf4\n Calendar: 0x5b7d7840 0x00061962\n\nPanicked task 0xffffffe000405ce8: 3386 pages, 205 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0007e5950, backtrace: 0xffffffe011ceb530, tid: 277\n\t\t lr: 0xfffffff0167f88f0 fp: 0xffffffe011ceb670\n\t\t lr: 0xfffffff0166e15f4 fp: 0xffffffe011ceb680\n\t\t lr: 0xfffffff016713a44 fp: 0xffffffe011ceb9f0\n\t\t lr: 0xfffffff016713dd4 fp: 0xffffffe011ceba50\n\t\t lr: 0xfffffff016715914 fp: 0xffffffe011ceba70\n\t\t lr: 0xfffffff015d73984 fp: 0xffffffe011cebae0\n\t\t lr: 0xfffffff015d75bc8 fp: 0xffffffe011cebb80\n\t\t lr: 0xfffffff015d7313c fp: 0xffffffe011cebc00\n\t\t lr: 0xfffffff015d32aa4 fp: 0xffffffe011cebc30\n\t\t lr: 0xfffffff016b70784 fp: 0xffffffe011cebc60\n\t\t lr: 0xfffffff016b700bc fp: 0xffffffe011cebc90\n\t\t lr: 0xfffffff0166ec500 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 95392 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available",
"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pageSize":16384,"memoryPressure":false,"memoryPages":

(Sorry for the formatting - I'm not used to pasting code)

So I'm not a kernel dev, but this was not like what I was seeing and could be T2 related. As it looks pointing to the ARM chip where the kernel did panic.

Thanks for posting, at least we can get an idea of what these issues are creating the panics.

 

[SDColorado]

Can software fix this?

I don't know if anyone knows yet. Jeremy Horowitz of Venture Beat wrote a pretty good summary, talking about how you would assume with the T2 issues piling up with the iMac Pro, that you would assume Apple would have addressed it prior to rolling it out in the MBP, but they didn't and also mentions how Apple has been supposedly quietly working on a software update, while also apparently blaming hardware and other possible issues. I was instructed by the Apple Engineer I spoke with to swap it for a replacement one. If it is a software fix, then why?

https://venturebeat.com/2018/07/25/apple-t2-chip-blamed-for-2018-macbook-pro-and-imac-pro-crashes/

 

[Apple Knowledge Navigator]

So I'm not a kernel dev, but this was not like what I was seeing and could be T2 related. As it looks pointing to the ARM chip where the kernel did panic.

Thanks for posting, at least we can get an idea of what these issues are creating the panics.

No problem. I should also point out that I've owned this MBP for 3 weeks now, and this is the first KP (or any issue, for that matter) that I've had. Apart from finger prints staining my screen...

Machine just froze, then after about 2-mins the screen went black. Trackpad was still active as in it could still 'click'. Tried pressing and holding the power button but nothing happed. After another couple of minutes the Apple logo appeared.

 

[dspdoc]

I don't know if anyone knows yet. Jeremy Horowitz of Venture Beat wrote a pretty good summary, talking about how you would assume with the T2 issues piling up with the iMac Pro, that you would assume Apple would have addressed it prior to rolling it out in the MBP, but they didn't and also mentions how Apple has been supposedly quietly working on a software update, while also apparently blaming hardware and other possible issues. I was instructed by the Apple Engineer I spoke with to swap it for a replacement one. If it is a software fix, then why?

https://venturebeat.com/2018/07/25/apple-t2-chip-blamed-for-2018-macbook-pro-and-imac-pro-crashes/

Exactly! And I went through 4 machines in total, 2 MBPs and 2 iMPs, they all did it.

 

[n3t_runn3r]

I opened a case with Apple yesterday and after an hour of basic attempts to resolve (remove launch agents, reboot, etc etc) to no avail, my case was escalated to a senior tech who had me reset the SMC. Once that was done, I could not reproduce the problem with the tech on the phone with me. The tech closed the ticket and now today, the problem is back. I torn between waiting for a firmware/ OS patch from Apple or asking for a replacement for this new Macbook Pro 13" TB.

 

[dspdoc]

I opened a case with Apple yesterday and after an hour of basic attempts to resolve (remove launch agents, reboot, etc etc) to no avail, my case was escalated to a senior tech who had me reset the SMC. Once that was done, I could not reproduce the problem with the tech on the phone with me. The tech closed the ticket and now today, the problem is back. I torn between waiting for a firmware/ OS patch from Apple or asking for a replacement for this new Macbook Pro 13" TB.

Why do people keep taking replacements? You are wasting your valuable time. I am not trying to be rude whatsoever, but if you scour this thread you will see replacement after replacement.

 

[SDColorado]

Exactly! And I went through 4 machines in total, 2 MBPs and 2 iMPs, they all did it.

Yet, at least apparently, they don't *all* do it. Which is why I have a hard time believing it is software/firmware. If it was, wouldn't all if not the majority be doing it if they all were running the same software/firmware? If Apple was convinced that a firmware patch was absolutely the cause, would the be having owners return them and collecting them?

Maybe I am wrong, but one thing I am fairly certain of, is that Apple isn't certain.

Why do people keep taking replacements? You are wasting your valuable time. I am not trying to be rude whatsoever, but if you scour this thread you will see replacement after replacement.

I am trying another because Apple incentivized the latest try after the replacement for the first one arrived damaged. We shall see how this one goes ...

 

[dspdoc]

Yet, at least apparently, they don't *all* do it. Which is why I have a hard time believing it is software/firmware. If it was, wouldn't all if not the majority be doing it if they all were running the same software/firmware? If Apple was convinced that a firmware patch was absolutely the cause, would the be having owners return them and collecting them?

Maybe I am wrong, but one thing I am fairly certain of, is that Apple isn't certain.

LOL I love that line. I am fairly certain they are most certainly not certain.

PM'd you

 

[SDColorado]

LOL I love that line. I am fairly certain they are most certainly not certain.

I am certain they are not certain what they are uncertain about... ahh never mind hahaha

Edit: So anyway I received a 3rd unit last night that is in effect my second attempt at a problem free one. I never even attempted to do anything with the damaged one. Sooo... giving it one more try, but less than 24 hours in.

 

[shawndebnath]

...The crashing behaviour is exactly the same between the two machines, and only occurs when the MBP sleeps with external display(s) connected....

On the very first night, I had it panic with no external displays or accessories connected, just the power chord. Though after properly resetting NVRAM and SMC, haven't had the issue repeat yet for about a week now. It's not limited to sleeping while connected to external displays.

I also tried the USB adapter repro (connect while sleeping and wake it back up) - no luck.

 

[n3t_runn3r]

Why do people keep taking replacements? You are wasting your valuable time. I am not trying to be rude whatsoever, but if you scour this thread you will see replacement after replacement.

Point taken, however my choices seem to be: (1) Make Apple fix it or (2)

Why do people keep taking replacements? You are wasting your valuable time. I am not trying to be rude whatsoever, but if you scour this thread you will see replacement after replacement.

You are not being rude at all. This is very frustrating for all of us.

Just off the phone again with Apple and re-opened my case. This time they want me to reinstall MacOS. Nice.

It would seem my (our?) options are:
1) Keep returning the machines. Maybe when we get to 100,000, someone will take notice?
2) Futz with Apple support: reinstall MACOS, reset SMC, reset NVRAM, rinse & repeat
3) Wait for Apple to acknowledge there truly is a problem and hope they will release a patch/fix before we die of old age.
4) Buy a Dell?

 

[dspdoc]

Point taken, however my choices seem to be: (1) Make Apple fix it or (2)


You are not being rude at all. This is very frustrating for all of us.

Just off the phone again with Apple and re-opened my case. This time they want me to reinstall MacOS. Nice.

It would seem my (our?) options are:
1) Keep returning the machines. Maybe when we get to 100,000, someone will take notice?
2) Futz with Apple support: reinstall MACOS, reset SMC, reset NVRAM, rinse & repeat
3) Wait for Apple to acknowledge there truly is a problem and hope they will release a patch/fix before we die of old age.
4) Buy a Dell?

I feel your pain my friend! I opted to get rid of all machines with T2 chips for the time being and revert back to a 2017 5K iMac. I sincerely hope Apple figures this out sooner rather than later. I do NOT like Dell, so I can't vote for that option. I don't know what the magic number of machines having issues needs to be before Apple sounds the fire alarm and gets serious about resolving this.

 

[Wags]

Point taken, however my choices seem to be: (1) Make Apple fix it or (2)


You are not being rude at all. This is very frustrating for all of us.

Just off the phone again with Apple and re-opened my case. This time they want me to reinstall MacOS. Nice.

It would seem my (our?) options are:
1) Keep returning the machines. Maybe when we get to 100,000, someone will take notice?
2) Futz with Apple support: reinstall MACOS, reset SMC, reset NVRAM, rinse & repeat
3) Wait for Apple to acknowledge there truly is a problem and hope they will release a patch/fix before we die of old age.
4) Buy a Dell?

5) Class action lawsuit

 

[n3t_runn3r]

For me, the panics have occurred while the lid is closed and laptop is charging. Roughly once every four days. No real custom configuration. FileVault and Touch ID enabled.

What I find most interesting is that during use, light use even, the keyboard is noticeably warm to the touch (approximately in the top left, E, R, 4, 3 keys). Looking at logic board diagrams, this is right above the T2 chip. Running iStats shows that the "Platform Controller Hub Die" is running at 48°C. That sounds like the T2 chip. It is roughly 5-10°C warmer than any other component, including CPU and GPU.

Are others experiencing a warm keyboard like this?

It seems you are running iStat Menu, as I am. How many of us experiencing this problem are running iStat Menu?

 

[RumorConsumer]

It seems you are running iStat Menu, as I am. How many of us experiencing this problem are running iStat Menu?

I am. Maybe just correlative though... but it is talking to Bridge OS to get all that data... you may have something... who isn’t who is having this issue is the better question...