Mac OS 10.15.4: Random restarts due to panic(cpu 1 caller

It is an OS issue so no need to reinstall, no need to reset SMC, no need to change power settings. For me the only way to reduce panics now is to reduce audio usage and don't use FaceTime for now (all my panics are caused by bridgeaudiod ). If I use FaceTime during the day I know in about 45 minutes I have a panic. When I don't use audio at all then I can run all day and no issues.

Since this CPU panic issue and hard restart is referencing sleep/power issues and I have observed this occurring when the machine goes to sleep. As others here have noted, I changed some settings that have put a temp fix in place to prevent the machine from going into sleep mode. I have not had the restart issues / CPU panic issues when the machine goes into sleep mode since making the System Settings change.

I unchecked the "Put hard disks to sleep when possible" and have not had the CPU panic issue when going into sleep mode overnight. So far, 3 overnights with no issue.

Clearly this is an issue with macOS 10.15.4 sleep functions. At least for me. Know others have random issues, but this work-around saved me from a lot of frustration. I will wait for Apple to resolve.

marcgarrow wrote:

Is SIP the "allow apps downloaded from: "? That's all? I do want to install from anywhere while taking cautions.. If its something else I'd appreciate if you tell me. I've been a Windows user for 20 years, first time on Mac..

No. That is "Gatekeeper"

You probably had to turn SIP off to make select that "everywhere" setting of Gatekeeper; but as I said, you can and should turn it back on again; the choice you made regarding Gatekeeper will persist.

[Not that it is a big problem leaving Gatekeeper at "App Store and identified developers"; you can STILL launch any application you want! All you have to do is, for the first time you launch only, control-click, choose Open and confirm. Subsequently, you can launch by double-clicking or any other method you prefer.]

The same issue happens for me - 16" MacBook Pro, 6-core i7, 16GB RAM, 10.15.4. Applications open at the time always include Xcode and Android Studio, along with Safari, email and a few terminal windows. There are days where it will happen 3-4x. It's _very_ frustrating especially when Apple plays their usual silent act, and is one of the several reasons I refuse to update to Catalina on my other Macs until Apple fixes this PoS.

I've got the issue on my macbook pro 13 inch late 2018 for months now, so the graphics switching is not the problem.

First thought external display was the problem, but it happens also without anything connected.

Mostly with video calls, but also without.

At first it seemed to only happen with sleeping (in/out) connected to the external monitor; which the errors did for the whole past year. Don't know exactly when, but could be from the first Catalina on.

Tweaked those sleep settings and then disciplined with decoupling external display.

But now it starts happening at other moments, with other log messages and doing different stuf.

Super random and had multiple types of panic messages...

So I don't know at this point, but working from home and having this 2 / 3 times a day is not nice.

Owh, and I upgraded to 10.15.5 two days ago and didn't help a thing.

Audio is doing weird things after the upgrade even, automatically switching audio output from cable headphones to my external display at random without putting it back when I change selection.

I hope this will be fixed soon, because it's horrible

Hello

i have had 2 new 16” MBP since March 2020 both had random freeze/restart. Yes, like you it happened when I was doing nothing special on Word, just typing. And lastest update not saved. But also happened while in Safari and other programs. No rhyme or reason.

i returned both for full refund.

maybe next year I will try again. Meanwhile I have a MB Air

I had the issue with Mojave as well: Mac mini 2018 Core i7 3.2Ghz. Screen freeze for a few seconds, then fans full speed, then reboot.

All these machines are so different, except for the infamous T2

I never got a chance to have it repaired under warranty so now I'm stuck with it; I use my 12 years old iMac most of the time...

... and probably going to move to Linux permanently. I'm so sick of it

HELP! What the **** is going on?

panic(cpu 1 caller 0xfffffff01bc77b8c): "void AppleEmbeddedPCIeUpLinkMgmt::_linkInterruptAction(IOInterruptEventSource *, int): " "A link timeout has been seen after 650000 microseconds and 49999 iterations."@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleEmbeddedPCIeUpLinkMgmt/AppleEmbeddedPCIeUpLinkMgmt-102.120.1/AppleEmbeddedPCIeUpLinkMgmt.cpp:3986
Debugger message: panic
Memory ID: 0xff
OS version: 17P5300
macOS version: 19F101
Kernel version: Darwin Kernel Version 19.5.0: Tue May 26 20:16:42 PDT 2020; root:xnu-6153.121.2~1/RELEASE_ARM64_T8010
Kernel UUID: 123C59BB-125A-31AF-A916-AAF729BE6BE8
iBoot version: iBoot-5540.125.4
secure boot?: YES
x86 EFI Boot State: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x5
x86 Previous Power Transitions: 0x10001000100
PCIeUp link state: 0x89473611
Paniclog version: 13
Kernel slide:     0x0000000013c2c000
Kernel text base: 0xfffffff01ac30000
mach_absolute_time: 0xa6ba0bcb24a
Epoch Time:        sec       usec
  Boot    : 0x5f0611cf 0x0000353c
  Sleep   : 0x5f154396 0x0008c9b5
  Wake    : 0x5f1544ec 0x00073d51
  Calendar: 0x5f156549 0x000b818e
Panicked task 0xffffffe0004b6a00: 3413 pages, 220 threads: pid 0: kernel_task
Panicked thread: 0xffffffe0008c2a40, backtrace: 0xffffffe01095b5b0, tid: 276
		  lr: 0xfffffff01b4f4764  fp: 0xffffffe01095b5f0
		  lr: 0xfffffff01b4f45c0  fp: 0xffffffe01095b660
		  lr: 0xfffffff01b60f1e0  fp: 0xffffffe01095b710
		  lr: 0xfffffff01babd62c  fp: 0xffffffe01095b720
		  lr: 0xfffffff01b4f3f28  fp: 0xffffffe01095ba90
		  lr: 0xfffffff01b4f4280  fp: 0xffffffe01095bae0
		  lr: 0xfffffff01c32a8f8  fp: 0xffffffe01095bb00
		  lr: 0xfffffff01bc77b8c  fp: 0xffffffe01095bb30
		  lr: 0xfffffff01bc72af8  fp: 0xffffffe01095bbc0
		  lr: 0xfffffff01ba2c8a4  fp: 0xffffffe01095bc10
		  lr: 0xfffffff01ba2b5d8  fp: 0xffffffe01095bc50
		  lr: 0xfffffff01ba2ae5c  fp: 0xffffffe01095bc90
		  lr: 0xfffffff01bac8514  fp: 0x0000000000000000

Catalina 10.15.6

MacBook Pro (13-inch, 2019, Two Thunderbolt 3 ports)

1.4 GHz Quad-Core Intel Core i5

Been getting the "void AppleEmbeddedPCIeUpLinkMgmt" crash for the last 4 days. Happens randomly, I can't pinpoint anything.

Apple support and their troubleshooting tips have been unhelpful. This is seriously aggravating.

I would like to verify that I have also not had a kernel panic since upgrading to 10.15.6 . This kernel panic issue has finally gone away. Thank God. I can finally focus kn my work without worrying that my macbook pro could shut down any moment, now.

I wish, to be so lucky as you are. I am still experiencing the same issue, even if I have 10.15.6 mbp 15" mid 2019.

The symptoms are still the same. The CPU CATERR appears only if I leave the laptop doing nothing. The cooler fans are going quiet, CPU is not doing anything what needs any performance, and after some time the reboot happens. I have two 4K monitors at one Thunderbolt3 cable on the left and one 2,5K monitor on the right thunderbolt connector. The temperature monitoring app does not record any suspicious value on any system component, before crash. But I still suspect there must be some component which is going to overheat. Because if the CPU is working and going hot, the fans are going loud and whole laptop is getting cooled by fans, this problem never appears.

I just disabled the Automatic Graphic Switching in Energy Saver and ticked "Prevent computer from sleeping..." 3 days ago

So far, not a single restart! Not the best solution, but it works!

The same with Teams, or Gotomeeting and multiple monitors or bluetooth headset.

Did you find something in the log or just your consideration?

GOT IT BACK.. reseted bak to factory. and they replaced the Logic board and the Touch ID bord... 1 week so far and NO GLITCHES, no problems.....I guess Hardware issues....

GOOD LUCK...