Hide Forgot
Description of problem: Occasionally, the X server locks up in a way that only the mouse works but nothing else, no keyboard input, etc. and the system has to be hard-rebooted... This is not predictable, but usually happens, if it happens, when running Openoffice.org, although once it has happened in another application too. Version-Release number of selected component (if applicable): How reproducible: It is not really reproducible (even though I've tried several times) Steps to Reproduce: 1. 2. 3. Actual results: The result is a complete system lock-up, often triggered through a mouse drag event (e.g., figure in openoffice impress) or graphical select (e.g., region in openoffice calc). Expected results: No lock-up Additional info: From Xorg.0.log: [ 4496.580] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [ 4496.584] Backtrace: [ 4496.906] 0: /usr/bin/X (xorg_backtrace+0x2f) [0x4a142f] [ 4496.906] 1: /usr/bin/X (mieqEnqueue+0x1e9) [0x4a0949] [ 4496.906] 2: /usr/bin/X (xf86PostMotionEventM+0xa3) [0x47db33] [ 4496.906] 3: /usr/bin/X (xf86PostMotionEventP+0x52) [0x47dc52] [ 4496.906] 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f5857315000+0x4b1b) [0x7f5857319b1b] [ 4496.906] 5: /usr/bin/X (0x400000+0x6b588) [0x46b588] [ 4496.906] 6: /usr/bin/X (0x400000+0x119c90) [0x519c90] [ 4496.906] 7: /lib64/libpthread.so.0 (0x348c800000+0xeeb0) [0x348c80eeb0] [ 4496.906] 8: /lib64/libc.so.6 (ioctl+0x7) [0x348c0d8957] [ 4496.906] 9: /usr/lib64/libdrm.so.2 (drmIoctl+0x28) [0x34a1003358] [ 4496.906] 10: /usr/lib64/libdrm_intel.so.1 (0x7f5858969000+0x4ed3) [0x7f585896ded3] [ 4496.906] 11: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5858b74000+0xb777) [0x7f5858b7f777] [ 4496.906] 12: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5858b74000+0x12056) [0x7f5858b86056] [ 4496.906] 13: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f5858b74000+0x2dcbe) [0x7f5858ba1cbe] [ 4496.906] 14: /usr/bin/X (0x400000+0xd459a) [0x4d459a] [ 4496.906] 15: /usr/bin/X (0x400000+0x2ec11) [0x42ec11] [ 4496.906] 16: /usr/bin/X (0x400000+0x22e1a) [0x422e1a] [ 4496.906] 17: /lib64/libc.so.6 (__libc_start_main+0xed) [0x348c02139d] [ 4496.906] 18: /usr/bin/X (0x400000+0x23101) [0x423101]
Created attachment 512374 [details] Test file for more or less reliably producing the lock-up Here is the procedure using the attached test file to more or less reliably produce the lock-up: 1. Boot the computer 2. Start openoffice 3. Load the attached spreadsheet 4. Use SHIFT plus cursor keys to select the 2x5 region 5. Press CTRL+INSERT to copy the region This should produce the lock-up in about one in five cases (if it doesn't, simply quite openoffice and repeat steps 2-5 again until the lock-up occurs).
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log), * output of rpm -q libdrm xorg-x11-drv-intel xorg-x11-server-Xorg (of course, I hope that these are the packages you generated the backtrace in the comment 0), * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 512444 [details] Xorg.0.log
Created attachment 512445 [details] Output from dmesg
Created attachment 512448 [details] messages
Output from "rpm -q libdrm xorg-x11-drv-intel xorg-x11-server-Xorg": libdrm-2.4.26-1.fc15.x86_64 libdrm-2.4.26-1.fc15.i686 xorg-x11-drv-intel-2.15.0-4.fc15.x86_64 xorg-x11-server-Xorg-1.10.2-1.fc15.x86_64
Created attachment 512450 [details] Created new Xorg.0.log.old file consistent with above files Since I updated the kernel and the intel drive between originally filing the bug and the posting the requested files, I just produced another lock-up and am now attaching the updated Xorg.0.log.old file that goes with the above files (please disregard the first one I posted)
Frame 2: /usr/bin/X (xf86PostMotionEventM+0xa3) [0x47db33] /usr/src/debug/xorg-server-1.10.2/hw/xfree86/common/xf86Xinput.c:1056 xf86PostMotionEventM Frame 3: /usr/bin/X (xf86PostMotionEventP+0x52) [0x47dc52] /usr/src/debug/xorg-server-1.10.2/hw/xfree86/common/xf86Xinput.c:1008 xf86PostMotionEventP Frame 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f32f17a6000+0x4b1b) [0x7f32f17aab1b] /usr/src/debug/xf86-input-evdev-2.6.0/src/evdev.c:820 EvdevProcessSyncEvent Frame 5: /usr/bin/X (0x400000+0x6b588) [0x46b588] /usr/src/debug/xorg-server-1.10.2/hw/xfree86/common/xf86Events.c:300 xf86SigioReadInput Frame 6: /usr/bin/X (0x400000+0x119c90) [0x519c90] /usr/src/debug/xorg-server-1.10.2/hw/xfree86/os-support/linux/../shared/sigio.c:106 xf86SIGIO Frame 10: /usr/lib64/libdrm_intel.so.1 (0x7f32f2dfa000+0x4ed3) [0x7f32f2dfeed3] /usr/src/debug/libdrm-2.4.26/intel/intel_bufmgr_gem.c:1633 drm_intel_gem_bo_mrb_exec2 Frame 11: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f32f3005000+0xb775) [0x7f32f3010775] /usr/src/debug/xf86-video-intel-2.15.0/src/intel_batchbuffer.c:217 intel_batch_submit Frame 12: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f32f3005000+0x125a8) [0x7f32f30175a8] /usr/src/debug/xf86-video-intel-2.15.0/src/intel_uxa.c:317 intel_uxa_solid Frame 13: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f32f3005000+0x2d36e) [0x7f32f303236e] /usr/src/debug/xf86-video-intel-2.15.0/uxa/uxa-render.c:1037 uxa_solid_rects Frame 14: /usr/bin/X (0x400000+0xd459a) [0x4d459a] /usr/src/debug/xorg-server-1.10.2/render/render.c:1487 ProcRenderFillRectangles Frame 15: /usr/bin/X (0x400000+0x2ec11) [0x42ec11] /usr/src/debug/xorg-server-1.10.2/dix/dispatch.c:431 Dispatch Frame 16: /usr/bin/X (0x400000+0x22e1a) [0x422e1a] /usr/src/debug/xorg-server-1.10.2/dix/main.c:296 main
This problem is really obnoxious and I have in the meantime experienced it with various other applications as well (e.g., text field in firefox); I'm surprised that nobody else has reported it as it very severely limits the usefulness of Fedora (I, as a Fedora user from the very beginning, have not experienced anything like it in any of the previous releases...). I would really really appreciate if somebody could look into the problem... Here is a backtrace from running audacity running on the same system as before. Note that audacity locked up the computer without any user input (it does, however, have a running vertical bar that it updates to indicate position in the wav file it is playing, so maybe that's the cause...) [ 52423.793] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [ 52423.794] Backtrace: [ 52423.869] 0: /usr/bin/X (xorg_backtrace+0x2f) [0x4a142f] [ 52423.874] 1: /usr/bin/X (mieqEnqueue+0x1e9) [0x4a0949] [ 52423.874] 2: /usr/bin/X (xf86PostMotionEventM+0xa3) [0x47db33] [ 52423.874] 3: /usr/bin/X (xf86PostMotionEventP+0x52) [0x47dc52] [ 52423.874] 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7ff2e0ef9000+0x4b1b) [0x7ff2e0efdb1b] [ 52423.874] 5: /usr/bin/X (0x400000+0x6b588) [0x46b588] [ 52423.874] 6: /usr/bin/X (0x400000+0x119c90) [0x519c90] [ 52423.874] 7: /lib64/libpthread.so.0 (0x348c800000+0xeeb0) [0x348c80eeb0] [ 52423.874] 8: /usr/lib64/xorg/modules/libfb.so (fbPolySegment32+0x401) [0x7ff2e1d2b811] [ 52423.874] 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7ff2e2758000+0x301cd) [0x7ff2e27881cd] [ 52423.874] 10: /usr/bin/X (0x400000+0xdb291) [0x4db291] [ 52423.874] 11: /usr/bin/X (0x400000+0x2b25f) [0x42b25f] [ 52423.874] 12: /usr/bin/X (0x400000+0x2ec11) [0x42ec11] [ 52423.874] 13: /usr/bin/X (0x400000+0x22e1a) [0x422e1a] [ 52423.874] 14: /lib64/libc.so.6 (__libc_start_main+0xed) [0x348c02139d] [ 52423.874] 15: /usr/bin/X (0x400000+0x23101) [0x423101]
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping