Bug 575575 - X hanged with message: EQ overflowing.
Summary: X hanged with message: EQ overflowing.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-21 15:17 UTC by Juha Heljoranta
Modified: 2010-11-01 20:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-01 19:34:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
output from sysrq-[dlmpqtw] (19.23 KB, application/x-gzip)
2010-03-21 15:17 UTC, Juha Heljoranta
no flags Details
Scott's Xorg.0.log file (143.68 KB, text/plain)
2010-06-01 07:30 UTC, Scott Smedley
no flags Details

Description Juha Heljoranta 2010-03-21 15:17:37 UTC
Created attachment 401564 [details]
output from sysrq-[dlmpqtw]

Description of problem:
Xorg hanged while browsing the internet. No apparent reason. Gui freezed except the mouse cursor moved. Keyboard went dead.

System seemed to be alive except the gui (there was some disk and network activity). Not even ctrl-alt-fX worked.

MagicSysRq worked.

Version-Release number of selected component (if applicable):
kernel-2.6.32.9-70.fc12.x86_64
xorg-x11-drv-intel-2.9.1-1.fc12.x86_64
xorg-x11-server-Xorg-1.7.5.902-1.fc12.x86_64

How reproducible:
N/A. Just happened by it self while browsing the internet.

Steps to Reproduce:
N/A
  
Actual results:
X hanged. Only two ways to reboot the system: MagicSysRq or power button.

Expected results:
No random gui freezing.

Additional info:
From /var/log/Xorg.0.log.old:

[mi] EQ overflowing. The server is probably stuck in an infinite loop.

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x49ee68]
1: /usr/bin/X (mieqEnqueue+0x1f4) [0x49e834]
2: /usr/bin/X (xf86PostMotionEventP+0xce) [0x47938e]
3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7ffef29b9000+0x516f) [0x7ffef29be16f]
4: /usr/bin/X (0x400000+0x6c247) [0x46c247]
5: /usr/bin/X (0x400000+0x117643) [0x517643]
6: /lib64/libpthread.so.0 (0x3a73200000+0xf0f0) [0x3a7320f0f0]
7: /usr/bin/X (0x400000+0x61f10) [0x461f10]
8: /lib64/libpthread.so.0 (0x3a73200000+0xf0f0) [0x3a7320f0f0]
9: /usr/lib64/libpixman-1.so.0 (0x3031000000+0x430a0) [0x30310430a0]
10: /usr/lib64/libpixman-1.so.0 (0x3031000000+0x432d8) [0x30310432d8]
11: /usr/lib64/libpixman-1.so.0 (pixman_blt+0x78) [0x303102f998]
12: /usr/lib64/xorg/modules/libfb.so (fbCopyNtoN+0x1bd) [0x7ffef349ca8d]
13: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7ffef3ee2000+0x5ae5a) [0x7ffef3f3ce5a]
14: /usr/bin/X (miCopyRegion+0x28d) [0x54632d]
15: /usr/bin/X (miDoCopy+0x44a) [0x54683a]
16: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7ffef3ee2000+0x5a6f0) [0x7ffef3f3c6f0]
17: /usr/bin/X (0x400000+0xd4908) [0x4d4908]
18: /usr/bin/X (0x400000+0x2b39c) [0x42b39c]
19: /usr/bin/X (0x400000+0x2c84c) [0x42c84c]
20: /usr/bin/X (0x400000+0x21e2a) [0x421e2a]
21: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3a72a1eb1d]
22: /usr/bin/X (0x400000+0x219e9) [0x4219e9]

Comment 1 Juha Heljoranta 2010-03-21 15:26:25 UTC
The graphics chip in question is:
00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 03)

Comment 2 Scott Smedley 2010-06-01 07:30:17 UTC
Created attachment 418509 [details]
Scott's Xorg.0.log file

Xorg server crash logfile.

Comment 3 Scott Smedley 2010-06-01 07:31:53 UTC
I am hitting this bug too.

I updated my system this morning, but X has crashed 3 times in the last ~5 hours.

I am able to ssh in remotely (after X crashes) indicating that the
kernel is working fine.

See "Scott's Xorg.log file" attachment.

Let me know if there's any way I can help diagnose this bug.

Scott. :)

Comment 4 Barbara 2010-06-02 23:22:26 UTC
Did you tried adding pcie_aspm=off to kernel parameters?

Comment 5 Eddie Lania 2010-08-14 17:00:29 UTC
Reproducible here with googleearth linux:

[ 24328.518] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 24328.519]
Backtrace:
[ 24328.566] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80ddfac]
[ 24328.566] 1: /usr/bin/Xorg (mieqEnqueue+0x1b7) [0x80d91b7]
[ 24328.567] 2: /usr/bin/Xorg (xf86PostMotionEventP+0xd2) [0x80b5692]
[ 24328.567] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x88c000+0x30a2) [0x88f0a2]
[ 24328.567] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x88c000+0x3349) [0x88f349]
[ 24328.567] 5: /usr/bin/Xorg (0x8048000+0x739e0) [0x80bb9e0]
[ 24328.567] 6: /usr/bin/Xorg (0x8048000+0x10fd04) [0x8157d04]
[ 24328.567] 7: (vdso) (__kernel_sigreturn+0x0) [0xac3400]
[ 24328.567] 8: (vdso) (__kernel_vsyscall+0x10) [0xac3424]
[ 24328.567] 9: /lib/libc.so.6 (ioctl+0x19) [0x1e50b9]
[ 24328.567] 10: /usr/lib/libdrm.so.2 (drmIoctl+0x2e) [0x736ea7e]
[ 24328.567] 11: /usr/lib/libdrm.so.2 (drmCommandWrite+0x3c) [0x736ee0c]
[ 24328.567] 12: /usr/lib/libdrm_nouveau.so.1 (0x5ba000+0x2a9a) [0x5bca9a]
[ 24328.567] 13: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xf1) [0x5bcc91]
[ 24328.568] 14: /usr/lib/libdrm_nouveau.so.1 (nouveau_bo_map+0x34) [0x5bcd64]
[ 24328.568] 15: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x8dd000+0x46ca) [0x8e16ca]
[ 24328.568] 16: /usr/lib/xorg/modules/libexa.so (0x4f3000+0x73cf) [0x4fa3cf]
[ 24328.568] 17: /usr/bin/Xorg (0x8048000+0xcb061) [0x8113061]
[ 24328.568] 18: /usr/bin/Xorg (0x8048000+0x4e2a5) [0x80962a5]
[ 24328.568] 19: /usr/bin/Xorg (0x8048000+0x50ab7) [0x8098ab7]
[ 24328.568] 20: /usr/bin/Xorg (0x8048000+0x1a595) [0x8062595]
[ 24328.568] 21: /lib/libc.so.6 (__libc_start_main+0xe6) [0x126cc6]
[ 24328.568] 22: /usr/bin/Xorg (0x8048000+0x1a181) [0x8062181]

Comment 6 Eddie Lania 2010-09-14 15:04:09 UTC
Just a note. This is not intel specific as show by my previous comment #5 where i tested it on a pc with a nvidia FX1500M video card.

Comment 7 Adam Jackson 2010-11-01 19:34:34 UTC
Bug conflation.  These two backtraces are utterly different.  Do not assume that bugs with the same symptom are the same problem.


Note You need to log in before you can comment on or make changes to this bug.