How to Read Kernel Panic Log

Question

Level 1

4 points

How to Read Kernel Panic Log

My 2019 13'' Macbook Pro crashes while it sleeps or sometimes when it is shut down. It is also hard to boot. It has a black screen but the trackpad is working. It also sometimes heats up while it is asleep. I get this panic log. Can somebody help on how to read a panic log?

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

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 21P5077

macOS version: Not set

Kernel version: Darwin Kernel Version 23.5.0: Wed Apr 24 19:52:07 PDT 2024; root:xnu-10063.121.3~1/RELEASE_ARM64_T8010

KernelCache UUID: 68C33D0C0879316ED057B3815B76B174

Kernel UUID: F3E3B8FE-D14A-34B5-BFFD-623AFAFE3572

Boot session UUID: 665EAF80-E47A-4291-9B44-AC820873016A

iBoot version: iBoot-10151.121.1

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0x1

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x5

x86 Previous Power Transitions: 0x405060400

PCIeUp link state: 0x89271611

macOS kernel slide: 0x600000

Paniclog version: 14

Kernel slide: 0x000000001361c000

Kernel text base: 0xfffffff01a620000

mach_absolute_time: 0xa791ecea33

Epoch Time: sec usec

Boot : 0x669eec7b 0x0000d6ee

Sleep : 0x669fcd2c 0x000bda0b

Wake : 0x66a02dfa 0x000d8ef6

Calendar: 0x66a02dfd 0x0005f449

Zone info:

Zone map: 0xffffffdc2ae2c000 - 0xffffffe22ae2c000

. VM : 0xffffffdc2ae2c000 - 0xffffffdd11490000

. RO : 0xffffffdd11490000 - 0xffffffdd5e15c000

. GEN0 : 0xffffffdd5e15c000 - 0xffffffde447c0000

. GEN1 : 0xffffffde447c0000 - 0xffffffdf2ae24000

. GEN2 : 0xffffffdf2ae24000 - 0xffffffe01148c000

. GEN3 : 0xffffffe01148c000 - 0xffffffe0f7af4000

. DATA : 0xffffffe0f7af4000 - 0xffffffe22ae2c000

Metadata: 0xffffffeff8628000 - 0xffffffeff9e28000

Bitmaps : 0xffffffeff9e28000 - 0xffffffeff9f48000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xffffffde44fe9050 0: 0x0000000000000001 0ro: 0x0000000000000000 }

CORE 0: PC=0xfffffff01a84b938, LR=0xfffffff01a84b938, FP=0xffffffe3efc87ef0

CORE 1 is the one that panicked. Check the full backtrace for details.

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Panicked task 0xffffffde4489ecf0: 0 pages, 227 threads: pid 0: kernel_task

Panicked thread: 0xffffffde44fe9050, backtrace: 0xffffffe3efc3f6e0, tid: 19969

lr: 0xfffffff01a81b1d4 fp: 0xffffffe3efc3f750

lr: 0xfffffff01a94ad44 fp: 0xffffffe3efc3f7c0

lr: 0xfffffff01a949d90 fp: 0xffffffe3efc3f8a0

lr: 0xfffffff01a7dd630 fp: 0xffffffe3efc3f8b0

lr: 0xfffffff01a81ac10 fp: 0xffffffe3efc3fc60

lr: 0xfffffff01aea2c44 fp: 0xffffffe3efc3fc80

lr: 0xfffffff0198731bc fp: 0xffffffe3efc3fcb0

lr: 0xfffffff019859fb4 fp: 0xffffffe3efc3fd10

lr: 0xfffffff0198605d4 fp: 0xffffffe3efc3fd60

lr: 0xfffffff01985a9ec fp: 0xffffffe3efc3fe00

lr: 0xfffffff0198597d4 fp: 0xffffffe3efc3fe30

lr: 0xfffffff01a870b58 fp: 0xffffffe3efc3ff20

lr: 0xfffffff01a7e86c4 fp: 0x0000000000000000

iPhone 13, iOS 17

Posted on Jul 23, 2024 3:44 PM

Reply

Answer 1

Jul 23, 2024 5:44 PM in response to lemonjerome

the kernel panic was caused by a catastrophic hardware error in the x86 intel processor.

read that very literally, because that is exactly what that means.

there are thousands of other kernel panics that can be caused by hardware, caused by software, or caused by complex and ambiguous causes. Your report is not ambiguous.

BUT -- Do not rush out the The Genius Bar just yet. They are NOT trained to read panic reports, and can only act when your Mac fails diagnostics.

you can contact Apple support, and work with the first responders through their initial checklist, and ask for a Specialist to contact you and read your report. You can reference the portion you posted on this public form, by your avatar or the discussion title.

Reply

Answer 2

Jul 23, 2024 5:15 PM in response to lemonjerome

the first line:

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

says that the kernel panic was caused by a catastrophic hardware error in the x86 intel processor.

the snippet of the panic report you posted does not contain the detailed reason, which would be much further down the report. you can post more using the additional text window:

...

Reply

Answer 3

HWTech

Level 9

68,426 points

Jul 24, 2024 8:24 PM in response to lemonjerome

You can try running the Apple Diagnostics to see if any hardware issue are detected. If the diagnostics report a problem, then Apple will probably repair the laptop. Unfortunately the diagnostics rarely detect problems, but it never hurts to try.

FYI, I personally would not spend any money repairing this laptop. A Logic Board repair is expensive. These 2019 laptops tend to have a higher rate of Logic Board failures than earlier models, plus the butterfly keyboards used by these 2016-2019 models have a lot of issues as well. In addition, this laptop will probably be needing a battery replacement (about $250) sometime soon since most batteries tend to need replaced between 3 - 5 years (depends on how much runtime you need on the battery). Some 13" 2019 MBPros will go Vintage around May 2025 and others around November 2025 since that is five years after being discontinued. The M-series Macs is where developers will focus most of their efforts soon so keep that in mind as well. I think the money you would spend on repairs is better spent going towards a new laptop. Just something to consider.

Reply

Answer 4

lemonjerome Author

Level 1

4 points

Jul 23, 2024 5:21 PM in response to Grant Bennet-Alder

Thank you for the response. The report that I posted is the complete report that I received. Does this report mean that it is a hardware issue? Or is there a software that is running to cause this problem?

Reply

How to Read Kernel Panic Log

Similar questions