You are not logged in.

#1 2015-08-07 21:30:04

KarlP
Member
From: Vorderstoder, AUSTRIA
Registered: 2015-01-01
Posts: 31

fatal IO error 11 on X server-Crashes

Since two months I have noticed X Server Crashes happening occasionally. After such a crash the login screen is appearing again.

So I have searched through journalctl for the string 'fatal IO error 11'. The latest occasion was:

journalctl --since=2015-08-01 | grep 'Aug 06 01:48'
Aug 06 01:48:08 evo063 org.a11y.atspi.Registry[445]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Aug 06 01:48:10 evo063 org.a11y.atspi.Registry[445]: after 337 requests (337 known processed) with 0 events remaining.
Aug 06 01:48:08 evo063 polkitd[402]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.7, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale de_AT.UTF-8) (disconnected from bus)
Aug 06 01:48:11 evo063 org.a11y.Bus[365]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Aug 06 01:48:11 evo063 acpid[300]: client 330[0:0] has disconnected
Aug 06 01:48:11 evo063 acpid[300]: client 330[0:0] has disconnected
Aug 06 01:48:11 evo063 acpid[300]: client connected from 1238[0:0]
Aug 06 01:48:11 evo063 acpid[300]: 1 client rule loaded
Aug 06 01:48:11 evo063 org.gtk.vfs.Daemon[365]: A connection to the bus can't be made
Aug 06 01:48:11 evo063 org.gtk.Private.UDisks2VolumeMonitor[365]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Aug 06 01:48:11 evo063 org.gtk.Private.AfcVolumeMonitor[365]: g_dbus_connection_real_closed: Remote peer vanished with error: Fehler beim Senden der Nachricht: Datenübergabe unterbrochen (broken pipe) (g-io-error-quark, 44). Exiting.
Aug 06 01:48:11 evo063 acpid[300]: client connected from 1238[0:0]
Aug 06 01:48:11 evo063 acpid[300]: 1 client rule loaded
Aug 06 01:48:11 evo063 org.gtk.vfs.Daemon[365]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Aug 06 01:48:11 evo063 org.gtk.vfs.Daemon[365]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

As I understand there is some “Resource temporarily unavailable” and something “has disconnected”.

Has somebody an idea what causes these crashes?

Offline

#2 2015-08-10 15:01:51

mike.dornitt
Member
Registered: 2015-08-10
Posts: 1

Re: fatal IO error 11 on X server-Crashes

Similar bug:

Jun 18 12:30:53 Aspire-7535 kernel: [ 4794.917287] [fglrx] IRQ 18 Disabled
Jun 18 12:30:53 Aspire-7535 gnome-session[3086]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.#012
Jun 18 12:30:53 Aspire-7535 kernel: [ 4795.002229] show_signal_msg: 36 callbacks suppressed
Jun 18 12:30:53 Aspire-7535 kernel: [ 4795.002235] firefox[8721]: segfault at c ip 00007f5ca6f50cc0 sp 00007fff28fc3ec8 error 4 in libxcb-glx.so.0.0.0[7f5ca6f43000+15000]
Jun 18 12:30:53 Aspire-7535 acpid: client 2890[0:0] has disconnected
Jun 18 12:30:53 Aspire-7535 acpid: client connected from 8737[0:0]
Jun 18 12:30:53 Aspire-7535 acpid: 1 client rule loaded
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.481828] [fglrx] GART Table is not in FRAME_BUFFER range 
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.482280] [fglrx] Could not enable MSI; System prevented initialization
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.483242] [fglrx] Firegl kernel thread PID: 8740
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.483544] [fglrx] Firegl kernel thread PID: 8741
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.483707] [fglrx] Firegl kernel thread PID: 8742
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.484101] [fglrx] IRQ 18 Enabled
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.746103] [fglrx] Gart USWC size:1156 M.
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.746108] [fglrx] Gart cacheable size:458 M.
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.746114] [fglrx] Reserved FB block: Shared offset:0, size:1000000 
Jun 18 12:30:54 Aspire-7535 kernel: [ 4795.746118] [fglrx] Reserved FB block: Unshared offset:fffb000, size:5000

