You are not logged in.
Since the 1.19.1-1 update to xorg-server it's started dumping core on me intermittently (a couple of times a day). This is on a laptop with an external monitor, and it's possible that the core dump is happening when moving the pointer rapidly between the external monitor to the laptop panel, but that could easily be a coincidence. The laptop has both an Intel and an Nvidia GPU. I'm only using the Intel driver, but haven't completely removed all Nvidia support ... if that is the problem, it hasn't been up until now.
Beyond the trace in the journal I'm not seeing anything obvious ... there's nothing out of the ordinary in the Xorg.0.log. Has anyone else had a similar experience?
The trace is below ... any advice on how to diagnose this would be very much appreciated.
Jan 13 11:43:06 tarski systemd[1]: Started Process Core Dump (PID 25123/UID 0).
Jan 13 11:43:06 tarski konsole[16430]: The X11 connection broke (error 1). Did the X11 server die?
Jan 13 11:43:06 tarski konsole[18192]: The X11 connection broke (error 1). Did the X11 server die?
Jan 13 11:43:06 tarski konsole[18192]: Konsole SessionManager destroyed with 2 session(s) still alive
Jan 13 11:43:06 tarski konsole[16430]: Konsole SessionManager destroyed with 2 session(s) still alive
Jan 13 11:43:06 tarski kernel: chrome[25153]: segfault at 968 ip 00007f2cc98e43a3 sp 00007ffd11be83f0 error 4 in libX11.so.6.3.0[7f2cc98b700
Jan 13 11:43:06 tarski systemd[1]: Started Process Core Dump (PID 25158/UID 0).
Jan 13 11:43:07 tarski systemd-coredump[25124]: Process 2791 (Xorg) of user 1000 dumped core.
Stack trace of thread 2799:
#0 0x00007fc44f026300 n/a (intel_drv.so)
#1 0x00007fc44f026d7d n/a (intel_drv.so)
#2 0x00000000004bb772 n/a (Xorg)
#3 0x0000000000582d13 n/a (Xorg)
#4 0x0000000000583b14 miPointerSetPosition (Xorg)
#5 0x000000000044cece n/a (Xorg)
#6 0x000000000044d6d3 n/a (Xorg)
#7 0x000000000044ef7f GetPointerEvents (Xorg)
#8 0x000000000044f530 QueuePointerEvents (Xorg)
#9 0x00007fc4441363c5 n/a (libinput_drv.so)
#10 0x00007fc444136f90 n/a (libinput_drv.so)
#11 0x0000000000599a8c n/a (Xorg)
#12 0x000000000059c191 n/a (Xorg)
#13 0x00000000005998e6 n/a (Xorg)
#14 0x00007fc453b97454 start_thread (libpthread.so.0)
#15 0x00007fc4538da7df __clone (libc.so.6)
Stack trace of thread 2791:
#0 0x00007fc453b9ff1c __lll_lock_wait (libpthread.so.0)
#1 0x00007fc453b99bb6 pthread_mutex_lock (libpthread.so.0)
#2 0x00000000005997d0 input_lock (Xorg)
#3 0x00000000004bbc56 n/a (Xorg)
#4 0x00000000004ba4c5 n/a (Xorg)
#5 0x00000000005833ab miPointerUpdateSprite (Xorg)
#6 0x00000000005835fa n/a (Xorg)
#7 0x00000000004c8de1 n/a (Xorg)
#8 0x0000000000515500 n/a (Xorg)
#9 0x000000000043f6c8 n/a (Xorg)
#10 0x0000000000440b07 WindowHasNewCursor (Xorg)
#11 0x0000000000468860 ChangeWindowAttributes (Xorg)
#12 0x00000000004305ed n/a (Xorg)
#13 0x00000000004368d5 n/a (Xorg)
#14 0x000000000043a858 n/a (Xorg)
#15 0x00007fc453812291 __libc_start_main (libc.so.6)
#16 0x000000000042453a _start (Xorg)
Stack trace of thread 2795:
#0 0x00007fc453b9d10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fc44f06a709 n/a (intel_drv.so)
#2 0x00007fc453b97454 start_thread (libpthread.so.0)
#3 0x00007fc4538da7df __clone (libc.so.6)
Stack trace of thread 2793:
#0 0x00007fc453b9d10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fc44f06a709 n/a (intel_drv.so)
#2 0x00007fc453b97454 start_thread (libpthread.so.0)
#3 0x00007fc4538da7df __clone (libc.so.6)
Stack trace of thread 2794:
#0 0x00007fc453b9d10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fc44f06a709 n/a (intel_drv.so)
#2 0x00007fc453b97454 start_thread (libpthread.so.0)
#3 0x00007fc4538da7df __clone (libc.so.6)
Jan 13 11:43:07 tarski systemd-coredump[25159]: Process 25153 (chrome) of user 1000 dumped core.
Stack trace of thread 25153:
#0 0x00007f2cc98e43a3 XInternAtoms (libX11.so.6)
#1 0x00005621537aaac0 n/a (chrome)
Jan 13 11:43:07 tarski kernel: nouveau 0000:01:00.0: DRM: resuming kernel object tree...
Jan 13 11:43:07 tarski kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1b40822c)
Jan 13 11:43:07 tarski kernel: nouveau 0000:01:00.0: DRM: resuming client object trees...
Jan 13 11:43:13 tarski kernel: nouveau 0000:01:00.0: DRM: evicting buffers...
Jan 13 11:43:13 tarski kernel: nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
Jan 13 11:43:13 tarski kernel: nouveau 0000:01:00.0: DRM: suspending client object trees...
Jan 13 11:43:13 tarski kernel: nouveau 0000:01:00.0: DRM: suspending kernel object tree...
Jan 13 11:43:23 tarski acpid[414]: client 2791[1000:1000] has disconnected
Jan 13 11:43:23 tarski acpid[414]: client 2791[1000:1000] has disconnected
Jan 13 11:44:02 tarski login[21809]: pam_unix(login:session): session opened for user miles by LOGIN(uid=0)
Last edited by milessabin (2017-01-13 12:41:20)
Offline
Do you use xf86-video-intel or the built in modesetting driver?
https://ugjka.net
paru > yay | vesktop > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
I use xf86-video-intel.
Offline
Try removing it and its related config files, intel has practically abandoned its development
https://ugjka.net
paru > yay | vesktop > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
Let me qualify that. I have this installed,
Name : xf86-video-intel
Version : 1:2.99.917+747+g028c946d-1
Which appears to be what's identified in Xorg.0.log,
[ 59.742] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 59.742] (II) intel: Driver for Intel(R) HD Graphics
[ 59.742] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 59.742] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 59.742] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 59.742] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[ 59.743] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20160711
[ 59.743] (II) intel(0): SNA compiled from 2.99.917-747-g028c946d
[ 59.744] (II) modeset(G0): using drv /dev/dri/card1
[ 59.744] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 59.744] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics P530
[ 59.744] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 4 threads
[ 59.744] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 59.744] (==) intel(0): Depth 24, (--) framebuffer bpp 32
Offline
intel has practically abandoned its development
Really? What's the status of the built in support for Intel GPUs? Does it have feature parity with xf86-video-intel?
Offline
Yes I understand. It is a dead driver, that distro's are starting to abandon
https://tjaalton.wordpress.com/2016/07/ … iver-on-x/
http://www.phoronix.com/scan.php?page=n … DDX-Switch
https://ugjka.net
paru > yay | vesktop > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
OK, thanks ... I've dug into this a bit more and it does seem that xf86-video-intel has been abandoned.
Following your advice ... much appreciated.
Offline
From your stack trace:
#0 0x00007fc44f026300 n/a (intel_drv.so)
Checking for it:
[ugjka@ArchT ~]$ pkgfile intel_drv.so
extra/xf86-video-intel
Clearly something crashing in that driver
Last edited by ugjka (2017-01-13 12:50:37)
https://ugjka.net
paru > yay | vesktop > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
xf86-video-intel dead? Not really… https://cgit.freedesktop.org/xorg/drive … -intel/log
Offline
xf86-video-intel dead? Not really… https://cgit.freedesktop.org/xorg/drive … -intel/log
Whatever they are doing clearly is not enough.
https://ugjka.net
paru > yay | vesktop > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
xf86-video-intel dead? Not really… https://cgit.freedesktop.org/xorg/drive … -intel/log
I'd be interested in opinions on the pros and cons of xf86-video-intel vs. the built in modesetting driver. Are there any downsides to using the latter?
Offline
I'd be interested in opinions on the pros and cons of xf86-video-intel vs. the built in modesetting driver. Are there any downsides to using the latter?
Only upside with intel that I can think of, is that you have the option to use the SNA 2d acceleration in X. It should be slightly faster but also buggier than "glamor" used by modesetting driver (you can also use glamor with intel driver though).
I've understood modesetting should be less cod, simpler design and more actively developed.
There shouldn't be any difference with 3d performance
Offline
I've switched over to the built in modesetting driver, and for the most part everything is fine. However I am seeing some flickering of the mouse pointer, towards the top edge of external monitor (which is my primary). This is fairly annoying, but preferable to core dumps. Does anyone have any pointers on fixing that? FTR, I've now blacklisted nouveau, so I'm only using the built in Intel GPU and driver.
Update: this only appears to be happening on the Chrome tab bar, and only when it's on the external monitor.
Update: I fixed the flicker by tweaking Chrome flags as described here.
Last edited by milessabin (2017-01-15 14:08:15)
Offline
I am having the same issues, got a Xorg core dump twice in 1 hour. Also uninstalled xf86-video-intel and haven't had a crash in the 7 hours since.
I have the exact same strack trace:
Jan 16 10:50:04 systemd-coredump[6294]: Process 1600 (Xorg) of
user 0 dumped core.
Stack trace of thread 1625:
#0 0x00007fd21be25300 n/a (intel_drv.so)
#1 0x00007fd21be25d7d n/a (intel_drv.so)
#2 0x00000000004bb772 n/a (Xorg)
#3 0x0000000000582d13 n/a (Xorg)
#4 0x0000000000583b14 miPointerSetPosition (Xorg)
#5 0x000000000044cece n/a (Xorg)
#6 0x000000000044d6d3 n/a (Xorg)
#7 0x000000000044ef7f GetPointerEvents (Xorg)
#8 0x000000000044f530 QueuePointerEvents (Xorg)
#9 0x00007fd218cda3c5 n/a (libinput_drv.so)
#10 0x00007fd218cdaf90 n/a (libinput_drv.so)
#11 0x0000000000599a8c n/a (Xorg)
#12 0x000000000059c191 n/a (Xorg)
#13 0x00000000005998e6 n/a (Xorg)
#14 0x00007fd220996454 start_thread (libpthread.so.0)
#15 0x00007fd2206d97df __clone (libc.so.6)
Stack trace of thread 1600:
#0 0x00007fd22099ef1c __lll_lock_wait (libpthread.so.0)
#1 0x00007fd220998bb6 pthread_mutex_lock (libpthread.so.0)
#2 0x00000000005997d0 input_lock (Xorg)
#3 0x00000000004bbc56 n/a (Xorg)
#4 0x00000000004ba4c5 n/a (Xorg)
#5 0x00000000005833ab miPointerUpdateSprite (Xorg)
#6 0x00000000005835fa n/a (Xorg)
#7 0x00000000004c8de1 n/a (Xorg)
#8 0x0000000000515500 n/a (Xorg)
#9 0x000000000043f6c8 n/a (Xorg)
#10 0x0000000000440b07 WindowHasNewCursor (Xorg)
#11 0x0000000000468860 ChangeWindowAttributes (Xorg)
#12 0x00000000004305ed n/a (Xorg)
#13 0x00000000004368d5 n/a (Xorg)
#14 0x000000000043a858 n/a (Xorg)
#15 0x00007fd220611291 __libc_start_main (libc.so.6)
#16 0x000000000042453a _start (Xorg)
Stack trace of thread 1617:
#0 0x00007fd22099c10f pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fd21be69709 n/a (intel_drv.so)
#2 0x00007fd220996454 start_thread (libpthread.so.0)
#3 0x00007fd2206d97df __clone (libc.so.6)
-- Subject: Process 1600 (Xorg) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: man:core(5)
--
-- Process 1600 (Xorg) crashed and dumped core.
--
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
I submitted the bug upstream: https://bugs.freedesktop.org/show_bug.cgi?id=99431
Last edited by sukosevato (2017-01-16 19:48:46)
Offline
Hmm... had the same issue so I removed xf86-video-intel, which improved the general performance of rendering, but I'm using the i3 window manager and for some reason, without xf86-video-intel, status bars do not show (although i3bar is running). Has anybody else had an issue like that? I've looked around and don't see anyone reporting issues like this one. I had no xorg config for video, just removed the package.
Offline
Actually, should mention I'm using i3-gaps, although I don't think it's related...
Offline
Hmm... had the same issue so I removed xf86-video-intel, which improved the general performance of rendering, but I'm using the i3 window manager and for some reason, without xf86-video-intel, status bars do not show (although i3bar is running). Has anybody else had an issue like that? I've looked around and don't see anyone reporting issues like this one. I had no xorg config for video, just removed the package.
I had the same issue, the name of the displays changed from DP1-1 to DP-1-1, DP2 to DP-2, etc.
Take a look at the output of xrandr.
Regards.
Offline
This was filed as a bug upstream at https://bugs.freedesktop.org/show_bug.cgi?id=99431, which was then identified as https://bugs.freedesktop.org/show_bug.cgi?id=99358. Patches for the latter have now been submitted, so there's hope that we'll see a real fix deployed soon!
Offline
Update: It looks like this is an xorg bug being tracked here.
Yeah, but if you have this issue on arch, google is going to send you here
Offline
shioyama wrote:Hmm... had the same issue so I removed xf86-video-intel, which improved the general performance of rendering, but I'm using the i3 window manager and for some reason, without xf86-video-intel, status bars do not show (although i3bar is running). Has anybody else had an issue like that? I've looked around and don't see anyone reporting issues like this one. I had no xorg config for video, just removed the package.
I had the same issue, the name of the displays changed from DP1-1 to DP-1-1, DP2 to DP-2, etc.
Take a look at the output of xrandr.
You are my hero! Thanks, working great now.
Last edited by shioyama (2017-02-10 00:11:58)
Offline