A fix for bug 1388490 now exists, so if this one becomes reproducible
then it might be fixed too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buffered compositing perfor
Hmm it seems this bug refuses to expire.
Can't be reproduced any more and only happens using a rendering approach
we have never used.
** No longer affects: mesa
** Changed in: mir
Status: Incomplete => New
** Changed in: mir
Status: New => Incomplete
** Changed in: mir
Sta
Two years later... Upstream has now offered some thoughts. Although I
don't think this bug is around any more(?)
https://bugs.freedesktop.org/show_bug.cgi?id=86366
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.laun
** Changed in: mir
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buffered compositing performance is sometimes ver
This might help:
http://lists.freedesktop.org/archives/intel-gfx/2015-April/063988.html
Although this bug seems to be gone since the end of 2014... hopefully.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launch
Incomplete. It appears we're both experiencing just bug 1447896 now. Bug
1377872 hasn't definitely been seen since late-2014.
** Changed in: mir
Status: Confirmed => Incomplete
** Changed in: mesa (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification becau
Sounds like kdub is experiencing bug 1447896 more than this one too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buffered compositing performance is sometimes very poor
Just for clarity's sake, INTEL_DEBUG=sync doesn't seem to make any
difference, but nbuffers=3 seems to avert the problem
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buff
I see the same symptoms on my intel system. The easiest way to reproduce
the systems for me is to have a host (in bypass mode, with nbuffers=2),
a nested server (with nbuffers = 2 or nbuffers = 3), and then run
eglplasma connected to the nested server.
If egltriangle is running, the host server co
Scratch that. What I found yesterday seems to be a different bug. Logged
in --> bug 1447896
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buffered compositing performance
Good-bad news!
I can reproduce this bug again today, after updating my vivid desktop
for the first time in two weeks. Seems some kernel/Mesa change has made
it re-appear. And the INTEL_DEBUG workaround no longer works. But
--nbuffers=3 does.
--
You received this bug notification because you are
** Description changed:
- Double-buffered compositing performance is poor.
+ Double-buffered compositing performance is sometimes artificially poor
+ on some intel systems. When this happens the frame rate seen is halved -
+ about 30 FPS. However at the same time, Mir is observed to use very
+ lit
Digging in the kernel, there's some suspicious logic in the i915 driver
(used by Mesa i965 etc):
/* Throttle our rendering by waiting until the ring has completed our requests
* emitted over 20 msec ago.
*
* Note that if we were to use the current jiffies each time around the loop,
* we wouldn
Sounds like there is some related movement happening:
https://nouveau.freedesktop.org/patch/40616/
http://patchwork.freedesktop.org/patch/44172/
Although it kind of sounds like the problem might get worse rather than
better. Not sure.
--
You received this bug notification because you are a membe
I wonder if calling gbm_surface_lock_front_buffer() a bit earlier would
keep the system sufficiently awake to avoid this?...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-
Confirmed by duplicate. kdub is seeing similar.
** Changed in: mir
Status: Incomplete => Confirmed
** Changed in: mesa (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https:
Can't reproduce this any more.
Mir now has double buffered clients as well as double buffered
compositing so the bug should be more visible, not less. Although vivid
also just got updated to Mesa 10.5 which is where I would expect a fix
to come from. Seems to be fixed, probably by recent Mesa/kern
Hmm, I wonder if this is another case of the i915 driver not keeping the kernel
awake enough? Although I found this bug on a reasonably powerful i7, I recently
also found an intel sleep states bug that affects low-end chips:
https://bugs.launchpad.net/mir/+bug/1388490
Maybe these two bugs are in
** Branch unlinked: lp:~vanvugt/mir/mesa-double
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buffered compositing performance is very poor (30 FPS) on intel
To manage no
Not work in progress any more.
I think the proposed branch is the final one but we need the more
significant performance bug 1395421 fixed first.
** Changed in: mir
Status: In Progress => Triaged
** Changed in: mir
Milestone: 0.10.0 => None
--
You received this bug notification beca
** Summary changed:
- Double-buffered compositing performance is very poor (30 FPS)
+ Double-buffered compositing performance is very poor (30 FPS) on intel
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.n
** Changed in: mir
Milestone: 0.9.0 => 0.10.0
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buffered compositing performance is very poor (30 FPS)
To manage notificat
** Branch linked: lp:~vanvugt/mir/mesa-double
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
Double-buffered compositing performance is very poor (30 FPS)
To manage notifications
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=86366.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
As I've tracked the issue into the intel driver code and the workarounds
for test case A don't help B, we might have to split this bug in two.
** Description changed:
Double-buffered compositing performance is poor.
Fortunately we don't use double-buffering in our default compositor
(mos
25 matches
Mail list logo
