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
Question marked as Top-ranking reply

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".

Similar questions

211 replies

May 12, 2020 1:17 PM in response to gac_nogales

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...


May 16, 2020 4:51 AM in response to BinnX1

I have similar issues and I can say, that it never appear when I am doing something. The hard shutdown and panic error only appear when I will leave my macbook pro 15" mid 2019 running, with no sleep settings. But when the CPU is computing something and the fans go loud, then everything is OK. When the CPU is not occupied and fans are quiet, then something goes overheat inside and the CPU get hard shutdown. It must be the T2 chip issue related. And it must be also somehow related that I am using 3 Thunderbolt monitors connected. The issue appears since the Catalina OS upgrade. Almost every day when I am going for lunch I came back and the laptop is shut down due the cpu panic.

Jun 24, 2020 9:48 AM in response to alikhanoom

I have also three external displays connected. From time to time the restart only happen when I am not working at all. And the cooling fans are at low rpm. When there is some CPU consuming process and the Cooling fans are loud, than the restart never occurs. I have a suspicion that it is related to the fact, there is some overheating happening and the fans are not going to spin faster to cool down the CPU. And somehow with the external displays it is connected also. And because of that the fans are controlled by the T2 chip, the issue must be in there.

I have the 15" 2019 mid MacbookPro.


Jul 7, 2020 8:35 AM in response to theo_alran

MacBook Pro 13 2019, 2.8 GHz Core i7. It started after I began using an external monitor so I originally blamed that but it once happened without it plugged in. I'm almost sure it was some hardware issue during high system use, which the external monitor almost surely exacerbates. The company is going to send it in for repair, I will report back if they hear about a what gets repaired.

Aug 26, 2020 9:48 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 and never closing the lid. So anytime I had to carry my MBP, I had to shut it down.

Unfortunately my maid closed the lid while cleaning my desk and this time when the Mac rebooted, it failed, saying I needed to perform a critical update to be able to use it. When it did, it was not capable of connecting to the Internet with my saved credentials and asked that I manually set them. Whenever doing it, it always failed, leaving me with 2 options, try again with always the same result or shut down. I was still able to restart in safe mode and when I did, it would automatically connect to the Internet.

But from safe mode, I couldn't use most of my softwares and couldn't access the App Store to perform the update.

I tried to reinstall from a TimeMachine backup, but it failed. Same thing happened when I erased my hard drive and made a clean install. Now my 3+ years old MBP is just unable to boot and Apple seems to be giving me a hard time to get it replaced as my Apple Care expired 2 months ago, while I had been reporting issues almost since day 1, had it repaired twice by Apple for all kind of issues and got most of the parts replaced but the motherboard which seems to be the issue.

All those times, I spent hundreds of hours in chat with tech support (and lost as much in work time because of the numerous issues (keyboard not working, restarts after not waking up from sleep mode, slow processing ...) while it was supposed to be the fastest Mac I ever had, custom made by Apple with all specs topped up) and asked for a replacement, which they never granted as it was not an off the shelf Mac but a custom. So that's my first lesson, I will never again buy a Custom Mac.

This being said, I have been constantly reporting issues and dysfunctions but I'm not an engineer, I relied on the Mac Genius and Tech to address the issue, but I now consider that they failed and that it shouldn't be me paying for this motherboard replacement as I had them fix my Mac twice in the last 18 months, in April 19 and December 19. And I firmly believe that the hardware failures I experienced and which led to the replacement of Keyboard, screen, battery, USB C ports for the most part originated from a defective motherboard. From my point of view, if pretty much all hardware parts have failed at some point, it's either that the Mac was all built from crappy parts (then I don't see why the motherboard would have been the only exception) or again that the defective motherboard caused them to fail.

What do you guys think? I would appreciate that some of you with a more tech profile share their thoughts about my analysis, as I have now to call them by phone as it seems like I've reached the limits of what the chat support can provide.


Thank you in advance.

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 31, 2020 12:33 AM in response to BinnX1

Same here!!


I took my 2018 13" MBP to w/ Touch Bar to Genius bar over a month ago for a 'Bad Magic' error and they couldn't figure it out.

Yesterday I updated to Catalina 10.15.4 from previous version and have had random errors 3 times now for 'Panic: watchdog detected', 'Bad Magic!' , and ' panic: CPU CATERR detected'.


This is really frustrating especially now with everything going on. Its my only way of working from home.

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

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