Ir para o conteúdo principal

Repair guides and disassembly information for the MacBook Pro 16'' released in November of 2019. Model A2141, EMC 3347.

191 Perguntas Visualizar todos

Crashing with Kernel panic i2c3


my Macbook Pro 16 (2019 Modell) is randomly crashing with the same kernel panic (i2c3::_checkBusStatus Bus is still in a bad state; see below). It started a few weeks ago. At first, the built-in camera didn't work anymore. The system report/profiler just shows a question mark as a serial number:

Produkt-ID: 0x8514
Hersteller-ID: 0x05ac (Apple Inc.)
Version: 2.01
Seriennummer: ?
Hersteller: Apple Inc.
Standort-ID: 0x80200000

So I guess the failure of the camera is somehow related to the kernel panics. The Macbook otherwise works flawlessly, sometimes running for a few days, sometimes only a few hours. The kernel panics are quite random and I have not managed to reproduce them somehow.

The kernel panic log:

panic(cpu 0 caller 0xfffffff027983140): "i2c3::_checkBusStatus Bus is still in a bad state; last read status 00010110 int shadow 00010100 xfer 00000000 fifo 00000000 for device als" @AppleS5L8940XI2C.cpp:451
Debugger message: panic
Memory ID: 0x6
OS release type: Not set yet
OS version: Not set yet
macOS version: Not set
Kernel version: Darwin Kernel Version 22.6.0: Wed Jul  5 21:38:08 PDT 2023; root:xnu-8796.141.3~1/RELEASE_ARM64_T8010
KernelCache UUID: 7A4ADA9F9D14E594F7F2E65E7778623B
Kernel UUID: F1805A53-5DF0-38E6-B1B8-0063FFF1926D
Boot session UUID: 3D9E2D28-247D-4F92-9F35-CCE9F6C6F817
iBoot version: iBoot-8422.141.2
secure boot?: YES
roots installed: 0
x86 EFI Boot State: not available
x86 System State: not available
x86 Power State: not available
x86 Shutdown Cause: not available
x86 Previous Power Transitions: not available
PCIeUp link state: not available
macOS kernel slide: not available
Paniclog version: 14
Kernel slide:      0x0000000021360000
Kernel text base:  0xfffffff028364000
mach_absolute_time: 0x59f2ccd
Epoch Time:        sec       usec
  Boot    : 0x00000000 0x00000000
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x00000000 0x00000000

Zone info:
  Zone map: 0xffffffdc0083c000 - 0xffffffe20083c000
  . VM    : 0xffffffdc0083c000 - 0xffffffdce6ea0000
  . RO    : 0xffffffdce6ea0000 - 0xffffffdd33b6c000
  . GEN0  : 0xffffffdd33b6c000 - 0xffffffde1a1d0000
  . GEN1  : 0xffffffde1a1d0000 - 0xffffffdf00834000
  . GEN2  : 0xffffffdf00834000 - 0xffffffdfe6e9c000
  . GEN3  : 0xffffffdfe6e9c000 - 0xffffffe0cd504000
  . DATA  : 0xffffffe0cd504000 - 0xffffffe20083c000
  Metadata: 0xffffffe21320c000 - 0xffffffe214a0c000
  Bitmaps : 0xffffffe214a0c000 - 0xffffffe214b30000
  Extra   : 0 - 0

