I *did* see those messages when I was initially debugging the problem. This is from dmesg in one of the logs I made:
```
[ 20.525519] amdgpu 0000:07:00.0: [drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 20.570355] amdgpu 0000:07:00.0: [drm] *ERROR* mstb 00000000f21f0a30 port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 20.614750] amdgpu 0000:07:00.0: [drm] *ERROR* mstb 00000000f21f0a30 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
```
At the time, I tried MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and didn't see any change. The only thing that worked was switching the monitors from DisplayPort to HDMI on the dock.
I *did* see those messages when I was initially debugging the problem. This is from dmesg in one of the logs I made:
```
[ 20.525519] amdgpu 0000:07:00.0: [drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 20.570355] amdgpu 0000:07:00.0: [drm] *ERROR* mstb 00000000f21f0a30 port 2: DPCD read on addr 0x4b0 for 1 bytes NAKed
[ 20.614750] amdgpu 0000:07:00.0: [drm] *ERROR* mstb 00000000f21f0a30 port 3: DPCD read on addr 0x4b0 for 1 bytes NAKed
```
At the time, I tried MUTTER_ DEBUG_ENABLE_ ATOMIC_ KMS=0 and didn't see any change. The only thing that worked was switching the monitors from DisplayPort to HDMI on the dock.