Closed uyu423 closed 8 months ago
Hi there,
thanks for reaching out and sorry about the trouble!
From the log section it seems like the issue is happening at low level (DCPEXT) is the part of the Apple Silicon chip that manages external displays, negotiating the connection. BetterDisplay does not directly communicate to this component but uses macOS APIs to interact with it, so it might be difficult to figure out what causes the issue or if there is a definite connection between the crash and the app (as sadly Apple Silicon Macs have a tendency to crash or mishandle display related stuff for a myriad of internal reasons). However if the issue is clearly linked to BetterDisplay running (happens only then), an approach might be to try to isolate which functionality triggers the issue with this specific display configuration (this means trying to disable various BetterDisplay features until the issue is pinpointed).
Questions:
Thank you!
@waydabber
Hello,
Thank you very much for your prompt and detailed response. Here are the answers to your questions based on my experience:
I will proceed with disabling the connection management feature to see if this change affects the occurrence of the issue. I appreciate your guidance on this matter and will report back with my findings.
Thank you for your assistance and patience.
ps) Is there a way to change BetterDisplay's language options? I'd like to share a screenshot of my settings, but it's in Korean so it might be difficult to understand. If you can tell me how to change the language to English, I will share the current settings screen.
ps2) Since I am not using the Pro version, I cannot change the Display Connections items....
Sure, you can change the language under System Settings > General > Language & Region > Applications.
All right, since the issue seems to be happening regardless of whether BetterDisplay is running or not, it might be some kind of display specific problem. The problem is related to the DCP which handles the framebuffer as well, so it might be that the configured custom resolution causes the issue. You can try with different custom resolutions or test if a reset to the default configuration fixes the issue or not.
I'll move this over to discussions, maybe others had/have similar issues and can chime in.
Description:
I've encountered a recurrent issue where my MacMini reboots from sleep mode accompanied by a kernel panic. This issue started occurring after I installed BetterDisplay, an open-source tool for enhanced display management on macOS. My setup includes one monitor connected via HDMI and a second monitor connected via USB-C.
Kernel Panic Log Summary:
The kernel panic references
AppleT602XDPTXPort
with a message indicating a timeout occurred duringdeactivate()
afterdisplayRelease()
. This seems to be related to display management, potentially linked to the operation of BetterDisplay. Below is a condensed version of the kernel panic log for reference:Steps to Reproduce:
Expected Behavior:
The system enters and exits sleep mode without issues, with all display configurations preserved and managed by BetterDisplay.
Actual Behavior:
The system experiences a kernel panic related to
AppleT602XDPTXPort
during sleep mode, leading to an unexpected reboot.System Configuration:
Request:
I am seeking assistance to resolve this kernel panic issue related to display management with BetterDisplay. Any insights, suggestions, or fixes would be greatly appreciated. Thank you for your support and for the development of this valuable tool.
Full logs