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

Hello VDawg2018,

a couple of questions:

• how many days have you been without a kernel panic?
• how did you stress test your mac?

For the reinstall i believe you followed hhttps://support.apple.com/en-us/HT204904

Thanks

I have similar issue with my MacBook. My main guess is that it becomes hot and restarts. Specially when I connect it to two monitors at home it happens more. Here is my MacBook specs:

macOS Catalina. version 10.15.4

MacBook Pro (15-inch, 2018)

Processor: 2.9 GHz 6-Core Intel Core i9

Memory: 32 GB 2400 MHz DDR4

Graphics: Radeon Pro 560X 4 GB

Intel UHD Graphics 630 1536 MB

Here is the log:

panic(cpu 0 caller 0xfffffff02400b7b4): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0xff

OS version: 17P4263

macOS version: 19E266

Kernel version: Darwin Kernel Version 19.4.0: root:xnu-6153.101.6~2/RELEASE_ARM64_T8010

Kernel UUID:

iBoot version: iBoot-5540.105.2

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x3

x86 Previous Power Transitions: 0x70707060400

PCIeUp link state: 0x1614

Paniclog version: 13

Kernel slide: 0x000000001bfd4000

Kernel text base: 0xfffffff022fd8000

mach_absolute_time: 0x6f9ee297b

Epoch Time: sec usec

Boot : 0x5e824c5e 0x000949c8

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x5e82513b 0x00003673

Panicked task 0xffffffe000564800: 3119 pages, 215 threads: pid 0: kernel_task

Panicked thread: 0xffffffe000955fb0, backtrace: 0xffffffe0156534b0, tid: 335

lr: 0xfffffff02389c764 fp: 0xffffffe0156534f0

lr: 0xfffffff02389c5c0 fp: 0xffffffe015653560

lr: 0xfffffff0239b6e7c fp: 0xffffffe015653610

lr: 0xfffffff023e6562c fp: 0xffffffe015653620

lr: 0xfffffff02389bf28 fp: 0xffffffe015653990

lr: 0xfffffff02389c280 fp: 0xffffffe0156539e0

lr: 0xfffffff0246d2934 fp: 0xffffffe015653a00

lr: 0xfffffff02400b7b4 fp: 0xffffffe015653a30

lr: 0xfffffff023ffcbe4 fp: 0xffffffe015653aa0

lr: 0xfffffff023ffeb0c fp: 0xffffffe015653b50

lr: 0xfffffff023ffc31c fp: 0xffffffe015653be0

lr: 0xfffffff023fc3780 fp: 0xffffffe015653c10

lr: 0xfffffff023dd2abc fp: 0xffffffe015653c50

lr: 0xfffffff023dd2340 fp: 0xffffffe015653c90

lr: 0xfffffff023e70514 fp: 0x0000000000000000

It is a new MacBook and I am going to use the warranty if it continues like this.

Do what louis suggested: download and run Etrecheck. Etrecheck is a diagnostic tool that was developed by one of the most respected users here in the ASC and recommended by Apple Support  to provide a snapshot of the system and help identify the more obvious culprits that can adversely affect a Mac's performance.

Copy the report

and use the Add Text button to include the report in your reply. How to use the Add Text Feature When Posting Large Amounts of Text, i.e. an Etrecheck Report

IMPORTANT:

Before running Etrecheck assign Full Disk Access to Etrecheck in the app's Privacy preference pane so that it can get additional information from the Console and log files for the report:

ALSO IMPORTANT:

Then we can examine the report and see if we can determine the root of the problem.

I have all "Energy Saver" settings disabled except for the first one, which is enabled ("Prevent computer from sleeping automatically..." is checked). In my case, I'm on a Mac Mini so I always have a display attached and I'm actually using an eGPU via one of Apple's recommended configurations. Note also that the kernel panic always occurs during active usage of the machine.

Specs as follows:

eGPU Setup Info -- I'm using the recommended setup per: https://support.apple.com/en-us/HT208544

Enclosure: 'Razer Core X'

GPU: 'AMD Radeon RX 5700 XT' (MSI brand 'RADEON RX 5700 XT MECH OC BV' from Best Buy)

Display: Single Display (LG 27UD58-B 27-Inch 4K UHD IPS Monitor w/ FreeSync)

Display Resolution: Running at native 3840 x 2160

Display Information from System Information App

Update from post below - this workaround is still successful for me - I have not powered off for 2 days, and changing power saver settings to not allow sleep mode has prevented spontaneous re-starts (indicating the problem seems to be related to sleep mode). 99% of the time my MacBook Pro 16-inch purchased Mar 2020 is connected to power supply, so I don't have to worry about the extra drain on battery power when disabling sleep mode.  

Apr 16, 2020 7:28 AM in response to Gabbor (by RetEngr670)

I’ve had this problem since upgrading to 10.15.4, no solution yet from Apple engineers working my case number.  Since my panic always occurs while sleeping, I have changed power saver and screen saver to never allow sleep mode, and to power off whenever away from MacBook for extended period. 

Here's mine:

panic(cpu 0 caller 0xffffff801de16487): "PRT0::setPowerState(0xffffff804e732400 : 0xffffff7fa001663a, 0 -> 2) timed out after 30420 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296

Backtrace (CPU 0), Frame : Return Address

0xffffff923c60bb40 : 0xffffff801d7215cd

0xffffff923c60bb90 : 0xffffff801d85a3c5

0xffffff923c60bbd0 : 0xffffff801d84bf7e

A crash every day... please do something fast.

