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: Tue, 26 Jul 2016 18:06:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1134004835==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id BFF9B6E2E7 for ; Tue, 26 Jul 2016 18:06:21 +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 --===============1134004835== Content-Type: multipart/alternative; boundary="14695563810.5e9bBcDf.8756"; charset="UTF-8" --14695563810.5e9bBcDf.8756 Date: Tue, 26 Jul 2016 18:06:21 +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 #8 from Bernd Steinhauser --- I noticed that those two lines coincident with a certain event I can trigge= r: Switching the DP-0 display off (an Eizo EV2455). This leads to a disconnect of the DP connection and that leads (somehow) to= the quoted messages about the failed vblank. (I'm not sure if the disconnect is actually a bug in the kernel (as it's a DP1.2 display) or if it's my hardware/mainboard/gpu too old.) However, this disconnect does not lead straight to the freeze. And so far I haven't seen the bug directly after a DP disconnect, but just = at some random point. --=20 You are receiving this mail because: You are the assignee for the bug.= --14695563810.5e9bBcDf.8756 Date: Tue, 26 Jul 2016 18:06:21 +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

Comment= # 8 on bug 97025<= /a> from Bernd Steinhauser 
I noticed that those two lines coincident with a certain event=
 I can trigger:
Switching the DP-0 display off (an Eizo EV2455).
This leads to a disconnect of the DP connection and that leads (somehow) to=
 the
quoted messages about the failed vblank.
(I'm not sure if the disconnect is actually a bug in the kernel (as it's a
DP1.2 display) or if it's my hardware/mainboard/gpu too old.)

However, this disconnect does not lead straight to the freeze.
And so far I haven't seen the bug directly after a DP disconnect, but just =
at
some random point.

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