Xorg freezing

sergenikov · 2015-02-14 17:17:49

Hello Arch Forums,

I am strangely excited to ask my first question on Arch forums. I've been with Arch for only four months, and it's great! Anyhow, I experience Xorg freezes; at least that's what I think it is. When I watch youtube, after a while the window manager stops responding. I am thinking it's Xorg's glitch, not wm's since no inputs are going through at all. However, the sound is still working. Here is what happens:

- YouTube video stops playing video;
- BUT sound still goes;
- window manager (i3) does not respond to keyboard input;
- mouse works for a while then also stops - sound from the video is still playing at this point;
- X restart sequence (ctrl+alt+backspace) does not work;
- I can't switch to virtual terminals because keyboard does not work.

Since nothing works the only way to get back into my computer is hard reboot (power button). I would really appreciate some pointers as to where to look for a problem and how to collect information about my system. So far I will (1) look at Xorg logs if there are any; (2) systems logs - i've never had to do this. I assume there is something, but I don't know.

[sergey@archone ~]$ lspci | grep -e VGA -e 3D
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)

Last edited by sergenikov (2015-02-14 17:18:25)

Head_on_a_Stick · 2015-02-14 17:29:24

X server logs are at ~/.local/share/xorg/Xorg.0.log

Also, read man journalctl
https://wiki.archlinux.org/index.php/Systemd#Journal

Which drivers is your card using?

Is <Ctrl>+<Alt>+<Backspace> activated on your system?
https://wiki.archlinux.org/index.php/Ke … BBackspace

sergenikov · 2015-02-14 17:41:28

I am looking at /var/log/Xorg.0.log and Xorg.0.log.old, but not sure how to read the output yet. It is kind of interesting. Does not look right. This happened yesterday, so I am looking at Xorg.0.log.old. Here are the last 200 lines of it. I don't know how to match it to the freezing event (maybe Firefox logs?). The leftmost column: is it a timestamp?

And what is "EQ overflowing" (highlighted line)?
And in lines like this: is WAIT a function and in (...) are its hex parameters?
[ 6906.681] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f0a4, 0x0000f0a4)

I have so many questions about this output.

