From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 176311] New: Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip
Date: Tue, 04 Oct 2016 19:42:47 +0000 [thread overview]
Message-ID: <bug-176311-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=176311
Bug ID: 176311
Summary: Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed
to get vblank before flip
Product: Drivers
Version: 2.5
Kernel Version: 4.7.5-200.fc24.x86_64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: vedran@miletic.net
Regression: No
As said in bug 176301, I have a Fiji card
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Fiji
[Radeon R9 FURY / NANO Series] (rev ca)
with two LG DisplayPort 27" 4K monitors. Locking screen while GNOME is running
on X makes both monitors go to sleep, all fine. Upon moving a mouse or pressing
a key, only one of them will wake up, and always the same one. Dmesg shows:
[drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR* failed to get vblank before flip
The other monitor will wake up if one switches to a console (e.g. Ctrl+Alt+F3)
and back or one powers any of the monitors off and back on.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-10-04 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 19:42 bugzilla-daemon [this message]
2016-10-04 20:08 ` [Bug 176311] Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip bugzilla-daemon
2016-10-25 15:24 ` bugzilla-daemon
2016-10-25 15:26 ` bugzilla-daemon
2016-10-25 15:26 ` bugzilla-daemon
2016-10-26 8:09 ` bugzilla-daemon
2016-11-02 16:53 ` bugzilla-daemon
2016-11-02 17:19 ` bugzilla-daemon
2018-04-17 15:24 ` bugzilla-daemon
2025-05-29 12:58 ` 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-176311-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).