[mi] EQ overflowing. The server is probably stuck in an infinite loop.
0: X (xorg_backtrace+0x28) [0x471518]
1: X (mieqEnqueue+0x1ae) [0x45e5ee]
2: X (xf86PostMotionEventP+0xd8) [0x4842e8]
3: X (xf86PostMotionEvent+0xb1) [0x4844b1]
4: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7fab2fda5000+0x6bc3) [0x7fab2fdabbc3]
5: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7fab2fda5000+0x71a6) [0x7fab2fdac1a6]
6: /usr/lib64/xorg/modules/input/mouse_drv.so (0x7fab2fda5000+0x7643) [0x7fab2fdac643]
7: X (0x400000+0x7af07) [0x47af07]
8: X (0x400000+0x114d67) [0x514d67]
9: /lib/libpthread.so.0 (0x7fab32aae000+0xe930) [0x7fab32abc930]
10: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7fab303bc000+0x3e51a) [0x7fab303fa51a]
11: X (0x400000+0x142d06) [0x542d06]
12: X (0x400000+0x16cf0f) [0x56cf0f]
13: X (0x400000+0x145b3c) [0x545b3c]
14: X (miPointerUpdateSprite+0x156) [0x45c4e6]
15: X (0x400000+0x5c659) [0x45c659]
16: X (0x400000+0xcb29e) [0x4cb29e]
17: X (0x400000+0x34474) [0x434474]
18: X (0x400000+0x3935b) [0x43935b]
19: X (0x400000+0xdab73) [0x4dab73]
20: X (0x400000+0x100a2e) [0x500a2e]
21: X (mieqProcessDeviceEvent+0x1c6) [0x45e216]
22: X (mieqProcessInputEvents+0xdb) [0x45e30b]
23: X (ProcessInputEvents+0x9) [0x47b0e9]
24: X (0x400000+0x2a189) [0x42a189]
25: X (0x400000+0x24f55) [0x424f55]
26: /lib/libc.so.6 (__libc_start_main+0xe6) [0x7fab30d095c6]
27: X (0x400000+0x24b09) [0x424b09]
Created attachment 31315 [details]
Created attachment 31316 [details]
This bug is reproduced again (with xf86-input-mouse now from git)
I add a few lines to config
# Disable "extmod"
Option "omit xfree86-dga"
now xserver just hangs after some mouse movement,
but doesn't write anything to /var/log/Xorg.0.log
Created attachment 31320 [details]
Created attachment 31321 [details]
*** This bug has been marked as a duplicate of bug 15473 ***
What makes you think this is a duplicate? The EQ overflow is a generic symptom that occurs when the server is too busy to promptly handle an event.
Arsen.Shnurkov: I've got a couple of Ubuntu bugs with a similar-looking backtrace, featuring miPointerUpdateSprite, also using Xinerama to bind multiple cards together. They report the problems when the mouse pointer leaves the first screen - is this the same behaviour you're experiencing?
That backtrace is confusing to me. Can you get a better backtrace with some
symbol names (or symbolicate the one you have), so we can get a better
understanding of how you're getting to that point?
Does this reproduce with the 1.11.1 server?
No response. No usable information. Closing.