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
Bugs, which is subscribed to 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().
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
