Replies: 37 comments 72 replies
-
|
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! |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
ps2) Since I am not using the Pro version, I cannot change the Display Connections items.... |
Beta Was this translation helpful? Give feedback.
-
|
Sure, you can change the language under System Settings > General > Language & Region > Applications. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I have the exact same issue after an update to Mac OS X 14.4 with BetterDisplay 2.2.5. After every post hibernation login there is a short pause followed by a kernel panic referencing the mentioned component (DCPEXT). Fun fact: Mac OS X 14.3.1 with BetterDisplay 1.x never had this problem (I had not realised I was using the wrong BD version for my OS previously), it was introduced with Mac OS X 14.4, not BetterDisplay 2.x. Forgot to mention: I use only 1 display (LG 43", 4K, HDMI) and the virtual screen feature with mirroring (150% scale). |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, the DCPEXT issue is a low level crash caused by some bug in the firmware running in the DCP part of the Apple Silicon chip (this handles the framebuffer and the connection to the display). Sonoma introduced various bugs that can cause this (typical culprit is using accessibility zoom for example). The DCP firmware is continuously tweaked - hopefully whatever causes the issue will be fixed in the next update. Make sure you sent these crash logs to Apple. |
Beta Was this translation helpful? Give feedback.
-
|
Today, for the fun of it, I changed the connection to the monitor to DP. Not only does the monitor now wake up automatically when hitting a key on the keyboard, the kernel panics are gone. As you already mentioned multiple times, it seems that macOS 14.4 is very picky in regards to the attached gear, and the ball is in Apple's field it seems ... |
Beta Was this translation helpful? Give feedback.
-
|
same here, every sleep, mac mini reboot
Device: Mac Mini M2 crash log has been sent to Apple |
Beta Was this translation helpful? Give feedback.
-
|
I get this when I use accessibility zoom on display B while a video is playing on display A. There are numerous DCP related issues, some displays are more affected than others - we can only hope Apple will fix them eventually. There is no way to debug any of that stuff as it's not open. |
Beta Was this translation helpful? Give feedback.
-
|
I stoped mirroring, no reboot, only feature used [High Resolution (HiDPI)] its enough for now |
Beta Was this translation helpful? Give feedback.
-
|
I faced the same problem after upgrading to macOS 14.4. Kernel Extensions in backtrace: com.apple.driver.AppleDisplayCrossbar |
Beta Was this translation helpful? Give feedback.
-
|
Hi there - does this issue happen only when running BetterDisplay? If so, can you try downgrading to some older version like v2.2.0 just to try if the issue still happens? This driver has something to do with DisplayPort communication via USB-C (as I deduce it from the i/o registry) but otherwise of course totally undocumented by Apple so who knows... What kind of display connection are you using? |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply. Since I only have this app related to the monitors, I uninstalled BetterDisplay. Before uninstalling, the restart happened within 3 to 12 hours after sleeping. After that, no restart happened after a 2-day-sleeping. I will try the older version. For the monitor, my mac mini m2 connects 2 monitors, one through HDMI and one through a type-C to HDMI cable. |
Beta Was this translation helpful? Give feedback.
-
|
All right. It might be that some feature of the app causes some issues with this specific config as each unexpected macOS issue is caused by the overall software/hardware environment and usage and BetterDisplay is for sure a part of it. The problem however that if the crash/bug occurs in a protected system component, only Apple can debug it. If they receive enough bug reports of some kind, a red flag will light up somewhere and they will eventually fix the code path that is crashing... |
Beta Was this translation helpful? Give feedback.
-
|
I want to update you on the new issues I'm encountering. My main purpose is to control the volume by keyboard, therefore I tried another app MonitorControl which was also developed by you. The latest version was released Sep 2023. I think the main components of OSD control are similar in the two applications. The same problem happened in just around 20 minutes after sleep. |
Beta Was this translation helpful? Give feedback.
-
|
Hello there, I came across this thread by searching for However, I'm not using BetterDisplay. I'm posting this here because I wanted to let you all know that whatever macOS panic reboots you're facing -- it's probably not because of BetterDisplay. And, for what it's worth, my machine specs:
I hope this is somehow helpful. Here's to hoping this issue will be solved by Apple ASAP. |
Beta Was this translation helpful? Give feedback.
-
|
Same here. I bought a new Mac Mini M2 Pro 3 days ago and upgrade to 14.4 right away, and it happens everyday since then, thought it was a quality issue. Thank you for all the discussion! |
Beta Was this translation helpful? Give feedback.
-
|
Just an update from my side: Yesterday, I begrudgingly bought a USB-C to DisplayPort cable from BestBuy and now my Mac Studio is connected via the USB-C port to my monitor, and the kernel panics are now gone. |
Beta Was this translation helpful? Give feedback.
-
|
I don't have any external monitors, and with or without uninstalling betterdisplay pro and waking up after a black screen, I experience a kernel panic and then a reboot. After going to the official shop dfu reset and time machine recovery, the issue came back the same day. I've read that some people say that using time machine recovery suggests selecting only file recovery, which will fix the problem. |
Beta Was this translation helpful? Give feedback.
-
|
I disabled Bluetooth. It solved this issue for me. I found it was happening only when my Airpods were trying to connect while my was waking up. Sonoma 14.4.1 It was happening every time, and since doing that it has not happened once. |
Beta Was this translation helpful? Give feedback.
-
|
I found this page based on searching for the same error many of you all are getting:
This has been happening since the macOS 14.4 update. I noticed it will do it more if I just lock the screen and not "log off" my user account. It's still annoying to see every time I wake my MacMini (M2 Pro, 16 GB of RAM, 1TB storage) from sleep. As far as I can tell, I do not have BetterDisplay installed. FWIW, here are the specs on my two monitors:
Thank you all for posting about this issue. I hope Apple (or someone) finds a resolution soon because it's getting annoying. |
Beta Was this translation helpful? Give feedback.
-
|
thanks @muli for chiming in. Indeed, it seems there is a general issue with 14.4 that affects some Macs - many report various display and USB related issues in general. Let's just hope things will be ironed out in a subsequent update soon. To be fair, various DCPEXT related crashes (unrelated to BetterDisplay) existed long before 14.4, I regularly encounter them in multi-monitor environments. Each OS release is unique in this regard as Apple is continuously tweaking both drivers and the DCP firmware - sadly none of these issues can be debugged as all these come from the locked-down parts of the system. 14.4 particularly seems to be extra picky with peripherals in general. |
Beta Was this translation helpful? Give feedback.
-
|
I read that this issue is not caused by BetterDisplay. (I hope this discussion is maintained for users searching for similar issues) |
Beta Was this translation helpful? Give feedback.
-
|
No problem. I understand people expect their Macs to work properly out of the box and whenever there is a crash, the first suspect is a third party app - and when the crash is related to a display, the suspect will be a third party app that deals with displays. I think in exactly the same lines whenever such a thing happens. :) These DCPEXT issues date back to the first Apple Silicon Macs. It seems Apple still could not resolve all these issues even though the DCP's formware/rtOS is being tweaked all the time. My experience is that Sonoma actually made things worse (as I mentioned, I can replicate the DCP error issue anytime by simply playing a video on a screen A and use accessibility zoom on screen B, the bug is probably related to the way Sonoma changed how multi-monitor zoom works. The same thing happens on M1, M2, M3, completely unrelated systems/installations. Also, many displays that work fine on PCs (or Intel Macs) produce all kinds of connection/sleepwake/no-signal etc issues on Apple Silicon Macs. There are many other display related bugs as well (obviously I came across these heavily). Let's hope Apple will eventually find a way to fix all these problems, it is (or it began) as a computer maker company after all. :) |
Beta Was this translation helpful? Give feedback.
-
|
@waydabber, thank you for staying positive and providing insight into DCPEXT. I, too, stumbled upon this issue after a Google search for the Although this issue was raised against your innocent software, I still found the discussion here extremely helpful and reassured me that this was an issue caused by macOS 14.4 and not but something I did to my system. Thanks again for keeping this discussion going and providing insight into what may be happening. 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Right. I am using a dongle myself - it has the Synaptics VMM7100 chipset - with a HDMI monitor even on the M3 (which has an otherwise capable HDMI 2.1 port) as things are much more stable this way (my display can actually wake and sleep properly + there are no "no-signal" issues unlike with the built-in HDMI port). |
Beta Was this translation helpful? Give feedback.
-
|
Note: some similar issues affecting MBAs without external displays. #2804 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, im experiencing this even without any external display, as soon as it goes to sleep for a while and on wake it reboots with the kernel panic log. I will try a clean install to see if it happens as I recently migrated to this MBA M2 from a MBP 14 incher using Migration assistant (the MBP did not have this issue). |
Beta Was this translation helpful? Give feedback.
-
|
Did you try updating to Sonoma 14.4.1 that was released yesterday? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, already happened on 14.4.1 . |
Beta Was this translation helpful? Give feedback.
-
|
Will try a clean install if it happens too often to see if that helps. |
Beta Was this translation helpful? Give feedback.
-
|
14.4.1 (23E224) released, but Apple not fix issue |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, Just chiming in to report that I think I am experiencing a related issue. I do not use BetterDisplay, but I am on an M2 Mac Air that has an external display connected to and powered via USB-C, and the external display also is connected to a wireless HDMI rx'er. The system crashed with:
|
Beta Was this translation helpful? Give feedback.
-
|
By the way, I wanted to add that I came in not knowing about BetterDisplay, and now I don’t see how I could live without it. |
Beta Was this translation helpful? Give feedback.
-
|
Also having this issue. With or without BetterDisplay - Crashes the mac every night. M2 Ultra Mac Studio |
Beta Was this translation helpful? Give feedback.
-
|
@corysus If I enable this option, will my Mac Mini not go into sleep mode? If so, I'm concerned about my power consumption. |
Beta Was this translation helpful? Give feedback.
-
|
The current issue with kernel panic occurs, if I understand correctly, when the Mac goes into hibernation mode. This is a mode in which macOS copies all RAM content to SSD and shuts everything down, entering a sort of standby mode. It's a bit complicated with macOS because it's not the same as with other systems; in short, it should consume less power when going into sleep mode, and the only difference is that when this option is enabled, RAM content will be transferred to HDD but will still remain active in RAM, unlike without this option, where the same process happens but in this case, RAM is also shut down to save even more power. Currently, I don't have a device with me to monitor power consumption to verify this, but this is what I could find on the internet. |
Beta Was this translation helpful? Give feedback.
-
|
I followed the comment mentioning the solution above and changed the screen saver to a photo, but the issue recurred. |
Beta Was this translation helpful? Give feedback.
-
|
This is the only way that works for me. Today marks 7 days without a crash.
|
Beta Was this translation helpful? Give feedback.
-
|
I have this checked since long time ago, and still having the crashes. |
Beta Was this translation helpful? Give feedback.
-
|
Same for me, I use Luna Display (USB-C), and an HDMI-connected BenQ monitor. I don't use BetterDisplay. Unexpected Restarts have been happening several times a day, tied to sleep. In settings - energy saver - I've now turned on "Prevent automatic sleeping." My system specs in case it helps: |
Beta Was this translation helpful? Give feedback.
-
The only way (for now) is to use this method: #2622 (reply in thread) Using this method, my Mac Mini has not been reset for over 21 days |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, but my macbook air isn't able to be set up that way, I'll update to macOS 14.5 beta4, I've read that some people say that the GPU acceleration issue seems to be resolved in that version. I will keep an eye on the issue. |
Beta Was this translation helpful? Give feedback.
-
|
After updating to 14.5 beta4, this doesn't happen as often as it did in 14.4.1. Rather, it happened a total of 2 times in a two day period like it did a long time ago, rather than many times in one day that can be easily reproduced. |
Beta Was this translation helpful? Give feedback.
-
|
After I updated to version 14.5beta4, it only rebooted twice. This never happened again after I updated to RC 14.5 (23F79). macbook air 13.3 m2 在我更新到14.5beta4版本后，只重启了两次。在我更新到RC 14.5(23F79)后，这种情况再没发生过。Macbook air 13.3 m2 |
Beta Was this translation helpful? Give feedback.
-
|
I also applied "Prevent automatic sleeping when the display is off" in this comment, and no forced reboot has occurred yet. please refer to this. 
|
Beta Was this translation helpful? Give feedback.
-
|
I use the same way to configure my m2 mini, but it doesn't works. |
Beta Was this translation helpful? Give feedback.
-
|
@joyivan I was experiencing a similar issue. It turns out one of my monitors had HDR enabled:
Disabling HDR on my monitor, in addition to enabling "Prevent automatic sleeping when the display is off," allowed me to successfully put my M2 Studio in sleep mode. If that doesn't work, try ensuring the refresh rate on your monitors are set to 60hz. |
Beta Was this translation helpful? Give feedback.
-
|
Just chiming in here. I've just bought a brand-new Mac Studio M2 Max with 96GB RAM. I installed BetterDisplay on day one (paid license), as my setup is:
I found I needed BetterDisplay to get the HiDPI working correctly. That first night, I had my first kernel panic. Since then I have had them every day. I Googled and found to associate them with sleep, so I tested a few things:
I got here today after Googling for: My current thinking is that I'm potentially close to a working combination... I think that when it sleeps, it's reverting to VRR due to that being active in some other configurations (I enabled VRR fairly early on, and if my iPad Sidecar disconnects, or my side monitors disconnect, it seems to fall back to a config that has VRR still enabled). So I think perhaps if I go through all possible setups and disable VRR on each, then it won't try to do VRR again when dealing with sleep. But that's a long shot, as the VRR is no by means definitely related to the while-I'm-working crashes. Interestingly, it still got a panic overnight one night even when I disabled sleep and also disabled the screens turning off... but it didn't panic last night so I thought I'd fixed it. The problem definitely seems related to sleep, but even more so to HDMI and turning an HDMI screen on and off. I found apparent initial success when keeping sleep enabled and carefully ensuring the HDMI display was turned back on again before the Mac was awoken. It seemed that the display not being present caused it to panic. This theory seemed supported by disabling "wake for network" seeming to help. I would try USB to HDMI instead of HDMI to HDMI, but the Apple specs say the Studio Max can only drive an 8K display through HDMI, unlike the Ultra, which can do it through USB C. TL;DR: If you are having this problem, and disabling sleep doesn't help, trying keeping sleep ENABLED, and DISABLE wake for network. Also, try disabling VRR. And, if you can, try something other than HDMI. This definitely doesn't appear to be anything to do with BetterDisplay, and I really hope Apple fix it soon - I've added my experience here in case what I've tried (and am still trying) helps anyone else, in case the other suggestions don't. |
Beta Was this translation helpful? Give feedback.
-
|
Success! Further to the above, I've not had a kernel panic for two days now! So - fingers crossed - I think I've identified the combination that works for me. Firstly, VRR - I had to disable Variable Rate Refresh, and ensure that it was disabled on all possible combinations of displays. This is important to ensure that VRR is not attempted at any point when returning from sleep. Secondly, sleep - it's important that it IS allowed to go to sleep, because if it stays awake then it panics when it loses a display. Thirdly, waking - it's important to DISABLE "wake for network", so that it has no opportunity to discover a display is gone. The above, combined with carefully ensuring to turn my HDMI display on before the Mac each time I wake it up, has so far been successful in resolving both the sleep-related panics and the random garbled-display panics too. Suffice to say there are some serious bugs in the Apple display drivers though! |
Beta Was this translation helpful? Give feedback.
-
|
To workaround, just use |
Beta Was this translation helpful? Give feedback.
-
|
After I updated to version 14.5beta4, it only rebooted twice. This never happened again after I updated to RC 14.5 (23F79). macbook air 13.3 m2 在我更新到14.5beta4版本后，只重启了两次。在我更新到RC 14.5(23F79)后，这种情况再没发生过。Macbook air 13.3 m2 |
Beta Was this translation helpful? Give feedback.
-
|
@ytgui the problem I'm experiencing (as I've described) is not due to the Mac sleeping. It's due to it not being able to handle the displays sleeping. As I mentioned, it still happens even with the Mac set to stay awake. @zhimaerfan unfortunately it is not cured by Sonoma 14.5 for me 😞 |
Beta Was this translation helpful? Give feedback.
-
|
Nice debugging work, I wish Apple would take it seriously. Anyhow, if you disable wake on network events, I can't SSH into the machine which I absolutely require. So people need to realize that this might not be optimal on a remote workstation. |
Beta Was this translation helpful? Give feedback.
-
|
@owah yeah it's absolutely not ideal. I have my screens on all the time to avoid the kernel panic issue. It sucks. BTW I had a support call with Apple and the chap who called me was very rude and hung up on me - basically he said if I don't like it, return it. Not impressed... 😮 |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, this fatal flaw is still there on MacOS 14.5. Actually, I begin to meet this kernel panic since MacOS 13.4, a workaround is to use To reproduce: (1) lock screen, (2) quick press ESC multiple times. The kernel implementation of Apple is actually incorrect and buggy, please show this reproducion to your closest Apple Store, and push Apple to fix. |
Beta Was this translation helpful? Give feedback.
-
That's what I did eventually: #2622 (reply in thread). |
Beta Was this translation helpful? Give feedback.
-
|
@muli I didn't see your post, so you don't have this problem anymore? |
Beta Was this translation helpful? Give feedback.
-
|
The issue was resolved for me. |
Beta Was this translation helpful? Give feedback.
-
|
The crash I posted above still happens for me with a USB-C to DisplayPort cable Interestingly enough, the colors are different (but everything else is the same - still static on half the screen etc) |
Beta Was this translation helpful? Give feedback.
-
|
Today is the second day without a kernel panic since I started using Type-C to DisplayPort. |
Beta Was this translation helpful? Give feedback.
-
|
These issues seem to be related: |
Beta Was this translation helpful? Give feedback.
-
|
Met the same issue this morning, and I have a BetterDisplay on my device(M2 Mac mini, MacOS 14.5), and I remember it autoupdate yesterday. Never met this before... And I uninstalled the app now... |
Beta Was this translation helpful? Give feedback.
-
|
Updating to the MacOS Sequoia Beta Preview For reference, I am using a MacBook Pro M3 Max 14in refurbished. The Beta was made public about an hour ago Wed, Jun 12 with the official release slated for June 18th |
Beta Was this translation helpful? Give feedback.
-
|
Yes, probably HDMI driver issue. You can find cheap Type-C to DP or HDMI adapters on AliExpress/eBay. I fixed my problem with this cheap adapter: https://www.aliexpress.com/item/1005005811478808.html?spm=a2g0o.order_list.order_list_main.23.730a1802n5lcrC. Also, you can find another solution for this in the posts above #2622 (reply in thread) |
Beta Was this translation helpful? Give feedback.
-
|
@corysus I get this issue regardless of using an external display. It always occurs when the computer goes to sleep. Keeping the computer from sleeping is the only fix I found that works (from #2622), but it severely drains the battery, and isn't the best long-term solution :( |
Beta Was this translation helpful? Give feedback.
-
I know, it's not perfect, but in my case, it was ok because I use a Mac Mini. But what's interesting is that I have an old MacBook Air M1 on version 14.4 and don't have any problems. I don't want to update it to the latest version because of this bug. But when I read all posts from above, it seems this bug only affects M2 and M3 chips and not M1. |
Beta Was this translation helpful? Give feedback.
-
|
@corysus in my case, using DP to USB-C didn't help :\ |
Beta Was this translation helpful? Give feedback.
-
|
@corysus unfortunately I cannot use USB-C because on the Mac Studio Max M2, the main HDMI port is the only one that can output 8K. I also have it connected to a display that only has HDMI inputs. So I am stuck 😂 |
Beta Was this translation helpful? Give feedback.
-
|
Not a BetterDisplay user but also have been experiencing this panic on 14.4x, 14.5, and now 15.0. |
Beta Was this translation helpful? Give feedback.
-
|
Yep - also not a BetterDisplay user, this crash happens when waking from sleep with absolutely nothing plugged in at all. I do have SM768 software installed for a dock so I can run an extra external monitor so wondering if that's related |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I have this too on my mac air m2 with 8gb ram. Not a betterdisplay user. This is causing me to lose work. panic(cpu 2 caller 0xfffffe002c0ed2a8): DCP PANIC - ASSERT!AppleDCPDPTXPowerController.cpp:538 No device added after powering on the rails. HPD=0 - dcpav(27) |
Beta Was this translation helpful? Give feedback.
-
|
FWIW i havent had this issue ever since upgrading to db2 However I can't be sure it wont happen again just yet, its been very sporadic |
Beta Was this translation helpful? Give feedback.
-
|
What is db2? |
Beta Was this translation helpful? Give feedback.
-
|
@ytgui macOS 15.0 developer beta 2 be aware that people had major issues with db1 (and db2?) before where a Spotlight bug would lead to SSD degrading very fast |
Beta Was this translation helpful? Give feedback.
-
|
Update: the issue is not resolved in 14.6 RC 
|
Beta Was this translation helpful? Give feedback.
-
|
So far to it seems to me the latest Sequoia betas solved a number of annoying issues, including the recurring inability to load display configurations properly (that bug was introduced with Sonoma). I did not experience any DCP issues either, multi-monitor accessibility zoom works reliably too (previously it tended to crash the Mac entirely when a video was playing). Moreover some other things (like the HDR bug with IINA) seems to be solved as well. Apple is improving things. |
Beta Was this translation helpful? Give feedback.
-
|
try downgrade to macos 12 (monterey) i did it and my macbook air M2 worked fine |
Beta Was this translation helpful? Give feedback.
-
|
14.6.0似乎就已经修复了无法睡眠的问题，因为我更新到此系统后，他提示我系统扩展需要重新授权，之后我再没出现过这种情况。现在我以更新到版本14.6.1 (23G93) |
Beta Was this translation helpful? Give feedback.
-
|
I just experienced this again for the first time in weeks, after updating to 15.1 DB2. The issue seems to still be present, although MUCH less frequent I hope that they didn't reintroduce it in DB2 as I didn't have the issue once ever since 15.0 DB3 (which was a while ago) |
Beta Was this translation helpful? Give feedback.
-
|
I have Macbook M2 air and the DCP panic error happened every time I put my Mac to sleep even though I don't have BetterDisplay. With the new Sonoma 14.6.1 its much less frequent but it happens from time to time. Anyone have a solution? I'm still on my warranty should I just replace my Mac or is it a universal problem with every Mac? |
Beta Was this translation helpful? Give feedback.
-
|
Did you try to use a Type-C adapter? After I switched from |
Beta Was this translation helpful? Give feedback.
-
|
@AdelShousha It is a universal problem, so you don't have a problem with your Mac. I agree about trying Type-C - I am stuck with HDMI and can't get around the issue, but anecdotally it does seem that using USB Type-C instead, if you can, may solve it. I tracked the issue down to something about the handling of the HDMI signals to do with sleep/wake of the display... |
Beta Was this translation helpful? Give feedback.
-
|
I've got the same issue recently after updating to Sequoia beta. No problems before. |
Beta Was this translation helpful? Give feedback.
-
|
Issue was fixed after updating to latest Developer Beta. I didn't notice there was a new one since I somehow managed to turn beta updates off. |
Beta Was this translation helpful? Give feedback.
and others
-
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
AppleT602XDPTXPortwith 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
AppleT602XDPTXPortduring 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
Beta Was this translation helpful? Give feedback.
All reactions