$ tail -n 200 Xorg.0.log.old
[    16.195] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found scroll wheel(s)
[    16.195] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found relative axes
[    16.195] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found absolute axes
[    16.195] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found absolute multitouch axes
[    16.195] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found x and y absolute axes
[    16.195] (--) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Found keys
[    16.195] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Forcing relative x/y axes to exist.
[    16.195] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Configuring as mouse
[    16.195] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Configuring as keyboard
[    16.195] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Adding scrollwheel support
[    16.195] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: YAxisMapping: buttons 4 and 5
[    16.195] (**) evdev: Microsoft Microsoft® Nano Transceiver v2.0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    16.195] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.2/0003:045E:0745.0005/input/input20/event17"
[    16.195] (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 12)
[    16.195] (**) Option "xkb_rules" "evdev"
[    16.195] (**) Option "xkb_model" "pc104"
[    16.195] (**) Option "xkb_layout" "us"
[    16.195] (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: initialized for relative axes.
[    16.195] (WW) evdev: Microsoft Microsoft® Nano Transceiver v2.0: ignoring absolute axes.
[    16.195] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) keeping acceleration scheme 1
[    16.195] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) acceleration profile 0
[    16.195] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) acceleration factor: 2.000
[    16.195] (**) Microsoft Microsoft® Nano Transceiver v2.0: (accel) acceleration threshold: 4
[    16.196] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/js0)
[    16.196] (II) No input driver specified, ignoring this device.
[    16.196] (II) This device may have been added with another device file.
[    16.196] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event3)
[    16.196] (II) No input driver specified, ignoring this device.
[    16.196] (II) This device may have been added with another device file.
[    16.196] (II) config/udev: Adding input device HDA Intel Line Out (/dev/input/event7)
[    16.196] (II) No input driver specified, ignoring this device.
[    16.196] (II) This device may have been added with another device file.
[    16.196] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event8)
[    16.196] (II) No input driver specified, ignoring this device.
[    16.196] (II) This device may have been added with another device file.
[    16.197] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event4)
[    16.197] (II) No input driver specified, ignoring this device.
[    16.197] (II) This device may have been added with another device file.
[    16.197] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event5)
[    16.197] (II) No input driver specified, ignoring this device.
[    16.197] (II) This device may have been added with another device file.
[    16.197] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event6)
[    16.197] (II) No input driver specified, ignoring this device.
[    16.197] (II) This device may have been added with another device file.
[    16.197] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[    16.197] (II) No input driver specified, ignoring this device.
[    16.197] (II) This device may have been added with another device file.
[    22.613] (II) NVIDIA(GPU-0): Display (DELL E198FP (CRT-1)) does not support NVIDIA 3D
[    22.613] (II) NVIDIA(GPU-0):     Vision stereo.
[    22.627] (II) NVIDIA(GPU-0): Display (LG Electronics L1753T (DFP-0)) does not support
[    22.628] (II) NVIDIA(GPU-0):     NVIDIA 3D Vision stereo.
[    29.210] (II) NVIDIA(GPU-0): Display (DELL E198FP (CRT-1)) does not support NVIDIA 3D
[    29.210] (II) NVIDIA(GPU-0):     Vision stereo.
[    29.225] (II) NVIDIA(GPU-0): Display (LG Electronics L1753T (DFP-0)) does not support
[    29.225] (II) NVIDIA(GPU-0):     NVIDIA 3D Vision stereo.
[    29.270] (II) NVIDIA(GPU-0): Display (DELL E198FP (CRT-1)) does not support NVIDIA 3D
[    29.270] (II) NVIDIA(GPU-0):     Vision stereo.
[    29.285] (II) NVIDIA(GPU-0): Display (LG Electronics L1753T (DFP-0)) does not support
[    29.285] (II) NVIDIA(GPU-0):     NVIDIA 3D Vision stereo.
[    29.330] (II) NVIDIA(GPU-0): Display (DELL E198FP (CRT-1)) does not support NVIDIA 3D
[    29.330] (II) NVIDIA(GPU-0):     Vision stereo.
[    29.345] (II) NVIDIA(GPU-0): Display (LG Electronics L1753T (DFP-0)) does not support
[    29.345] (II) NVIDIA(GPU-0):     NVIDIA 3D Vision stereo.
[   122.773] (II) NVIDIA(GPU-0): Display (DELL E198FP (CRT-1)) does not support NVIDIA 3D
[   122.773] (II) NVIDIA(GPU-0):     Vision stereo.
[   122.788] (II) NVIDIA(GPU-0): Display (LG Electronics L1753T (DFP-0)) does not support
[   122.788] (II) NVIDIA(GPU-0):     NVIDIA 3D Vision stereo.
[   122.833] (II) NVIDIA(GPU-0): Display (DELL E198FP (CRT-1)) does not support NVIDIA 3D
[   122.833] (II) NVIDIA(GPU-0):     Vision stereo.
[   122.848] (II) NVIDIA(GPU-0): Display (LG Electronics L1753T (DFP-0)) does not support
[   122.848] (II) NVIDIA(GPU-0):     NVIDIA 3D Vision stereo.
[   122.894] (II) NVIDIA(GPU-0): Display (DELL E198FP (CRT-1)) does not support NVIDIA 3D
[   122.894] (II) NVIDIA(GPU-0):     Vision stereo.
[   122.908] (II) NVIDIA(GPU-0): Display (LG Electronics L1753T (DFP-0)) does not support
[   122.908] (II) NVIDIA(GPU-0):     NVIDIA 3D Vision stereo.
[  6906.681] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f0a4, 0x0000f0a4)
[  6909.707] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f0d8, 0x0000f0d8)
[  6912.708] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f10c, 0x0000f10c)
[  6915.709] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f140, 0x0000f140)
[  6918.710] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f174, 0x0000f174)

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< FROM HERE IT GETS INTERESTING

(EE) [mi] EQ overflowing.  Additional events will be discarded until existing events are processed.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x52) [0x81df352]
(EE) 1: /usr/bin/Xorg.bin (mieqEnqueue+0x24c) [0x81bf5ec]
(EE) 2: /usr/bin/Xorg.bin (QueueKeyboardEvents+0x5b) [0x8090f0b]
(EE) 3: /usr/bin/Xorg.bin (xf86PostKeyEventM+0x68) [0x80ca8a8]
(EE) 4: /usr/bin/Xorg.bin (xf86PostKeyboardEvent+0x4d) [0x80caabd]
(EE) 5: /usr/lib/xorg/modules/input/evdev_drv.so (0xb2d1f000+0x4cf4) [0xb2d23cf4]
(EE) 6: /usr/lib/xorg/modules/input/evdev_drv.so (0xb2d1f000+0x53cd) [0xb2d243cd]
(EE) 7: /usr/bin/Xorg.bin (0x8048000+0x71746) [0x80b9746]
(EE) 8: /usr/bin/Xorg.bin (0x8048000+0x9ca6a) [0x80e4a6a]
(EE) 9: linux-gate.so.1 (__kernel_sigreturn+0x0) [0xb776eb88]
(EE) 10: linux-gate.so.1 (__kernel_vsyscall+0x10) [0xb776ebac]
(EE) 11: /usr/lib/libc.so.6 (__gettimeofday+0x16) [0xb7401786]
(EE) 12: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb38f4000+0xa8cac) [0xb399ccac]
(EE) 
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause.  It is a victim.
[  6921.914] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f1a8, 0x0000f1a8)
[  6924.915] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f1dc, 0x0000f1dc)
[  6927.916] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f210, 0x0000f210)
[  6930.917] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000f244, 0x0000f244)
[  6930.917] [mi] Increasing EQ size to 1024 to prevent dropped events.
[  6930.918] [mi] EQ processing has resumed after 39 dropped events.
[  6930.918] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[  6933.932] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000ed1c, 0x0000ed1c)
[  6936.933] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000ed50, 0x0000ed50)
[  6939.934] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000ed84, 0x0000ed84)
[  6942.935] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000edb8, 0x0000edb8)
[  6945.936] (WW) NVIDIA(0): WAIT (0, 4, 0x8000, 0x0000edec, 0x0000edec)
.... is keeps going like this until...
[  7213.926] (WW) NVIDIA(0): WAIT (0, 6, 0x8000, 0x00002890, 0x00002890)

