From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99330] Severe flickering with Fiji on Wayland
Date: Wed, 11 Jan 2017 09:49:23 +0000 [thread overview]
Message-ID: <bug-99330-502-aEkdINRih1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99330-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 796 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #7 from Michel Dänzer <michel@daenzer.net> ---
Please attach the dmesg output, preferably captured after the problem occurred.
(In reply to Vedran Miletić from comment #6)
> Jan 10 17:44:30 localhost.localdomain gnome-shell[22110]: Failed to flip:
> Invalid argument
>
> I also got the following in dmesg, but it's likely unrelated as I get it
> with Xorg as well:
>
> [Tue Jan 10 17:44:29 2017] [drm:amdgpu_crtc_page_flip [amdgpu]] *ERROR*
> failed to get vblank before flip
It might be related. There might be similar messages about the page flip ioctl
failing in the Xorg log file, Xorg might just be more resilient against it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1647 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:[~2017-01-11 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 14:59 [Bug 99330] Severe flickering with Fiji on Wayland bugzilla-daemon
2017-01-09 15:53 ` bugzilla-daemon
2017-01-09 17:33 ` bugzilla-daemon
2017-01-09 20:05 ` bugzilla-daemon
2017-01-09 21:12 ` bugzilla-daemon
2017-01-10 15:27 ` bugzilla-daemon
2017-01-10 16:46 ` bugzilla-daemon
2017-01-11 9:49 ` bugzilla-daemon [this message]
2017-01-16 17:42 ` 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-99330-502-aEkdINRih1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox