You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

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:


  1. "BAD MAGIC! (flag set in iBoot panic header)" (freezes, need to restart manually, 5-6 times a day)
  2. panic(cpu 1 caller 0xfffffff00df677b4): x86 CPU CATERR detected (automatic restart)
  3. 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

Reply

Similar questions

211 replies

Aug 26, 2020 11:09 PM in response to BinnX1

I have been experiencing those panics and restarts since 4 months and could deal with it by always keeping my MBP 15 connected to power supply and never closing the lid. So anytime I had to carry my Mac, I had to shut it down.

Unfortunately 2 weeks ago my maid close the lid while cleaning my desk and when the Mac book rebooted it failed.


From there it would ask to perform a critical update to be able to use it. It also couldn't no longer connect to the Internet with y saved credentials and asked that I manually set them. Whenever doing it, the process always failed leaving me with 2 options :

  • Try again (which failed every time)
  • Shut down (with same results when I restarted)


From there I was only able to reboot in safe mode and when I did, it would automatically connect to my Internet Network.

But from safe mode, I couldn't use most of my softwares and couldn't access the App Store to perform the required update. (app not launching)


I tried to reinstall from a Time Machine backup, but again it failed and I ended up in the same situation.

Same thing happened when I erased my hard drive and made a clean install following a senior adviser advice who promised Apple won't let e down this time.


Now my 3 years+ MBP is just unable to boot but in safe mode and Apple seems to be giving me a hard time to get it fixed as my Apple Care expired 2 months ago, while I had been reporting issues with this Mac almost since day 1, had it repaired twice by Apple for all kind of issues and got most of the parts replaced but the mother board which seems to be the issue.


During 3 years, I spent hundreds of hours trying to fix my Mac and dealing with ac support teams, explaining up to 4 times the same issues to different people as they seem to not read thoroughly the previous chats or notes, and also wasted hundred of hours trying to work with a defective computer which was slow (while it was a 4000€ custom MBP 15 with all specs topped up by Apple which should have been my best and fastest Mac ever) and was deprived from my work tool for 1 month in April 19 and 2 weeks in December 19 while it was fixed by Apple.


From this experience I learnt I will never ever buy another custom Mac but off the shelf ones only as from gurus' feedbacks, it makes it much harder to get it replaced when there is a problem as it's not standard and hence not stocked in stores.


As I explained it, I have been constantly reporting issues and dysfunctions but I'm not an engineer and I relied on the Mac genius and techs to identify the underlying problem and address it. I now consider they failed making the appropriate diagnosis and that the problem identified today should have been looked after by them and that I should not have to fix this motherboard issue at my own expense. My Mac was supposedly fix by Apple twice in the last 18 months and they have replaced most hardware components but the motherboard and I firmly believe that all those hardware failures originated from the defective motherboard.


From my point of view and as most hardware parts have failed at some points, there are 2 ways to analyze it :

1º This Mac was built only with crappy parts and if it's the case, there is no reason why the motherboard would be the only exception

2º The defective motherboard has caused if not all but most of those parts to fail


In both scenarios, the motherboard should have been incriminated.


What do you guys think?

I would really appreciate that some of you with a more tech profile than mine share their thoughts about my analysis.


Thank you in advance

Aug 26, 2020 11:56 PM in response to cobaye-conso

unfortunately, I can’t say much on your issue, since I just got a mac a few months ago and haven’t encountered such a weird issue. *knock twice on wood* What I can say though, is:

  1. that I have not experienced the panic restart since upadting to the latest Mac OS.
  2. I know that chat support is pretty limited and every one of my calls has ended with some solution. That should work out really well for you.
  3. Like I said, I’m new to macs and can’t really recommend many solutions.

Good luck!

Sep 15, 2020 5:37 AM in response to BinnX1

Same story here MB PRO 16 32gb I9 2.4ghz Radeon Pro 5500M 4GB

but:

  • computer was 4 months old when the first one occurred and it was fatal - fans went high speed and the computer was bricked.

Sent to apple - motherboard replaced.

Got the computer back for maybe 4 days - same thing occurred but this time it recovered.

All happened when I had an external drive and a 2nd monitor attached.


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

I have same issue on 2018 macbook pro.

I was running Creative Cloud (Adobe apps), editing video at Premiere Pro. When it freezes, i realize the CPUs temperature is too high.

