I'm marking the nouveau/Mesa crash as high severity. And the secondary
Mir crash is only medium because that's not really the problem at all.
Here's the Mesa crash:
#9 <signal handler called>
No locals.
#10 0x00007fe1e4c4f06c in pushbuf_kref () from
/tmp/apport_sandbox_hSYpvb/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
No symbol table info available.
#11 0x00007fe1e4c4f709 in pushbuf_validate () from
/tmp/apport_sandbox_hSYpvb/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
No symbol table info available.
#12 0x00007fe1e2fb25ef in nv50_state_validate (nv50=nv50@entry=0x5608093d9c40,
mask=mask@entry=4096, validate_list=validate_list@entry=0x7fe1e35ef660
<validate_list_3d>, size=size@entry=25, dirty=dirty@entry=0x5608093da018,
bufctx=0x5608093dd6f0) at
../../../../../src/gallium/drivers/nouveau/nv50/nv50_state_validate.c:554
state_mask = <optimized out>
ret = <optimized out>
i = <optimized out>
#13 0x00007fe1e2fb2797 in nv50_state_validate_3d
(nv50=nv50@entry=0x5608093d9c40, mask=mask@entry=4096) at
../../../../../src/gallium/drivers/nouveau/nv50/nv50_state_validate.c:564
ret = <optimized out>
#14 0x00007fe1e2fb4e01 in nv50_clear (pipe=0x5608093d9c40, buffers=4,
color=0x7fe1ebbf5acc, depth=1, stencil=0) at
../../../../../src/gallium/drivers/nouveau/nv50/nv50_surface.c:528
push = 0x56080930e500
fb = 0x5608093dae28
i = <optimized out>
j = <optimized out>
k = <optimized out>
mode = 0
#15 0x00007fe1e2c7ea32 in st_Clear (ctx=0x7fe1ebbf4010, mask=2) at
../../../src/mesa/state_tracker/st_cb_clear.c:463
depthRb = <optimized out>
stencilRb = <optimized out>
quad_buffers = <optimized out>
clear_buffers = 4
i = <optimized out>
#16 0x00007fe1eb9249f1 in
mir::renderer::gl::Renderer::render(std::vector<std::shared_ptr<mir::graphics::Renderable>,
std::allocator<std::shared_ptr<mir::graphics::Renderable> > > const&) const
(this=0x7fe1d00008c0, renderables=...) at ./src/renderers/gl/renderer.cpp:246
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** Summary changed:
- unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
+ unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
[nouveau crashed during glClear()]
** Tags added: nouveau
** Summary changed:
- unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
[nouveau crashed during glClear()]
+ unity-system-compositor crashed with "Failed to schedule page flip", but only
after nouveau crashed in glClear().
** Also affects: libdrm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libdrm (Ubuntu)
Importance: Undecided => High
** Tags added: unity8-desktop
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: mir
Status: New => Triaged
** Changed in: mir (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1623507
Title:
unity-system-compositor crashed with "Failed to schedule page flip",
but only after nouveau crashed in glClear().
Status in Canonical System Image:
New
Status in Mir:
Triaged
Status in libdrm package in Ubuntu:
New
Status in mesa package in Ubuntu:
New
Status in mir package in Ubuntu:
Triaged
Bug description:
16.10 first unity 8 run
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Sep 14 10:34:45 2016
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard:
Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen
Core Processor Integrated Graphics Controller [1462:7817]
NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00
[VGA controller])
Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988]
InstallationDate: Installed on 2016-09-14 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913)
ProcCmdline: /usr/sbin/unity-system-compositor
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket
--from-dm-fd 11 --to-dm-fd 14 --vt 7
ProcEnviron:
Signal: 6
SourcePackage: unity-system-compositor
StacktraceTop:
mir::fatal_error_abort(char const*, ...) () from
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
?? () from
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10
?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: unity-system-compositor crashed with SIGABRT in
mir::fatal_error_abort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
version.libdrm: libdrm2 2.4.70-1
version.lightdm: lightdm 1.19.4-0ubuntu1
version.mesa: libegl1-mesa-dev N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
