Bug 93593 - Random X crashes with intel drivers and dual monitor setup
Summary: Random X crashes with intel drivers and dual monitor setup
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-05 14:38 UTC by sven
Modified: 2016-02-02 16:55 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (34.04 KB, text/plain)
2016-01-05 14:38 UTC, sven
no flags Details

Description sven 2016-01-05 14:38:30 UTC
Created attachment 120815 [details]
Xorg.0.log

My Xserver randomly crashes on my Thinkpad T540p. I have no idea how to approach this issue.

------

Additional information:

* Distro: Fedora 23
* `uname -a`
  * Linux svenwltr 4.2.8-300.fc23.x86_64 #1 SMP Tue Dec 15 16:49:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
* Notebook has Nvidia Optimus technology
* `lspci |grep -E "VGA|3D"`
  * 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
  * 01:00.0 VGA compatible controller: NVIDIA Corporation GK208M [GeForce GT 730M] (rev a1)
* `dnf info xorg-x11-drv-intel`
  * Version     : 2.99.917
  * Release     : 16.20150729.fc23

------

Part of /var/log/Xorg.0.log:

[ 13380.997] (EE) 
[ 13380.998] (EE) Backtrace:
[ 13380.998] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59afb9]
[ 13380.998] (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7ff83ef04b1f]
[ 13380.999] (EE) 2: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xaa38) [0x7ff839b0e1a8]
[ 13380.999] (EE) 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0xbe27) [0x7ff839b109a7]
[ 13380.999] (EE) 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x149ad) [0x7ff839b21ffd]
[ 13381.000] (EE) 5: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x66e79) [0x7ff839bc69e9]
[ 13381.000] (EE) 6: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x6904a) [0x7ff839bca53a]
[ 13381.000] (EE) 7: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x3eda7) [0x7ff839b74f97]
[ 13381.000] (EE) 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x1f7bf) [0x7ff839b3789f]
[ 13381.001] (EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (_init+0x1f9c2) [0x7ff839b38082]
[ 13381.001] (EE) 10: /usr/libexec/Xorg (DamageRegionAppend+0x3551) [0x524d81]
[ 13381.001] (EE) 11: /usr/libexec/Xorg (SyncVerifyFence+0x1d89) [0x4d7a39]
[ 13381.001] (EE) 12: /usr/libexec/Xorg (SyncVerifyFence+0x36c5) [0x4daf25]
[ 13381.001] (EE) 13: /usr/libexec/Xorg (SendErrorToClient+0x2df) [0x4369bf]
[ 13381.001] (EE) 14: /usr/libexec/Xorg (remove_fs_handlers+0x453) [0x43a9e3]
[ 13381.002] (EE) 15: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7ff83eef0580]
[ 13381.002] (EE) 16: /usr/libexec/Xorg (_start+0x29) [0x424ce9]
[ 13381.002] (EE) 17: ? (?+0x29) [0x29]
[ 13381.002] (EE) 
[ 13381.002] (EE) Segmentation fault at address 0x0
[ 13381.002] (EE) 
Fatal server error:
[ 13381.002] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 13381.002] (EE) 
[ 13381.002] (EE) 
Please consult the Fedora Project support 
         at http://wiki.x.org
 for help. 
[ 13381.002] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 13381.002] (EE) 
[ 13381.002] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 13381.034] (EE) Server terminated with error (1). Closing log file.
Comment 1 sven 2016-01-18 10:04:01 UTC
This is still a problem with kernel `Linux svenwltr 4.3.3-300.fc23.x86_64 #1 SMP Tue Jan 5 23:31:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux`.
Comment 2 sven 2016-02-02 09:53:39 UTC
bump
Comment 3 Chris Wilson 2016-02-02 10:21:14 UTC
Symptoms match but without a usable stacktrace, it really is just guessing:


commit 7817949314a21293c8bc34dec214b42932b19aaf
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Jan 27 10:54:46 2016 +0000

    sna/dri2: Avoiding marking a pending-signal on a dead Drawable
    
    If the Drawable is gone, we cannot send it a frame-complete signal, and
    in particular we cannot continue the pending flip-chain.
    
    References: https://bugs.freedesktop.org/show_bug.cgi?id=93844
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Comment 4 sven 2016-02-02 16:55:19 UTC
Doesn't look like there will be a new release, soon? But thanks for your help.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.