Apple Event: May 7th at 7 am PT

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

Anyone know what happened to my computer?

panic(cpu 5 caller 0xfffffe0030682a44): "i2c2::_checkBusStatus Bus is still in a bad state; last read status 00010110 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-codec-output" Debugger message: panic Memory ID: 0x6 OS release type: User OS version: 20G95 Kernel version: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:27 PDT 2021; root:xnu-7195.141.2~5/RELEASE_ARM64_T8101 Fileset Kernelcache UUID: 15F4DFDFA9E0154FED96EA8997E65429 Kernel UUID: AC4A14A7-8A8E-3AE6-85A6-55E6B2502BF9 iBoot version: iBoot-6723.140.2 secure boot?: YES Paniclog version: 13 KernelCache slide: 0x0000000027688000 KernelCache base: 0xfffffe002e68c000 Kernel slide: 0x00000000281d0000 Kernel text base: 0xfffffe002f1d4000 Kernel text exec base: 0xfffffe002f2a0000 mach_absolute_time: 0x44699e61ac3 Epoch Time: sec usec Boot : 0x6131624f 0x0003d1ac Sleep : 0x613b4522 0x00038a36 Wake : 0x613b481b 0x0009717d Calendar: 0x613b4f08 0x00029ea2 CORE 0 recently retired instr at 0xfffffe002f412d6c CORE 1 recently retired instr at 0xfffffe002f412d6c CORE 2 recently retired instr at 0xfffffe002f412d6c CORE 3 recently retired instr at 0xfffffe002f412d6c CORE 4 recently retired instr at 0xfffffe002f412d70 CORE 5 recently retired instr at 0xfffffe002f4116a4 CORE 6 recently retired instr at 0xfffffe002f412d70 CORE 7 recently retired instr at 0xfffffe002f412d70 CORE 0 PVH locks held: None CORE 1 PVH locks held: None CORE 2 PVH locks held: None CORE 3 PVH locks held: None CORE 4 PVH locks held: None CORE 5 PVH locks held: None CORE 6 PVH locks held: None CORE 7 PVH locks held: None CORE 0: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe4019ae3ee0 CORE 1: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe401ea9bee0 CORE 2: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe4016afbee0 CORE 3: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe401aa3bee0 CORE 4: PC=0xfffffe002f2ce0b8, LR=0xfffffe002f2f5810, FP=0xfffffe401716bbe0 CORE 5 is the one that panicked. Check the full backtr

MacBook Pro 13″, macOS 11.5

Posted on Sep 10, 2021 5:56 AM

Reply
Question marked as Best reply

Posted on Sep 10, 2021 6:34 AM

parintorn208 wrote:

panic(cpu 5 caller 0xfffffe0030682a44): "i2c2::_checkBusStatus Bus is still in a bad state; last read status 00010110 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-codec-output" Debugger message: panic Memory ID: 0x6 OS release type: User OS version: 20G95 Kernel version: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:27 PDT 2021; root:xnu-7195.141.2~5/RELEASE_ARM64_T8101 Fileset Kernelcache UUID: 15F4DFDFA9E0154FED96EA8997E65429 Kernel UUID: AC4A14A7-8A8E-3AE6-85A6-55E6B2502BF9 iBoot version: iBoot-6723.140.2 secure boot?: YES Paniclog version: 13 KernelCache slide: 0x0000000027688000 KernelCache base: 0xfffffe002e68c000 Kernel slide: 0x00000000281d0000 Kernel text base: 0xfffffe002f1d4000 Kernel text exec base: 0xfffffe002f2a0000 mach_absolute_time: 0x44699e61ac3 Epoch Time: sec usec Boot : 0x6131624f 0x0003d1ac Sleep : 0x613b4522 0x00038a36 Wake : 0x613b481b 0x0009717d Calendar: 0x613b4f08 0x00029ea2 CORE 0 recently retired instr at 0xfffffe002f412d6c CORE 1 recently retired instr at 0xfffffe002f412d6c CORE 2 recently retired instr at 0xfffffe002f412d6c CORE 3 recently retired instr at 0xfffffe002f412d6c CORE 4 recently retired instr at 0xfffffe002f412d70 CORE 5 recently retired instr at 0xfffffe002f4116a4 CORE 6 recently retired instr at 0xfffffe002f412d70 CORE 7 recently retired instr at 0xfffffe002f412d70 CORE 0 PVH locks held: None CORE 1 PVH locks held: None CORE 2 PVH locks held: None CORE 3 PVH locks held: None CORE 4 PVH locks held: None CORE 5 PVH locks held: None CORE 6 PVH locks held: None CORE 7 PVH locks held: None CORE 0: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe4019ae3ee0 CORE 1: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe401ea9bee0 CORE 2: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe4016afbee0 CORE 3: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe401aa3bee0 CORE 4: PC=0xfffffe002f2ce0b8, LR=0xfffffe002f2f5810, FP=0xfffffe401716bbe0 CORE 5 is the one that panicked. Check the full backtr



