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: Sun, 20 May 2018 15:09:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1790875030==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id E977F6E248 for ; Sun, 20 May 2018 15:09:37 +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 --===============1790875030== Content-Type: multipart/alternative; boundary="15268289771.E009e2E.31687" Content-Transfer-Encoding: 7bit --15268289771.E009e2E.31687 Date: Sun, 20 May 2018 15:09:37 +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 #29 from Bernd Steinhauser --- (In reply to Michel D=C3=A4nzer from comment #28) > (In reply to Bernd Steinhauser from comment #27) > >=20 > > Although I'm not sure if it works as expected, since the display does s= till > > seem to disconnect when I turn the screen off. >=20 > AFAIK that's either a monitor or general DisplayPort issue. The drivers > can't prevent it but have to cope with it. Quite possible. I've seen such behaviour on Windows as well on some display= s. Don't really get it, it's very annoying if your windows are rearrange just because you turned off a display to save some power. Anyway back to topic: [595475.710884] [drm:amdgpu_atombios_dp_link_train] *ERROR* displayport link status failed [595475.710902] [drm:amdgpu_atombios_dp_link_train] *ERROR* clock recovery failed I do still get those messages sometimes, but at least I didn't experience a= ny lockups or freezes. --=20 You are receiving this mail because: You are the assignee for the bug.= --15268289771.E009e2E.31687 Date: Sun, 20 May 2018 15:09:37 +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 # 29 on bug 97025<= /a> from Bernd Steinhauser 
(In reply to Michel D=C3=A4nzer from comment #28)
> (In reply to Bernd Steinhauser from comment #27)
> >=20
> > Although I'm not sure if it works as expected, since the display =
does still
> > seem to disconnect when I turn the screen off.
>=20
> AFAIK that's either a monitor or general DisplayPort issue. The drivers
> can't prevent it but have to cope with it.

Quite possible. I've seen such behaviour on Windows as well on some display=
s.
Don't really get it, it's very annoying if your windows are rearrange just
because you turned off a display to save some power.

Anyway back to topic:
[595475.710884] [drm:amdgpu_atombios_dp_link_train] *ERROR* displayport link
status failed
[595475.710902] [drm:amdgpu_atombios_dp_link_train] *ERROR* clock recovery
failed

I do still get those messages sometimes, but at least I didn't experience a=
ny
lockups or freezes.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15268289771.E009e2E.31687-- --===============1790875030== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1790875030==--