From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100289] 'flip queue failed in radeon_scanout_flip: Invalid argument' error and small frame buffer allocated on turning off and on new monitor
Date: Mon, 20 Mar 2017 17:59:43 +0000 [thread overview]
Message-ID: <bug-100289-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2862 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100289
Bug ID: 100289
Summary: 'flip queue failed in radeon_scanout_flip: Invalid
argument' error and small frame buffer allocated on
turning off and on new monitor
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: OmegaPhil@startmail.com
Created attachment 130326
--> https://bugs.freedesktop.org/attachment.cgi?id=130326&action=edit
Xorg log
I have just bought a 3rd monitor, successfully hooked up via Display Port to
the R9 290X (Tahiti XT) card and configured fine as 3 non-mirrored outputs in
XFCE4.
I found that when I turned it off for ~10 seconds or more, after turning it
back on all screens would go black and appear to reinialise. XFCE4 gets
confused and clones the primary monitor output to the new 3rd screen, fiddling
in the XFCE4 Display program fixes this (after the problem happens it seems to
put the primary and new monitor on top of each other...).
Looking into Xorg.0.log, when I turn the monitor off for less than 10 seconds,
I just get the following event:
===============================================================================
[ 512.737] (WW) RADEON(0): flip queue failed in radeon_scanout_flip: Invalid
argument
===============================================================================
Being off for 10 seconds or more results in:
===============================================================================
[ 1891.671] (II) RADEON(0): Allocate new frame buffer 3840x1200 stride 3840
[ 1891.677] (WW) RADEON(0): flip queue failed in radeon_scanout_flip: Device
or resource busy
[ 1891.678] (WW) RADEON(0): flip queue failed in radeon_scanout_flip: Device
or resource busy
===============================================================================
It now makes sense why monitor output appears to be mirrored (only 2 unique
outputs) - 3840 is 1920*2. When I fix the configuration with XFCE4, the correct
frame buffer is set up:
===============================================================================
[ 2001.120] (II) RADEON(0): Allocate new frame buffer 5760x1200 stride 5760
===============================================================================
I have attached the X log.
I'm currently running Devuan Testing (based off Debian Testing)
uname -a: Linux omega1 4.9.0-2-amd64 #1 SMP Debian 4.9.13-1 (2017-02-27) x86_64
GNU/Linux
X: 1.19.2-1
radeon: 7.8.0
Thanks for any help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4309 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:[~2017-03-20 17:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 17:59 bugzilla-daemon [this message]
2017-03-22 9:19 ` [Bug 100289] 'flip queue failed in radeon_scanout_flip: Invalid argument' error and small frame buffer allocated on turning off and on new monitor bugzilla-daemon
2017-03-22 9:30 ` bugzilla-daemon
2017-03-22 19:46 ` bugzilla-daemon
2017-03-23 9:30 ` bugzilla-daemon
2017-03-23 15:49 ` bugzilla-daemon
2017-03-23 19:45 ` bugzilla-daemon
2017-03-23 19:47 ` bugzilla-daemon
2017-03-24 18:58 ` bugzilla-daemon
2017-04-19 6:34 ` bugzilla-daemon
2017-06-26 19:39 ` bugzilla-daemon
2017-06-26 20:13 ` bugzilla-daemon
2017-06-27 16:19 ` bugzilla-daemon
2017-07-21 19:39 ` bugzilla-daemon
2017-07-22 14:24 ` bugzilla-daemon
2018-02-04 18:24 ` bugzilla-daemon
2018-02-04 18:58 ` bugzilla-daemon
2018-03-09 17:26 ` bugzilla-daemon
2018-03-09 17:35 ` bugzilla-daemon
2018-03-10 11:43 ` bugzilla-daemon
2019-11-19 9:26 ` 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-100289-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.