I found this info:
10de:0421 X crashes with gnome-session: Fatal IO error 11 (launchpad.net)
http://iswwwup.com/t/59385096874f/ubunt … or-11.html

I hope this will help you.

Offline

#3 2015-08-11 11:35:38

KarlP
Member
From: Vorderstoder, AUSTRIA
Registered: 2015-01-01
Posts: 31

Re: fatal IO error 11 on X server-Crashes

Thank you for your info.

So, if I got it right, there is still no solution for this bug!?

Offline

#4 2016-01-14 16:45:49

Vyre
Member
Registered: 2011-06-18
Posts: 16

Re: fatal IO error 11 on X server-Crashes

I'm having the same issue.  It keeps causing lxdm to close my session, losing the current state of my desktop.  Tends to happen when I leave it idol for a bit.

Offline

#5 2016-01-16 19:56:37

Vyre
Member
Registered: 2011-06-18
Posts: 16

Re: fatal IO error 11 on X server-Crashes

Some of the same errors are happening in this thread.  It's being reported as an issue with rebooting, but they appear to be related.  In particular, this series of errors seem to be common:

Jan 16 13:46:15 siona org.a11y.atspi.Registry[19935]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jan 16 13:46:15 siona org.a11y.atspi.Registry[19935]: after 9901 requests (9901 known processed) with 0 events remaining.
Jan 16 13:46:15 siona polkitd[474]: Unregistered Authentication Agent for unix-session:c3 (system bus name :1.33, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

org.a11y.atspi.Registry appears to come from the at-spi2-core package.  Perhaps we should file a bug with this package?

Offline

#6 2016-02-15 03:57:01

HoZ
Member
Registered: 2008-03-30
Posts: 38

Re: fatal IO error 11 on X server-Crashes

I am having this issue and the same error messages as well.  I have noticed, however, that it seems to depend on which xscreensaver that I select.  GLSlideshow will consistently result in an X crash after some time, and kick me back out to a VT.  Others (GLMatrix) will not.  I am unsure how all of this relates, but maybe another piece to the puzzle.

Offline

#7 2016-02-15 15:21:47

Vyre
Member
Registered: 2011-06-18
Posts: 16

Re: fatal IO error 11 on X server-Crashes

As I lay out in another forum post, for me this issue ultimately was an Xorg issue that gets solved in the linked post.

Offline

#8 2016-02-15 20:50:05

HoZ
Member
Registered: 2008-03-30
Posts: 38

Re: fatal IO error 11 on X server-Crashes

Thank you.  Although it may still be too early to tell for sure, this seems to be effective for me as well.   I have not yet had an issue since switching to UXA. 

Vyre wrote:

As I lay out in another forum post, for me this issue ultimately was an Xorg issue that gets solved in the linked post.

Offline

#9 2016-07-14 19:00:41

Meach
Member
Registered: 2016-07-14
Posts: 1

Re: fatal IO error 11 on X server-Crashes

Any further tips on how to prevent this?   I am running Violo's Catalyst (15.12) and Xorg(1.17).    Most of the tips refer to intel drivers.   This is driving me batty.    Twice a week Xorg takes a big crap and restarts.

I can't believe I would actually consider going back to Windows for a stable desktop.   Yet I need native docker and others.

Offline

#10 2016-09-16 22:10:22

pid_wolf
Member
Registered: 2016-09-16
Posts: 1

Re: fatal IO error 11 on X server-Crashes

For me the same problem occurs. Ubuntu 16.04, using video Sky Lake Integrated Graphics. After the computer lock the session, sometimes occurs, you can not unlock the session. The screen goes black. You must restart the lighdm.

Using the xorg below:

Section "Device"
     Identifier "Intel Graphics"
     Driver "intel"
     Option "AccelMethod" "sna"
     Option "TearFree" "true"
     Option "DRI" "3"
EndSection

Offline

Board footer

Powered by FluxBB