Frozen desktop, minimal or no response from keyboard or mouse

Asked by brad haack on 2014-11-18

Very often (about once/day) I'm experiencing a frozen desktop. minimal response from keyboard or mouse, usually degrades to no response. No response from ^-alt-F1 or ^-alt-esc. Here's today's Xorg.0.log.old:

[ 47.809] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 47.809] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 3682.886] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 3683.260] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 3735.480] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 3735.480] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 7662.648] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 7662.999] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 7807.242] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 7807.242] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 9095.040] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 9095.404] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 9896.981] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 9896.981] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
(EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7666fe3]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
(EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) [0xb6e1698f]
(EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
(EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
(EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
(EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
(EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
(EE) 10: /usr/bin/X (0xb74df000+0x12d650) [0xb760c650]
(EE) 11: /usr/bin/X (0xb74df000+0x4ebb0) [0xb752dbb0]
(EE) 12: /usr/bin/X (DeliverRawEvent+0x65) [0xb752ddb5]
(EE) 13: /usr/bin/X (0xb74df000+0x131730) [0xb7610730]
(EE) 14: /usr/bin/X (0xb74df000+0x155a07) [0xb7634a07]
(EE) 15: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7667414]
(EE) 16: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
(EE) 17: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
(EE) 18: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
(EE) 19: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
(EE) 20: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
(EE) 21: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
(EE) 22: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
(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.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7686eaf]
(EE) 1: /usr/bin/X (mieqEnqueue+0xe5) [0xb7666eb5]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb75342ed]
(EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb756da8b]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6e12000+0x498f) [0xb6e1698f]
(EE) 5: /usr/bin/X (0xb74df000+0x7e0f5) [0xb755d0f5]
(EE) 6: /usr/bin/X (0xb74df000+0xa8dfb) [0xb7587dfb]
(EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
(EE) 8: /usr/bin/X (0xb74df000+0x1ac170) [0xb768b170]
(EE) 9: (vdso) (__kernel_sigreturn+0x0) [0xb74bc400]
(EE) 10: /usr/bin/X (0xb74df000+0x13163d) [0xb761063d]
(EE) 11: /usr/bin/X (0xb74df000+0x15d2ba) [0xb763c2ba]
(EE) 12: /usr/bin/X (mieqProcessDeviceEvent+0x1d6) [0xb76673e6]
(EE) 13: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb766753d]
(EE) 14: /usr/bin/X (ProcessInputEvents+0x14) [0xb755d294]
(EE) 15: /usr/bin/X (0xb74df000+0x3c9ac) [0xb751b9ac]
(EE) 16: /usr/bin/X (0xb74df000+0x40ce5) [0xb751fce5]
(EE) 17: /usr/bin/X (0xb74df000+0x2aa3e) [0xb7509a3e]
(EE) 18: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb70b6a83]
(EE) 19: /usr/bin/X (0xb74df000+0x2aa74) [0xb7509a74]
(EE)
[ 11472.953] [mi] EQ processing has resumed after 132 dropped events.
[ 11473.029] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu xorg Edit question
Assignee:
No assignee Edit question
Last query:
2015-03-09
Last reply:
2015-01-17
brad haack (bradhaack-g) said : #1

Using xubuntu 14.04

What is the output of:

sudo lshw -C display; lsb_release -a; uname -a

Thanks

brad haack (bradhaack-g) said : #3

dt1:sudo lshw -C display
  *-display
       description: VGA compatible controller
       product: 2nd Generation Core Processor Family Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:43 memory:fe000000-fe3fffff memory:c0000000-cfffffff ioport:f000(size=64)

dt1:lsb_release -a
LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch:core-4.1-ia32:core-4.1-noarch:security-4.0-ia32:security-4.0-noarch:security-4.1-ia32:security-4.1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty

dt1:uname -a
Linux dt1 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:31:23 UTC 2014 i686 i686 i686 GNU/Linux

Try the Intel driver installer. Omgubuntu has a guide.

brad haack (bradhaack-g) said : #5

Thanks. Installing now. I also updated the bios. I'll give it a couple of days & report back.

brad haack (bradhaack-g) said : #6

installed intel driver, rebooted. Similar. This time when it stopped responding I waited patiently without trying anything and it recovered. Here's the bottom of Xorg.0.log

[ 69.761] (II) intel(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
[ 69.761] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 69.761] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 1691.210] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 1691.571] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 1800.431] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 1800.431] (II) intel(0): switch to mode 1680x1050@59.9 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x4f) [0xb7757eaf]
(EE) 1: /usr/bin/X (mieqEnqueue+0x213) [0xb7737fe3]
(EE) 2: /usr/bin/X (QueuePointerEvents+0x6d) [0xb76052ed]
(EE) 3: /usr/bin/X (xf86PostMotionEventM+0x24b) [0xb763ea8b]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0xb6ee3000+0x498f) [0xb6ee798f]
(EE) 5: /usr/bin/X (0xb75b0000+0x7e0f5) [0xb762e0f5]
(EE) 6: /usr/bin/X (0xb75b0000+0xa8dfb) [0xb7658dfb]
(EE) 7: (vdso) (__kernel_sigreturn+0x0) [0xb758d400]
(EE) 8: /usr/bin/X (0xb75b0000+0x430a8) [0xb75f30a8]
(EE) 9: /usr/bin/X (0xb75b0000+0x49d1c) [0xb75f9d1c]
(EE) 10: /usr/bin/X (0xb75b0000+0x131265) [0xb76e1265]
(EE) 11: /usr/bin/X (0xb75b0000+0x131963) [0xb76e1963]
(EE) 12: /usr/bin/X (0xb75b0000+0x155a07) [0xb7705a07]
(EE) 13: /usr/bin/X (mieqProcessDeviceEvent+0x204) [0xb7738414]
(EE) 14: /usr/bin/X (mieqProcessInputEvents+0xfd) [0xb773853d]
(EE) 15: /usr/bin/X (ProcessInputEvents+0x14) [0xb762e294]
(EE) 16: /usr/bin/X (0xb75b0000+0x3c90d) [0xb75ec90d]
(EE) 17: /usr/bin/X (0xb75b0000+0x40ce5) [0xb75f0ce5]
(EE) 18: /usr/bin/X (0xb75b0000+0x2aa3e) [0xb75daa3e]
(EE) 19: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xb7187a83]
(EE) 20: /usr/bin/X (0xb75b0000+0x2aa74) [0xb75daa74]
(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.
[ 21724.740] [mi] EQ processing has resumed after 58 dropped events.
[ 21724.940] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.

Launchpad Janitor (janitor) said : #7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

brad haack (bradhaack-g) said : #8

Seriously, expired? I never got an answer. I still have the problem, altho it may be different now. I still get a frozen state every couple of days, but now there is nothing unusual in Xorg.log

brad haack (bradhaack-g) said : #9

Still having this problem. Seems to be less frequent now than before the driver update. Still about once or twice a week. Nothing unusual in Xorg.log anymore.
The most recent 'lock-up' I tried to get a console open, & got my user & pw in, but never got a shell prompt.
Let me know if there are any other logs I should look at or post here.
I'm interested in any workarounds. If we can't make it work with this graphics card and monitor I'd even consider hardware changes.

Launchpad Janitor (janitor) said : #10

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

brad haack (bradhaack-g) said : #11

On January 1, 2015 3:52:18 AM MST, Launchpad Janitor <email address hidden> wrote:
>Your question #257827 on xorg in Ubuntu changed:
>https://answers.launchpad.net/ubuntu/+source/xorg/+question/257827
>
> Status: Open => Expired
>
>Launchpad Janitor expired the question:
>This question was expired because it remained in the 'Open' state
>without activity for the last 15 days.

brad haack (bradhaack-g) said : #12

Any help out there? What do I need? New display? New graphics card? New OS?

Launchpad Janitor (janitor) said : #13

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

brad haack (bradhaack-g) said : #14

Bumping to keep it open

Can you help with this problem?

Provide an answer of your own, or ask brad haack for more information if necessary.

To post a message you must log in.