Ubuntu
mir package

[regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it fails to turn vsync signal on

Bug #1345533 reported by Ricardo Salveti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Critical
Kevin DuBois
Mir 0.6.0
0.5
Fix Released
Critical
Kevin DuBois
Mir 0.5.1
mir (Ubuntu)
Fix Released
Critical
Mir development team

Bug Description

Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5 (hammerhead), as it fails to turn the vsync signal on.

This is what I get from logcat:

D/libEGL ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so
D/libEGL ( 3038): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
D/libEGL ( 3038): loaded /vendor/lib/egl/libGLESv2_adreno.so
I/qdutils ( 3038): Right Split=0
D/qdhwcomposer( 3038): int qhwc::adRead(): /sys/class/graphics/fb2/ad could not be opened : No such file or directory
I/qdhwcomposer( 3038): Initializing Qualcomm Hardware Composer
I/qdhwcomposer( 3038): MDP version: 500
I/Adreno-EGL( 3038): <qeglDrvAPI_eglInitialize:320>: EGL 1.4 QUALCOMM Build: I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, width = 1080
D/qdhwcomposer( 3038): hwc_getDisplayAttributes disp = 0, height = 1920
I/Adreno-EGL( 3038): <qeglDrvAPI_eglInitialize:320>: EGL 1.4 QUALCOMM Build: I0404c4692afb8623f95c43aeb6d5e13ed4b30ddbDate: 11/06/13
I/qdhwcomposer( 3038): hwc_registerProcs
I/qdhwcomposer( 3038): Initializing UEVENT Thread
I/qdhwcomposer( 3038): Initializing VSYNC Thread
I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=0 from /sys/class/graphics/fb0/vsync_event
I/qdhwcomposer( 3038): vsync_loop: Reading vsync for dpy=1 from /sys/class/graphics/fb1/vsync_event
D/qdhwcomposer( 3038): hwc_blank: Unblanking display: 0
D/qdhwcomposer( 3038): hwc_blank: Done unblanking display: 0
E/qdhwcomposer( 3038): hwc_vsync_control: vsync control failed. Dpy=0, enable=1 : Operation not supported
W/libEGL ( 3038): eglTerminate() called w/ 1 objects remaining
E/libEGL ( 3038): validate_display:263 error 3001 (EGL_NOT_INITIALIZED)
I/ServiceManager( 913): service 'display.qservice' died

The vsync control failed message was always there, and Mir 0.4 worked fine with it still.

System compositor log:
root@ubuntu-phablet:/var/log/lightdm# cat unity-system-compositor.log
ERROR: /build/buildd/mir-0.5.0+14.10.20140717/src/platform/graphics/android/real_hwc_wrapper.cpp(75): Throw in function virtual void mir::graphics::android::RealHwcWrapper::vsync_signal_on() const
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
std::exception::what: error turning vsync signal on. rc = ffffffa1

Tags: regression

Related branches

lp:~mir-team/mir/fix-1345533-0.5
PS Jenkins bot (community): Needs Fixing (continuous-integration)
Mir development team: Pending requested
Diff: 0 lines
Superseded for merging into lp:mir/ubuntu
PS Jenkins bot (community): Approve (continuous-integration)
Mir development team: Pending requested
Diff: 71 lines (+41/-4) (has conflicts)
3 files modified
debian/changelog (+15/-3)
src/platform/graphics/android/hwc_common_device.cpp (+8/-1)
tests/unit-tests/graphics/android/test_hwc_common_device.cpp (+18/-0)
lp:~kdub/mir/fix-1345533
PS Jenkins bot (community): Approve (continuous-integration)
Alberto Aguirre (community): Approve
Diff: 45 lines (+26/-1)
2 files modified
src/platform/graphics/android/hwc_common_device.cpp (+8/-1)
tests/unit-tests/graphics/android/test_hwc_common_device.cpp (+18/-0)
Superseded for merging into lp:mir/ubuntu
Mir development team: Pending requested
Diff: 4766 lines (+3030/-569)
63 files modified
3rd_party/android-deps/std/Log.h (+4/-0)
3rd_party/android-input/android/frameworks/base/services/input/MirLog.cpp (+11/-8)
CMakeLists.txt (+5/-1)
cmake/src/mir/mir_discover_gtest_tests.cpp (+5/-0)
debian/control (+2/-2)
debian/libmirserver24.install (+1/-1)
examples/demo-shell/demo_shell.cpp (+20/-0)
examples/demo-shell/window_manager.cpp (+11/-0)
examples/fingerpaint.c (+6/-0)
include/client/mir_toolkit/mir_surface.h (+14/-0)
include/server/mir/default_server_configuration.h (+4/-9)
include/server/mir/frontend/surface.h (+1/-0)
include/server/mir/shell/host_lifecycle_event_listener.h (+44/-0)
include/shared/mir_toolkit/common.h (+4/-0)
include/test/mir_test/auto_unblock_thread.h (+5/-0)
include/test/mir_test_doubles/mock_frontend_surface.h (+1/-0)
include/test/mir_test_doubles/mock_rpc_report.h (+2/-2)
include/test/mir_test_doubles/stub_scene_surface.h (+1/-0)
src/client/logging/rpc_report.cpp (+4/-4)
src/client/logging/rpc_report.h (+2/-2)
src/client/lttng/rpc_report.cpp (+2/-2)
src/client/lttng/rpc_report.h (+2/-2)
src/client/mir_surface.cpp (+6/-3)
src/client/mir_surface.h (+3/-0)
src/client/mir_surface_api.cpp (+49/-10)
src/client/rpc/CMakeLists.txt (+3/-1)
src/client/rpc/make_socket_rpc_channel.cpp (+10/-5)
src/client/rpc/mir_basic_rpc_channel.h (+1/-1)
src/client/rpc/mir_protobuf_rpc_channel.cpp (+143/-285)
src/client/rpc/mir_protobuf_rpc_channel.h (+34/-36)
src/client/rpc/null_rpc_report.cpp (+2/-2)
src/client/rpc/null_rpc_report.h (+2/-2)
src/client/rpc/rpc_report.h (+2/-2)
src/client/rpc/stream_socket_transport.cpp (+440/-0)
src/client/rpc/stream_socket_transport.h (+66/-0)
src/client/rpc/stream_transport.h (+151/-0)
src/platform/graphics/android/hwc_common_device.cpp (+8/-1)
src/server/CMakeLists.txt (+1/-1)
src/server/compositor/buffer_queue.cpp (+14/-1)
src/server/frontend/default_configuration.cpp (+0/-23)
src/server/frontend/session_mediator.cpp (+9/-0)
src/server/graphics/default_configuration.cpp (+2/-1)
src/server/graphics/nested/mir_client_host_connection.cpp (+16/-2)
src/server/graphics/nested/mir_client_host_connection.h (+5/-1)
src/server/scene/basic_surface.cpp (+125/-62)
src/server/scene/basic_surface.h (+9/-8)
src/server/shell/default_configuration.cpp (+12/-0)
src/server/shell/null_host_lifecycle_event_listener.h (+38/-0)
src/shared/protobuf/mir_protobuf.proto (+2/-0)
tests/acceptance-tests/CMakeLists.txt (+1/-0)
tests/acceptance-tests/test_client_library.cpp (+1/-1)
tests/acceptance-tests/test_client_surface_visibility.cpp (+4/-1)
tests/acceptance-tests/test_macros.cpp (+28/-0)
tests/acceptance-tests/test_nested_mir.cpp (+72/-0)
tests/acceptance-tests/test_server_shutdown.cpp (+3/-0)
tests/integration-tests/shell/test_session_lifecycle_event.cpp (+1/-0)
tests/unit-tests/client/CMakeLists.txt (+2/-0)
tests/unit-tests/client/test_client_mir_surface.cpp (+38/-26)
tests/unit-tests/client/test_protobuf_rpc_channel.cpp (+381/-0)
tests/unit-tests/client/test_stream_transport.cpp (+1060/-0)
tests/unit-tests/graphics/android/test_hwc_common_device.cpp (+18/-0)
tests/unit-tests/scene/test_basic_surface.cpp (+117/-15)
tests/unit-tests/scene/test_surface_impl.cpp (+0/-46)
lp:ubuntu/utopic-proposed/mir
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

From http://launchpadlibrarian.net/180157436/mir_0.4.1%2B14.10.20140714-0ubuntu1_0.5.0%2B14.10.20140717-0ubuntu1.diff.gz it seems that the reason is that now this error is fatal, while before it wasn't even checking the return value.

Do we need this error to be fatal?

Daniel van Vugt (vanvugt)
Changed in mir:
importance: Undecided → Critical
Changed in mir (Ubuntu):
importance: Undecided → Critical
Changed in mir:
milestone: none → 0.6.0
summary: - [hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync
- signal on
+ [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to
+ turn vsync signal on
tags: added: regression
Kevin DuBois (kdub)
Changed in mir:
assignee: nobody → Kevin DuBois (kdub)
Revision history for this message
Kevin DuBois (kdub) wrote : Re: [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to turn vsync signal on

seems to affect nexus 10/5, but not 4/7

Changed in mir:
status: New → In Progress
Revision history for this message
Kevin DuBois (kdub) wrote :

fix checked on the n10, still need confirmation on the n5. Regression came in rev 1767 and caused the error from the drivers (which was previously ignored) to generate an exception on startup.

Daniel van Vugt (vanvugt)
Changed in mir:
status: In Progress → Fix Committed
Changed in mir (Ubuntu):
status: New → In Progress
Daniel van Vugt (vanvugt)
Changed in mir (Ubuntu):
assignee: nobody → Mir development team (mir-team)
summary: - [regression][hammerhead] Mir fails to start on Nexus 5 as it fails to
- turn vsync signal on
+ [regression][hammerhead] Mir fails to start on Nexus 5 & 10 as it fails
+ to turn vsync signal on
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mir - 0.5.0+14.10.20140722-0ubuntu1

---------------
mir (0.5.0+14.10.20140722-0ubuntu1) utopic; urgency=medium

  [ Kevin Gunn ]
  * Fixed: [regression] Mir fails to start on Nexus 5 / Nexus 10 (LP: #1345533)
 -- Ubuntu daily release <email address hidden> Tue, 22 Jul 2014 02:17:22 +0000

Changed in mir (Ubuntu):
status: In Progress → Fix Released
kevin gunn (kgunn72)
Changed in mir:
status: Fix Committed → Fix Released
Daniel van Vugt (vanvugt)
Changed in mir:
status: Fix Released → Fix Committed
Daniel van Vugt (vanvugt)
Changed in mir:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.