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.

User profile for user: William Huchting
William Huchting Author
User level: Level 1
18 points

Kernel panic 2019 MacBook Pro 32g ram and Radeon Pro Vega 13.6 Mac OS

I am getting this kernel panic after plugging my Mac into a USB-hub at school. Did it short out my motherboard????


Attempting to forcibly halt cpu 0


cpu 0 failed to halt with error -5: halt not supported for this configuration


Debugger synchronization timed out; waited 240000 nanoseconds


panic(cpu 1 caller 0xfffffff0191eaddc): Spinlock[0xffffffe22e42f360] timeout after 12585600 ticks; current owner: 0xffffffdf2e5628a8 (on cpu 0), start time: 566079824770, now: 566092410370, timeout: 12582912 @locks.c:446


Debugger message: panic


Memory ID: 0x6


OS release type: User


OS version: 21P365


macOS version: 22G120


Kernel version: Darwin Kernel Version 23.0.0: Thu Aug 17 20:55:28 PDT 2023; root:xnu-10002.1.11~1/RELEASE_ARM64_T8010


KernelCache UUID: 83132AB4798578E2E86BE4877CB66C17


Kernel UUID: 4D383FA8-C2B8-30E0-87FD-74DE482E481E


Boot session UUID: 5C680FC1-2322-4FC3-BF56-5DD2C1008D80


iBoot version: iBoot-10151.1.1


secure boot?: YES


roots installed: 0


x86 EFI Boot State: 0xe


x86 System State: 0x0


x86 Power State: 0x0


x86 Shutdown Cause: 0xec


x86 Previous Power Transitions: 0x20002000200


PCIeUp link state: 0x94721614


macOS kernel slide: 0x8e00000


Paniclog version: 14


Kernel slide:      0x0000000011fd8000


Kernel text base:  0xfffffff018fdc000


mach_absolute_time: 0x83cdd96cb0


Epoch Time:        sec       usec


  Boot    : 0x650cf9ca 0x000dde11


  Sleep   : 0x650e0751 0x00005307


  Wake    : 0x650e0753 0x00083d9c


  Calendar: 0x650e142a 0x0009b90e




Zone info:


  Zone map: 0xffffffdc2e4a0000 - 0xffffffe22e4a0000


  . VM    : 0xffffffdc2e4a0000 - 0xffffffdd14b04000


  . RO    : 0xffffffdd14b04000 - 0xffffffdd617d0000


  . GEN0  : 0xffffffdd617d0000 - 0xffffffde47e34000


  . GEN1  : 0xffffffde47e34000 - 0xffffffdf2e498000


  . GEN2  : 0xffffffdf2e498000 - 0xffffffe014b00000


  . GEN3  : 0xffffffe014b00000 - 0xffffffe0fb168000


  . DATA  : 0xffffffe0fb168000 - 0xffffffe22e4a0000


  Metadata: 0xffffffe22f6a0000 - 0xffffffe230ea0000


  Bitmaps : 0xffffffe230ea0000 - 0xffffffe230fb8000


  Extra   : 0 - 0




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


CORE 0: PC=0x0000000000000000, LR=0x0000000000000000, FP=0x0000000000000000


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

MacBook Pro 15″, macOS 13.6

Posted on Sep 22, 2023 3:43 PM

Reply
Question marked as Top-ranking reply
User profile for user: John Galt
John Galt
User level: Level 10
146,390 points

Posted on Sep 22, 2023 7:31 PM

Refer to If your Mac restarts and a message appears - Apple Support.


Follow those suggestions. It is unclear to me if the KPs persist after disconnecting all external devices as that document suggests.

View in context

Similar questions

2 replies
User profile for user: HWTech
HWTech
User level: Level 9
60,446 points

Sep 24, 2023 5:05 PM in response to William Huchting

You are missing some critical parts of the Kernel Panic log. When posting logs, you need to use the "Additional Text" icon which looks like a piece of paper.


Also, it is best to post several Kernel Panic logs so we can see if there is any pattern to them. You can find the Kernel Panic logs in "/Library/Logs/DiagnosticReports" with file names beginning with "kernel". If you cannot find any within that folder, then look within the "Retired" subfolder since macOS can quickly move them there.


It may also be useful to run EtreCheck and post the report here using the "Additional Text" icon on the forum editing window toolbar. Review the EtreCheck instructions for copying the report (must click "Share Report" and select "Copy" or "Copy Report" within the EtreCheck app). Software issues are just as likely to cause a Kernel Panic as a hardware issue.


FYI, I am always hesitant to connecting to any devices which are not my own. If it is a school supplied device of good quality, then it should be relative safe to use. However, someone else may have accidentally damaged the hub or its cable which in turn could possibly damage any other device which later connects to it.


Disconnecting all external devices as suggested by @John Galt is also recommended just in case one of them is causing a problem. And do you have any external devices connected to the same USB-C port as the one you used for the school hub? Or the same side of the laptop?


You can try running the Apple Diagnostics to see if any hardware issues are detected. Unfortunately the diagnostics don't detect most hardware issues.

Reply

Kernel panic 2019 MacBook Pro 32g ram and Radeon Pro Vega 13.6 Mac OS

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