Réparez vos affaires Communauté Boutique

Lancé le 20 septembre, le plus grand et plus cher smartphone Apple de l'année 2019 impressionne avec son écran OLED de 6,5 pouces, sa caméra à triple objectif et l'amélioration de l'autonomie de sa batterie. Il succède à l'iPhone XS Max.

165 questions Voir tout

Options

11 pro max screen display glitching and distorted and restarts

My iphone is randomly have screen glitch and distorted and then restarts once in 2 weeks ive got a panic log but i cant analyze it. It says ''''"panicString": "panic (cpu 1 caller Oxfffffff02a175744): |"Timing out on commit.

Waited 5 s. KSWMPR INTERRUPT AP:0x0!"

@AppleSynopsysMIPIDS|Controller.cp:842\nDebugger message: panicinMemory

ID: 0x6\nOS release type: User\nOS version: 20D47\nKernel version: Darwin Kernel

Version 22.3.0: Wed Jan 4 21:25:00 PST 2023; root:xnu-8792.82.2~1V

RELEASE_ARM64_T8030\nFileset Kernelcache UUID:

F71BE3007A3C1018B7F4B740A55B91F7\nKernel UUID: BC87557C-955F-30F3-

B098-A51038EA70FB\Boot session UUID: D088F9BE-8A21-4E02-

BB46-103E7C8642AE\niBoot version: iBoot-8419.82.1\nsecure boot?: YES\nroots installed: O\Paniclog version: 14\nKernelCache slide:

0x0000000020db0000\nKernelCache base: Oxfffffff027db4000\nKernel slide:

0x0000000021a34000\Kernel text base: Oxfffffff028a38000\Kernel text exec slide: 0x0000000021af0000\nKernel text exec base: "panicString": "panic (cpu 1 caller Oxfffffff02a175744): |"Timing out on commit.

Waited 5 s. KSWMPR INTERRUPT AP:0x0!"

@AppleSynopsysMIPIDS|Controller.cp:842\nDebugger message: panicinMemory

ID: 0x6\nOS release type: User\nOS version: 20D47\nKernel version: Darwin Kernel

Version 22.3.0: Wed Jan 4 21:25:00 PST 2023; root:xnu-8792.82.2~1V

RELEASE_ARM64_T8030\nFileset Kernelcache UUID:

F71BE3007A3C1018B7F4B740A55B91F7\nKernel UUID: BC87557C-955F-30F3-

B098-A51038EA70FB\Boot session UUID: D088F9BE-8A21-4E02-

BB46-103E7C8642AE\niBoot version: iBoot-8419.82.1\nsecure boot?: YES\nroots installed: O\Paniclog version: 14\nKernelCache slide:

0x0000000020db0000\nKernelCache base: Oxfffffff027db4000\nKernel slide:

0x0000000021a34000\Kernel text base: Oxfffffff028a38000\Kernel text exec slide: 0x0000000021af0000\nKernel text exec base:

Update (02/06/2023):

Block Image

Répondre à cette question J'ai le même problème

Cette question est-elle utile ?

Oui Non
Indice 0
Ajouter un commentaire

2 Réponses

Filtrer par :
Les plus utiles Les plus récentes Les plus ancien(ne)s
Réponse la plus utile

Options

I believe this is related to the display itself. The panic makes reference to AppleSynopsysMIPIDS. This would lead me to a Synopsis chip which makes use of MIPI type communications and the DS would likely refer to Display Serial Interface, a subset of the MIPI standard interface. I believe that chip is on the display.

If not, the actual display, it's something on the board end with either the display connector or communications between the display and the CPU. But I would wager display first.

Cette réponse est-elle utile ?

Oui Non
Indice 1

5 commentaires:

TL;DR: Screen's probably shot, try replacing it. If that doesn't work, there's something wrong on the logic board, which will be a difficult repair, not something us DIY-ers are equipped to tackle.

par

@dadibrokeit Yes. That exactly.

par

So its a high chance that it is the screening problem? Because after ut restarts it is okay again, but after 2 weeks the issue keeps coming back

par

@Kristian Vincent Mabalot Yeah, as Alisha explained, the phone appears to be losing communication with a chip on the screen. It seems to be very intermittent; if the error was there continuously you'd see a reboot every three minutes.

There are some cases where a kernel panic is caused by a software error; when that happens a full restore of the phone usually clears it up. Your case seems to fall somewhere in between the two ranges, as it doesn't explicitly call out a particular sensor, but the error is originating in a hardware communication bus.

Before going to the trouble and expense of replacing the screen, it would be worth your while to back up your phone, do a full restore and see if the error returns. If it's still there then it's almost certainly a hardware error, which could be caused by any of the issues Alisha mentioned previously. Basically, the only feasible fix is replacing the screen because if that's not the problem then it's in the motherboard, which is a whole lot harder to fix.

par

Kristian, From the image, I’d say you’ll probably need a replacement screen. Make sure it’s a good quality one (I prefer iFixit screens). It could still be something else, as Alisha explained, but replacing the screen is the first thing I would do!

par

Ajouter un commentaire

Options

It happen again today, and im able to take a picture of it before restarting is it a display issue?

Block Image

Cette réponse est-elle utile ?

Oui Non
Indice 0

1 commentaire:

Kristian, I went ahead and updated your question with the image (from your comment a couple of minutes ago). iFixit doesn’t allow pictures in the comments, and it’s much better to update your question with new information, as posting it as “answers” can flood and distort the question :)

par

Ajouter un commentaire

Ajouter une réponse

Kristian Vincent Mabalot sera éternellement reconnaissant.
Nombre de vues :

Dernières 24 heures : 0

7 derniers jours : 14

30 derniers jours : 55

Total : 693