Created attachment 15889 [details]
xorg conf file
Start X on display :0, then start another X on display :1, if switch VT, X will crashed with below backtrace info:
0: X(xf86SigHandler+0x65) [0x476a25]
1: /lib64/libc.so.6 [0x3d10430620]
2: /opt/X11R7/lib64/xorg/modules/drivers//intel_drv.so [0x7f47934cc262]
3: /opt/X11R7/lib64/xorg/modules/drivers//intel_drv.so [0x7f47934ced1f]
4: /opt/X11R7/lib64/xorg/modules/drivers//intel_drv.so [0x7f47934d2c25]
5: X(AbortDDX+0x88) [0x45f2c8]
6: X(AbortServer+0x18) [0x4ead58]
7: X(FatalError+0xd5) [0x4eb335]
8: /opt/X11R7/lib64/xorg/modules/drivers//intel_drv.so(I830WaitLpRing+0x165) [0x7f47934c7325]
9: /opt/X11R7/lib64/xorg/modules/drivers//intel_drv.so(I830Sync+0x1a7) [0x7f47934c7707]
10: /opt/X11R7/lib64/xorg/modules/drivers//intel_drv.so [0x7f47934d2ad8]
11: /opt/X11R7/lib64/xorg/modules/drivers//intel_drv.so [0x7f47934d3598]
12: X [0x46b39e]
13: X [0x488c25]
14: /opt/X11R7/lib64/xorg/modules/extensions//libglx.so [0x7f4793b6ff8f]
15: X(xf86Wakeup+0x3c1) [0x477651]
16: X(WakeupHandler+0x55) [0x449435]
17: X(WaitForSomething+0x1bb) [0x4debab]
18: X(Dispatch+0x7b) [0x4458db]
19: X(main+0x495) [0x42d715]
20: /lib64/libc.so.6(__libc_start_main+0xf4) [0x3d1041daa4]
21: X(FontFileCompleteXLFD+0xa1) [0x42cab9]
FatalError re-entered, aborting
Caught signal 11. Server aborting
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0.0"
xinit: connection to X server lost.
Created attachment 15890 [details]
Same problem here: intel 965GM (22.214.171.1243) running debian unstable (64bits)
On my computer I use a first X server without dri (disabled from xorg.conf) and on a second server I enable dri, triplebuffer and pageflipping. xvmc is enabled on both.
When I fire up kdm on the second server X starts and little after crashes, eaving video useless. System is responsive but since I can't see anything I need to restart. Log and backtrace available. Totally repeatable up to now.
Sorry I meant intel driver version 2.2.903, but same problem on final 2.3.
Seems that there's some problem with enabling a 2nd server with dri acceleration. If I only fire the first one with dri disabled the problem doesn't reproduce. But as soon as I run a 2nd one with dri enabled (even after having shutdown the first one) video starts to behave strangely.
For example, when I fire up the 2nd xserver with dri on, I then go to my text virtual terminal using vesa frame buffer where I see one strange detail. On black background you won't notice anything but if you run anything more colourful (e.g.: aptitude ) you will see like a slow and very fine pitched raster going from left to right and once it the right border it starts over from the next line. If you leave the screen like this, xserver will end up hanging with the detailed backtrace and screen will be unusable after some xserver reboot trials.
Hope this helps,
This is probably fixed in xf86-video-intel master branch. Please verify.
Author: Eric Anholt <firstname.lastname@example.org>
Date: Tue May 6 18:48:20 2008 -0700
Bug #15807: Fix use of the ring while VT-switched, hit by fast user
The fix for flushing at blockhandler with no DRI on 965 was broken and
try to flush the chip even when the driver wasn't in control of the VT.