You are not logged in.

#1 2021-06-30 03:54:20

afontenot
Member
Registered: 2020-11-26
Posts: 5

Getting a partially replicable X.org crash - can anyone help me debug?

I think the issue is probably with the Intel graphics driver. Various graphics-intensive things like opening a game in full screen will occasionally crash the X.org session. Once something starts crashing the X.org session, doing it again will crash the X.org session until I reboot, with the exact same traceback. The exact timing doesn't seem precise, though. The game will usually run for a few seconds before X.org crashes, or crash X.org when I alt-tab to a different program. If the game starts successfully and runs for more than a minute, I can play for hours with no crashes.

I've also seen a few kernel panics in recent months. They seem to occur when I'm using a lot of memory (Intel graphics share memory with the system) and doing something that utilizes the graphics chip.

System: Intel Core i7-2630QM CPU @ 2.00GHz - with Intel HD Graphics 3000

The issue doesn't seem to be game specific, but one I've been playing a lot lately and therefore experiencing the issue with is Celeste (the native Linux build, not running under Wine).

I'm not sure how to confirm whether the issue is with the Intel driver or in X.org, and where exactly I should report the issue and what debugging information would be useful.

Here are the tracebacks I have. From Xorg.0.log:

[158625.015] (EE) Backtrace:
[158625.019] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x53) [0x555751583fd3]
[158625.020] (EE) 1: /usr/lib/Xorg (0x55575143d000+0x151df5) [0x55575158edf5]
[158625.020] (EE) 2: /usr/lib/libc.so.6 (0x7f939bc9a000+0x3cda0) [0x7f939bcd6da0]
[158625.020] (EE) 3: /usr/lib/Xorg (0x55575143d000+0xc1fde) [0x5557514fefde]
[158625.020] (EE) 4: /usr/lib/Xorg (0x55575143d000+0x1b9611) [0x5557515f6611]
[158625.020] (EE) 5: /usr/lib/Xorg (0x55575143d000+0xd2a72) [0x55575150fa72]
[158625.020] (EE) 6: /usr/lib/Xorg (0x55575143d000+0xd9241) [0x555751516241]
[158625.020] (EE) 7: /usr/lib/Xorg (0x55575143d000+0xdabac) [0x555751517bac]
[158625.020] (EE) 8: /usr/lib/Xorg (0x55575143d000+0xd72ec) [0x5557515142ec]
[158625.020] (EE) 9: /usr/lib/Xorg (0x55575143d000+0x3a195) [0x555751477195]
[158625.020] (EE) 10: /usr/lib/libc.so.6 (__libc_start_main+0xd5) [0x7f939bcc1b25]
[158625.020] (EE) 11: /usr/lib/Xorg (_start+0x2e) [0x5557514775de]
[158625.020] (EE) 
[158625.020] (EE) Segmentation fault at address 0x20
[158625.020] (EE) 
Fatal server error:
[158625.020] (EE) Caught signal 11 (Segmentation fault). Server aborting
[158625.020] (EE) 
[158625.020] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[158625.020] (EE) Please also check the log file at "/home/adam/.local/share/xorg/Xorg.0.log" for additional information.
[158625.020] (EE) 
[158625.021] (II) AIGLX: Suspending AIGLX clients for VT switch
[158625.069] (EE) Server terminated with error (1). Closing log file.

And here is a more extensive traceback from a crashdump created by systemd:

systemd-coredump[63171]: Process 30436 (Xorg) of user 1000 dumped core.

Stack trace of thread 30436:
#0  0x00007f939bcd6d22 raise (libc.so.6 + 0x3cd22)
#1  0x00007f939bcc0862 abort (libc.so.6 + 0x26862)
#2  0x000055575158775a OsAbort (Xorg + 0x14a75a)
#3  0x0000555751589221 FatalError (Xorg + 0x14c221)
#4  0x000055575158ee59 n/a (Xorg + 0x151e59)
#5  0x00007f939bcd6da0 __restore_rt (libc.so.6 + 0x3cda0)
#6  0x00005557514fefde n/a (Xorg + 0xc1fde)
#7  0x00005557515f6611 n/a (Xorg + 0x1b9611)
#8  0x000055575150fa72 n/a (Xorg + 0xd2a72)
#9  0x0000555751516241 n/a (Xorg + 0xd9241)
#10 0x0000555751517bac n/a (Xorg + 0xdabac)
#11 0x00005557515142ec n/a (Xorg + 0xd72ec)
#12 0x0000555751477195 n/a (Xorg + 0x3a195)
#13 0x00007f939bcc1b25 __libc_start_main (libc.so.6 + 0x27b25)
#14 0x00005557514775de _start (Xorg + 0x3a5de)