Last edited by sergenikov (2015-02-14 17:44:48)

sergenikov · 2015-02-14 17:49:22

Head_on_a_Stick wrote:

X server logs are at ~/.local/share/xorg/Xorg.0.log
Also, read man journalctl
https://wiki.archlinux.org/index.php/Systemd#Journal
>>> thank you
Which drivers is your card using?

[sergey@archone log]$ lspci -v | grep -A 11 VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller])
	Subsystem: ZOTAC International (MCO) Ltd. Device 1044
	Flags: bus master, fast devsel, latency 0, IRQ 33
	Memory at 92000000 (32-bit, non-prefetchable) [size=16M]
	Memory at 80000000 (64-bit, prefetchable) [size=256M]
	Memory at 90000000 (64-bit, prefetchable) [size=32M]
	I/O ports at 2000 [size=128]
	[virtual] Expansion ROM at 93080000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: nvidia
	Kernel modules: nouveau, nvidia

Head_on_a_Stick wrote:

X server logs are at ~/.local/share/xorg/Xorg.0.log
Is <Ctrl>+<Alt>+<Backspace> activated on your system?
https://wiki.archlinux.org/index.php/Ke … BBackspace

>>> Probably not since I did not do it. I will do this now.

Last edited by sergenikov (2015-02-14 17:50:14)

Head_on_a_Stick · 2015-02-14 17:50:06

If you have a look at the date that file was last modified I think you will find that log was left before we upgraded to version 1.16 of Xorg (with X running under the non-root user) -- the current logs are in the location I indicated.

sergenikov · 2015-02-14 17:52:08

Head_on_a_Stick wrote:

If you have a look at the date that file was last modified I think you will find that log was left before we upgraded to version 1.16 of Xorg (with X running under the non-root user) -- the current logs are in the location I indicated.

If I use ls -l the time stamp is as follows:

-rw-r--r--  1 root root             27K Feb 14 09:02 Xorg.0.log
-rw-r--r--  1 root root             37K Feb 13 23:26 Xorg.0.log.old

Is this what you mean? The time is the right time of the freeze yesterday. I am looking at the location you specified and I don't have xorg folder in there. Where else can they be?

Last edited by sergenikov (2015-02-14 18:00:49)

karol · 2015-02-14 17:58:26

Is your system up to date?
Are you running X as root? How exactly are you starting X?
What's the output of 'uname -a'?

Last edited by karol (2015-02-14 18:00:58)

sergenikov · 2015-02-14 18:03:55

karol wrote:

Are you running X as root? How exactly are you starting X?
What's the output of 'uname -a'?

I use lxdm to start X. I don't think I am running X as root. Lxdm logs me as me. My account only has a few sudo commands like poweroff and suspend, nothing more. I use root for pacman, etc.

[sergey@archone ~]$ uname -a
Linux archone 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:58:19 UTC 2014 i686 GNU/Linux

And no, my system is not up to date. I've been procrastinating update: with school did not have the time to read how to update Arch properly. Will have to do it this week (reading week).

Last edited by sergenikov (2015-02-14 18:05:19)

Head_on_a_Stick · 2015-02-14 18:06:32

Well you need to update your system -- you should do this before posting on the forums.

I must be wrong about the logs, but my /var/log file hasn't been modified since the end of last July...

sergenikov · 2015-02-14 18:08:14

Sorry about not updating the OS. I read this: https://bbs.archlinux.org/viewtopic.php?id=57855 , but still wanted to post. Will not do that next time.

sergenikov · 2015-02-14 18:10:43

Head_on_a_Stick wrote:

Well you need to update your system -- you should do this before posting on the forums.
I must be wrong about the logs, but my /var/log file hasn't been modified since the end of last July...

How can you tell that logs were not modified since July? I thought this would give a valid timestamp? Where are you finding this information?

-rw-r--r--  1 root root             37K Feb 13 23:26 Xorg.0.log.old

EDIT: Sorry, Head_on_a_Stick, I misread your post. Scratch this question out.

Last edited by sergenikov (2015-02-14 18:12:18)

sergenikov · 2015-02-14 18:49:33

Here is some output from journalctl right before reboot yesterday. I don't think there is anything in it. I was trying to install a package from AUR, but makepkg needed to resolve dependencies. My account cannot run pacman as sudo, hence the messages below. But otherwise, nothing that relates to the freeze.

Feb 13 22:42:36 archone su[3194]: pam_unix(su-l:session): session opened for user root by sergey(uid=1000)
Feb 13 22:42:50 archone su[3194]: pam_unix(su-l:session): session closed for user root
Feb 13 22:42:55 archone sudo[3246]: sergey : TTY=pts/0 ; PWD=/opt/aurbuilds/compton-git ; USER=root ; COMMAND=/usr/bin/pacman -S --asdeps libconfig
Feb 13 22:42:55 archone sudo[3246]: pam_unix(sudo:session): session opened for user root by sergey(uid=0)
Feb 13 22:43:00 archone sudo[3246]: pam_unix(sudo:session): session closed for user root
Feb 13 22:43:04 archone sudo[3287]: sergey : command not allowed ; TTY=pts/0 ; PWD=/opt/aurbuilds/compton-git ; USER=root ; COMMAND=/usr/bin/pacman -S --asdeps asciidoc
Feb 13 23:26:10 archone systemd-logind[215]: Power key pressed.
Feb 13 23:26:11 archone systemd-logind[215]: Powering Off...
Feb 13 23:26:11 archone systemd-logind[215]: System is powering down.
-- Reboot --

Head_on_a_Stick · 2015-02-14 19:24:01

sergenikov wrote:

My account cannot run pacman as sudo

Please elaborate on this.

rebootl · 2015-02-15 12:33:04

@Head_on_a_Stick, all: When using nvidia, X is started as root (automatically by xorg.wrap, see manpage). So, the logs are still under /var/log/... then.

Googling that error "(EE) [mi] EQ overflowing. Additional events " leads to e.g.:
https://devtalk.nvidia.com/default/topi … verflows-/
http://forums.gentoo.org/viewtopic-p-74 … ml#7475096

Which seems to indicate a bug/error in nvidia...

But yes, upgrade first.

Edit:

sergenikov wrote:
My account cannot run pacman as sudo
Please elaborate on this.

I think he configured it that way.

sergenikov wrote:

My account only has a few sudo commands like poweroff and suspend, nothing more. I use root for pacman, etc.

Last edited by rebootl (2015-02-15 12:37:25)

sergenikov · 2015-02-20 00:57:51

Thank you and sorry for a delay in reply - school.

Yes, sudo is configured to run only a few commands. I have add makepkg to it, I guess so that I don't run it as root. I haven't been able to find anything in logs in X and did not have any other freezes so far. If it happens again, I will try to change Nvidia driver to a different closest version (newer or older), That's what linked posts above suggest to do in this situation. But nothing else I can think of for now. Thank you for your help on this.

Last edited by sergenikov (2015-02-20 01:01:38)

Arch Linux

#1 2015-02-14 17:17:49

Xorg freezing

#2 2015-02-14 17:29:24

Re: Xorg freezing

#3 2015-02-14 17:41:28

Re: Xorg freezing

#4 2015-02-14 17:49:22

Re: Xorg freezing

#5 2015-02-14 17:50:06

Re: Xorg freezing

#6 2015-02-14 17:52:08

Re: Xorg freezing

#7 2015-02-14 17:58:26

Re: Xorg freezing

#8 2015-02-14 18:03:55

Re: Xorg freezing

#9 2015-02-14 18:06:32

Re: Xorg freezing

#10 2015-02-14 18:08:14

Re: Xorg freezing

#11 2015-02-14 18:10:43

Re: Xorg freezing

#12 2015-02-14 18:49:33

Re: Xorg freezing

#13 2015-02-14 19:24:01

Re: Xorg freezing

#14 2015-02-15 12:33:04

Re: Xorg freezing

#15 2015-02-20 00:57:51

Re: Xorg freezing

Board footer