TPIDRx_ELy = {1: 0xffffffdf00b3e4e0  0: 0x0000000000000000  0ro: 0x0000000000000000 }
CORE 0 is the one that panicked. Check the full backtrace for details.
CORE 1: PC=0xfffffff028a60db0, LR=0xfffffff028a60db0, FP=0xffffffe206a535c0
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Panicked task 0xffffffdf007738c0: 0 pages, 171 threads: pid 0: kernel_task
Panicked thread: 0xffffffdf00b3e4e0, backtrace: 0xffffffe206ad74b0, tid: 390
          lr: 0xfffffff028555624  fp: 0xffffffe206ad7520
          lr: 0xfffffff0286758d4  fp: 0xffffffe206ad7590
          lr: 0xfffffff028674888  fp: 0xffffffe206ad7670
          lr: 0xfffffff0285195fc  fp: 0xffffffe206ad7680
          lr: 0xfffffff028555060  fp: 0xffffffe206ad7a30
          lr: 0xfffffff028ba8ef4  fp: 0xffffffe206ad7a50
          lr: 0xfffffff027983140  fp: 0xffffffe206ad7af0
          lr: 0xfffffff027983298  fp: 0xffffffe206ad7b10
          lr: 0xfffffff027982c94  fp: 0xffffffe206ad7b60
          lr: 0xfffffff027413e4c  fp: 0xffffffe206ad7b80
          lr: 0xfffffff027413cb4  fp: 0xffffffe206ad7bb0
          lr: 0xfffffff028af76e4  fp: 0xffffffe206ad7c20
          lr: 0xfffffff027414860  fp: 0xffffffe206ad7c80
          lr: 0xfffffff027a65fe4  fp: 0xffffffe206ad7ca0
          lr: 0xfffffff027a6818c  fp: 0xffffffe206ad7d20
          lr: 0xfffffff028ac9cb0  fp: 0xffffffe206ad7e00
          lr: 0xfffffff028ac9108  fp: 0xffffffe206ad7e70
          lr: 0xfffffff028acce20  fp: 0xffffffe206ad7f20
          lr: 0xfffffff0285246c0  fp: 0x0000000000000000

In the more detailed report I can also see this:

{"roots_installed":0,"caused_by":"bridgeos","os_version":"Bridge OS 7.6 (20P6072)","macos_system_state":"not set","incident_id":"3D9E2D28-247D-4F92-9F35-CCE9F6C6F817","bridgeos_roots_installed":0,"bug_type":"210","timestamp":"2023-08-30 13:09:19.00 +0000"}

What I did so far:
- Reflashing T2 chip with another Mac and the Apple Configurator
- Resetting basically everything (SMC, NVRAM, etc.)
- Memtest without errors
- Reinstalling MacOS

Does anyone have any ideas what I can do to make the kernel panics stop? If the camera would work again it would be a bonus, but I don't really need it.

Responder a esta pergunta Também tenho esse problema

Esta é uma boa pergunta?

Pontuação 0
1 comentário

Does the crashing still occur in Safe Mode?


Adicionar um comentário

1 resposta

Pergunta mais útil

This is a bit of a hand-waving guess, but looking though the log, I see:

"i2c3::_checkBusStatus Bus is still in a bad state; last read status 00010110 int shadow 00010100 xfer 00000000 fifo 00000000 for device als"

The "device als" is probably referring to the ambient light sensor, and in most MacBooks from this era (not sure about the 2019 16" model) it is in the display, near the webcam. The fact that you mentioned the camera not working is another hint. You may have a problem within your display assembly, or an issue with the connection between the display and the logic board, both of which could cause issues with the camera and ambient light sensor. This issue seems similar though with a slightly different model.

The first thing to try would be re-seating all cables associated with the display assembly, as shown in this guide. If that doesn't do it, you may need to start replacing parts. iFixit sells a replacement display cable, which might be a good thing to try before replacing the whole display assembly.

Imagem de MacBook Pro 16" (2019) Display Cable


MacBook Pro 16" (2019) Display Cable


Esta resposta foi útil?

Pontuação 1

4 comentários:

Thanks for your answer!

Per se, the ambient light sensor works - when I shine a flashlight on it, the display gets brighter and when I remove it, it gets darker again. The system profiler also detects the sensor correctly unlike the camera.

I have now ordered the cable anyway and see if a swap will do any good. To replace the whole display would unfortunately no longer be financially reasonable.

Thanks again for the tip and I'll get back to you as soon as it's replaced.


Unfortunately, it didn't work, the error is the same.


Does the webcam also still not work? If you haven't already, try to re-seat the camera/ALS connection to the display board (the board that the ribbon connects to, see the linked thread in my post above).


Yes, the camera is still recognized with a ? as a serial number.

Re-seating the camera cable didn't help either :(


Adicionar um comentário

Adicionar a sua resposta

testosus será eternamente grato(a).
Exibir estatísticas:

Últimas 24 horas: 0

Últimos 7 dias: 4

Últimos 30 dias: 26

Duração total: 178