<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - flip queue failed: Device or resource busy"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97025#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - flip queue failed: Device or resource busy"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97025">bug 97025</a>
from <span class="vcard"><a class="email" href="mailto:linux@bernd-steinhauser.de" title="Bernd Steinhauser <linux@bernd-steinhauser.de>"> <span class="fn">Bernd Steinhauser</span></a>
</span></b>
<pre>I noticed that I updated my kernel from 4.6.3 to 4.6.4 on 12th of July, so I
thought it could be related and had a little investigation.
Then I stumbled across this log, which I think was the first time this
happened. This is from journald:
Jul 09 08:59:43 orionis kernel: Linux version 4.6.3-amdgpu (root@orionis) (gcc
version 5.3.0 (GCC) ) #1 SMP PREEMPT Sat Jun 25 21:20:12 CEST 2016
[...]
Jul 09 17:04:08 orionis kernel: [drm:amdgpu_crtc_page_flip] *ERROR* failed to
get vblank before flip
Jul 09 17:04:09 orionis kernel: [drm:amdgpu_crtc_page_flip] *ERROR* failed to
get vblank before flip
No idea why in this case I can find some messages in the journal and in the
other cases not.
Anyway, this means that the origin is not the update mesa-12.0.0-rc4 -> final
and also not linux 4.6.3 -> 4.6.4.
Also unlikely 4.6.2 -> 4.6.3, since (as you can see above) this was built
approx. 2 weeks before and within that amount of time I would surely have
experienced the problem.
(Had it approx. 8 to 10 times during the last 2 weeks.)
Another message I found in a different log is:
Jul 24 00:45:17 orionis kernel: [drm:amdgpu_atombios_dp_link_train] *ERROR*
displayport link status failed
Jul 24 00:45:17 orionis kernel: [drm:amdgpu_atombios_dp_link_train] *ERROR*
clock recovery failed
Not sure if it is related.
With regards to what package started to bring this up, I'm now almost out of
ideas.
The only thing left would be kwin/plasma 5. The Update from Plasma 5.6.95 to
5.7.0 was performed on the 5th of July.
So, since kwin is what I use as a compositor (and Plasma 5 as a desktop), it
might be able that this triggers a bug?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>