unity-system-compositor crashed with SIGSEGV

Bug #1672793 reported by Aram Paronikyan on 2017-03-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity System Compositor
unity-system-compositor (Ubuntu)

Bug Description

I just got this on the first login to my new Ubuntu user profile

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: unity-system-compositor 0.9.1+17.04.20170216-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
Uname: Linux 4.10.0-11-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Tue Mar 14 20:14:24 2017
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller])
InstallationDate: Installed on 2013-09-15 (1275 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 13 --to-dm-fd 22 --vt 8

 Segfault happened at: 0x7f8dc76dd07f: mov 0x8(%r15),%edx
 PC (0x7f8dc76dd07f) ok
 source "0x8(%r15)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-system-compositor
 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
 () at /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
Title: unity-system-compositor crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)

version.libdrm: libdrm2 2.4.75-1ubuntu1
version.lightdm: lightdm 1.21.5-0ubuntu1
version.mesa: libegl1-mesa-dev 13.0.4-1ubuntu1

Aram Paronikyan (paronikyan) wrote :

 pushbuf_kref (push=push@entry=0x564379e96ea0, bo=0x0, flags=0) at ../../nouveau/pushbuf.c:165
 pushbuf_validate (push=0x564379e96ea0, retry=<optimized out>) at ../../nouveau/pushbuf.c:506
 nouveau_pushbuf_validate (push=<optimized out>) at ../../nouveau/pushbuf.c:753
 nv50_state_validate (nv50=nv50@entry=0x564379ee91d0, mask=mask@entry=4096, validate_list=validate_list@entry=0x7f8dc866d5a0 <validate_list_3d>, size=size@entry=26, dirty=dirty@entry=0x564379ee95c8, bufctx=0x564379ee72a0) at ../../../../../src/gallium/drivers/nouveau/nv50/nv50_state_validate.c:582
 nv50_state_validate_3d (nv50=nv50@entry=0x564379ee91d0, mask=mask@entry=4096) at ../../../../../src/gallium/drivers/nouveau/nv50/nv50_state_validate.c:592

Changed in unity-system-compositor (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1553328, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

information type: Private → Public
Daniel van Vugt (vanvugt) wrote :

The nouveau driver is too unstable to handle multi-threaded rendering (which Mir and Unity8 uses by default). If you want to use nouveau maybe try unplugging one of your monitors.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers