Bug 1152259 - X freezes/crashes
Summary: X freezes/crashes
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-13 17:53 UTC by Cristian Ciupitu
Modified: 2015-06-29 22:53 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:53:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/var/log/Xorg.0.log.old (54.46 KB, text/plain)
2014-10-13 17:53 UTC, Cristian Ciupitu
no flags Details
/etc/X11/xorg.conf.d/00-keyboard.conf (232 bytes, text/plain)
2014-10-13 17:54 UTC, Cristian Ciupitu
no flags Details
/etc/X11/xorg.conf.d/99-intel-hd4000.conf (1.18 KB, text/plain)
2014-10-13 17:54 UTC, Cristian Ciupitu
no flags Details
/var/log/Xorg.0.log.old-2 (34.30 KB, text/plain)
2014-10-14 12:58 UTC, Cristian Ciupitu
no flags Details
/var/log/Xorg.0.log-3 (41.06 KB, text/plain)
2014-10-21 16:52 UTC, Cristian Ciupitu
no flags Details
/sys/kernel/debug/dri/0/i915_opregion (1.52 KB, application/x-xz)
2014-10-21 16:53 UTC, Cristian Ciupitu
no flags Details
/sys/kernel/debug/dri/0/i915_error_state after the hang (87.90 KB, application/x-xz)
2014-10-21 16:54 UTC, Cristian Ciupitu
no flags Details
intel_reg_dumper (14.75 KB, text/plain)
2014-10-21 16:56 UTC, Cristian Ciupitu
no flags Details

Description Cristian Ciupitu 2014-10-13 17:53:57 UTC
Created attachment 946527 [details]
/var/log/Xorg.0.log.old

Description of problem:
X freezes/crashes out of the sudden, although for some reason the mouse
pointer still moves. ABRT wasn't able to get any information:

    19:56:51 hermes sh[1276]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input
    19:56:53 hermes sh[1276]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input
    19:57:09 hermes sh[1276]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input
    19:57:11 hermes sh[1276]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input
    19:57:13 hermes sh[1276]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input
    19:57:15 hermes sh[1276]: abrt-watch-log: Warning, '/usr/bin/abrt-dump-xorg' did not process its input

The video card is an Intel HD 4000 connected to a monitor via
DisplayPort, the mouse is a wired Dell and the keyboard is a wireless HP
connected to an USB dongle.


Version-Release number of selected component (if applicable):
xorg-x11-apps-7.7-7.fc20.x86_64
xorg-x11-drv-evdev-2.8.4-1.fc20.x86_64
xorg-x11-drv-intel-2.21.15-7.fc20.x86_64
xorg-x11-drv-keyboard-1.7.0-2.fc20.x86_64
xorg-x11-drv-modesetting-0.8.0-2.fc20.x86_64
xorg-x11-drv-mouse-1.9.0-2.fc20.x86_64
xorg-x11-drv-wacom-0.23.0-5.fc20.x86_64
xorg-x11-glamor-0.5.1-3.20140115gitfb4d046c.fc20.x86_64
xorg-x11-server-common-1.14.4-11.fc20.x86_64
xorg-x11-server-utils-7.7-6.fc20.x86_64
xorg-x11-server-Xorg-1.14.4-11.fc20.x86_64
xorg-x11-server-Xvfb-1.14.4-11.fc20.x86_64
xorg-x11-utils-7.5-12.fc20.x86_64
xorg-x11-xauth-1.0.9-1.fc20.x86_64
xorg-x11-xbitmaps-1.1.1-6.fc20.noarch
xorg-x11-xinit-1.3.4-1.fc20.x86_64
xorg-x11-xkb-extras-7.7-8.fc20.x86_64
xorg-x11-xkb-utils-7.7-8.fc20.x86_64


How reproducible:
It happened to me twice.


Steps to Reproduce:
1. I have no idea. The last time I it happened, I was reading a PDF with
   evince.


