Server frozen

[Richard Schwarting]

I wonder if it's related to this Fedora 11 bug.
https://bugzilla.redhat.com/show_bug.cgi?id=489907

On Fri, Jun 12, 2009 at 05:08, Magnus Kessler<Magnus.Kessler at gmx.net> wrote:
> With git HEAD of xserver, xf86-video-intel, mesa, libdrm, and the input
> drivers the X server does not seem to come back once the screen saver in KDE
> has kicked in and DPMS has turned off the display. This happens on both a
> laptop with the G45 and a desktop with the 965G graphic chips. The desktop
> environment is KDE-4.2.4. Both machines run the 2.6.30 kernel, but I had these
> errors under 2.6.29.4 as well recently, where the server would suddenly freeze
> with just the mouse pointer being reactive when using a 3D application
> (including kwin compositing manager). It is possible to log into the machine
> via ssh, but the server cannot be killed succesfully. Only a reboot brings the
> display back.
>
> The end of the Xorg log shows this error:
>
> [mi] EQ overflowing. The server is probably stuck in an infinite loop.
>
> Backtrace:
> 0: /usr/bin/X(xorg_backtrace+0x28) [0x46e648]
> 1: /usr/bin/X(mieqEnqueue+0x1e4) [0x45daf4]
> 2: /usr/bin/X(xf86PostMotionEventP+0xd8) [0x471a58]
> 3: /usr/bin/X(xf86PostMotionEvent+0xa9) [0x471c19]
> 4: /usr/lib64/xorg/modules/input/synaptics_drv.so [0x7f5d127bb85e]
> 5: /usr/lib64/xorg/modules/input/synaptics_drv.so [0x7f5d127bdb58]
> 6: /usr/bin/X [0x47b587]
> 7: /usr/bin/X [0x5071ea]
> 8: /lib/libpthread.so.0 [0x7f5d173e6600]
> 9: /lib/libc.so.6(ioctl+0x7) [0x7f5d15111607]
> 10: /usr/lib/libdrm_intel.so.1(drm_intel_gem_bo_start_gtt_access+0x4d)
> [0x7f5d134c97dd]
> 11: /usr/lib64/dri/i965_dri.so(intelFinish+0x56) [0x7f5d12dd0226]
> 12: /usr/lib64/xorg/modules/extensions/libglx.so [0x7f5d141c160d]
> 13: /usr/lib64/xorg/modules/extensions/libglx.so [0x7f5d141c5aee]
> 14: /usr/bin/X [0x455bc4]
> 15: /usr/bin/X [0x425d65]
> 16: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f5d15069a0d]
> 17: /usr/bin/X [0x4258f9]
>
> The problem first appeared for me after the Xi2 code landed in the server. Has
> somebody else observed this bug? Which component is most likely to cause this?
> The intel driver, mesa or the server?
>
> Many thanks for any pointers.
>
> Magnus
>
>
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>