From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97025] flip queue failed: Device or resource busy
Date: Wed, 31 Aug 2016 14:44:13 +0000 [thread overview]
Message-ID: <bug-97025-502-vpsK78pPC3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97025-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2137 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97025
--- Comment #15 from Bernd Steinhauser <linux@bernd-steinhauser.de> ---
I tried a few things, but wasn't really able to nail this down.
I downgraded to mesa 11.2 to see if that helps, but it does not.
However, today I had plasmashell freezing after unlocking the screen.
Only plasmashell froze, everything else kept working as expected.
I contacted Martin on IRC and he thought it might be related to this.
I'll attach the log from the conversation as well as the backtrace.
He might be right, because around the time when this happened, I get these
messages in dmesg:
[88765.431890] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[88765.436865] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[88765.441940] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[88765.446861] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[88765.451865] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[88765.456903] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[89579.510005] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[89579.514998] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[89579.520053] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[89579.525158] [drm:amdgpu_crtc_page_flip] *ERROR* failed to reserve new rbo
buffer before flip
[113833.139104] [drm:amdgpu_atombios_dp_link_train] *ERROR* displayport link
status failed
[113833.139117] [drm:amdgpu_atombios_dp_link_train] *ERROR* clock recovery
failed
[113833.361471] [drm:amdgpu_atombios_dp_link_train] *ERROR* displayport link
status failed
[113833.361484] [drm:amdgpu_atombios_dp_link_train] *ERROR* clock recovery
failed
[113836.962993] [drm:amdgpu_crtc_page_flip] *ERROR* failed to get vblank before
flip
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2917 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-08-31 14:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 15:15 [Bug 97025] flip queue failed: Device or resource busy bugzilla-daemon
2016-07-22 1:49 ` bugzilla-daemon
2016-07-22 4:45 ` bugzilla-daemon
2016-07-24 15:28 ` bugzilla-daemon
2016-07-26 3:42 ` bugzilla-daemon
2016-07-26 4:01 ` bugzilla-daemon
2016-07-26 4:02 ` bugzilla-daemon
2016-07-26 4:15 ` bugzilla-daemon
2016-07-26 18:06 ` bugzilla-daemon
2016-07-30 8:05 ` bugzilla-daemon
2016-08-09 18:36 ` bugzilla-daemon
2016-08-10 8:30 ` bugzilla-daemon
2016-08-12 17:27 ` bugzilla-daemon
2016-08-18 16:03 ` bugzilla-daemon
2016-08-21 15:37 ` bugzilla-daemon
2016-08-31 14:44 ` bugzilla-daemon [this message]
2016-08-31 14:44 ` bugzilla-daemon
2016-08-31 14:45 ` bugzilla-daemon
2016-09-01 3:44 ` bugzilla-daemon
2016-09-01 5:08 ` bugzilla-daemon
2016-09-06 4:50 ` bugzilla-daemon
2016-09-07 21:34 ` bugzilla-daemon
2016-09-07 21:34 ` bugzilla-daemon
2016-09-07 21:35 ` bugzilla-daemon
2017-01-12 18:46 ` bugzilla-daemon
2017-01-12 18:47 ` bugzilla-daemon
2018-04-17 15:30 ` bugzilla-daemon
2018-05-12 8:27 ` bugzilla-daemon
2018-05-14 10:01 ` bugzilla-daemon
2018-05-20 15:09 ` bugzilla-daemon
2018-08-13 15:31 ` bugzilla-daemon
2019-11-19 8:08 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-97025-502-vpsK78pPC3@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.