We attempted to run a burn-in test while connected to our MacBook Pro M4 Max, but this crashed about 10 minutes into testing. Can Action Star see if you are able to run a 2-hour burn-in on your own M4 Max host while charging the battery from below 5%, running six bus-powered drives (via ATTO/Black Magic/IOmeter), hitting the RJ45 port for 2.5Gbps (via JPerf), and streaming at least 4K60Hz video content to two displays? Please measure the outer temperature on the hottest part of the enclosure as well.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Created
We attempted to run a burn-in test while connected to our MacBook Pro M4 Max, but this crashed about 10 minutes into testing.
We tried to run a 2-hour burn-in on M4 Max host while charging the battery from below 5%, running six bus-powered drives (via ATTO/Black Magic/IOmeter), hitting the RJ45 port for 2.5Gbps (via JPerf), and streaming at least 4K60Hz video content to two display, however, M4 Max will crashed in 20 [minutes.](
https://www.example.com/)
Topic:
App & System Services
SubTopic:
Core OS
Problem description:
Connected to a Sharp 8TC60DWTX (8K) display, but unable to select 4K resolution
Setup Condition
Apple MacBook Pro 16-inch M4 Max
Sharp 8TC60DWTX (8K)
3.Duplicate Procedure
After connecting to 8K MNT and select 4K solution, it still display as 8K.
Vendor analysis:
8K60 shows no image; switching to 30 Hz works normally
→ After analysis, we found that the 8K60 timing output from the MacBook is incorrect.
The horizontal blanking (H-CBlanking) is too small to accommodate the audio data, so the RTD2191E does not output video to the monitor.
→ This issue does not occur on Windows platforms, confirming that this is a host-side issue.
Topic:
Community
SubTopic:
Apple Developers
Problem Description
When the Type-C port is connected to an ASUS ROG Swift OLED PG32UCDM monitor set to 3840×2160 @ 120 Hz, and the DP port is connected to a Samsung U28E590D monitor set to 3840×2160 @ 60 Hz, the DP port shows no response and no video output after the system wakes from sleep.
The DP monitor is not detected.
Reproduction Steps
Apple MacBook Pro (14-inch ,2024) connect the DP port to Samsung U28E590D and set the resolution to 3840×2160 @ 60 Hz.
Connect the Type-C port to ASUS ROG Swift OLED PG32UCDM and set the resolution to 3840×2160 @ 120 Hz.
Put the platform into sleep mode, then wake it up.
After wake-up, the DP port has no response and no video output.
Bug Description
When the Type-C port is connected to an ASUS ROG Swift OLED PG32UCDM at 3840×2160 @ 120 Hz, and the DP port is connected to a Samsung U28E590D at 3840×2160 @ 60 Hz, the DP port fails to output video after system sleep and wake-up, and the monitor is not detected.
Topic:
Community
SubTopic:
Apple Developers
Problem Description
DP extended display: When hot-plugging the downstream DP port, there is no audio output. (Occurs randomly)
2. Setup Condition
The product is connected to the following platform:
Platform: Apple MacBook Pro (16-inch, M4 Max, 2024)
The DP port is connected to the following monitor:
3. Reproduction Procedure
Step 1:
Connect the DP port to the extended display ASUS VP28U (4K 60Hz)
Step 2:
Connect the platform Apple MacBook Pro (16-inch, M4 Max, 2024)
Step 3:
Hot-plug the downstream DP port → no audio output (random occurrence)
Bug Description
DP extended display: When hot-plugging the downstream DP port, there is no audio output. (Random)
Affected Platform & Monitor Combination
Apple MacBook Pro (16-inch, M4 Max, 2024) & Samsung S32BG850NC (4K 240Hz)
Vendor Anaysis:
After analysis, we found that the issue also fails when the host is directly connected to the monitor (tested with two different USB-C to DP cables, both showing the same failure).
The RTS5490 only bypasses the audio and video signals, and no abnormal behavior was observed in the logs.
In addition, we found that different behaviors occur when switching the monitor OSD between DP 1.1 and DP 1.2:
OSD set to DP 1.1:
Direct connection: Pass
Connected through RTS5490: Pass
OSD set to DP 1.2:
Direct connection: Fail
Connected through RTS5490: Fail (same issue reported by Tongxing)
Testing with other monitors does no
Topic:
Community
SubTopic:
Apple Developers