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

Last night.. just running a spreadsheet and safari.. got the same error 8 times in 2 hours.. FRUSTRATING!! can't get any work done.

Apple can NOT duplicate the error so they are NOT willing to help and/or to exchange ANYTHING on the Mac Pro because according to them there s NOTHING wrong with the Pro.. I have documented the faults for the last 6 months.... have screen shots with the "Computer restarted because fo a problem" ...panic... and still!!!

after 30 min o a frustrating call with service were they go through the same 10 items on the "to do list" finally got a supervisor on the line.. but same thing.. if they can't duplicate the error when they connect or look at the laptop, then it's a no problem.. even with 60 documented time sin 6 months.. The best they can do is have me send it to them so that THEY can reinitialize it and test it... if they see any little ding or scratch they will blame it on me dropping it (it's on a protective case) and bill me their time... With all it's flat in Windows... at least Dell service was more cooperative and took the user's side not the company's side...

I'll keep you guys posted...

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?

Sorry but what do you mean by SIP? I will uninstall WD software. I installed because I can't mount my WD Passport External Drive. Apparently there is a bug Catalina can't mount them.... *rolling eyes*.

The drive it's not defective. I can still use it perfectly on other computers. There are thousands of threads on the internet and this forum about that topic. Tried with two different drives from WD on TWO different Macbooks with Catalina. Cheers

marcgarrow wrote:

The drive it's not defective. I can still use it perfectly on other computers. There are thousands of threads on the internet and this forum about that topic. Tried with two different drives from WD on TWO different Macbooks with Catalina. Cheers

I have drives from several different manufacturers (none of them WD, because they make crap). Not a single one has a problem with Catalina.

Cheers

Congratulations to you! I was talking about WD drives which you don't have so why affirm something you don't know?

"No, there isn't. If the drive needs some software to mount, it is defective." by Barney

Cheers. Stay humble.

tried it.. did NOT WORK.. gut good luck.. this is so random that different things work for different people.. sometime I've seen a fix work for 1 week.. then out of the blue it happens.. first sparsely then more often.. then ALL DAY LONG

Same thing has happened to me. 16" 2019 MBP 32GB, 1TB. Apple Support has suggested reinstalling Mac OS, booting in Safe Mode, and the typical nvram and smc reset or whatever its called. Still doing the issue. I really hope this gets fixed because I run my business with their products and I'm losing a lot of faith with their support. Took 10 months for them to fix my Home Kit issue. Its crazy.

No it doesn't fix this for me at least. I think the connection of a NAS, which for some reason has trouble being ejected at shutdown is the culpret for me, which has persisted through two different imacs and from Mojave to catalina, and for two different Synology NAS units. Something in the way Apple handles the remote storage . . Anyway a hang in Mojave has turneded in to an error reprot after reboot or startup on catalina. harmless, but very annoying...

Upgraded to macOS 10.15.5 yesterday, hoped it was going to fix my CPU panic issues on PowerState (sleep), BUT IT DID NOT. SAME CPU PANIC. Again, I have a Lacie 2Big Dock 8TB drive which I use for docking and storage, bought from Apple store - ideally this is not the issue, but if it is, it's sold on Apple's website so FIX YOUR SH*T APPLE!!!!!!!!!!!!!!!!!!!!!

panic(cpu 0 caller 0xffffff8004815f47): "PRT4::setPowerState(0xffffff8035318800 : 0xffffff7f86a1763a, 0 -> 2) timed out after 30406 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.121.1/iokit/Kernel/IOServicePM.cpp:5296

Backtrace (CPU 0), Frame : Return Address

0xffffff9222b73b40 : 0xffffff800411f5cd

0xffffff9222b73b90 : 0xffffff8004258b05

0xffffff9222b73bd0 : 0xffffff800424a68e

0xffffff9222b73c20 : 0xffffff80040c5a40

0xffffff9222b73c40 : 0xffffff800411ec97

0xffffff9222b73d40 : 0xffffff800411f087

0xffffff9222b73d90 : 0xffffff80048c27ec

0xffffff9222b73e00 : 0xffffff8004815f47

0xffffff9222b73e50 : 0xffffff8004815829

0xffffff9222b73e60 : 0xffffff800482cdbe

0xffffff9222b73ea0 : 0xffffff80048145d8

0xffffff9222b73ec0 : 0xffffff8004161565

0xffffff9222b73f40 : 0xffffff8004161091

0xffffff9222b73fa0 : 0xffffff80040c513e

BSD process name corresponding to current thread: kernel_task

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:

19F96

4 times in the last 48hrs!!!

I have the same problem. I am so mad that I can't find a fix anywhere.

I get this message:

panic(cpu 1 caller 0xfffffff01779d3dc): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0x6

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: 0x405060400

PCIeUp link state: 0x8927160d

Paniclog version: 13

Kernel slide: 0x000000000f764000

Kernel text base: 0xfffffff016768000

mach_absolute_time: 0xfe9560f8fe

Epoch Time: sec usec

Boot : 0x5ed5956d 0x000e4ce4

Sleep : 0x5ed7524d 0x0005bf2d

Wake : 0x5ed7f4f5 0x000c7d89

Calendar: 0x5ed8000e 0x0007a4af

Panicked task 0xffffffe0003b3000: 3551 pages, 222 threads: pid 0: kernel_task

Panicked thread: 0xffffffe0007aef88, backtrace: 0xffffffe0157a34b0, tid: 342

lr: 0xfffffff01702c764 fp: 0xffffffe0157a34f0

lr: 0xfffffff01702c5c0 fp: 0xffffffe0157a3560

lr: 0xfffffff0171471e0 fp: 0xffffffe0157a3610

lr: 0xfffffff0175f562c fp: 0xffffffe0157a3620

lr: 0xfffffff01702bf28 fp: 0xffffffe0157a3990

lr: 0xfffffff01702c280 fp: 0xffffffe0157a39e0

lr: 0xfffffff017e62934 fp: 0xffffffe0157a3a00

lr: 0xfffffff01779d3dc fp: 0xffffffe0157a3a30

lr: 0xfffffff01778e80c fp: 0xffffffe0157a3aa0

lr: 0xfffffff017790734 fp: 0xffffffe0157a3b50

lr: 0xfffffff01778df44 fp: 0xffffffe0157a3be0

lr: 0xfffffff0177553a8 fp: 0xffffffe0157a3c10

lr: 0xfffffff0175635d8 fp: 0xffffffe0157a3c50

lr: 0xfffffff017562e5c fp: 0xffffffe0157a3c90

lr: 0xfffffff017600514 fp: 0x0000000000000000

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.

I upgraded to 10.15.5 a week ago, but the same panic happened again today. My MBP is a 2019 16", 6-core i7.

I was editing a source file. Apparently that sort of thing isn't supported by macOS anymore :-/

Seriously, Catalina is such a piece of s***. My non-work Macs will be staying on Mojave for the foreseeable future.

Regards,

John