물건을 수리하세요 커뮤니티 상점

9월 20일에 출시된 가장 크고 비싼 2019년 Apple 스마트폰으로 6.5" OLED 디스플레이를, 트리플-렌즈 카메라 시스템및 크게 향상된 배터리 수명이 특징입니다. iPhone XS Max의 후속 제품입니다.

20 질문 전체 보기 | 27 부품 둘러보기

옵션

i2c3::_checkBusStatus SCL is stuck low; last write status 00010110

bug_type":"210","timestamp":"2024-04-02 09:22:11.00 +0200","os_version":"iPhone OS 17.4.1 (21E236)","roots_installed":0,"incident_id":"23B2C304-02B2-4433-AA84-2E2B7CB4AAFE"}

{

"build" : "iPhone OS 17.4.1 (21E236)",

"product" : "iPhone12,5",

"socId" : "8030",

"socRevision" : "11",

"incident" : "23B2C304-02B2-4433-AA84-2E2B7CB4AAFE",

"crashReporterKey" : "425ad00ac43617f1bcc5c6dc967243b2948053cd",

"kernel" : "Darwin Kernel Version 23.4.0: Fri Mar 8 23:26:31 PST 2024; root:xnu-10063.102.14~67\/RELEASE_ARM64_T8030",

"date" : "2024-04-02 09:22:11.21 +0200",

"panicString" : "panic(cpu 3 caller 0xfffffff0261f0d24): \"i2c3::_checkBusStatus SCL is stuck low; last write status 00010110 int shadow 01090100 xfer 00000000 fifo 00000000 for device roswell\" @AppleS5L8940XI2C.cpp:470\nDebugger message: panic\nMemory ID: 0x1\nOS release type: User\nOS version: 21E236\nKernel version: Darwin Kernel Version 23.4.0: Fri Mar 8 23:26:31 PST 2024; root:xnu-10063.102.14~67\/RELEASE_ARM64_T8030\nFileset Kernelcache UUID: B603FBC2B014FFD42F13F9D47BF3EED9\nKernel UUID: B8517801-F3D0-341C-AF4B-80D5D3825EBA\nBoot session UUID: 23B2C304-02B2-4433-AA84-2E2B7CB4AAFE\niBoot version: iBoot-10151.102.2\nsecure boot?: YES\nroots installed: 0\nPaniclog version: 14\nKernelCache slide: 0x000000001d134000\nKernelCache base: 0xfffffff024138000\nKernel slide: 0x000000001d13c000\nKernel text base: 0xfffffff024140000\nKernel text exec slide: 0x000000001de70000\nKernel text exec base: 0xfffffff024e74000\nmach_absolute_time: 0x34b2b0b1\nEpoch Time: sec usec\n Boot : 0x660bb1c4 0x00007c74\n Sleep : 0x00000000 0x00000000\n Wake : 0x00000000 0x00000000\n Calendar: 0x660bb1de 0x000c5661\n\nZone info:\n Zone map: 0xffffffdc08614000 - 0xffffffe208614000\n . VM : 0xffffffdc08614000 - 0xffffffdceec78000\n . RO : 0xffffffdceec78000 - 0xffffffdd3b944000\n . GEN0 : 0xffffffdd3b944000 - 0xffffffde21fa8000\n . GEN1 : 0xffffffde21fa8000 - 0xffffffdf0860c000\n . GEN2 : 0xffffffdf0860c000 - 0xffffffdfeec74000\n . GEN3 : 0xffffffdfeec74000 - 0xffffffe0d52dc000\n . DATA : 0xffffffe0d52dc000 - 0xffffffe208614000\n Metadata: 0xffffffdc00354000 - 0xffffffdc01b54000\n Bitmaps : 0xffffffdc01b54000 - 0xffffffdc02604000\n Extra : 0 - 0\n\nCORE 0 recently retired instr at 0xfffffff024ffe1d4\nCORE 1 recently retired instr at 0xfffffff024ffe1d4\nCORE 2 recently retired instr at 0xfffffff024ffe1d4\nCORE 3 recently retired instr at 0xfffffff024ffcc74\nCORE 4 recently retired instr at 0xfffffff024ffe1d4\nCORE 5 recently retired instr at 0xfffffff024ffe1d4\nTPIDRx_ELy = {1: 0xffffffdf0470d780 0: 0x0000000000000003 0ro: 0x0000000000000000 }\nCORE 0: PC=0x00000001027d3404, LR=0x00000001027d3400, FP=0x000000016da85c20\nCORE 1: PC=0x00000001a262eee4, LR=0x0000000100afdbb0, FP=0x000000016f39e1b0\nCORE 2: PC=0x000000019a564214, LR=0x000000019a56506c, FP=0x000000016b8b6240\nCORE 3 is the one that panicked. Check the full

이 질문에 답하기 저도 같은 문제가 있습니다

좋은 질문입니까?

예 아니요
점수 0
댓글 달기

답변 1개

필터 기준:
가장 유용함 가장 최근 가장 오래된
가장 유용한 답변

옵션

Okay, luckily enough I happen to have schematics for the 11 Pro Max, or we'd be out of luck figuring this one out.

Alisha (@flannelist), can you double check my reasoning and logic here?

All right, the I2C bus labelled I2C3 goes to three connectors on the board; the FCAM connector J7600, the Tele Camera Connector J7300, and the Touch Connector, J8100. The I/O address table for J8100 lists two addresses used for something called "Roswell", and the "Touch EEPROM". J8100 is specifically shown as going to the digitizer on the screen in the screen replacement guide.

Given that your panic log explicitly mentions Roswell:

i2c3::_checkBusStatus SCL is stuck low; last write status 00010110 int shadow 01090100 xfer 00000000 fifo 00000000 for device roswell

I would say it's a pretty good bet the problem is being caused by a bad screen; specifically the digitizer on it. Of course, you haven't given us any other information about this error such as, did it start as a result of being dropped or some other damage to the phone?

In the absence of any other knowledge, I'd say you're probably in the market for a new screen. That would be what I would do if it was my phone.

이 답변이 도움이 되었나요?

예 아니요
점수 3

댓글 3개:

On the nose. I just saw this same panic in a group the other day actually. But yes, Roswell (likely the touch controller, Apple loves a code name) and the touch eeprom are both on the cable on the back of the display. So New screen would be my first guess.

의

What if I ignore it and don't replace the screen? Will something fatal happen?

의

@ammarhaidar Although it's impossible to be sure, best guess is that whatever symptoms you're seeing now most likely won't get any worse, but there are no guarantees. It is, however, unlikely that anything fatal to the whole operation of the phone will happen, so if it's working well enough to be usable then I don't see why you wouldn't be able to keep using it that way until it either gets worse or you fix the problem.

의

댓글 달기

답변을 추가하세요

FOE Transition 영원히 감사할 것입니다.
조회 통계:

지난 24시간: 1

지난 7일: 36

지난 30일: 185

전체 시간: 5,381