eero, chris: michel informs me that this is a known bug in
xserver-xorg-core 1.19.0 and that upgrading to at least 1.19.1 or
above fixes the problem. i'll need to wait until another unscheduled
reboot but will keep you informed, and will try out DRI2 as well as
DRI3.
l.
well it had to happen eventually (i forgot to keep the battery charged
up) so the opportunity to restart arrived - changed to DRI=3 and,
ta-daaa, problem's gone.
... or, at least, carrying out the previously 100%-repeatable test
(resize of a window under fvwm2) is no longer 100% repeatable. i'll
On Thu, Apr 6, 2017 at 11:36 AM, Eero Tamminen
wrote:
>> LIBGL_DEBUG=verbose glxgears
>> libGL: Using DRI2 for screen 0
>>
>> huh. so i _thought_ it was going to be DRI3. that's supposed to be
>> the default, isn't it?
>
>
> You need it enabled in Intel DDX build,
Hi,
On 06.04.2017 00:36, Luke Kenneth Casson Leighton wrote:
eero, apologies, the mesa-dev list's traffic is very high, i'll switch
over to digest, so please do cc me each time, to mitigate that.
OK.
there's a whole stack of people reporting this occurring, running the
full range of
ok installed libxcb1-dbg from debian, that gives more info, sorry i
can't install all the dbg symbols because of conflicting dependencies,
it seems that the packages are not fully sync'd at debian/testing.
starting to look like an x11 (xcb-related) bug, not mesa, what do you think?
l.
On Wed, Apr 5, 2017 at 10:43 PM, Chris Wilson wrote:
>> 303 frames in 5.0 seconds = 60.424 FPS
>> 212 frames in 11.7 seconds = 18.079 FPS
>
> Overshoots by 6s.
that's because, after the first 5 seconds, i did the fvwm2-based
"window resize" operation which triggered
On Wed, Apr 05, 2017 at 10:36:14PM +0100, Luke Kenneth Casson Leighton wrote:
> eero, apologies, the mesa-dev list's traffic is very high, i'll switch
> over to digest, so please do cc me each time, to mitigate that.
> ---
> crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
>
eero, apologies, the mesa-dev list's traffic is very high, i'll switch
over to digest, so please do cc me each time, to mitigate that.
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Wed, Apr 5, 2017 at 1:31 PM, Eero Tamminen wrote:
>
Hi,
On 04.04.2017 14:10, Luke Kenneth Casson Leighton wrote:
On Tue, Apr 4, 2017 at 11:04 AM, Eero Tamminen
wrote:
anyway, apologies: nobody whose applications are affected by this
really has a clue where the *actual* bug is so i am escalating it down
the chain of
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, Apr 4, 2017 at 12:10 PM, Luke Kenneth Casson Leighton
wrote:
>> Does DRI2 vs. DRI3 have any effect on it?
>
> hmm, good question. i'm running with "DRI" "true" (so don't know if
> it's 2 or 3),
On Tue, Apr 4, 2017 at 11:04 AM, Eero Tamminen
wrote:
>> anyway, apologies: nobody whose applications are affected by this
>> really has a clue where the *actual* bug is so i am escalating it down
>> the chain of library dependencies, making people aware. it could be
Hi,
On 04.04.2017 09:23, Luke Kenneth Casson Leighton wrote:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848895
there's a really strange and comprehensively cross-application
intermittent bug that's only occurring on opengl-based applications,
that's been introduced some time in the past
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848895
there's a really strange and comprehensively cross-application
intermittent bug that's only occurring on opengl-based applications,
that's been introduced some time in the past year. to be absolutely
honest nobody's even sure it's actually
13 matches
Mail list logo