In the last week, it occoured several times. Im so frustaded. Help us Apple :(


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

Debugger message: panic

Memory ID: 0x6

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

x86 Previous Power Transitions: 0x50604000200

PCIeUp link state: 0x94721614

Paniclog version: 13

Kernel slide: 0x000000000615c000

Kernel text base: 0xfffffff00d160000

mach_absolute_time: 0x1c7f4950b69

Epoch Time: sec usec

Boot : 0x5e849f50 0x000712eb

Sleep : 0x5e87486d 0x000f3773

Wake : 0x5e87487e 0x000aaa30

Calendar: 0x5e875259 0x00044d5b


Panicked task 0xffffffe00060f600: 3399 pages, 216 threads: pid 0: kernel_task

Panicked thread: 0xffffffe0009e1fb0, backtrace: 0xffffffe0172f34b0, tid: 334

lr: 0xfffffff00da24764 fp: 0xffffffe0172f34f0

lr: 0xfffffff00da245c0 fp: 0xffffffe0172f3560

lr: 0xfffffff00db3ee7c fp: 0xffffffe0172f3610

lr: 0xfffffff00dfed62c fp: 0xffffffe0172f3620

lr: 0xfffffff00da23f28 fp: 0xffffffe0172f3990

lr: 0xfffffff00da24280 fp: 0xffffffe0172f39e0

lr: 0xfffffff00e85a934 fp: 0xffffffe0172f3a00

lr: 0xfffffff00e1937b4 fp: 0xffffffe0172f3a30

lr: 0xfffffff00e184be4 fp: 0xffffffe0172f3aa0

lr: 0xfffffff00e186b0c fp: 0xffffffe0172f3b50

lr: 0xfffffff00e18431c fp: 0xffffffe0172f3be0

lr: 0xfffffff00e14b780 fp: 0xffffffe0172f3c10

lr: 0xfffffff00df5aabc fp: 0xffffffe0172f3c50

lr: 0xfffffff00df5a340 fp: 0xffffffe0172f3c90

lr: 0xfffffff00dff8514 fp: 0x0000000000000000





[Image Edited by Moderator to Remove Personal Information]

May 14, 2020 6:55 AM in response to cobaye-conso

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.


Mar 26, 2020 6:00 AM in response to Barney-15E

I have the same issue.

There is a full log below:


panic(cpu 1 caller 0xfffffff014d277b4): 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: 0x70707060400

PCIeUp link state: 0x1614

Paniclog version: 13

Kernel slide: 0x000000000ccf0000

Kernel text base: 0xfffffff013cf4000

mach_absolute_time: 0x2e6d98a0c3

Epoch Time: sec usec

Boot : 0x5e7c836b 0x00050d7d

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x5e7ca3db 0x000e888f


Panicked task 0xffffffe000407600: 3338 pages, 216 threads: pid 0: kernel_task

Panicked thread: 0xffffffe0007f6a40, backtrace: 0xffffffe015e034b0, tid: 318

lr: 0xfffffff0145b8764 fp: 0xffffffe015e034f0

lr: 0xfffffff0145b85c0 fp: 0xffffffe015e03560

lr: 0xfffffff0146d2e7c fp: 0xffffffe015e03610

lr: 0xfffffff014b8162c fp: 0xffffffe015e03620

lr: 0xfffffff0145b7f28 fp: 0xffffffe015e03990

lr: 0xfffffff0145b8280 fp: 0xffffffe015e039e0

lr: 0xfffffff0153ee934 fp: 0xffffffe015e03a00

lr: 0xfffffff014d277b4 fp: 0xffffffe015e03a30

lr: 0xfffffff014d18be4 fp: 0xffffffe015e03aa0

lr: 0xfffffff014d1ab0c fp: 0xffffffe015e03b50

lr: 0xfffffff014d1831c fp: 0xffffffe015e03be0

lr: 0xfffffff014cdf780 fp: 0xffffffe015e03c10

lr: 0xfffffff014aeeabc fp: 0xffffffe015e03c50

lr: 0xfffffff014aee340 fp: 0xffffffe015e03c90

lr: 0xfffffff014b8c514 fp: 0x0000000000000000


Mar 26, 2020 7:39 AM in response to NidelKO

That's not the whole panic log. Open the file, copy the text, and paste it into the Additional Text area (document icon).

You should be able to find the panic logs in /Library/Logs/DiagnosticReports/

The name will start with Kernel.

There should be a section titled "loaded kexts"

If there isn't a section like that, then no point in posting the log.


Mar 30, 2020 3:33 PM in response to Ochuko

Not at all. Apple suggested reinstalling the macOS from scratch.


Anyways, just to update you guys, I remember that I installed Skype for Business along with regular Skype few days back. I thought why not remove both and see if these two applications are the culprit, and voila! So far no random restarts. I’ll check for next few days and if I won’t get any more random shutdowns that would be great.


However, my wife has the exact same MacBook that I have and I checked her recent logs, no random restarts or shutdowns despite of having both Skype versions installed.

Mar 30, 2020 3:40 PM in response to BinnX1

Thanks BinnX1. Apple's suggestion is very far from being helpful in my circumstance. Since I got this MacBook in December 2019, I have had issues with it doing this panic thing. Took it in January and dude said I had Mcafee installed and might be causing the issue and that there were some other stuff going on due to backup reinstall from an older machine that didn't quite happen smoothly. Long story we did a factory reset in store, and no the problem hasn't gone. Very annoyed to say the least.

Mar 30, 2020 4:24 PM in response to BinnX1

So called Apple geniuses can only reinstall macOS and give some lame information. I think if someone can reinstall the OS and see for few days if this problem reoccur at least one thing can be ruled out that it is not a hardware problem and is caused by some third party App (for sure not everyone has time to do this).


I have also searched on some threads, people say that this new macOS Mojave and Catalina conflicts with third party code thus throwing kernel panics.


If the problem won’t fix after OS reinstall logic board needs replacement.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.