Please attach xorg.conf and Xorg.0.log.

Does it work better with 2.2.0 if you set XAA in xorg.conf?

(In reply to comment #1)
> Please attach xorg.conf and Xorg.0.log.
> 
> Does it work better with 2.2.0 if you set XAA in xorg.conf?
> 

First I messed up first sentence: 2.2.0 doesnt work, but 2.1.1 works. I see 2.2.0 defaults to EXA. When I switched from EXA to XAA by  Option "AccelMethod" "XAA", everything was back to normal. I see you guys are writing new acceleration methods for Xorg, but I'd suggest to use XAA by default on older chipsets as i810, since none wont possibly be running compositing manager on such old piece of hardware anyway.

It seems that 2.2.0 driver crashes a lot when switched back to XAA instead of EXA. Especially when using vncviewer. 

log please. I wonder if it's 810 or 830.

Created attachment 13876 [details]
Xorg.0.log: Forced XAA, Intel video driver version 2.2.0, working properly

Created attachment 13877 [details]
xorg.conf: Forced XAA; Intel video driver 2.2.0; working properly

(==) Configured Mouse: YAxisMapping: buttons 4 and 5
(**) Configured Mouse: EmulateWheel, EmulateWheelButton: 2, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(**) Configured Mouse: Buttons: 9
(**) Configured Mouse: Sensitivity: 1
(II) evaluating device (Configured Mouse)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) evaluating device (Generic Keyboard)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(II) Configured Mouse: ps2EnableDataReporting: succeeded
AUDIT: Wed Jan 23 23:56:16 2008: 6705 X: client 23 rejected from local host (uid 0)
AUDIT: Thu Jan 24 00:12:00 2008: 6705 X: client 24 rejected from local host (uid 0)

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80bddee]
1: [0xb7f0d420]
2: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b1c827]
3: /usr/bin/X [0x80de315]
4: /usr/lib/xorg/modules/extensions//libextmod.so(XvdiPutImage+0x178) [0xb7b686d8]
5: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7b6b546]
6: /usr/bin/X [0x814b98e]
7: /usr/bin/X(Dispatch+0x2bf) [0x808c9cf]
8: /usr/bin/X(main+0x48b) [0x8073f3b]
9: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7cd6390]
10: /usr/bin/X(FontFileCompleteXLFD+0x209) [0x80732b1]

Fatal server error:
Caught signal 11.  Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch


VNC and XV cause such errors on 2.2.0 with XAA

So it's 830M, not 810.

Let's focus on EXA issue on this bug.

XAA will be obsolete soon? What can I do about EXA?

Using XAA (2.2.0) minimized mplayer (XV outpu) and restored again and then I got another crash:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80bddee]
1: [0xb7f7b420]
2: /lib/libc.so.6(vsnprintf+0xb4) [0xb7d8ec84]
3: /usr/bin/X(LogVWrite+0xb7) [0x81b8e47]
4: /usr/bin/X(LogVMessageVerb+0x99) [0x81b9379]
5: /usr/bin/X(xf86VDrvMsgVerb+0xda) [0x80cab6a]
6: /usr/bin/X(xf86DrvMsg+0x3d) [0x80cbb4d]
7: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b7fc81]
8: /usr/lib/xorg/modules/drivers//intel_drv.so(i830_free_memory+0x2e) [0xb7b7fd19]
9: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7b8590b]
10: /usr/bin/X [0x80dc9cc]
11: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7bd5dfa]
12: /usr/bin/X [0x80dcdf8]
13: /usr/lib/xorg/modules/extensions//libdbe.so [0xb7f6e865]
14: /usr/bin/X(compDestroyWindow+0xc5) [0x8101d65]
15: /usr/bin/X [0x807b3c1]
16: /usr/bin/X(DeleteWindow+0x158) [0x807b5b8]
17: /usr/bin/X(FreeResource+0x119) [0x8075ab9]
18: /usr/bin/X(ProcDestroyWindow+0x7f) [0x8088c3f]
19: /usr/bin/X [0x814ba0e]
20: /usr/bin/X(Dispatch+0x2bf) [0x808c9cf]
21: /usr/bin/X(main+0x48b) [0x8073f3b]
22: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7d44390]
23: /usr/bin/X(FontFileCompleteXLFD+0x209) [0x80732b1]

Lauri, Xv crash bug has been fixed in current git master. Could you try it?

For exa performance issue, we have seperate bug to track, and the work is under way in intel-batchbuffer branch.

I fixed a major performance issue with EXA on 830 machines a month or two ago.

Lauri, ping for response...

feedback timeout, so closing.