992738 - Xorg sometimes errors out during reboot with "(EE) failed to create screen resources(EE)"

Status: RESOLVED WONTFIX

(Mozilla QA Graveyard :: Infrastructure, defect)

Description

[Andrei Eftimie]

We had mm-ub-1310-64-2 disconnect from master during the weekend.

It wouldn't accept VNC connections. SSH'ed in, restarted lightdm. This resumed the VNC service. The machine had a dialog that stated "System program problem detected". More details revealed the problem was with Xorg: "Sorry, the program "Xorg" closed unexpectedly".

Xorg logfile:
> [2133406.245] (II) SELinux: Disabled on system
> [2133406.246] (II) AIGLX: Screen 0 is not DRI2 capable
> [2133406.246] (II) AIGLX: Screen 0 is not DRI capable
> [2133406.247] (II) AIGLX: Loaded and initialized swrast
> [2133406.247] (II) GLX: Initialized DRISWRAST GL provider for screen 0
> [2133406.247] (EE)
> Fatal server error:
> [2133406.247] (EE) failed to create screen resources(EE)
> [2133406.247] (EE)
> Please consult the The X.Org Foundation support
>    at http://wiki.x.org
>  for help.
> [2133406.247] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
> [2133406.247] (EE)
> [2133406.247] (WW) vmware(0): drmDropMaster failed: Invalid argument
> [2133406.252] (EE) Server terminated with error (1). Closing log file.

Similar in nature to bug 987540 (eg. Window manager failure). I am not sure about the relation of Xorg and gnome. I assume gnome runs on top of Xorg.

The Jenkins client was also closed when Xorg crashed.
We had no testruns affected by this crash.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 10/02 - 10/06)]

Andrei, can you please attach the content of /var/log/Xorg.1.log? Thanks.

Comment 2

[Andrei Eftimie]

Attachment: Xorg.1.log

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 10/02 - 10/06)]

This might not be a crash but due to some other circumstances the machine has been restarted. That explains why Jenkins was not connected. Andrei can you please check the syslog files around that time? Maybe we see something which caused the restart.

What I think is that we are most likely affected by:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/993078

Comment 4

[Andrei Eftimie]

Attachment: mm-ub-1310-64-2.syslog.txt

I think this was the error:
> Apr  6 08:16:30 mm-ub-1310-64-2 gnome-session[1421]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 10/02 - 10/06)]

Could we enable verbose gnome-session output on that node so we get more details?

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2] (away 10/02 - 10/06)]

Mozmill-CI will be shutdown on Monday next week. So this is not needed anymore.