Studio Display XDR - Slow to Wake

[jdelcorr]

Anybody else notice how the new XDR is much slower to wake than previous Studio Display? I use it on an M2 Max MacBook in clamshell.

 

[BBman]

I noticed this too, 2-3 sec delay with an mbp m5. Perhaps the TB4 on our computers is working a bit more to push 5K/120hz with dsc causing this delay?

Anyone with tb5 Mac also seeing this delay?

 

[djinn]

Maybe the DSC synch latency with TB4? Just a guess.

 

[jdelcorr]

I was also experiencing the dreaded "kernel panic." Just had it replaced at the Apple Store, fixed the issue. Check to see if yours also had that, perhaps it's a faulty chip.

Screen would go dark, with the other half displaying static. Forcing the computer to shut off.

 

[djinn]

I was also experiencing the dreaded "kernel panic." Just had it replaced at the Apple Store, fixed the issue. Check to see if yours also had that, perhaps it's a faulty chip.

Screen would go dark, with the other half displaying static. Forcing the computer to shut off.

Oh wow! That sucks. Did Apple give you grief or challenge you on the issue?

 

[jdelcorr]

Oh wow! That sucks. Did Apple give you grief or challenge you on the issue?

Not at all, they had one in stock at the store and gave it to me.

 

[PaulD-UK]

@jdelcorr "I was also experiencing the dreaded "kernel panic."
Screen would go dark, with the other half displaying static. Forcing the computer to shut off."

Apparently this is caused by a failure of the Mac and the monitor to correctly negotiate the DSC (compressed data rate) properly.
Later Macs, after the M2-/M3- have a reengineered, lower, DSC rate, so are less likely to behave like this.
TB5 Macs don't need to use DSC at all, so if the DSC handshake fails, then they can instantly recover unto the uncompressed state.

With M2 Pro/Max chips, a point of failure is that if the Mac's CPU is heavily loaded with opening a CPU/GPU intensive app at the moment the display handshake happens, then the negotiation can fail.

"...perhaps it's a faulty chip"
The Studio Display's firmware probably need a future update to make the display controller more stable.

 

[jdelcorr]

@jdelcorr "I was also experiencing the dreaded "kernel panic."
Screen would go dark, with the other half displaying static. Forcing the computer to shut off."

Apparently this is caused by a failure of the Mac and the monitor to correctly negotiate the DSC (compressed data rate) properly.
Later Macs, after the M2-/M3- have a reengineered, lower, DSC rate, so are less likely to behave like this.
TB5 Macs don't need to use DSC at all, so if the DSC handshake fails, then they can instantly recover unto the uncompressed state.

With M2 Pro/Mac chips, a point of failure is that if the Mac's CPU is heavily loaded with opening a CPU/GPU intensive app at the moment the display handshake happens, then the negotiation can fail.

"...perhaps it's a faulty chip"
The Studio Display's firmware probably need a future update to make the display controller more stable.

Thanks Paul. I can confirm I have the same issue with the second display I received. Hopefully they release an update soon.

 

[lukevu15]

Takes ~1 - 2s to me. M4 Max Studio.

 

[ascender]

I was also experiencing the dreaded "kernel panic." Just had it replaced at the Apple Store, fixed the issue. Check to see if yours also had that, perhaps it's a faulty chip.

Screen would go dark, with the other half displaying static. Forcing the computer to shut off.

I've only had that specific crash happen once since release day so I'm assuming it's a software thing rather than hardware fault. No harm in getting it swapped out though!