From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 97025] flip queue failed: Device or resource busy Date: Wed, 07 Sep 2016 21:34:16 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1039257001==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B9A886EC40 for ; Wed, 7 Sep 2016 21:34:15 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1039257001== Content-Type: multipart/alternative; boundary="14732840550.CdCDAa.9508"; charset="UTF-8" --14732840550.CdCDAa.9508 Date: Wed, 7 Sep 2016 21:34:15 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D97025 --- Comment #21 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 be= fore flip [338324.489710] [drm:amdgpu_crtc_page_flip] *ERROR* failed to get vblank be= fore 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=20 [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=20 [338324.942] (WW) AMDGPU(0): flip queue failed: Device or resource busy=20 [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. --=20 You are receiving this mail because: You are the assignee for the bug.= --14732840550.CdCDAa.9508 Date: Wed, 7 Sep 2016 21:34:15 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 21 on bug 97025<= /a> from Bernd Steinhauser 
Ok, so I replaced the DP cable and reenabled the screen. Immed=
iately after that
I got these messages in dmesg. Note the time.
[338324.267684] [drm:amdgpu_crtc_page_flip] *ERROR* failed to get vblank be=
fore
flip
[338324.489710] [drm:amdgpu_crtc_page_flip] *ERROR* failed to get vblank be=
fore
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=20
[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=20
[338324.942] (WW) AMDGPU(0): flip queue failed: Device or resource busy=20
[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.
= --14732840550.CdCDAa.9508-- --===============1039257001== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1039257001==--