From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99330] Severe flickering with Fiji on Wayland
Date: Tue, 10 Jan 2017 15:27:09 +0000 [thread overview]
Message-ID: <bug-99330-502-Aj1zbHtHBz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99330-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 923 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #5 from Vedran Miletić <vedran@miletic.net> ---
(In reply to Ernst Sjöstrand from comment #3)
> I happen to have 2 4K monitors and a Fury as well actually.
>
> I actually couldn't run Wayland at all for some time, perhaps it was fixed
> by:
> mutter (3.22.2-3) unstable; urgency=medium
>
> [ Jeremy Bicha ]
> * Add git_flush_all_swap_notifies_on_idle.patch:
> - Add patch from 3.22 branch that fixes freezes with multiple monitors
> on Wayland
> landing in my Ubuntu repos.
>
That's also in Fedora as far as I can tell:
https://koji.fedoraproject.org/koji/buildinfo?buildID=823521
(In reply to Ernst Sjöstrand from comment #4)
> Does it work with an older mesa/llvm version for you?
Mesa 13 and LLVM 3.8 in stock Fedora doesn't help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1932 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-10 15:27 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 [this message]
2017-01-10 16:46 ` bugzilla-daemon
2017-01-11 9:49 ` bugzilla-daemon
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-Aj1zbHtHBz@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