Ubuntu
xserver-xorg-video-intel package

Kicked out of desktop

Bug #1443116 reported by Páll Haraldsson on 2015-04-12

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xserver-xorg-video-intel (Ubuntu)	Expired	Medium	Unassigned

Bug Description

[Update, see first comment #8 and #7 (or first comment #5 and my response at #6).]

If memory runs out, maybe not much can be done, but I believe this has not happened to me in older Ubuntu versions:

Apr 12 14:29:51 Ryksugan kernel: [15064.494054] Xorg: page allocation failure: order:0, mode:0xa00d4
Apr 12 14:29:51 Ryksugan kernel: [15064.494063] CPU: 0 PID: 792 Comm: Xorg Tainted: P W OE 3.19.0-13-generic #13-Ubuntu
Apr 12 14:29:51 Ryksugan kernel: [15064.494065] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009
Apr 12 14:29:51 Ryksugan kernel: [15064.494067] 0000000000000000 ffff8800d784f618 ffffffff817c2205 ffff88011fc0fd78
Apr 12 14:29:51 Ryksugan kernel: [15064.494071] 00000000000a00d4 ffff8800d784f6a8 ffffffff8117f148 ffff8800d784f698
Apr 12 14:29:51 Ryksugan kernel: [15064.494074] 0000000100000000 0000000000000000 0000000000000042 ffff88011fff8e38
Apr 12 14:29:51 Ryksugan kernel: [15064.494078] Call Trace:

At about 14:30 I felt the machine sluggish and I knew chromium-browser had been eating up memory (4 GB RAM and 4 GB SSD swap, have seen it or parts of it get killed before without this result). [In the past I've had trouble, usually could do unity --replace in virtual console.]

[Note, after]
Apr 12 14:30:37 Ryksugan kernel: [15110.743287] chromium-browse: page allocation failure: order:0, mode:0xa00d4

[Note before and all this probably unrelated, last chrome error before, /var/log/syslog.1 in reverse order:]
Apr 12 14:14:35 Ryksugan kernel: [14148.682087] Out of memory: Kill process 13674 (chromium-browse) score 381 or sacrifice child
..
Apr 12 14:04:24 Ryksugan kernel: [13537.199125] traps: chromium-browse[13500] trap invalid opcode ip:7fc6d4201fc9 sp:7ffcda1791f8 error:0 in libv8.so[7f
c6d3d34000+5dc000]
Apr 12 14:04:25 Ryksugan kernel: [13538.257833] traps: chromium-browse[13462] trap invalid opcode ip:7fc6d4201fc9 sp:7ffcda17ab68 error:0 in libv8.so[7f
c6d3d34000+5dc000]

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
Uname: Linux 3.19.0-13-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.17-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Apr 12 14:51:03 2015
DistUpgraded: 2015-04-06 16:46:01,057 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:022f]
Subsystem: Dell Device [1028:022f]
InstallationDate: Installed on 2014-08-21 (233 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 1525
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to vivid on 2015-04-06 (5 days ago)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Sun Apr 12 14:30:42 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 12631
vendor SEC
xserver.version: 2:1.17.1-0ubuntu3

See original description

Tags:

Revision history for this message

Páll Haraldsson (pall-haraldsson) wrote on 2015-04-12:

syslog.1 Edit (7.2 MiB, application/octet-stream)
BootLog.txt Edit (6.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (252.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (6.0 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (422 bytes, text/plain; charset="utf-8")
DpkgLog.txt Edit (3.2 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (46.2 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (2.0 MiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (1.1 KiB, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (11.1 KiB, text/plain; charset="utf-8")
LightdmGreeterLogOld.txt Edit (7.6 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (10.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (620 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (319 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (136.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (286.0 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (601 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (24.2 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (28.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (4.2 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (4.9 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (409 bytes, text/plain; charset="utf-8")

Revision history for this message

Páll Haraldsson (pall-haraldsson) wrote on 2015-04-12:

syslog Edit (921.8 KiB, text/plain)

Revision history for this message

Páll Haraldsson (pall-haraldsson) wrote on 2015-04-12:

Really?: "Server terminated successfully (0). Closing log file" Edit (28.2 KiB, application/x-trash)

Revision history for this message

Páll Haraldsson (pall-haraldsson) wrote on 2015-04-12:

Just in case, seems this only shows correct startup after crash Edit (24.2 KiB, text/plain)

summary:

- Xorg crash (probably out of memory)
+ Xorg crash(?) (probably out of memory)

Revision history for this message

Chris Wilson (ickle) wrote on 2015-04-12: Re: Xorg crash(?) (probably out of memory)

Just to clarify, X did not crash. gnome-session crashed because of mesa not handling the failure. X itself should be pretty robust against oom.

Revision history for this message

Páll Haraldsson (pall-haraldsson) wrote on 2015-04-12:

Download full text (6.3 KiB)

[Not sure what (mesa) package to tag, there is a gnome-session[-bin] on likely (more so than mesa that is not included in logs). Gnome-session without -bin ending isn't even installed (GNOME3).]

Thanks for clarifying, I think you are saying, about here is the first real error:

Apr 12 14:30:38 Ryksugan gnome-session[1509]: intel_do_flush_locked failed: Cannot allocate memory
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Loading plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Starting plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App 'compiz.desktop' exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop' exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App 'compiz.desktop' respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop' respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: Unrecoverable failure in required component compiz.desktop
Apr 12 14:30:39 Ryksugan gnome-session[1509]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: CRITICAL: We failed, but the fail whale is dead. Sorry....

[Then previous (allocation) failure(s) weren't really "failures", that is, the processes handle them? At least Xorg, also compiz?]

[One thing first, if this can't be fixed for sure, even Windows had a "virtual memory low" dialog box warning, years ago when I used it. Probably easy to make for Linux, might be available as an optional package, but should it be built in?]

Since gnome-session failed with "intel_do_flush_locked failed", does that mean this has to do with drivers (Intel graphics)? Would other GPUs (possibly) handle better?

Good to know that "X itself should be pretty robust against oom" implying oom can be survived and should be for all components such as, mesa, ngome-session[-bin], compiz[-core], drivers (and possibly even chrome..).

[I feel at least the Linux kernel should. Yes, it didn't really fail here, but sometimes thrashing has been a real problem and even getting to virtual terminal is impossible or very slow because of thrashing or something. I feel the kernel should hold up better so I can at least go in and kill stuff..]

If compiz[-core] is for sure not the package (with compiz.desktop) with a problem, but possibly also a package with a problem, should I report that or can I add it too here?

[Not sure what (mesa) package to tag, there is a gnome-session[-bin] on likely (more so than mesa that is not included in logs).  Gnome-session without -bin ending isn't even installed (GNOME3).]

Thanks for clarifying, I think you are saying, about here is the first real error:

[Then previous (allocation) failure(s) weren't really "failures", that is, the processes handle them? At least Xorg, also compiz?]

Since gnome-session failed with "intel_do_flush_locked failed", does that mean this has to do with drivers (Intel graphics)? Would other GPUs (possibly) handle better?

If compiz[-core] is for sure not the package (with compiz.desktop) with a problem, but possibly also a package with a problem, should I report that or can I add it too here?

Apr 12 14:29:51 Ryksugan kernel: [15064.494054] Xorg: page allocation failure: order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.740973] compiz: page allocation failure: order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.743287] chromium-browse: page allocation failure: order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.744173] chromium-browse invoked oom-killer: gfp_mask=0x0, order=0, oom_score_adj=200
Apr 12 14:30:37 Ryksugan kernel: [15110.744176] chromium-browse cpuset=session-c2.scope mems_allowed=0
..
Apr 12 14:30:37 Ryksugan kernel: [15110.744808] Out of memory: Kill process 13574 (chromium-browse) score 364 or sacrifice child
Apr 12 14:30:37 Ryksugan kernel: [15110.744813] Killed process 13574 (chromium-browse) total-vm:1642476kB, anon-rss:392980kB, file-rss:3536kB
Apr 12 14:30:38 Ryksugan gnome-session[1509]: intel_do_flush_locked failed: Cannot allocate memory
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Loading plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Starting plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App 'compiz.desktop' exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop' exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App 'compiz.desktop' respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop' respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: Unrecoverable failure in required component compiz.desktop
Apr 12 14:30:39 Ryksugan gnome-session[1509]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Apr 12 14:30:39 Ryksugan org.ayatana.bamf[1401]: ** (bamfdaemon:1435): WARNING **: Got an X error: BadWindow (invalid Window parameter)
Apr 12 14:30:39 Ryksugan pulseaudio[15446]: [pulseaudio] main.c: User-configured server at {f94f7f1731f6b57488f4027d53f78730}unix:/run/user/1000/pulse/native, which appears to be local. Probing deeper.
Apr 12 14:30:39 Ryksugan gnome-session[1509]: (nm-applet:1727): GLib-GObject-WARNING **: The property GtkSettings:gtk-color-palette is deprecated and shouldn't be used anymore. It will be removed in a future version.
Apr 12 14:30:40 Ryksugan gnome-session[1509]: (update-notifier:2286): GLib-GObject-WARNING **: The property GtkSettings:gtk-color-palette is deprecated and shouldn't be used anymore. It will be removed in a future version.
Apr 12 14:30:40 Ryksugan rtkit-daemon[968]: Successfully made thread 15449 of process 15449 (n/a) owned by '1000' high priority at nice level -11.
Apr 12 14:30:40 Ryksugan rtkit-daemon[968]: Supervising 1 threads of 1 processes of 1 users.
Apr 12 14:30:40 Ryksugan pulseaudio[15449]: [pulseaudio] pid.c: Stale PID file, overwriting.
Apr 12 14:30:40 Ryksugan gnome-session[1509]: compiz (core) - Info: Loading plugin: ccp
Apr 12 14:30:40 Ryksugan gnome-session[1509]: compiz (core) - Info: Starting plugin: ccp
..
Apr 12 14:30:41 Ryksugan gnome-session[1509]: [15419:15419:0412/143041:ERROR:browser_main_loop.cc(216)] Gtk: cannot open display: :0
Apr 12 14:30:41 Ryksugan gnome-session[1509]: compiz (core) - Warn: SmcOpenConnection failed: Could not open network socket
Apr 12 14:30:41 Ryksugan gnome-session[1509]: XIO:  fatal IO error 111 (Connection refused) on X server ":0"
Apr 12 14:30:41 Ryksugan gnome-session[1509]: after 2023 requests (2016 known processed) with 203 events remaining.
Apr 12 14:30:41 Ryksugan gnome-session[1509]: compizconfig - Info: Backend     : gsettings
Apr 12 14:30:41 Ryksugan gnome-session[1509]: compizconfig - Info: Integration : true
Apr 12 14:30:41 Ryksugan gnome-session[1509]: compizconfig - Info: Profile     : unity

affects:	xorg (Ubuntu) → ubuntu
summary:	- Xorg crash(?) (probably out of memory) + Kicked out of desktop (gnome-session failed I'm told) (probably out of + memory)

Páll Haraldsson (pall-haraldsson) on 2015-04-12

description:

updated

Revision history for this message

Páll Haraldsson (pall-haraldsson) wrote on 2015-04-12: Re: Kicked out of desktop (gnome-session failed I'm told) (probably out of memory)

>Since gnome-session failed with "intel_do_flush_locked failed", does that mean this has to do with drivers (Intel graphics)? Would other GPUs (possibly) handle better?

Thinking about this more, yes, I think Wilson is blaming ""intel_do_flush_locked"=mesa. I think of mesa as 3D, but it is the project with (also) open source drivers? Still not sure what is the right package, xserver-xorg-video-intel (or something like libgl1-mesa-dri, not sure about intricate details of mesa, but none of them drivres or relevant?)?

[Assume Intel [..] i965=GM965/GL960]
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)

Revision history for this message

Páll Haraldsson (pall-haraldsson) wrote on 2015-04-12:

Not sure about this. This package and/or gnome-session (and/or compiz)?

affects:	ubuntu → xserver-xorg-video-intel (Ubuntu)
description:	updated
description:	updated

penalvch (penalvch) on 2015-09-27

tags:

added: latest-bios-a19

Revision history for this message

penalvch (penalvch) wrote on 2016-02-01:

Páll Haraldsson, given Vivid is EOL'ing imminently, to see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

tags:	added: latest-bios-a17 removed: latest-bios-a19
Changed in xserver-xorg-video-intel (Ubuntu):
importance:	Undecided → Medium
status:	New → Incomplete
summary:	- Kicked out of desktop (gnome-session failed I'm told) (probably out of - memory) + Kicked out of desktop

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-04-01:

#10

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-video-intel (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuxserver-xorg-video-intel package

Kicked out of desktop

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xserver-xorg-video-intel package