Not solved!

Michel Dänzer michel at
Fri Feb 6 09:35:51 PST 2009

On Thu, 2009-02-05 at 18:43 +0000, Nix wrote:
> On 5 Feb 2009, Michel Dänzer verbalised:
> > EXA offscreen memory is probably fragmented. I have a defragmentation
> > patch that I hope to clean up and push one of these days.
> A kludgy approach would be to do whatever gets done on VT switch (dump
> and repopulate the entirety of EXA offscreen memory?) whenever a
> significant fraction of allocation requests start to fail due to
> fragmentation.

Yeah, but I implemented something fancier. :) Care to try the attached

> It certainly doesn't log anything about this case. Right now the only
> EXA-related message I see in the logs after X startup is a single lonely
> exaCopyDirty: Pending damage region empty!
> which is presumably unrelated.

Right, I pushed a change to guard this by a debugging #define.

P.S. Moving to the xorg-devel list.

Earthling Michel Dänzer           |      
Libre software enthusiast         |          Debian, X and DRI developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: exa-defragment.diff
Type: text/x-patch
Size: 12798 bytes
Desc: not available
URL: <>

More information about the xorg mailing list