The failure is only seen when a second reset is issued to the core while a previous reset sequence is underway.
The reset sequence is started automatically after configuration, so this could happen if the main core reset is toggled shortly after the device is configured.
This issue has been resolved in the DisplayPort v4.2 Rev. 2 and later.
More details on this issue can be found in (Xilinx Answer 60489).