Created attachment 955515 [details] journal of Xorg output. Description of problem: Xorg will hang freezing the display, mouse and keyboard. ctl-alt-f2 has no effect. numlock will not toggle nunlock led. Keyboard is totally non-responsive. It is possible to ssh into the machine to reboot it, but the reboot hangs for a long time. This hang seems to happen more when viewing graphic intensive web pages (like google+) under google-chrome-stable. Version-Release number of selected component (if applicable): xorg-x11-drv-ati.x86_64 7.5.0-1.fc21 installed xorg-x11-drv-evdev.x86_64 2.9.0-3.fc21 installed xorg-x11-drv-fbdev.x86_64 0.4.3-19.fc21 installed xorg-x11-drv-intel.x86_64 2.99.916-2.fc21 installed xorg-x11-drv-modesetting.x86_64 0.9.0-2.fc21 installed xorg-x11-drv-nouveau.x86_64 1:1.0.11-1.fc21 installed xorg-x11-drv-openchrome.x86_64 0.3.3-12.fc21 installed xorg-x11-drv-qxl.x86_64 0.1.2-1.fc21 installed xorg-x11-drv-synaptics.x86_64 1.8.0-9.fc21 installed xorg-x11-drv-vesa.x86_64 2.3.2-19.fc21 installed xorg-x11-drv-vmmouse.x86_64 13.0.0-13.fc21 installed xorg-x11-drv-vmware.x86_64 13.0.2-5.20140613git82c9b0c.fc21 installed xorg-x11-drv-wacom.x86_64 0.25.0-2.fc21 installed xorg-x11-font-utils.x86_64 1:7.5-23.fc21 installed xorg-x11-fonts-Type1.noarch 7.5-11.fc21 installed xorg-x11-proto-devel.noarch 7.7-12.fc21 installed xorg-x11-server-Xorg.x86_64 1.16.1-1.fc21 installed xorg-x11-server-Xwayland.x86_64 1.16.1-1.fc21 installed xorg-x11-server-common.x86_64 1.16.1-1.fc21 installed xorg-x11-server-devel.x86_64 1.16.1-1.fc21 installed xorg-x11-server-utils.x86_64 7.7-9.fc21 @updates-testing xorg-x11-util-macros.noarch 1.19.0-3.fc21 installed xorg-x11-utils.x86_64 7.5-16.fc21 @updates-testing xorg-x11-xauth.x86_64 1:1.0.9-2.fc21 installed xorg-x11-xinit.x86_64 1.3.4-2.fc21 installed xorg-x11-xkb-utils.x86_64 7.7-10.fc21 installed google-chrome-stable.x86_64 38.0.2125.111-1 @google-chrome How reproducible: variable. It tends to happen within a half hour of reading google+ Steps to Reproduce: 1. browse google plus 2. 3. Actual results: hang Expected results: no hang Additional info: Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) Backtrace: Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 0: /usr/libexec/Xorg.bin (mieqEnqueue+0x24b) [0x578f9b] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 1: /usr/libexec/Xorg.bin (QueuePointerEvents+0x52) [0x450952] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x3042) [0x7f01c86b8852] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x3505) [0x7f01c86b99a5] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 4: /usr/libexec/Xorg.bin (DPMSSupported+0xe8) [0x4772c8] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 5: /usr/libexec/Xorg.bin (xf86SerialModemClearBits+0x277) [0x4a1cc7] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 6: /lib64/libc.so.6 (__restore_rt+0x0) [0x7f01cd9bc94f] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 7: /lib64/libc.so.6 (ioctl+0x7) [0x7f01cda7e957] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 8: /lib64/libdrm.so.2 (drmIoctl+0x28) [0x7f01ced7b6c8] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 9: /lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f01ced7defb] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 10: /lib64/libdrm_radeon.so.1 (_init+0x519) [0x7f01c8e7a229] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 11: /usr/lib64/xorg/modules/drivers/radeon_drv.so (_init+0x39a38) [0x7f01c9104d28] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 12: /usr/lib64/xorg/modules/drivers/radeon_drv.so (_init+0x39c31) [0x7f01c9105291] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 13: /lib64/libdrm.so.2 (drmHandleEvent+0x7e) [0x7f01ced8045e] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 14: /usr/libexec/Xorg.bin (WakeupHandler+0x6b) [0x43dc8b] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 15: /usr/libexec/Xorg.bin (WaitForSomething+0x1c7) [0x5951d7] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 16: /usr/libexec/Xorg.bin (SendErrorToClient+0x111) [0x438e41] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 17: /usr/libexec/Xorg.bin (remove_fs_handlers+0x416) [0x43d186] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 18: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f01cd9a7fe0] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 19: /usr/libexec/Xorg.bin (_start+0x29) [0x42761e] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 20: ? (?+0x29) [0x29] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) [mi] mieq is *NOT* the cause. It is a victim. Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) [mi] EQ overflow continuing. 100 events have been dropped. Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) Backtrace: Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 0: /usr/libexec/Xorg.bin (QueuePointerEvents+0x52) [0x450952] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 1: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x3042) [0x7f01c86b8852] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x3505) [0x7f01c86b99a5] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 3: /usr/libexec/Xorg.bin (DPMSSupported+0xe8) [0x4772c8] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 4: /usr/libexec/Xorg.bin (xf86SerialModemClearBits+0x277) [0x4a1cc7] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 5: /lib64/libc.so.6 (__restore_rt+0x0) [0x7f01cd9bc94f] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 6: /lib64/libc.so.6 (ioctl+0x7) [0x7f01cda7e957] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 7: /lib64/libdrm.so.2 (drmIoctl+0x28) [0x7f01ced7b6c8] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 8: /lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f01ced7defb] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 9: /lib64/libdrm_radeon.so.1 (_init+0x519) [0x7f01c8e7a229] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 10: /usr/lib64/xorg/modules/drivers/radeon_drv.so (_init+0x39a38) [0x7f01c9104d28] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 11: /usr/lib64/xorg/modules/drivers/radeon_drv.so (_init+0x39c31) [0x7f01c9105291] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 12: /lib64/libdrm.so.2 (drmHandleEvent+0x7e) [0x7f01ced8045e] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 13: /usr/libexec/Xorg.bin (WakeupHandler+0x6b) [0x43dc8b] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 14: /usr/libexec/Xorg.bin (WaitForSomething+0x1c7) [0x5951d7] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 15: /usr/libexec/Xorg.bin (SendErrorToClient+0x111) [0x438e41] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 16: /usr/libexec/Xorg.bin (remove_fs_handlers+0x416) [0x43d186] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 17: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f01cd9a7fe0] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 18: /usr/libexec/Xorg.bin (_start+0x29) [0x42761e] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE) 19: ? (?+0x29) [0x29] Nov 09 07:03:16 capsicum.wsrcc.com gdm-Xorg-:0[2957]: (EE)
Created attachment 955951 [details] kernel messages indicating a radeon ring 0 stall. radeon ring 0 stalled for more than 10028msec
I can reliably reproduce a very similar error on one of my systems by using the Fedora 21 Beta Xfce live image. The error occurs when bringing up the window that normally allows entire of a Wifi network password. The window outline appears, but the text entry box does not appear. After the hang-up, the mouse still controls cursor movement, but the mouse buttons and keyboard are dead. The affected hardware is a vintage 2007 Dell Inspiron 1420 with an Intel GM965 graphics chipset. I can ssh in if I connect it via Ethernet before attempting the WiFi connection, so let me know if you'd like me to gather more info to assist in debugging this relatively severe problem.
Just a note, after the updates to my Fedora 20 system the week of Nov 2nd my system would crash. Soon after starting up and opening my usual windows the menu bar would disappear and all my windows in different virtual desktops would combine into one window. The keyboard would stop working and the upperpart of my windows would disappear but I could close the windows by clicking on File - Close. After some touble-shooting such as switchng keyboards and trying Gnome instead of my regular KDE I removed xorg-x11-drv-ati and now my system is stable again.My video card is a ATI 8770 and I take it I'm now running some form of generic driver. I'm good until Fedora 21 comes out.
Created attachment 1035776 [details] Xorg.0.log error error messages
I see the same problem on Fedora 21 when using a 3.18, 3.19, or 4.0 kernel. As a result, I normally run the 3.16 kernel, where I have not seen this problem. (3.17 has other, more severe problems.) I am running a G660TI card using the nouveau driver. Most recently, the problem occurred when trying to close a tab in Firefox showing a YouTube Flash video. The mouse moves the cursor, but all other input (keyboard and mouse clicks) is ignored. I can log in using ssh.
Unable to submit attachment containing the relevant section of /var/log/messages, so here's the contents: Jun 6 22:04:43 banner kernel: [319187.970507] nouveau E[ PFIFO][0000:01:00.0] read fault at 0x001791e000 [UNSUPPORTED_KIND] from GR/GPC1/T1_0 on channel 0x007fa1a000 [Xorg.bin[2046]] Jun 6 22:04:43 banner kernel: [319187.970523] nouveau E[ PFIFO][0000:01:00.0] PGR engine fault on channel 2, recovering... Jun 6 22:04:43 banner kernel: [319187.970546] nouveau E[ PGR][0000:01:00.0] TRAP ch 2 [0x007fa1a000 Xorg.bin[2046]] Jun 6 22:04:43 banner kernel: [319187.970560] nouveau E[ PGR][0000:01:00.0] GPC0/TPC0/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: [319187.970570] nouveau E[ PGR][0000:01:00.0] GPC0/TPC1/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: [319187.970581] nouveau E[ PGR][0000:01:00.0] GPC1/TPC0/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: [319187.970590] nouveau E[ PGR][0000:01:00.0] GPC1/TPC1/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: [319187.970601] nouveau E[ PGR][0000:01:00.0] GPC2/TPC0/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: [319187.970612] nouveau E[ PGR][0000:01:00.0] GPC3/TPC0/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: [319187.970622] nouveau E[ PGR][0000:01:00.0] GPC3/TPC1/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: nouveau E[ PFIFO][0000:01:00.0] read fault at 0x001791e000 [UNSUPPORTED_KIND] from GR/GPC1/T1_0 on channel 0x007fa1a000 [Xorg.bin[2046]] Jun 6 22:04:43 banner kernel: nouveau E[ PFIFO][0000:01:00.0] PGR engine fault on channel 2, recovering... Jun 6 22:04:43 banner kernel: nouveau E[ PGR][0000:01:00.0] TRAP ch 2 [0x007fa1a000 Xorg.bin[2046]] Jun 6 22:04:43 banner kernel: nouveau E[ PGR][0000:01:00.0] GPC0/TPC0/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: nouveau E[ PGR][0000:01:00.0] GPC0/TPC1/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: nouveau E[ PGR][0000:01:00.0] GPC1/TPC0/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: nouveau E[ PGR][0000:01:00.0] GPC1/TPC1/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: nouveau E[ PGR][0000:01:00.0] GPC2/TPC0/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: nouveau E[ PGR][0000:01:00.0] GPC3/TPC0/TEX: 0x80000049 Jun 6 22:04:43 banner kernel: nouveau E[ PGR][0000:01:00.0] GPC3/TPC1/TEX: 0x80000049
I am suffering from this too and it is very serious as it requires a powerdown of the system to recover. Same error messages as above. It happened when I was opeining a tab in google-chrome.
I can confirm this from kernel versions v4.0.7 - v4.1.3 for Fedora 21. It started off randomly, and annoyingly where - like others above - I could SSH back in and kill Chrome and recover from an otherwise unresponsive desktop (keyboard, and sometimes mouse). Audio would likely continue if playing. GDM logs: Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are pr ocessed. Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) Backtrace: Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 0: ? (?+0x21203b18) [0x362177cfa8] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 1: ? (?+0x21203b18) [0x36216545b8] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x2f0f) [0x7efd4919c91f] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x3655) [0x7efd4919dbe5] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 4: /usr/libexec/Xorg.bin (?+0x3655) [0x47aa35] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 5: /usr/libexec/Xorg.bin (?+0x3655) [0x4a52a5] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 6: /lib64/libc.so.6 (__restore_rt+0x0) [0x313b83495f] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 7: /lib64/libc.so.6 (ioctl+0x7) [0x313b8f6407] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 8: /lib64/libdrm.so.2 (drmIoctl+0x28) [0x3621203b18] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 9: /lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x362120667b] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 10: /lib64/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8c) [0x7efd4db9c76c] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 11: /lib64/libdrm_nouveau.so.2 (nouveau_pushbuf_space+0xde) [0x7efd4db9da8e] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 12: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (_init+0x1f566) [0x7efd4de10ee6] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 13: /usr/lib64/xorg/modules/libexa.so (exaMoveOutPixmap+0x5604) [0x7efd4d9907f4] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 14: /usr/lib64/xorg/modules/libexa.so (exaMoveOutPixmap+0x593c) [0x7efd4d9917fc] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 15: /usr/libexec/Xorg.bin (?+0x593c) [0x57d25c] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 16: /usr/libexec/Xorg.bin (?+0x593c) [0x57d54c] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 17: /usr/lib64/xorg/modules/libexa.so (exaMoveOutPixmap+0x3f65) [0x7efd4d98e495] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 18: /usr/libexec/Xorg.bin (?+0x3f65) [0x5259e5] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 19: /usr/libexec/Xorg.bin (?+0x3f65) [0x438f95] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 20: /usr/libexec/Xorg.bin (?+0x3f65) [0x43ce25] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 21: /usr/libexec/Xorg.bin (?+0x3f65) [0x440e65] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 22: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x313b81ffe0] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 23: /usr/libexec/Xorg.bin (?+0xf0) [0x4277b5] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) 24: ? (?+0xf0) [0xf0] Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] mieq is *NOT* the cause. It is a victim. Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] EQ overflow continuing. 100 events have been dropped. Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) Aug 7 09:18:03 arrowsmithlap1 gdm-Xorg-:0: (EE) Backtrace: ... which continues until: Aug 7 09:18:07 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] EQ overflow continuing. 1000 events have been dropped. Aug 7 09:18:07 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] No further overflow reports will be reported until the clog is cleared. Triggers are usually something graphical: - fading to black screen saver - Youtube playback (even when hidden) - how I know audio continues - hovertext for a browser tab Another one minutes after reboot: Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) Backtrace: Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 0: /usr/libexec/Xorg.bin (mieqEnqueue+0x24b) [0x5796db] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 1: /usr/libexec/Xorg.bin (QueuePointerEvents+0x52) [0x450af2] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x2f0f) [0x7f134373191f] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x3655) [0x7f1343732be5] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 4: /usr/libexec/Xorg.bin (DPMSSupported+0xe8) [0x4774c8] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 5: /usr/libexec/Xorg.bin (xf86SerialModemClearBits+0x277) [0x4a1ec7] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 6: /lib64/libc.so.6 (__restore_rt+0x0) [0x313b83495f] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 7: /lib64/libc.so.6 (ioctl+0x7) [0x313b8f6407] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 8: /lib64/libdrm.so.2 (drmIoctl+0x28) [0x3621203b18] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 9: /lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x362120667b] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 10: /lib64/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8c) [0x7f134813176c] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 11: /lib64/libdrm_nouveau.so.2 (nouveau_pushbuf_space+0xde) [0x7f1348132a8e] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 12: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (_init+0x1f431) [0x7f13483a5c71] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 13: /usr/lib64/xorg/modules/libexa.so (exaMoveOutPixmap+0x5595) [0x7f1347f25785] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 14: /usr/lib64/xorg/modules/libexa.so (exaMoveOutPixmap+0x593c) [0x7f1347f267fc] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 15: /usr/libexec/Xorg.bin (miCopyRegion+0x1a7) [0x577ac7] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 16: /usr/libexec/Xorg.bin (miDoCopy+0x45e) [0x57806e] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 17: /usr/lib64/xorg/modules/libexa.so (exaMoveOutPixmap+0x3f65) [0x7f1347f23495] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 18: /usr/libexec/Xorg.bin (DamageRegionAppend+0x33ed) [0x524e6d] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 19: /usr/libexec/Xorg.bin (dixDestroyPixmap+0x87a) [0x4358aa] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 20: /usr/libexec/Xorg.bin (SendErrorToClient+0x2f7) [0x4391b7] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 21: /usr/libexec/Xorg.bin (remove_fs_handlers+0x416) [0x43d316] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 22: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x313b81ffe0] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 23: /usr/libexec/Xorg.bin (_start+0x29) [0x4276ee] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) 24: ? (?+0x29) [0x29] Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. Aug 7 09:34:00 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] mieq is *NOT* the cause. It is a victim. ... and another less than an hour later: Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) Backtrace: Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 0: /usr/libexec/Xorg.bin (mieqEnqueue+0x24b) [0x5796db] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 1: /usr/libexec/Xorg.bin (QueuePointerEvents+0x52) [0x450af2] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x2f0f) [0x7f24b05a091f] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x3655) [0x7f24b05a1be5] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 4: /usr/libexec/Xorg.bin (DPMSSupported+0xe8) [0x4774c8] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 5: /usr/libexec/Xorg.bin (xf86SerialModemClearBits+0x277) [0x4a1ec7] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 6: /lib64/libc.so.6 (__restore_rt+0x0) [0x313b83495f] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 7: /lib64/libc.so.6 (ioctl+0x7) [0x313b8f6407] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 8: /lib64/libdrm.so.2 (drmIoctl+0x28) [0x3621203b18] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 9: /lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x362120667b] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 10: /lib64/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8c) [0x7f24b4fa076c] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 11: /lib64/libdrm_nouveau.so.2 (nouveau_pushbuf_space+0xde) [0x7f24b4fa1a8e] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 12: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (_init+0x20271) [0x7f24b5216841] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 13: /usr/lib64/xorg/modules/libexa.so (exaEnableDisableFBAccess+0x8e5) [0x7f24b4d93ec5] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 14: /usr/lib64/xorg/modules/libexa.so (exaEnableDisableFBAccess+0x119d) [0x7f24b4d9555d] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 15: /usr/lib64/xorg/modules/libexa.so (exaMoveOutPixmap+0x8055) [0x7f24b4d99e45] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 16: /usr/libexec/Xorg.bin (DamageRegionAppend+0x7d3) [0x51f5d3] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 17: /usr/libexec/Xorg.bin (AddTraps+0x4677) [0x519137] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 18: /usr/libexec/Xorg.bin (SendErrorToClient+0x2f7) [0x4391b7] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 19: /usr/libexec/Xorg.bin (remove_fs_handlers+0x416) [0x43d316] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 20: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x313b81ffe0] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 21: /usr/libexec/Xorg.bin (_start+0x29) [0x4276ee] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) 22: ? (?+0x29) [0x29] Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. Aug 7 10:29:06 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] mieq is *NOT* the cause. It is a victim. Aug 7 10:29:07 arrowsmithlap1 gdm-Xorg-:0: (EE) [mi] EQ overflow continuing. 100 events have been dropped. . . . Aug 7 10:29:58 arrowsmithlap1 gdm-Xorg-:0: (EE) Aug 7 10:30:09 arrowsmithlap1 kernel: [ 1989.564828] nouveau E[chrome[20679]] failed to idle channel 0xcccc0000 [chrome[20679]] Aug 7 10:30:09 arrowsmithlap1 kernel: nouveau E[chrome[20679]] failed to idle channel 0xcccc0000 [chrome[20679]] Aug 7 10:30:24 arrowsmithlap1 kernel: [ 2004.584464] nouveau E[chrome[20679]] failed to idle channel 0xcccc0000 [chrome[20679]] Aug 7 10:30:24 arrowsmithlap1 kernel: nouveau E[chrome[20679]] failed to idle channel 0xcccc0000 [chrome[20679]] Aug 7 10:30:24 arrowsmithlap1 gdm-Xorg-:0: [mi] Increasing EQ size to 1024 to prevent dropped events. Aug 7 10:30:24 arrowsmithlap1 gdm-Xorg-:0: [mi] EQ processing has resumed after 639 dropped events. Aug 7 10:30:24 arrowsmithlap1 gdm-Xorg-:0: [mi] This may be caused my a misbehaving driver monopolizing the server's resources. Aug 7 10:30:24 arrowsmithlap1 gnome-session: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Aug 7 10:31:22 arrowsmithlap1 gdm-Xorg-:0: (II) Server zapped. Shutting down. Hardware: [root@arrowsmithlap1 ~]# lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04) 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [NVS 4200M] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) 0b:00.0 FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05) 0b:00.1 SD Host controller: O2 Micro, Inc. OZ600RJ0/OZ900RJ0/OZ600RJS SD/MMC Card Reader Controller (rev 05) 0b:00.2 Mass storage controller: O2 Micro, Inc. O2 Flash Memory Card (rev 05)
Created attachment 1061286 [details] xorg.0 log of another instance of this problem I have also been experiencing this bug lately. Fedora 20, x86_64, radeon. I have only seen it happen when the system is idle, and when I return to it, I can wake up the screensaver, move the mouse, but everything else is unresponsive. Another report of a similar problem suggested the radeon glamor driver was the culprit so I forced it to use EXA instead (which you can see around line 346 of this log), but the problem still happens. I installed this minimal xorg.conf to set the option: Section "Device" Identifier "Radeon" Driver "radeon" Option "AccelMethod" "EXA" EndSection The last time it happened, it seemed to happen JUST before I tried to use the system, and it wasn't yet completely unresponsive. I managed to log out, causing it to restart X, and the system returned to normal. The EQ backtrace lines don't have a time on them, but I expect they shortly preceded the messages which follow. You can see it is a matter of 5 minutes from the first timestamp associated with the problem and the messages from X shutting down.
Updating my report of 6/6. tl;dr: Problem occurs with latest 4.1.3-100.fc21.x86_64 kernel With 3.18, 3.19, 4.0 kernels, the problem was occasional - once every several days coincident with unresponsive browser activity. With the 4.1.3 kernel, it occurred the first time I booted that kernel. I stepped away from the system for a while, and when I came back the system was unresponsive, except for a cursor on a black screen. As before, able to ssh in to the system. Back to running 3.16.6-203.fc20.x86_64 where I've never experienced the problem.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.