org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address

[themusicgod1]

Went to log into my fairly newly upgraded ubuntu artful system today but was presented with a new login instead of a login with all my applications running, similar to #1728474 ( https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728474 ), only I didn't have to Ctrl-Alt-F1 to get a new login, I was presented with one when I came to log in in the morning.

syslog gives a clue:

Nov 5 02:17:43 eva org.gnome.Shell.desktop[29954]: intel_do_flush_locked failed: Bad address
Nov 5 02:17:44 eva gnome-shell[29954]: Connection to xwayland lost
Nov 5 02:17:44 eva kernel: [1339701.543472] traps: gnome-shell[29954] trap int3 ip:7fcceb716961 sp:7ffd8b486020 error:0 in libglib-2.0.so.0.5400.1[7fcceb6c6000+111000]

This, followed by everything that was running failing to various degrees of cleanness.

intel-microcode:
  Installed: 3.20170707.1
  Candidate: 3.20170707.1
  Version table:
 *** 3.20170707.1 500
        500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/restricted amd64 Packages
        500 https://mirror.its.sfu.ca/mirror/ubuntu artful/restricted amd64 Packages
        100 /var/lib/dpkg/status

xserver-xorg-video-intel:
  Installed: 2:2.99.917+git20170309-0ubuntu1
  Candidate: 2:2.99.917+git20170309-0ubuntu1
  Version table:
 *** 2:2.99.917+git20170309-0ubuntu1 500
        500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages
        500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status

