| 2017-06-23 08:51:10 |
Alan Griffiths |
description |
This is on zesty, with Mir 0.27, MirAL 1.4 and rebuilds of QtMir and USC (in silo 2818 at the time of report)
https://code.launchpad.net/~mir-team/mir/0.27/+merge/325738
https://code.launchpad.net/~alan-griffiths/miral/1.4/+merge/325737
https://code.launchpad.net/~alan-griffiths/qtmir/mir-0.27-compat/+merge/325749
https://code.launchpad.net/~alan-griffiths/unity-system-compositor/mir-0.27-compat/+merge/325751
with a "live" USB. Steps to reproduce:
1. boot off the USB
2. sudo apt-add-repository ppa:ci-train-ppa-service/2818
3. sudo apt update
4. sudo apt upgrade -y
5. sudo service lightdm restart
6. Log out
7. select U8 session
8. sign in as ubuntu/<blank>
8. Search "ter" & down arrow to select Terminal
Lockup
The lockup happens in Unity8's renderer thread, once it calls
eglSwapBuffers after adding the client surface to the scene.
eglSwapBuffers prints a familiar error:
intel_do_flush_locked failed: No such file or directory
and calls __GI_exit() on the renderer thread, which causes Qt's threads
to block is a awkward way.
So something has changed in Mir 0.27 that Mesa/i915 is unhappy with. |
Simpler scenario to reproduce:
1. Take a Zesty system with Intel graphics and Mir trunk
2. Apply lp:~alan-griffiths/mir/dont-handle-nested-input-on-rpc-thread
(To avoid the issue seen in comment #1)
3. Start a host server running mesa-kms (CNR using mesa-x11)
$ sudo bin/mir_demo_server --vt 4 --arw-file --window-manager system-compositor
4. Start a nested server with an EGL client
$ bin/mir_demo_server --no-file --host /tmp/mir_socket --launch bin/mir_demo_client_egltriangle
5. Resize the window (Alt-Middle drag) until the display freezes (doesn't take long)
Expect: the display doesn't freeze
Actual: the nested server (step 3) has exited with "intel_do_flush_locked failed: No such file or directory" (but the client is still running).
=== original description ===
This is on zesty, with Mir 0.27, MirAL 1.4 and rebuilds of QtMir and USC (in silo 2818 at the time of report)
https://code.launchpad.net/~mir-team/mir/0.27/+merge/325738
https://code.launchpad.net/~alan-griffiths/miral/1.4/+merge/325737
https://code.launchpad.net/~alan-griffiths/qtmir/mir-0.27-compat/+merge/325749
https://code.launchpad.net/~alan-griffiths/unity-system-compositor/mir-0.27-compat/+merge/325751
with a "live" USB. Steps to reproduce:
1. boot off the USB
2. sudo apt-add-repository ppa:ci-train-ppa-service/2818
3. sudo apt update
4. sudo apt upgrade -y
5. sudo service lightdm restart
6. Log out
7. select U8 session
8. sign in as ubuntu/<blank>
8. Search "ter" & down arrow to select Terminal
Lockup
The lockup happens in Unity8's renderer thread, once it calls
eglSwapBuffers after adding the client surface to the scene.
eglSwapBuffers prints a familiar error:
intel_do_flush_locked failed: No such file or directory
and calls __GI_exit() on the renderer thread, which causes Qt's threads
to block is a awkward way.
So something has changed in Mir 0.27 that Mesa/i915 is unhappy with. |
|
