It appears this crash is a secondary crash that's come after an earlier
one.
We have two compositor threads (two monitors connected). One of them has
crashed in the renderer during glClear, which would be a nouveau bug(?).
Then our crash handler has tried to clean up and change VTs back to
their original state, which races with the other compositor thread
that's still running. And once the active VT changes, that second
compositor thread will fail to schedule a page flip, which is expected
because Mir no longer has DRM mastership.
So there are two bugs here:
(1) nouveau crashed in glClear. That's the main problem because it was the
trigger for the second.
(2) Our DRM page flipping code can't deal with flip failures without
crashing. But we already know about that thanks to bug 1489689 and bug 1584894.
** Package changed: unity-system-compositor (Ubuntu) => mir (Ubuntu)
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor 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