libglib2.0-0:
  Installed: 2.54.1-1ubuntu1
  Candidate: 2.54.1-1ubuntu1
  Version table:
 *** 2.54.1-1ubuntu1 500
        500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages
        500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 5 07:27:04 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'libreoffice-calc.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'userapp-New Moon-YU8MZY.desktop', 'onioncircuits.desktop', 'org.gnome.Screenshot.desktop', 'emacs25.desktop', 'ricochet-im.desktop', 'gpa.desktop', 'org.gnome.Cheese.desktop']"
 b'org.gnome.desktop.interface' b'cursor-blink-time' b'1264'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-04-18 (200 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (16 days ago)

[Daniel van Vugt (vanvugt)]

Please attach more of the syslog or output from 'journalctl'.

[themusicgod1 (themusicgod1)]

happened again, (this happens every few days)

Nov 26 00:14:17 eva anacron[23338]: Job `cron.daily' terminated
Nov 26 00:14:17 eva anacron[23338]: Normal exit (1 job run)
Nov 26 00:15:01 eva CRON[23799]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Nov 26 00:17:01 eva CRON[23832]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 26 00:19:14 eva gnome-terminal-[14037]: Allocating size to GtkBox 0x559969997170 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Nov 26 00:19:14 eva gnome-terminal-[14037]: Allocating size to GtkBox 0x559969997170 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Nov 26 00:24:35 eva dhclient[13921]: DHCPREQUEST of 192.168.250.13 on wlp1s0 to 192.168.250.1 port 67 (xid=0x15efd074)
Nov 26 00:24:35 eva dhclient[13921]: DHCPACK of 192.168.250.13 from 192.168.250.1
Nov 26 00:24:35 eva NetworkManager[796]: <info> [1511673875.2164] dhcp4 (wlp1s0): address 192.168.250.13
Nov 26 00:24:35 eva NetworkManager[796]: <info> [1511673875.2165] dhcp4 (wlp1s0): plen 24 (255.255.255.0)
Nov 26 00:24:35 eva NetworkManager[796]: <info> [1511673875.2165] dhcp4 (wlp1s0): gateway 192.168.250.1
Nov 26 00:24:35 eva NetworkManager[796]: <info> [1511673875.2166] dhcp4 (wlp1s0): lease time 86400
Nov 26 00:24:35 eva NetworkManager[796]: <info> [1511673875.2166] dhcp4 (wlp1s0): nameserver '192.168.250.1'
Nov 26 00:24:35 eva NetworkManager[796]: <info> [1511673875.2166] dhcp4 (wlp1s0): domain name 'Home'
Nov 26 00:24:35 eva NetworkManager[796]: <info> [1511673875.2166] dhcp4 (wlp1s0): state changed bound -> bound
Nov 26 00:24:35 eva dbus[771]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov 26 00:24:35 eva dhclient[13921]: bound to 192.168.250.13 -- renewal in 35065 seconds.
Nov 26 00:24:35 eva systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 26 00:24:35 eva dbus[771]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 26 00:24:35 eva systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 26 00:24:35 eva nm-dispatcher: req:1 'dhcp4-change' [wlp1s0]: new request (1 scripts)
Nov 26 00:24:35 eva nm-dispatcher: req:1 'dhcp4-change' [wlp1s0]: start running ordered scripts...
Nov 26 00:25:01 eva CRON[23994]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Nov 26 00:25:18 eva org.gnome.Shell.desktop[13689]: Window manager warning: last_user_time (633959360) is greater than comparison timestamp (633959359). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Nov 26 00:25:18 eva org.gnome.Shell.desktop[13689]: Window manager warning: 0x26000c9 (Edit Revie) appears to be one of the offending windows with a timestamp of 633959360. Working around...
Nov 26 00:25:18 eva org.gnome.Shell.desktop[13689]: Window manager warning: last_user_time (633959390) is greater than comparison timestamp (633959389). This most likely represents a buggy client sending inaccurate ...

[Teoh Han Hui (teohhanhui)]

This caused data loss for me, as I was resizing a large NTFS partition using gparted.

[Teoh Han Hui (teohhanhui)]

Note: I'm not using Ubuntu, but I couldn't find a more appropriate place to give more visibility to this bug.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[sfc (sfc-0)]

Same here, sometimes the system will just freeze (even caps lock led not working), and after about 1 minute, the gnome-shell crashed to login screen, with all running apps crashed. Happens two or more times a day.

It's really annoying because sometimes this causes some lines of code I just wrote in IDE lost.

journalctl:

...
12月 21 15:30:37 sfc-HP-ENVY13 gsd-wacom[19116]: gsd-wacom: Fatal IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 chromium-browser.desktop[24804]: [24876:24876:1221/153037.848583:ERROR:x11_util.cc(89)] X IO error received (X server probably
12月 21 15:30:37 sfc-HP-ENVY13 gsd-xsettings[19120]: gsd-xsettings: Fatal IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 gsd-keyboard[19146]: gsd-keyboard: Fatal IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 chromium-browser.desktop[24804]: [24804:24804:1221/153037.848637:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] X IO error r
12月 21 15:30:37 sfc-HP-ENVY13 kerneloops-applet.desktop[19608]: kerneloops-applet: Fatal IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 gsd-clipboard[19136]: gsd-clipboard: Fatal IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 org.a11y.atspi.Registry[18957]: after 74933 requests (74933 known processed) with 0 events remaining.
12月 21 15:30:37 sfc-HP-ENVY13 org.a11y.atspi.Registry[18957]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
12月 21 15:30:37 sfc-HP-ENVY13 gsd-a11y-keyboa[19129]: gsd-a11y-keyboard: Fatal IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 wmsystemtray.desktop[19619]: after 1043 requests (1043 known processed) with 0 events remaining.
12月 21 15:30:37 sfc-HP-ENVY13 wmsystemtray.desktop[19619]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
12月 21 15:30:37 sfc-HP-ENVY13 gnome-shell[18907]: Connection to xwayland lost
12月 21 15:30:37 sfc-HP-ENVY13 guake.desktop[19617]: guake: Fatal IO error 11 (资源暂时不可用) on X server :0.
12月 21 15:30:37 sfc-HP-ENVY13 org.gnome.Shell.desktop[18907]: intel_do_flush_locked failed: Bad address
12月 21 15:30:35 sfc-HP-ENVY13 wmsystemtray.desktop[19619]: wmsystemtray: Tray icon 540000d was destroyed, removing
12月 21 15:30:35 sfc-HP-ENVY13 wmsystemtray.desktop[19619]: wmsystemtray: A poorly-behaved application tried to unmap window 540000d!
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
12月 21 15:30:03 sfc-HP-ENVY13 gnome-shell[18907...

[Daniel van Vugt (vanvugt)]

Yes it appears your gnome-shell process is crashing with "Connection to xwayland lost".

So this is generally either bug 1505409 or bug 1556601.

It's unclear if "intel_do_flush_locked" is related because in the first instance you showed that happening before the crash, and in the second instance it is logged after (with the same timestamp though).

[Daniel van Vugt (vanvugt)]

If we assume that "intel_do_flush_locked" is related to the gnome-shell crash and this is a specific and not general duplicate of one of the above bugs, the we should be looking in the package where "intel_do_flush_locked" exists too. So that's the function "do_flush_locked" in mesa's src/mesa/drivers/dri/i915/intel_batchbuffer.c

[Daniel van Vugt (vanvugt)]

Also, it appears Mesa could be trying harder to handle the error without taking down the whole process. At present Mesa will just kill the gnome-shell process when the error occcurs:

   if (ret != 0) {
      fprintf(stderr, "intel_do_flush_locked failed: %s\n", strerror(-ret));
      exit(1);
   }

[sfc (sfc-0)]

Thanks for your reply. Sometimes the crash will produce a huge coredump in my home (~200MB), but I cannot find anything useful in it with gdb. I will attach it when the next time it occurs.

[sfc (sfc-0)]

As for the log timestamp, mine is the same order as the themusicgod1's, first intel_do_flush_locked, then xwayland connection lost. I'm using journalctl -r to print the log, so the order is reversed.

[Daniel van Vugt (vanvugt)]

Please don't attach crash files or core dumps to bugs. It is a security risk for you, and not helpful to us. Instead use the 'ubuntu-bug' command to upload .crash files automatically and securely.

[sfc (sfc-0)]

Today I got the coredump, but ubuntu-bug cannot upload it, saying "ValueError ('not enough values to unpack (expected 2, got 1)',)". So I use "ubuntu-bug xwayland" command, and attached the generated report. This crash now seems only happens when the system is under load for some time (in my case high cpu usage).

gdb stacktrace of this coredump, if anything helpful:

Reading symbols from Xwayland...Reading symbols from /usr/lib/debug/.build-id/65/efba1189e8c1122d2e74c13bf7e54825c3e367.debug...done.
done.
[New LWP 3455]
[New LWP 3460]
[New LWP 3461]
[New LWP 3462]
[New LWP 3463]
[New LWP 3464]
[New LWP 3465]
[New LWP 3466]
[New LWP 3467]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录.
[Current thread is 1 (Thread 0x7f97acaffa80 (LWP 3455))]
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007f97a9b8ff5d in __GI_abort () at abort.c:90
#2 0x0000555ce6faf13a in OsAbort () at ../../../../os/utils.c:1361
#3 0x0000555ce6fb4c53 in AbortServer () at ../../../../os/log.c:877
#4 0x0000555ce6fb5a75 in FatalError (f=f@entry=0x555ce6fbd640 "failed to read Wayland events: %s\n") at ../../../../os/log.c:1015
#5 0x0000555ce6e3b43f in xwl_read_events (xwl_screen=0x555ce8f96a40) at ../../../../../hw/xwayland/xwayland.c:594
#6 0x0000555ce6faccb1 in ospoll_wait (ospoll=0x555ce8f8ba20, timeout=<optimized out>) at ../../../../os/ospoll.c:412
#7 0x0000555ce6fa5cbb in WaitForSomething (are_ready=<optimized out>) at ../../../../os/WaitFor.c:226
#8 0x0000555ce6f719f3 in Dispatch () at ../../../../dix/dispatch.c:422
#9 0x0000555ce6f75c90 in dix_main (argc=11, argv=0x7ffce0ab28c8, envp=<optimized out>) at ../../../../dix/main.c:287
#10 0x00007f97a9b781c1 in __libc_start_main (main=0x555ce6e3aa60 <main>, argc=11, argv=0x7ffce0ab28c8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7ffce0ab28b8) at ../csu/libc-start.c:308
#11 0x0000555ce6e3aa9a in _start ()

[Daniel van Vugt (vanvugt)]

Thanks. That is bug 1731911. Although what you're seeing with your desktop is gnome-shell committing suicide as a result of Xwayland crashing, so that is bug 1505409 or bug 1556601.

It would be most useful to you to track the root cause of the problem so I'll mark this as a duplicate of bug 1731911.

[Daniel van Vugt (vanvugt)]

Whoops, sorry, you are not the original reporter.

sfc: Please subscribe to bug 1731911 instead.

This bug remains about "intel_do_flush_locked failed: Bad address"

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.