Did you notice if is something related to sound device? I've seen there was trouble looking to the sound devices on multiple Video, when I start a conference start the audio and then panic:

panic(cpu 1 caller 0xfffffff01ad677b4): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID:

Have the same problem! I bought a new MBP 16" 16GB RAM i7 2.6 ghz 6-core one week ago.

Every night I put my Mac to sleep while being plugged. In the morning after log in I see a "Your computer was restarted because of a problem..." :

panic(cpu 2 caller 0xf..........): "AppleIntelFramebuffer::setPowerState(0xf............) timed out after 45986 ms"

I will try suggested workarounds but it's clearly an OS problem.

I ran EtreCheck here is my report - does anyone see something here?

Same here. Although I had issues when updating from the beta macOS Big Sur to the official Big Sur, the kernel panics issue is long gone. It looks like some sort of update that came out recently must have fixed the issue, quietly. I will definitely hop back into this thread in case the kernel panics return, but for now we should be good.

Issue = solved?

Solution = Update to macOS Big Sur

Here's a link with more info on macOS Big Sur.

How to upgrade to macOS Big Sur - Apple Support

You could try some of these things. Since I did these, no more restarts:

• Disk utility: First aid on all disks.
• Restart in safe mode (hold shift key while booting up)
• Diagnostics: hold D key while booting.

Another suspected culprit might be external displays. Try using you notebook without them.

I turned off Auto adjust brightness on both external and internal displays.

Actually I've done that after contacting support...

... and I still have the bug.

I agree with some of you saying it's random although there's some kind of pattern somehow because it has to do with the T2.

• I was using an external drive -> now disconnected
• I was playing music while working -> not any more
• I had little snitch (installing a kext) -> not reinstalled
• I had some other software using FUSE (another kext) -> not reinstalled.

It seems to be a bit more stable this way.

But no, reinstalling from scratch didn't fix it!

I mean if I have to restrain myself using the Mac it's not going to stay here for very long. For anything important I'm still using my old 2009 iMac which has never ever crashed in the last 10 years of heavy use. Those were the days...

I'm telling you, they're going to lose loyal customers...

I'm also experiencing the issue on a 16 mbp 2019, 2,6 GHz 6-Core Intel Core i7, AMD Radeon Pro 5300M 4 GB.

• My crash dumps are always either:

• • panic(cpu 0 caller 0xfffffff00c237b8c): "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

or

• • panic(cpu 1 caller 0xfffffff00eb353dc): x86 CPU CATERR detected
• the ratios between the 2 crash messages is ~50%, only once i did have a crash with different message (about "mp_cpus_call_wait() timeout")
• the frequency varies a lot, it could be as low as twice a week or as high as 5 times in a day. I don't have a way to predict the frequency, i'm always using the mac with the same sets of applications. I wonder if environmental temperature played a role (hotter days?)
• it seems to happen slightly more frequently when audio/video applications are executing, like when on a audio/video call (Webex or Zoom or Bluejean) or when watching a youtube video. It's not a necessary condition, several times it crashed while simply browsing or even when i was not using it at all.
• it seemed like disabling GPU switching may have reduced the frequency, however it's likely to be just coincidence, yesterday i did have 5 crashes despite it.
• it's not related to which devices are plugged in, it happened also while no device was plugged in.
• it happened with all versions of MacOS that i had on this machine, namely 10.15.4, 10.15.5, 10.15.5 with security update (19F101)
• Applications I'm frequently using:
  • Firefox
  • FUSE for OSX (to mount sshfs)
  • iterm2
  • Thunderbird
  • Davmail
  • Atom (editor)
  • Apple Calendar
  • MySQLWorkbench
  • Microsoft Excel
  • Microsoft Word
  • Cisco Anyconnect
  • Webex
  • Webex Teams
  • Cisco Jabber
  • Crashplan (never active, not configured)
  • Cisco AMP
• I was using the very same set of applications on my previous mbp (not running Catalina) and I never experienced the issue there.

Also: I tried to trigger the crashes myself via stress testing by running at the same time:

• cinebench (for CPU)
• https://web.basemark.com/ (for GPU, the webgl tests)

no luck in triggering the crashes even if i had all cores maxed out and decent gpu utilization peaks (while running the webgl tests) and consequently fans spinning high.

Yes, that is the website that the Apple advisor must have used to assist me with my reinstallation of MacOs.

as far as your questions....

1. I have been almost a whole week without a kernel panic.
2. I repeated the steps that got me into the panic into the forst place. I opened Netflix and had mutliple other applications running. I even had Netflix and this graphics intensive video game open. The game is called World of Tanks Blitz if you need that info. It used to throttle my windows laptop and make it freak out, but this MacBook Pro 16” does not present issues with the same game. I never hear the fans blasting because they are quite and I don’t feel the keyboard getting hotter either (since the battery is close to the keyboard because of the slim design).

My conclusion is that reinstalling MacOs did fix the issue for me.

I want to cautiously note that since the upgrade to 10.15.6 i no longer have any of the crashes:

• panic(cpu 0 caller 0xfffffff00c237b8c): "void AppleEmbeddedPCIeUpLinkMgmt::_linkInterruptAction(IOInterruptEventSource *, int): " "A link timeout has been seen after 650000 microseconds and 49999 iterations."
• panic(cpu 1 caller 0xfffffff00eb353dc): x86 CPU CATERR detected

I've upgraded ~10 days ago, but last week i used the macbook lightly as i was on vacation so i will definitely monitor it more, let's see.