Hans de Goede writes:
> Judging from the amount of people filing bugs in Fedora's
> bugzilla about this, quite a few people are hitting this, but
> so far no one from the RH graphics team has been able to
> reproduce :|
I may have found a possible route to this bug and have
Olivier Fourdan writes:
>> FlushAllOutput() in /usr/src/debug/xorg-server-20160929/os/io.c:612
>> Dispatch() in /usr/src/debug/xorg-server-20160929/dix/dispatch.c:3491
>> dix_main() in /usr/src/debug/xorg-server-20160929/dix/main.c:296
I have a theory about how this
I think it is possible that output could get queued to a client during
CloseDownClient. After it is removed from the pending queue, active
grabs are released, the client is awoken if sleeping and any work
queue entries related to the client are processed.
To fix this, move the call removing it
On Wed, Aug 31, 2016 at 9:11 AM, Nikhil Mahale wrote:
>>
>> OTOH this may indeed be a server bug, but your fix is not the right
>> one, I wonder why we are doing a RRSetScreenSize for slave GPU-s at
>> all. Since we already check that the Screen is big enough in
>>
On Wed, 2016-11-02 at 17:18 +0200, Timo Aaltonen wrote:
> Import changes from these mesa commits:
> 85ea8deb26da420 i965: Removing PCI IDs that are no longer listed as Kabylake.
> bdff2e554735ed9 i956: Add more Kabylake PCI IDs.
> f1fa8b4a1ca73fa i965/bxt: Add 2x6 variant
> d1ab544bb883d04
This code is using GetImage to accumulate a logical view of the window
image (since the windows will be clipped to their containing screen),
and then PutImage to load that back into the pixmap. What it wasn't
doing was constructing a region for the obscured areas of the window and
emitting
On Wednesday, November 2, 2016, Eric Anholt wrote:
> Adam Jackson > writes:
>
> > Regeneration is fast enough these days, we can skip this. This
> > eliminates about 40 minutes of wall time from a full xts run.
>
> If not sleeping is a problem, we
Adam Jackson writes:
> Regeneration is fast enough these days, we can skip this. This
> eliminates about 40 minutes of wall time from a full xts run.
If not sleeping is a problem, we should figure out a way to make
regeneration not racy. Sleeps aren't OK.
Reviewed-by: Eric
Hi,
On 02-11-16 16:50, Keith Packard wrote:
Michel Dänzer writes:
Somebody still needs to come up with a fix for the FlushAllOutput
crashes, right?
That would sure be nice; can anyone reproduce them at all?
Judging from the amount of people filing bugs in Fedora's
Michel Dänzer writes:
> Somebody still needs to come up with a fix for the FlushAllOutput
> crashes, right?
That would sure be nice; can anyone reproduce them at all?
--
-keith
signature.asc
Description: PGP signature
___
Import changes from these mesa commits:
85ea8deb26da420 i965: Removing PCI IDs that are no longer listed as Kabylake.
bdff2e554735ed9 i956: Add more Kabylake PCI IDs.
f1fa8b4a1ca73fa i965/bxt: Add 2x6 variant
d1ab544bb883d04 i965/chv: Display proper branding
20e8ee36627f874 i965/skl: Update
Am 02.11.2016 15:09, schrieb Adam Jackson:
> Regeneration is fast enough these days, we can skip this. This
> eliminates about 40 minutes of wall time from a full xts run.
>
> Signed-off-by: Adam Jackson
> ---
> xts5/src/libXtTest/avs_init.c | 7 ---
> 1 file changed, 7
Regeneration is fast enough these days, we can skip this. This
eliminates about 40 minutes of wall time from a full xts run.
Signed-off-by: Adam Jackson
---
xts5/src/libXtTest/avs_init.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/xts5/src/libXtTest/avs_init.c
On Wed, 2016-11-02 at 13:00 +, Emil Velikov wrote:
> Gist:
> The kernel does not expose separate file for the revision field, yet
> there's a [freshly sent] kernel patch to address that.
> Thus libpciaccess's reads through the config file and wakes up the
> device, which we want to avoid
[Adjusting CC list - moving to xorg-devel + dropping the libdrm users]
Gist:
The kernel does not expose separate file for the revision field, yet
there's a [freshly sent] kernel patch to address that.
Thus libpciaccess's reads through the config file and wakes up the
device, which we want to
On 02/11/16 01:05 PM, Keith Packard wrote:
>
> I don't know of any more patches that need to hit the code before we
> ship.
Somebody still needs to come up with a fix for the FlushAllOutput
crashes, right?
--
Earthling Michel Dänzer | http://www.amd.com
Libre
16 matches
Mail list logo