Bug#901497: XWayland: Hard system hangs after upgrade from Mesa 18.0.5-1 to 18.1.1-1
Dear Josh, dear Tehnic, dear Mourad, dear Jacek, On 06/16/18 22:37, Josh Triplett wrote: > On Thu, Jun 14, 2018 at 11:59:20PM -0700, Josh Triplett wrote: >> On Thu, Jun 14, 2018 at 11:56:03PM -0700, Josh Triplett wrote: >>> reassign 901497 >>> retitle 901497 Xwayland: hangs spinning on write and SIGALRM >>> thanks >>> >>> After further investigation, I can reproduce this with Mesa 18.0.5-1 as >>> well, just not as often. >>> >>> After encountering this issue, I managed to switch to a text console, >>> and found that Xwayland was using 100% CPU. strace of the running >>> Xwayland produced the attached strace, in which Xwayland appears to be >>> spinning, running a zero-byte writev, and periodically processing a >>> SIGALRM. Other threads appear to be blocked on futexes. >> >> Forgot to attach the strace, sorry. Will provide one again next time it >> happens, but it consisted entirely of "write(14, [], 0) = 0" on one >> thread. > > Here's a fresh strace. I'm encountering this quite frequently. Could you please test if it’s the same issue as [1], and test the two X.Org X server commits below [2]? 1. https://cgit.freedesktop.org/xorg/xserver/commit/?id=3da999a 2. https://cgit.freedesktop.org/xorg/xserver/commit/?id=4d5950c Kind regards, Paul [1]: https://bugzilla.redhat.com/1579067 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1579067#c26 smime.p7s Description: S/MIME Cryptographic Signature
Bug#901497: backtrace
Here's a backtrace of Xwayland after triggering this bug: #0 0x7f9d27227017 in __GI___writev (fd=15, iov=iov@entry=0x7ffc7e53bec0, iovcnt=iovcnt@entry=0) at ../sysdeps/unix/sysv/linux/writev.c:26 #1 0x55912d2bb56e in _XSERVTransSocketWritev (ciptr=0x55912fa10090, buf=0x7ffc7e53bec0, size=) at /usr/include/X11/Xtrans/Xtranssock.c:2367 #2 0x55912d2b5fcd in FlushClient (who=who@entry=0x55912f9536b0, oc=oc@entry=0x55912f922c30, __extraBuf=__extraBuf@entry=0x7ffc7e53c010, extraCount=extraCount@entry=-4) at ../../../../os/io.c:882 #3 0x55912d2b659e in WriteToClient (who=who@entry=0x55912f9536b0, count=count@entry=-4, __buf=__buf@entry=0x7ffc7e53c010) at ../../../../os/io.c:795 #4 0x55912d21cdac in proc_dri3_buffers_from_pixmap (client=0x55912f9536b0) at ../../../../dri3/dri3_request.c:555 #5 0x55912d280dc8 in Dispatch () at ../../../../dix/dispatch.c:478 #6 0x55912d284dc8 in dix_main (argc=12, argv=0x7ffc7e53c218, envp=) at ../../../../dix/main.c:276 #7 0x7f9d2715aa87 in __libc_start_main (main=0x55912d158520 , argc=12, argv=0x7ffc7e53c218, init=, fini=, rtld_fini=, stack_end=0x7ffc7e53c208) at ../csu/libc-start.c:310 #8 0x55912d15855a in _start ()
Bug#901497: XWayland: Hard system hangs after upgrade from Mesa 18.0.5-1 to 18.1.1-1
Hello Paul, applying this two patches seem to solve the problem (at least here for me). I'll keep this setup for now to test more. Kind regards, Robert On Tue, 19 Jun 2018 10:14:38 +0200 Paul Menzel wrote: > Dear Josh, dear Tehnic, dear Mourad, dear Jacek, > > > On 06/16/18 22:37, Josh Triplett wrote: > > On Thu, Jun 14, 2018 at 11:59:20PM -0700, Josh Triplett wrote: > >> On Thu, Jun 14, 2018 at 11:56:03PM -0700, Josh Triplett wrote: > >>> reassign 901497 > >>> retitle 901497 Xwayland: hangs spinning on write and SIGALRM > >>> thanks > >>> > >>> After further investigation, I can reproduce this with Mesa 18.0.5-1 as > >>> well, just not as often. > >>> > >>> After encountering this issue, I managed to switch to a text console, > >>> and found that Xwayland was using 100% CPU. strace of the running > >>> Xwayland produced the attached strace, in which Xwayland appears to be > >>> spinning, running a zero-byte writev, and periodically processing a > >>> SIGALRM. Other threads appear to be blocked on futexes. > >> > >> Forgot to attach the strace, sorry. Will provide one again next time it > >> happens, but it consisted entirely of "write(14, [], 0) = 0" on one > >> thread. > > > > Here's a fresh strace. I'm encountering this quite frequently. > > Could you please test if it’s the same issue as [1], and test the two > X.Org X server commits below [2]? > > 1. https://cgit.freedesktop.org/xorg/xserver/commit/?id=3da999a > 2. https://cgit.freedesktop.org/xorg/xserver/commit/?id=4d5950c > > > Kind regards, > > Paul > > > [1]: https://bugzilla.redhat.com/1579067 > [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1579067#c26 > -- Robert
Bug#901789: mesa: white screen when running Xfwm4 with compositing
On Mon, 18 Jun 2018 14:06:10 +0200 Yves-Alexis Perez > since the upgrade from 18.0.5-1 to 18.1.1-1 of the various mesa > packages, xfwm4 with compositing enabling only display a white screen. > The cursor is shown on top, but no window appears. When restarting > xfwm4 I can briefly see the windows, then the white screen. > > Disabling compositing in xfwm4 workarounds the problem but then you > lose all compositing-related features. Hello, Not sure it helps, but I observe the same here (xfwm4 with compositing + mesa 18.1.1-1 fail, and a white screen is displayed) but only with xfwm4 in experimental (4.13.0-1). Unstable version (4.12.4-1) is perfectly fine with mesa 18.1.1-1 (intel graphics HD4000, CPU generation is Ivy Bridge, and modesetting driver is used). Yves-Alexis, which xfwm4 version do you use ? Best regards, Pascal Dormeau
[Git][xorg-team/lib/mesa] Pushed new tag mesa-18.1.2-1
Timo Aaltonen pushed new tag mesa-18.1.2-1 at X Strike Force / lib / mesa -- View it on GitLab: https://salsa.debian.org/xorg-team/lib/mesa/tree/mesa-18.1.2-1 You're receiving this email because of your account on salsa.debian.org.
Processing of mesa_18.1.2-1_source.changes
mesa_18.1.2-1_source.changes uploaded successfully to localhost along with the files: mesa_18.1.2-1.dsc mesa_18.1.2.orig.tar.gz mesa_18.1.2.orig.tar.gz.asc mesa_18.1.2-1.diff.gz mesa_18.1.2-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
mesa_18.1.2-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 19 Jun 2018 17:50:24 +0300 Source: mesa Binary: libxatracker2 libxatracker-dev libgbm1 libgbm-dev libegl-mesa0 libegl1-mesa libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa libgles2-mesa-dev libglapi-mesa libglx-mesa0 libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-dev mesa-common-dev libosmesa6 libosmesa6-dev mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers mesa-opencl-icd Architecture: source Version: 18.1.2-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force Changed-By: Timo Aaltonen Description: libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library libegl1-mesa - transitional dummy package libegl1-mesa-dev - free implementation of the EGL API -- development files libgbm-dev - generic buffer management API -- development files libgbm1- generic buffer management API -- runtime libgl1-mesa-dev - free implementation of the OpenGL API -- GLX development files libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules libgl1-mesa-glx - transitional dummy package libglapi-mesa - free implementation of the GL API -- shared library libgles2-mesa - transitional dummy package libgles2-mesa-dev - free implementation of the OpenGL|ES 2.x API -- development files libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor library libosmesa6 - Mesa Off-screen rendering extension libosmesa6-dev - Mesa Off-screen rendering extension -- development files libwayland-egl1-mesa - transitional dummy package libxatracker-dev - X acceleration library -- development files libxatracker2 - X acceleration library -- runtime mesa-common-dev - Developer documentation for Mesa mesa-opencl-icd - free implementation of the OpenCL API -- ICD runtime mesa-va-drivers - Mesa VA-API video acceleration drivers mesa-vdpau-drivers - Mesa VDPAU video acceleration drivers mesa-vulkan-drivers - Mesa Vulkan graphics drivers Changes: mesa (18.1.2-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 073de2130e3c139e7d5eea93fc520e1b6bdf8d3e 5097 mesa_18.1.2-1.dsc d372eeaed5162d86c0e141bd2b1e38439163a0c8 18878574 mesa_18.1.2.orig.tar.gz 204d6ca30c7b0641ad7144e78bd39cbb56cb54c9 274 mesa_18.1.2.orig.tar.gz.asc 7a1636a8d7178aa6c0ecc2838dca83b7ed5feaeb 9 mesa_18.1.2-1.diff.gz 36a4a5ca1cac42453addcf11e67f273944c7783e 8695 mesa_18.1.2-1_source.buildinfo Checksums-Sha256: 906f9f1e14fa55d4d7c42989829f236dc4d547e2464d003b130e517511f59071 5097 mesa_18.1.2-1.dsc a644df23937f4078a2bd9a54349f6315c1955f5e3a4ac272832da51dea4d3c11 18878574 mesa_18.1.2.orig.tar.gz 9e9b13bc309a4d9cb41a19a866e6b0507b12dafd7a868d7d4fefd9f08f12697a 274 mesa_18.1.2.orig.tar.gz.asc 1ee4ef181df074a2ea257a6ddcc02bdd6059f64ae0baa334812007e4a986d047 9 mesa_18.1.2-1.diff.gz 34392ebe8b712d6f0a91b66dee0d41d557e1dd2bfba87ffeb0239c71e44c0872 8695 mesa_18.1.2-1_source.buildinfo Files: bc8420aa6e1f2aa7c54c9c34ec140e15 5097 graphics optional mesa_18.1.2-1.dsc 66ec197f796090b8782f4d162bdebc66 18878574 graphics optional mesa_18.1.2.orig.tar.gz 9a64d92bd24d6282ad68ae45f0c5a410 274 graphics optional mesa_18.1.2.orig.tar.gz.asc a25ae9a28f726a89da3d4d34279f8e1a 9 graphics optional mesa_18.1.2-1.diff.gz 0cb67127913589749518c0f357743ab2 8695 graphics optional mesa_18.1.2-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlspGFsACgkQy3AxZaiJ hNwXIw/9FZJRTKhx3ks9fiseTAZ4yEL4oyf4jtDnVN3o1KLq5aLuhLyG5eyyJp2M 5X8ik2wE6BN6ucmwqS4HwWNhyztjo+MmU9IVT3iTbL6lszBwtil0QYUJE00Cq7Ap ndeNTvtBW/edKSUR3fgLZx3LBN8J30RHJL6v1co+MYOncDwiRD/4eC20MdgdZjft P+d93mYdjfy0pQg72u1tHIkIZzuHrsGLUPcQb0nMBWmckuy86k/vw11EIPdnQxI7 26ezvQ7HlhUv7dWKb9o+LqflXIDeIlta5MjwjDWdWDNPFGKoi/monIg8CL5aIGDT XcgDr4jUdFKyiBrtl2d/b1YUjJIgBwZnqoElT7gwSjqP0gopCslbwrIlv3UIFx9h nJ5Ny9lwTZfyhyuXNvxj+odiW+Me5u8CvW74E3KJGUDtRzfUg68xn7NtVR46rzkI 7mqA+QjTn5DwmGrMSuNvrnKF4zSTpopx/VQ+vm44KMCI7CJcTIVLx0BL+XT5iHQU 0tKvB4eC1gPjiymivB6rSjKfAQGx5MhywNePGUeoWtuDykEXT31kM/vapdY2aj1w L/Ft+uHelo59x1tGtDXzmDCs++kqyacgC91sebjGSVGzLXKm8nU/jfSs6gpF0Dxu hMEX1bdMev0t8CK+98NzBHdAtVa0XAmrhd1SAOxQds+u0S06QFk= =VvGj -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#901789: mesa: white screen when running Xfwm4 with compositing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2018-06-19 at 16:26 +0200, Pascal Dormeau wrote: > Not sure it helps, but I observe the same here (xfwm4 with compositing + > mesa 18.1.1-1 fail, and a white screen is displayed) but only with > xfwm4 in experimental (4.13.0-1). > Unstable version (4.12.4-1) is perfectly fine with mesa 18.1.1-1 (intel > graphics HD4000, CPU generation is Ivy Bridge, and modesetting driver > is used). > > Yves-Alexis, which xfwm4 version do you use ? Indeed that's a good point, I'm also using xfwm4 4.13 from experimental. - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlspS8cACgkQ3rYcyPpX RFsLywgAptdKK3e9MSeaTpraqXbYVQuZdzmpHYkY+2tivBf1PBeHte3VFyg6967+ C2CJ51rGHRPnKUTY2bpHKxRl0M939FqGUqNNToNxMCvxpjCtMV9u+1Qm8ZDhHnW4 FYMGKxrTDCPojOBjlh5rQiod33cLS2YbaHbAF1VMi0GzW+JQwJMRCFVmfoCCb2nB ZSdu2QDHeY+NHLatM37Wp3POCU+WBBZ2SSTm5taqCsaeAf4U/lmSlVm1NKST7ywi 138MmiNCViVfyhNogyH/K8HRFJRbBjv6tQtoS2XCXqe7/1YFu2s3fZD4ioMtLDfX PP9pqrg7hZyNiwy3avBietPEuM2q/Q== =+OJ9 -END PGP SIGNATURE-
Processed: affects 901789
Processing commands for cont...@bugs.debian.org: > affects 901789 xfwm4 Bug #901789 [src:mesa] mesa: white screen when running Xfwm4 with compositing Added indication that 901789 affects xfwm4 > thanks Stopping processing here. Please contact me if you need assistance. -- 901789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#901883: xwayland: Firefox causes Xwayland to freeze and eat 100% CPU
Package: xwayland
Version: 2:1.20.0-2
Severity: normal
Tags: patch
Dear Maintainer,
while trying to watch the German TV show "Die Sendung mit der Maus" from
https://www.wdrmaus.de/aktuelle-sendung/, my Gnome desktop freezes. I can
SSH into the machine and see that Xwayland eats 100% CPU. The freeze can be
reproduced, it happened every time I accessed the above URL in Firefox 60.
I found a similar issue in the Red Hat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1579067
The issue mentions patches in
https://patchwork.freedesktop.org/series/43618/. I applied them to the
xorg-server source, built and installed the package and the freeze does not
happen anymore.
The patches are also attached to this bugreport.
Regards,
Tino
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.2 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xwayland depends on:
ii libaudit1 1:2.8.3-1
ii libbsd0 0.9.1-1
ii libc6 2.27-3
ii libdrm2 2.4.92-1
ii libegl1 1.0.0+git20180308-3
ii libepoxy0 1.4.3-1
ii libgbm1 18.1.1-1
ii libgcrypt20 1.8.3-1
ii libgl1 1.0.0+git20180308-3
ii libpixman-1-0 0.34.0-2
ii libselinux1 2.8-1
ii libsystemd0 238-5
ii libwayland-client0 1.15.0-2
ii libxau6 1:1.0.8-1+b2
ii libxdmcp6 1:1.1.2-3
ii libxfont2 1:2.0.3-1
ii libxshmfence1 1.3-1
ii xserver-common 2:1.20.0-2
xwayland recommends no packages.
xwayland suggests no packages.
-- debconf-show failed
diff --git a/glamor/glamor.c b/glamor/glamor.c
index d984d20f3..e2c74d17a 100644
--- a/glamor/glamor.c
+++ b/glamor/glamor.c
@@ -836,20 +836,20 @@ glamor_fds_from_pixmap(ScreenPtr screen, PixmapPtr pixmap, int *fds,
glamor_get_screen_private(pixmap->drawable.pScreen);
if (!glamor_priv->dri3_enabled)
-return -1;
+return 0;
switch (pixmap_priv->type) {
case GLAMOR_TEXTURE_DRM:
case GLAMOR_TEXTURE_ONLY:
if (!glamor_pixmap_ensure_fbo(pixmap, pixmap->drawable.depth == 30 ?
GL_RGB10_A2 : GL_RGBA, 0))
-return -1;
+return 0;
return glamor_egl_fds_from_pixmap(screen, pixmap, fds,
strides, offsets,
modifier);
default:
break;
}
-return -1;
+return 0;
}
_X_EXPORT int
diff --git a/glamor/glamor.c b/glamor/glamor.c
index e2c74d17a..63f0947fa 100644
--- a/glamor/glamor.c
+++ b/glamor/glamor.c
@@ -865,17 +865,15 @@ glamor_fd_from_pixmap(ScreenPtr screen,
&modifier);
/* Pixmaps with multi-planes/modifier are not supported in this interface */
-if (ret > 1) {
-while (ret > 0)
-close(fds[--ret]);
-return -1;
+if (ret == 1 && offsets[0] == 0) {
+*stride = strides[0];
+*size = pixmap->drawable.height * *stride;
+return fds[0];
}
-ret = fds[0];
-*stride = strides[0];
-*size = pixmap->drawable.height * *stride;
-
-return ret;
+while (ret > 0)
+close(fds[--ret]);
+return -1;
}
_X_EXPORT int
Processing of glslang_6.2.2596-1_amd64.changes
glslang_6.2.2596-1_amd64.changes uploaded successfully to localhost along with the files: glslang_6.2.2596-1.dsc glslang_6.2.2596.orig.tar.gz glslang_6.2.2596-1.diff.gz glslang-dev_6.2.2596-1_amd64.deb glslang-tools_6.2.2596-1_amd64.deb glslang_6.2.2596-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
glslang_6.2.2596-1_amd64.changes is NEW
binary:glslang-dev is NEW. binary:glslang-tools is NEW. binary:glslang-dev is NEW. binary:glslang-tools is NEW. source:glslang is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Bug#901497: xserver-xorg-core: Also Related to these bugs?
Package: xserver-xorg-core Version: 2:1.20.0-2 Followup-For: Bug #901497 I have likely the same bug I just filed against firefox here: https://bugzilla.mozilla.org/show_bug.cgi?id=1468930 Mozillans pointed me to these bugs filed in arch and redhat https://bugs.archlinux.org/task/58705#comment169691 https://bugzilla.redhat.com/show_bug.cgi?id=1579067 Could we get a build of 1.20.0-5 to test in debian to see if it fixes our problem? -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27) Xorg X server log files on system: -- -rw-r--r-- 1 ryan ryan 47017 Jan 22 16:10 /home/ryan/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 root root 32371 Jan 25 20:24 /var/log/Xorg.1.log -rw-r--r-- 1 root root 36544 Jan 25 22:57 /var/log/Xorg.0.log -rw-r--r-- 1 ryan ryan 54641 Jun 15 13:15 /home/ryan/.local/share/xorg/Xorg.0.log Contents of most recent Xorg X server log file (/home/ryan/.local/share/xorg/Xorg.0.log): - [ 1267.907] (--) Log file renamed from "/home/ryan/.local/share/xorg/Xorg.pid-2427.log" to "/home/ryan/.local/share/xorg/Xorg.0.log" [ 1267.909] X.Org X Server 1.20.0 X Protocol Version 11, Revision 0 [ 1267.909] Build Operating System: Linux 4.9.0-6-amd64 x86_64 Debian [ 1267.909] Current Operating System: Linux Cirdan 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 [ 1267.909] Kernel command line: BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/mapper/Cirdan--vg-root ro quiet [ 1267.909] Build Date: 24 May 2018 04:23:27PM [ 1267.909] xorg-server 2:1.20.0-2 (https://www.debian.org/support) [ 1267.909] Current version of pixman: 0.34.0 [ 1267.909]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1267.909] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1267.909] (==) Log file: "/home/ryan/.local/share/xorg/Xorg.0.log", Time: Fri Jun 15 13:08:51 2018 [ 1267.910] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1267.912] (==) No Layout section. Using the first Screen section. [ 1267.912] (==) No screen section available. Using defaults. [ 1267.912] (**) |-->Screen "Default Screen Section" (0) [ 1267.912] (**) | |-->Monitor "" [ 1267.914] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 1267.914] (==) Automatically adding devices [ 1267.914] (==) Automatically enabling devices [ 1267.914] (==) Automatically adding GPU devices [ 1267.914] (==) Max clients allowed: 256, resource mask: 0x1f [ 1267.914] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 1267.914]Entry deleted from font path. [ 1267.914] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 1267.914] (==) ModulePath set to "/usr/lib/xorg/modules" [ 1267.914] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 1267.914] (II) Loader magic: 0x5650599a8de0 [ 1267.914] (II) Module ABI versions: [ 1267.914]X.Org ANSI C Emulation: 0.4 [ 1267.914]X.Org Video Driver: 24.0 [ 1267.914]X.Org XInput driver : 24.1 [ 1267.914]X.Org Server Extension : 10.0 [ 1267.916] (++) using VT number 2 [ 1267.919] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_34 [ 1267.920] (II) xfree86: Adding drm device (/dev/dri/card0) [ 1267.921] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0 [ 1267.924] (--) PCI:*(0@0:2:0) 8086:1916:1028:0704 rev 7, Mem @ 0xdb00/16777216, 0x9000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072 [ 1267.924] (II) LoadModule: "glx" [ 1267.925] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 1267.929] (II) Module glx: vendor="X.Org Foundation" [ 1267.929]compiled for 1.20.0, module version = 1.0.0 [ 1267.929]ABI class: X.Org Server Extension, version 10.0 [ 1267.929] (==) Matched modes
Bug#901497: XWayland: Hard system hangs after upgrade from Mesa 18.0.5-1 to 18.1.1-1
On Tue, Jun 19, 2018 at 10:14:38AM +0200, Paul Menzel wrote: > Dear Josh, dear Tehnic, dear Mourad, dear Jacek, > On 06/16/18 22:37, Josh Triplett wrote: > > On Thu, Jun 14, 2018 at 11:59:20PM -0700, Josh Triplett wrote: > >> On Thu, Jun 14, 2018 at 11:56:03PM -0700, Josh Triplett wrote: > >>> reassign 901497 > >>> retitle 901497 Xwayland: hangs spinning on write and SIGALRM > >>> thanks > >>> > >>> After further investigation, I can reproduce this with Mesa 18.0.5-1 as > >>> well, just not as often. > >>> > >>> After encountering this issue, I managed to switch to a text console, > >>> and found that Xwayland was using 100% CPU. strace of the running > >>> Xwayland produced the attached strace, in which Xwayland appears to be > >>> spinning, running a zero-byte writev, and periodically processing a > >>> SIGALRM. Other threads appear to be blocked on futexes. > >> > >> Forgot to attach the strace, sorry. Will provide one again next time it > >> happens, but it consisted entirely of "write(14, [], 0) = 0" on one > >> thread. > > > > Here's a fresh strace. I'm encountering this quite frequently. > > Could you please test if it’s the same issue as [1], and test the two > X.Org X server commits below [2]? > > 1. https://cgit.freedesktop.org/xorg/xserver/commit/?id=3da999a > 2. https://cgit.freedesktop.org/xorg/xserver/commit/?id=4d5950c After rebuilding Xwayland with these two patches, I can no longer reproduce the problem; sites that reliably triggered this issue in Firefox no longer do.