Stack trace of thread 30437:
#0  0x00007f939bb948ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
#1  0x00007f939bb8e270 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf270)
#2  0x00007f939aedab90 n/a (intel_drv.so + 0xb0b90)
#3  0x00007f939bb88259 start_thread (libpthread.so.0 + 0x9259)
#4  0x00007f939bd985e3 __clone (libc.so.6 + 0xfe5e3)

Stack trace of thread 30438:
#0  0x00007f939bb948ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
#1  0x00007f939bb8e270 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf270)
#2  0x00007f939aedab90 n/a (intel_drv.so + 0xb0b90)
#3  0x00007f939bb88259 start_thread (libpthread.so.0 + 0x9259)
#4  0x00007f939bd985e3 __clone (libc.so.6 + 0xfe5e3)

Stack trace of thread 30439:
#0  0x00007f939bb948ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
#1  0x00007f939bb8e270 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf270)
#2  0x00007f939aedab90 n/a (intel_drv.so + 0xb0b90)
#3  0x00007f939bb88259 start_thread (libpthread.so.0 + 0x9259)
#4  0x00007f939bd985e3 __clone (libc.so.6 + 0xfe5e3)

Stack trace of thread 30444:
#0  0x00007f939bb948ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
#1  0x00007f939bb8e270 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf270)
#2  0x00007f93986e518c n/a (i965_dri.so + 0x23f18c)
#3  0x00007f93986e4b48 n/a (i965_dri.so + 0x23eb48)
#4  0x00007f939bb88259 start_thread (libpthread.so.0 + 0x9259)
#5  0x00007f939bd985e3 __clone (libc.so.6 + 0xfe5e3)

Stack trace of thread 30446:
#0  0x00007f939bb948ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
#1  0x00007f939bb8e270 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf270)
#2  0x00007f93986e518c n/a (i965_dri.so + 0x23f18c)
#3  0x00007f93986e4b48 n/a (i965_dri.so + 0x23eb48)
#4  0x00007f939bb88259 start_thread (libpthread.so.0 + 0x9259)
#5  0x00007f939bd985e3 __clone (libc.so.6 + 0xfe5e3)

Stack trace of thread 30445:
#0  0x00007f939bb948ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
#1  0x00007f939bb8e270 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf270)
#2  0x00007f93986e518c n/a (i965_dri.so + 0x23f18c)
#3  0x00007f93986e4b48 n/a (i965_dri.so + 0x23eb48)
#4  0x00007f939bb88259 start_thread (libpthread.so.0 + 0x9259)
#5  0x00007f939bd985e3 __clone (libc.so.6 + 0xfe5e3)

Stack trace of thread 30443:
#0  0x00007f939bb948ca __futex_abstimed_wait_common64 (libpthread.so.0 + 0x158ca)
#1  0x00007f939bb8e270 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf270)
#2  0x00007f93986e518c n/a (i965_dri.so + 0x23f18c)
#3  0x00007f93986e4b48 n/a (i965_dri.so + 0x23eb48)
#4  0x00007f939bb88259 start_thread (libpthread.so.0 + 0x9259)
#5  0x00007f939bd985e3 __clone (libc.so.6 + 0xfe5e3)

Offline

#2 2021-06-30 04:00:34

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Getting a partially replicable X.org crash - can anyone help me debug?

First step would be to remove the Intel driver and use native modesetting: it is almost always more stable.

If that doesn't work, the full Xorg.log would help.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2021-07-01 03:08:59

afontenot
Member
Registered: 2020-11-26
Posts: 5

Re: Getting a partially replicable X.org crash - can anyone help me debug?

jasonwryan wrote:

First step would be to remove the Intel driver and use native modesetting: it is almost always more stable.

If that doesn't work, the full Xorg.log would help.

Thanks for the reply. I will give that a go, although unfortunately the fact that this bug isn't 100% replicable means that I will have to try it for a few days before I know that it's made a difference.

Unfortunately, performance seems slightly worse with the modesetting driver. Possibly placebo, I'll have to check some framerates. I will have to live with it if it fixes the crashing issue and I can't find something precise to report to the upstream developers, but it's too bad as I've used the Intel driver on this install for 8 years now with no issues until the last few months.

Quick side node, for any one who finds this issue with a search. Removing the Intel driver led to X.org not starting for me, with a "no drivers available" error. I could see from the log that it wasn't even trying anything but the Intel driver, which told me that something was telling X.org to use the Intel driver for this screen. I didn't have any reference to Intel in my configuration files in /etc/X11/. I eventually found the problem in /usr/share/X11/xorg.conf.d/20-intel.conf. I don't think I created this file (I would have put the config in /etc/X11), but it wasn't currently owned by any package, so I deleted it. That fixed the problem. Maybe it was created or left behind by something I used previously.

Offline

Board footer

Powered by FluxBB