Comment # 21
on bug 97025
from Bernd Steinhauser
Ok, so I replaced the DP cable and reenabled the screen. Immediately after that I got these messages in dmesg. Note the time. [338324.267684] [drm:amdgpu_crtc_page_flip] *ERROR* failed to get vblank before flip [338324.489710] [drm:amdgpu_crtc_page_flip] *ERROR* failed to get vblank before flip [338526.834794] [drm:amdgpu_atombios_dp_link_train] *ERROR* displayport link status failed [338526.834801] [drm:amdgpu_atombios_dp_link_train] *ERROR* clock recovery failed [338526.838652] [drm:amdgpu_atombios_dp_link_train] *ERROR* displayport link status failed [338526.838655] [drm:amdgpu_atombios_dp_link_train] *ERROR* clock recovery failed After that, no messages (related to the graphics stack) appeared in dmesg so far. However, the X server log is now spammed with messages every few seconds: [338324.859] (WW) AMDGPU(0): flip queue failed: Invalid argument [338324.859] (WW) AMDGPU(0): Page flip failed: Invalid argument [338324.859] (EE) AMDGPU(0): present flip failed [338324.940] (WW) AMDGPU(0): get vblank counter failed: Invalid argument [338324.942] (WW) AMDGPU(0): get vblank counter failed: Invalid argument [338324.942] (WW) AMDGPU(0): flip queue failed: Device or resource busy [338324.942] (WW) AMDGPU(0): Page flip failed: Device or resource busy This started right after activating the DP screen. I guess sooner or later that will result in the freeze that I'm seeing. (I'll upload both dmesg and Xorg.0.log.) So yeah, it seems like this a problem with the DP. Since I don't think that I have two broken DP cables, I guess the problem is somewhere else. If that would help, I can connect one of the other screens via DP and see if that makes a difference.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