You can try running the Diagnostic—https://support.apple.com/en-us/HT202731

Similar questions

6 replies
Question marked as Best reply

Sep 10, 2021 6:34 AM in response to parintorn208

parintorn208 wrote:

panic(cpu 5 caller 0xfffffe0030682a44): "i2c2::_checkBusStatus Bus is still in a bad state; last read status 00010110 int shadow 00010100 xfer 00000000 fifo 00000000 for device audio-codec-output" Debugger message: panic Memory ID: 0x6 OS release type: User OS version: 20G95 Kernel version: Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:27 PDT 2021; root:xnu-7195.141.2~5/RELEASE_ARM64_T8101 Fileset Kernelcache UUID: 15F4DFDFA9E0154FED96EA8997E65429 Kernel UUID: AC4A14A7-8A8E-3AE6-85A6-55E6B2502BF9 iBoot version: iBoot-6723.140.2 secure boot?: YES Paniclog version: 13 KernelCache slide: 0x0000000027688000 KernelCache base: 0xfffffe002e68c000 Kernel slide: 0x00000000281d0000 Kernel text base: 0xfffffe002f1d4000 Kernel text exec base: 0xfffffe002f2a0000 mach_absolute_time: 0x44699e61ac3 Epoch Time: sec usec Boot : 0x6131624f 0x0003d1ac Sleep : 0x613b4522 0x00038a36 Wake : 0x613b481b 0x0009717d Calendar: 0x613b4f08 0x00029ea2 CORE 0 recently retired instr at 0xfffffe002f412d6c CORE 1 recently retired instr at 0xfffffe002f412d6c CORE 2 recently retired instr at 0xfffffe002f412d6c CORE 3 recently retired instr at 0xfffffe002f412d6c CORE 4 recently retired instr at 0xfffffe002f412d70 CORE 5 recently retired instr at 0xfffffe002f4116a4 CORE 6 recently retired instr at 0xfffffe002f412d70 CORE 7 recently retired instr at 0xfffffe002f412d70 CORE 0 PVH locks held: None CORE 1 PVH locks held: None CORE 2 PVH locks held: None CORE 3 PVH locks held: None CORE 4 PVH locks held: None CORE 5 PVH locks held: None CORE 6 PVH locks held: None CORE 7 PVH locks held: None CORE 0: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe4019ae3ee0 CORE 1: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe401ea9bee0 CORE 2: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe4016afbee0 CORE 3: PC=0xfffffe002f319a64, LR=0xfffffe002f319a5c, FP=0xfffffe401aa3bee0 CORE 4: PC=0xfffffe002f2ce0b8, LR=0xfffffe002f2f5810, FP=0xfffffe401716bbe0 CORE 5 is the one that panicked. Check the full backtr



You can try running the Diagnostic—https://support.apple.com/en-us/HT202731

Sep 10, 2021 7:41 AM in response to parintorn208

parintorn208 wrote:

So what do I do next?
https://discussions.apple.com/content/attachment/b6c3bc35-4fd1-4036-80db-f36dcfd4b75f


reference code ADP000—




Uninstall all third party apps that are Cleaners/Optimizers/Anti-Virus/VPN

all known to cause issues on the macOS



Kernel Panics are predominately caused by hardware faults or faulty third-party kernel extensions.


Learn what to do if your computer restarts or shuts down unexpectedly, or you get a message that your computer restarted or shut down because of a problem.


If your Mac spontaneously restarts or displays a ... - Apple Support

 https://support.apple.com/en-us/HT200553



If no insight or resolve you get a good look at your System config. and reveal conflicts or issues, you can download/run this trusted utility https://etrecheck.com  


If you need help interpreting the report you can post it here in its entirety in the "Additional Text" box in the editing toolbar below, in your reply.

Anyone know what happened to my computer?

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