Actual results:
(EE) [mi] EQ overflowing.  Additional events will be discarded until existing events are processed.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/bin/Xorg (mieqEnqueue+0x22b) [0x5835db]
(EE) 1: /usr/bin/Xorg (QueuePointerEvents+0x52) [0x4513f2]
(EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (_init+0x2d4d) [0x7fb639700d1d]
(EE) 3: /usr/bin/Xorg (DPMSSupported+0xe8) [0x48b408]
(EE) 4: /usr/bin/Xorg (xf86SerialModemClearBits+0x260) [0x4b4980]
(EE) 5: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7fb6424366cf]
(EE) 6: /lib64/libpthread.so.0 (__read_nocancel+0x24) [0x7fb6424357f4]
(EE) 7: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x43e8f) [0x7fb63ccc379f]
(EE) 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x44980) [0x7fb63ccc4ae0]
(EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x330bc) [0x7fb63cca18ac]
(EE) 10: /usr/bin/Xorg (BlockHandler+0x44) [0x43e444]
(EE) 11: /usr/bin/Xorg (WaitForSomething+0x134) [0x46a7d4]
(EE) 12: /usr/bin/Xorg (SendErrorToClient+0x111) [0x439ff1]
(EE) 13: /usr/bin/Xorg (_init+0x3afa) [0x42bfaa]
(EE) 14: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7fb641068d65]
(EE) 15: /usr/bin/Xorg (_start+0x29) [0x428be5]
(EE) 16: ? (?+0x29) [0x29]
(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.

Expected results:
No errors, no freezes.


Additional info:
# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09)
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09)
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
00:1c.2 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 [8086:1e14] (rev c4)
00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4)
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation Z77 Express Chipset LPC Controller [8086:1e44] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
03:00.0 PCI bridge [0604]: Integrated Technology Express, Inc. Device [1283:8892] (rev 30)
05:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 04)

Comment 1 Cristian Ciupitu 2014-10-13 17:54:27 UTC
Created attachment 946528 [details]
/etc/X11/xorg.conf.d/00-keyboard.conf

Comment 2 Cristian Ciupitu 2014-10-13 17:54:52 UTC
Created attachment 946529 [details]
/etc/X11/xorg.conf.d/99-intel-hd4000.conf

Comment 3 Cristian Ciupitu 2014-10-13 17:57:02 UTC
Forgot to mention that the kernel was kernel-3.16.4-200.fc20.x86_64 and
it was booted with:

    initrd=\865b8ff295c29b42a3eef3ecebbeea5a\3.16.4-200.fc20.x86_64\initrd root=UUID=ca0414e3-a3f3-4a12-9bf2-47a528bea489 ro resume=UUID=e5c87795-39af-46d4-b2ea-3980db1c0e54 vconsole.font=latarcyrheb-sun16 video=VGA-1:d intel_iommu=on rhgb quiet

Comment 4 Cristian Ciupitu 2014-10-14 12:58:55 UTC
Created attachment 946873 [details]
/var/log/Xorg.0.log.old-2

It happened again with kernel-3.16.5-200.fc20.x86_64.

Comment 5 Cristian Ciupitu 2014-10-21 16:48:27 UTC
It happened twice again with kernel-3.16.6-200.fc20.x86_64.

Comment 6 Cristian Ciupitu 2014-10-21 16:52:02 UTC
Created attachment 949046 [details]
/var/log/Xorg.0.log-3

Comment 7 Cristian Ciupitu 2014-10-21 16:53:17 UTC
Created attachment 949048 [details]
/sys/kernel/debug/dri/0/i915_opregion

Comment 8 Cristian Ciupitu 2014-10-21 16:54:10 UTC
Created attachment 949049 [details]
/sys/kernel/debug/dri/0/i915_error_state after the hang

Comment 9 Cristian Ciupitu 2014-10-21 16:56:20 UTC
Created attachment 949050 [details]
intel_reg_dumper

Comment 10 Fedora End Of Life 2015-05-29 13:04:40 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.

Comment 11 Fedora End Of Life 2015-06-29 22:53:01 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


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