Bug 91839 - Caught signal 11 (Segmentation fault). Server aborting
Summary: Caught signal 11 (Segmentation fault). Server aborting
Status: RESOLVED DUPLICATE of bug 91607
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-01 15:40 UTC by mikhail.v.gavrilov
Modified: 2015-09-01 15:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
system.log (798.68 KB, text/plain)
2015-09-01 15:40 UTC, mikhail.v.gavrilov 		no flags Details
Xorg.log (27.27 KB, text/plain)
2015-09-01 15:41 UTC, mikhail.v.gavrilov 		no flags Details
View All

Description mikhail.v.gavrilov 2015-09-01 15:40:03 UTC 
Created attachment 118034 [details]
system.log

[   723.458] (EE) 
[   723.458] (EE) Backtrace:
[   723.466] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59ab89]
[   723.469] (EE) 1: /lib64/libc.so.6 (__restore_rt+0x0) [0x7fb23f3e1b1f]
[   723.469] (EE) 2: /usr/libexec/Xorg (FlushAllOutput+0xa6) [0x59a0c6]
[   723.469] (EE) 3: /usr/libexec/Xorg (SendErrorToClient+0x15e) [0x43a3ee]
[   723.470] (EE) 4: /usr/libexec/Xorg (remove_fs_handlers+0x41b) [0x43e68b]
[   723.470] (EE) 5: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7fb23f3cd580]
[   723.471] (EE) 6: /usr/libexec/Xorg (_start+0x29) [0x428a49]
[   723.472] (EE) 7: ? (?+0x29) [0x29]
[   723.472] (EE) 
[   723.472] (EE) Segmentation fault at address 0x49705a0
[   723.472] (EE) 
Fatal server error:
[   723.472] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   723.472] (EE) 
[   723.472] (EE)
Comment 1 mikhail.v.gavrilov 2015-09-01 15:41:59 UTC 
Created attachment 118035 [details]
Xorg.log
Comment 2 Chris Wilson 2015-09-01 15:43:06 UTC 

*** This bug has been marked as a duplicate of bug 91607 ***

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.