Level 1

49 points

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

My MacBook is restarting randomly from last few days with following error messages:

"BAD MAGIC! (flag set in iBoot panic header)" (freezes, need to restart manually, 5-6 times a day)
panic(cpu 1 caller 0xfffffff00df677b4): x86 CPU CATERR detected (automatic restart)
panic(cpu 0 caller 0xfffffff025f05f64): "void AppleEmbeddedPCIeUpLinkMgmt: (automatic restart)

In all three cases, only safari was open with background services (Creative Cloud and OneDrive only). Nothing installed recently.

Can someone please explain the reason for these panics, logs are as follows:

Case 2:

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

Debugger message: panic

Memory ID: 0xff

OS version: 17P4263

macOS version: 19E266

Kernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010

Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7

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

x86 Previous Power Transitions: 0x10001000100

PCIeUp link state: 0x89473614

Paniclog version: 13

Kernel slide: 0x0000000005f30000

Kernel text base: 0xfffffff00cf34000

mach_absolute_time: 0x63d86ef5e6

Epoch Time: sec usec

Boot : 0x5e7aa096 0x000606d7

Sleep : 0x5e7ab184 0x000525ba

Wake : 0x5e7ab672 0x000d3056

Calendar: 0x5e7af45a 0x000baf4f

Panicked task 0xffffffe0000c8200: 3144 pages, 214 threads: pid 0: kernel_task

Panicked thread: 0xffffffe000380fd8, backtrace: 0xffffffe0154e34b0, tid: 323

lr: 0xfffffff00d7f8764 fp: 0xffffffe0154e34f0

lr: 0xfffffff00d7f85c0 fp: 0xffffffe0154e3560

lr: 0xfffffff00d912e7c fp: 0xffffffe0154e3610

lr: 0xfffffff00ddc162c fp: 0xffffffe0154e3620

lr: 0xfffffff00d7f7f28 fp: 0xffffffe0154e3990

lr: 0xfffffff00d7f8280 fp: 0xffffffe0154e39e0

lr: 0xfffffff00e62e934 fp: 0xffffffe0154e3a00

lr: 0xfffffff00df677b4 fp: 0xffffffe0154e3a30

lr: 0xfffffff00df58be4 fp: 0xffffffe0154e3aa0

lr: 0xfffffff00df5ab0c fp: 0xffffffe0154e3b50

lr: 0xfffffff00df5831c fp: 0xffffffe0154e3be0

lr: 0xfffffff00df1f780 fp: 0xffffffe0154e3c10

lr: 0xfffffff00dd2eabc fp: 0xffffffe0154e3c50

lr: 0xfffffff00dd2e340 fp: 0xffffffe0154e3c90

lr: 0xfffffff00ddcc514 fp: 0x0000000000000000

Case 3:

panic(cpu 0 caller 0xfffffff025f05f64): "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.100.1/AppleEmbeddedPCIeUpLinkMgmt.cpp:3986

Debugger message: panic

Memory ID: 0xff

OS version: 17P4263

macOS version: 19E266

Kernel version: Darwin Kernel Version 19.4.0: Mon Mar 2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010

Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7

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

x86 Previous Power Transitions: 0x10001000100

PCIeUp link state: 0x89473611

Paniclog version: 13

Kernel slide: 0x000000001debc000

Kernel text base: 0xfffffff024ec0000

mach_absolute_time: 0x935988e94

Epoch Time: sec usec

Boot : 0x5e7af472 0x000636b9

Sleep : 0x5e7ba195 0x000e2a08

Wake : 0x5e7bbb14 0x0005f8d1

Calendar: 0x5e7bbc86 0x000ab712

Panicked task 0xffffffe00053fc00: 3131 pages, 214 threads: pid 0: kernel_task

Panicked thread: 0xffffffe00093d520, backtrace: 0xffffffe0157335b0, tid: 275

lr: 0xfffffff025784764 fp: 0xffffffe0157335f0

lr: 0xfffffff0257845c0 fp: 0xffffffe015733660

lr: 0xfffffff02589ee7c fp: 0xffffffe015733710

lr: 0xfffffff025d4d62c fp: 0xffffffe015733720

lr: 0xfffffff025783f28 fp: 0xffffffe015733a90

lr: 0xfffffff025784280 fp: 0xffffffe015733ae0

lr: 0xfffffff0265ba8f8 fp: 0xffffffe015733b00

lr: 0xfffffff025f05f64 fp: 0xffffffe015733b30

lr: 0xfffffff025f00ed0 fp: 0xffffffe015733bc0

lr: 0xfffffff025cbbd88 fp: 0xffffffe015733c10

lr: 0xfffffff025cbaabc fp: 0xffffffe015733c50

lr: 0xfffffff025cba340 fp: 0xffffffe015733c90

lr: 0xfffffff025d58514 fp: 0x0000000000000000

MacBook Pro 13”, macOS 10.15

Posted on Mar 25, 2020 1:34 PM

Top-ranking reply

forgetfulfrank

Level 1

4 points

Posted on Sep 14, 2020 5:14 AM

I want to confirm that after the upgrade to 10.15.6 i haven't had a single kernel panic, it has been a month an a half crash free, so i believe it got solved, even if nothing hints at the possibility in the Release Notes of 10.15.6.

My crashes were "void AppleEmbeddedPCIeUpLinkMgmt" and "x86 CPU CATERR detected".

View in context

Similar questions

211 replies

Driekant

Level 1

4 points

Apr 22, 2020 10:42 AM in response to BinnX1

I have the same issues as well on my macbook pro 13" 2019 (with touch bar).

All 3 error messages. Where I got the cpu 1 caller after I updated to 10.15.4.

