Bug 91412 - Segfault (perhaps due to low memory?)
Summary: Segfault (perhaps due to low memory?)
Status: NEEDINFO
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-21 13:14 UTC by ggb12.10.Toranaga-San
Modified: 2015-07-29 21:02 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
A different backtrace (12.11 KB, text/plain)
2015-07-22 14:38 UTC, ggb12.10.Toranaga-San
no flags Details
Backtrace from Xorg (72.31 KB, text/plain)
2015-07-22 17:10 UTC, ggb12.10.Toranaga-San
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description ggb12.10.Toranaga-San 2015-07-21 13:14:02 UTC
I am using this version of X11 (Xorg -version)

X.Org X Server 1.17.2
Release Date: 2015-06-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.0.4-2-ARCH x86_64 
Current Operating System: Linux myhostname 4.1.2-2-ARCH #1 SMP PREEMPT Wed Jul 15 08:30:32 UTC 2015 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=7d34dba7-6a7e-4a72-85e4-09006e2f257c rw quiet
Build Date: 17 July 2015  05:38:19PM
 
Current version of pixman: 0.32.6
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.

This seems to be related to the intel driver, I have this version installed:

xf86-video-intel 1:2.99.917+364+gb24e758


I get the following segfault:

Jul 21 14:45:49 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:45:49 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:46:45 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:46:48 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:47:20 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:47:20 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:47:37 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:47:38 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:49:57 myhostname chromium.desktop[17722]: [17722:17745:0721/144957:ERROR:channel.cc(300)] RawChannel read error (connection broken)
Jul 21 14:50:05 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:50:05 myhostname chromium.desktop[17722]: libpng warning: iCCP: known incorrect sRGB profile
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE)
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) Backtrace:
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 0: /usr/lib/xorg-server/Xorg (OsLookupColor+0x139) [0x596d09]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 1: /usr/lib/libc.so.6 (__restore_rt+0x0) [0x7fcff3ce35af]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 2: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x142a4) [0x7fcfee8a69b4]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x156bf) [0x7fcfee8a91cf]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x242df) [0x7fcfee8c698f]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x24539) [0x7fcfee8c6ee9]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x3254a) [0x7fcfee8e2a6a]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x351bb) [0x7fcfee8e84eb]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x49142) [0x7fcfee9105d2]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (_init+0x49662) [0x7fcfee910f02]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 10: /usr/lib/xorg-server/Xorg (DamageRegionAppend+0x3783) [0x5214e3]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 11: /usr/lib/xorg-server/Xorg (SendGraphicsExpose+0xeb3) [0x4366a3]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 12: /usr/lib/xorg-server/Xorg (SendErrorToClient+0x2ff) [0x438e4f]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 13: /usr/lib/xorg-server/Xorg (remove_fs_handlers+0x41b) [0x43cf4b]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 14: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7fcff3cd0790]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 15: /usr/lib/xorg-server/Xorg (_start+0x29) [0x427319]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) 16: ? (?+0x29) [0x29]
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE)
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) Segmentation fault at address 0x7fd0089003e0
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE)
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: Fatal server error:
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE)
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE)
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: Please consult the The X.Org Foundation support
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: at http://wiki.x.org
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: for help.
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) Please also check the log file at "/home/christoph/.local/share/xorg/Xorg.0.log" for additional information.
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE)
Jul 21 14:51:57 myhostname /usr/lib/gdm/gdm-x-session[17149]: (II) AIGLX: Suspending AIGLX clients for VT switch
Jul 21 14:51:58 myhostname /usr/lib/gdm/gdm-x-session[17149]: (EE) Server terminated with error (1). Closing log file.

This might be due to low memory, but I am not sure. I wasn't doing anything at the time when the error occured, just watching a youtube video without interacting with my machine.

Maybe this is related?

http://forums.fedoraforum.org/showthread.php?t=303183
Comment 1 ggb12.10.Toranaga-San 2015-07-21 13:15:54 UTC
Maybe it is related to this as well (though it is marked closed?)

https://bugs.freedesktop.org/show_bug.cgi?id=87207
Comment 2 Chris Wilson 2015-07-21 13:17:29 UTC
That backtrace doesn't tell us anything. Try addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x7fcfee8a69b4
Comment 3 ggb12.10.Toranaga-San 2015-07-21 13:23:07 UTC
> addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so -i 0x7fcfee8a69b4
??:0

Same thing for all each other address.
Comment 4 ggb12.10.Toranaga-San 2015-07-22 14:38:45 UTC
Created attachment 117298 [details]
A different backtrace

I compiled the intel driver with debugging flags enabled. I saw another segfault, presumably due to the same cause as above. This line might be interesting:

Jul 22 16:26:35 myhostname /usr/lib/gdm/gdm-x-session[885]: (EE) __kgem_retire_requests_upto:3185 assertion 'tmp->ring == rq->ring' failed

Does this help at all?
Comment 5 Chris Wilson 2015-07-22 15:02:32 UTC
That is quite suspect. Can you please extract the full Xorg.0.log?
Comment 6 ggb12.10.Toranaga-San 2015-07-22 15:31:40 UTC
I am afraid I can't. The X server is apparently restarted a couple of times and I guess the lockfile is overwritten at some point?! The output is from "journalctl -xe". I'd be happy to provide you with the entire file, but that is about 5M in size... Is there anything else I can do?
Comment 7 Chris Wilson 2015-07-22 15:36:54 UTC
Try something like journalctl _COMM=Xorg (where that has to match the executable name used by X on your system).
Comment 8 ggb12.10.Toranaga-San 2015-07-22 17:10:05 UTC
Created attachment 117299 [details]
Backtrace from Xorg

I was able to salvage some data like this:

journalctl _SYSTEMD_UNIT=gdm.service

This is from the second occurrence (at Jul 22 16:26:35). You can see that the server is restarted 10 seconds later.
Comment 9 Chris Wilson 2015-07-29 21:02:32 UTC
Those logs are not complete and don't contain anything useful. But you are missing

commit 41f401ae27ee753d66aae341be60b27167bc5b62
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Sat Jun 27 20:24:45 2015 +0100

    sna/dri2: Early return for empty DRI2CopyRegion

which does prevent one related crash.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct.