From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97025] flip queue failed: Device or resource busy
Date: Thu, 21 Jul 2016 15:15:26 +0000 [thread overview]
Message-ID: <bug-97025-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2420 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97025
Bug ID: 97025
Summary: flip queue failed: Device or resource busy
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: linux@bernd-steinhauser.de
Since last week I have random freezes with the amdgpu driver (running on
Kaveri).
Once the issue occurs the display freezes. It's not fixable by switch to VT2
and back.
In Xorg.0.log I can find multiple times:
[ 92357.021] (WW) AMDGPU(0): flip queue failed: Device or resource busy
[ 92357.021] (WW) AMDGPU(0): Page flip failed: Device or resource busy
[ 92357.021] (EE) AMDGPU(0): present flip failed
No related messages in the journal or dmesg afaics.
It does not seem to be related to a specific event (like a video playing), but
just happens out of nowhere.
I didn't find a way to reproduce it specifically.
Possibly related packages that I built in that time:
* dev-lang/llvm-scm::arbor 2016-06-11 07:42:19 UTC
* dev-lang/llvm-scm::arbor 2016-06-19 07:29:42 UTC
* x11-dri/mesa-12.0.0-rc4::x11 2016-06-21 21:40:48 UTC
* dev-lang/llvm-scm::arbor 2016-07-02 11:57:34 UTC
* dev-lang/clang-scm::arbor 2016-07-02 12:43:00 UTC
* dev-lang/llvm-3.8.0-r1::arbor 2016-07-12 20:04:14 UTC
* dev-lang/clang-3.8.0::arbor 2016-07-12 20:48:27 UTC
* x11-dri/mesa-12.0.0::x11 2016-07-13 04:42:47 UTC
* x11-dri/mesa-12.0.1::x11 2016-07-17 14:25:44 UTC
* x11-server/xorg-server-1.18.4::x11 2016-07-20 16:06:18 UTC
I couldn't get mesa 12 to built with llvm-scm anymore, so I downgraded.
Still, I doubt it's related.
It's hard to be certain about this, but it could have been a regressing coming
with mesa 12 and possibly mesa-12.0.0.
I'm pretty sure I haven't seen the freeze before 12.0.0 final, but it's hard to
be certain about this with an issue so random.
In case it matters, my xorg settings are:
Section "Device"
Identifier "AMDGPU"
Driver "amdgpu"
Option "TearFree" "Off"
Option "EnablePageFlip" "On"
Option "DRI" "3"
EndSection
IIRC, this is now standard, so nothing special here.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3800 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 reply other threads:[~2016-07-21 15:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 15:15 bugzilla-daemon [this message]
2016-07-22 1:49 ` [Bug 97025] flip queue failed: Device or resource busy 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
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@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.