Bug 25166

Summary: radeon_drv causes mieq to overflow
Product: xorg Reporter: Arsen.Shnurkov <Arsen.Shnurkov>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED WORKSFORME QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: high CC: chalserogers, jeremyhu, thomas
Version: git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard: 2011BRB_Reviewed
i915 platform: i915 features:
Attachments:
Description Flags
/var/log/Xorg.0.log
none
/etc/X11/xorg.conf
none
/var/log/Xorg.0.log (new)
none
/etc/X11/xorg.conf (new) none

Description Arsen.Shnurkov 2009-11-18 10:54:24 UTC 
[mi] EQ overflowing. The server is probably stuck in an infinite loop.

Backtrace:
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]
Comment 1 Arsen.Shnurkov 2009-11-19 09:32:00 UTC 
Created attachment 31315 [details]
/var/log/Xorg.0.log
Comment 2 Arsen.Shnurkov 2009-11-19 09:33:34 UTC 
Created attachment 31316 [details]
/etc/X11/xorg.conf
Comment 3 Arsen.Shnurkov 2009-11-19 09:35:38 UTC 
This bug is reproduced again (with xf86-input-mouse now from git)
Comment 4 Arsen.Shnurkov 2009-11-19 10:29:18 UTC 
I add a few lines to config 

Section "Module"
...

#	Disable  "extmod"
	SubSection "extmod"
	    Option "omit xfree86-dga"
	EndSub

...
EndSection

now xserver just hangs after some mouse movement,
but doesn't write anything to /var/log/Xorg.0.log
Comment 5 Arsen.Shnurkov 2009-11-19 10:30:10 UTC 
Created attachment 31320 [details]
/var/log/Xorg.0.log (new)
Comment 6 Arsen.Shnurkov 2009-11-19 10:30:40 UTC 
Created attachment 31321 [details]
/etc/X11/xorg.conf (new)
Comment 7 Kai 2010-04-12 09:49:35 UTC 

*** This bug has been marked as a duplicate of bug 15473 ***
Comment 8 Christopher James Halse Rogers 2010-05-02 21:24:38 UTC 
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[1][2] 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?

[1] https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/572113
[2] https://bugs.launchpad.net/bugs/572192
Comment 9 Jeremy Huddleston Sequoia 2011-10-03 19:51:20 UTC 
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?
Comment 10 Jeremy Huddleston Sequoia 2011-10-15 16:47:54 UTC 
No response.  No usable information.  Closing.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.