Did it help for any of you guys to reinstall macOS as earlier suggested by Apple??

Apr 22, 2020 5:40 PM in response to BinnX1

Having the same issue on and of with my MacBook Pro (15-inch,2018) macOS Catalina Ver 10.15.4 since Summer 2019. On the phone with Apple Tech for hrs, never got it solved, they tried everything. Took it in to Apple store for tech support for 3 days in a row, spent about 12 hrs, reinstalled, tried everything never found anything and it kept on happening. They asked me to create another user and dump the old one... I did.. 3 times.. nothing.. I have a log of all the times I freeze and copies of the print screen from Neve to date.. still no answer and apple has no idea what it is...

This is my first Mac . I switched over from Windows because I got tired of windows coming or updating every day, and the blue screen ...at least I knew what it was with them, and that I would loose 20-30 min.. but with apple I thought it be different...

BinnX1 Author

Level 1

49 points

Apr 22, 2020 7:02 PM in response to gac_nogales

I’m a Mac and Windows user from the past 14 years and believe me it is better than Windows. I still need to use Windows for some engineering tools.

Anyways, I understand how frustrating it is to have first Mac and these problems. I have spend hours with Apple support and no luck till date.

I hope this would come out as a software bug that they’ll take care in next update.

BinnX1 Author

Level 1

49 points

Apr 22, 2020 7:07 PM in response to dimas-adhyaksa

These general steps are great starting point For troubleshooting. This CPU 1 CATERR issue is intermittent. I sometimes do not get this issue when working on Mac whole day, but some times it is 3-4 times a day.

No solution till date.

Apr 23, 2020 9:12 AM in response to BinnX1

I have the same situation since being upgraded to 10.15.4. Seem that the issue is still not fixed with the Beta 1 (even the kernel panic they talk about here is about after waking from sleep): https://mrmacintosh.com/category/10-15-catalina-beta/

It sometimes happens 2 times a day, sometimes only once every 5-7 days. It is driving me crazy and thanks Apple for deploying crappy software!

StooksG

Level 1

8 points

Apr 28, 2020 8:04 AM in response to BinnX1

Similar issue as stated with the "panic(cpu 1 caller 0xfffffff01c4577b4): x86 CPU CATERR detected" error.

Brand new MacBook Pro 16" with 16 gigs of memory, just pulled it out of the box a week ago. The first day I had it reboot 4 times or so. 2 times during a zoom call with family. All went well for a last 5 days or so then it appears to have rebooted last night when inactive, same error.

Really hoping it is a software issue that can be corrected with an update.

Apr 28, 2020 9:03 AM in response to Gabbor

Good LUCK!! Tried it before and it will clear it for a couple of days then it comes back.. lost stretch was for 3 weeks in March 2020.

I just read an article that it could be the power saving part of it.. I'll play with it

Apr 30, 2020 10:45 AM in response to BinnX1

Got hit by case 2 today. Brought my MBP 2019 out of sleep attached a USB C drive to run a weekly time machine backup.

Hardcore crash.

panic(cpu 1 caller 0xfffffff00df677b4): x86 CPU CATERR detected (automatic restart)

rpeegee

Level 1

16 points

May 1, 2020 7:39 AM in response to BinnX1

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

MacOS Problem Report

May 9, 2020 1:51 AM in response to Paveway

Lucky you! I can no longer send reports, it freezes!

For me it all started after I upgraded to 10.15.4 and when I ran out of battery while working on Photoshop (unplugged)

I realised I had 1% left of battery only and ran to get my charger and to plug my mac, which took a bit of time.

I was happily surprised as it didn't shut down (while Photoshop usually drains the battery so fast).

The charging icon showed up and I resumed working thinking everything was ok.

30 seconds later, the mac turned off (while it was charging or supposed to).

It woke up to say it didn't shut down properly and would send a report.

Since that episode, my MBP 15 2017 keeps on restarting whenever it's in sleep mode.

The worst being that it even reboot when the screen is closed which cause an additional overheating.

Guys, It's time to publish an update with a fix!

As it was said earlier we don't buy 3-4K computer to play videogames but to work.

And each time our computer restarts, it a total waste of our time in a period where we need everything but this.

Where is the support?

May 11, 2020 6:45 AM in response to BinnX1

Same issue after plugging in a USB cable into my Hyperdrive dongle... there wasn't even anything plugged in at the other end... just instant crash.

What I have noticed in the logs posted is that they seem all to have the Darwin Kernel Version 19.4.0... my 16" MBP as well... so I wonder if that is the issue...

MJNPsych

Level 1

4 points

May 11, 2020 7:41 AM in response to rpeegee

It is RANDOM! It has NOTHING to do with your Lacie drive. The 16"mbp can be fine for days or crash every hour. People blame what they were doing when it happens, but if you read enough of the posts you will see it is RANDOM!

May 11, 2020 9:01 AM in response to cobaye-conso

And it tends to happen when you are working in smelting that you have NOT yet saved or updated... freezes, reboots and you lost not only your work, but your train of thought just went out the window.... Frustrating as heck

Hands0me

Level 1

4 points

May 12, 2020 5:35 AM in response to XSirio

The sound relation might be possible, I experienced this also today, while join conference via Microsoft Teams twice, although yesterday I had this issue also with Google Chrome with 10+ tabs with video opened. And also as mentioned before with Node servers.

XSirio

Level 1

4 points

May 12, 2020 6:16 AM in response to Hands0me

I've found just that sometime the audio of LG Ultrafine 5K monitor or the camera sometime is not present when I attach it to the mac.

And more I see that LG Ultrafine is shown as USB and not Thunderbolt, or DisplayPort...

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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