Linaro-android February 2016

linaro-android@lists.linaro.org

1 participants
3 discussions

by Shawn Guo

Hi Guys, I need help on a Lollipop booting issue. I'm trying to boot Android 5.1.1 on a customer SoC which integrates Cortex-A9 MP and Mali 400. It's quite close to get into the launcher, but it fails to due to an ANR in SystemUI. The full logcat is attached, and some highlights of the log are as below. 1. There are quite some messages from Choreographer like this: I/Choreographer( 1220): Skipped 391 frames! The application may be doing too much work on its main thread. 2. There a number of window freeze timeout messages in the log. W/WindowManager( 1220): Window freeze timeout expired. W/WindowManager( 1220): Force clearing orientation change: Window{xxxxxxxxxxxxxx} 3. I see "Boot is finished", but right before it, there is a "BOOT TIMEOUT". W/WindowManager( 1220): ***** BOOT TIMEOUT: forcing display enabled I/SurfaceFlinger( 874): Boot is finished (88437 ms) I'm a bit new to Android, and running out of idea what is happening here. So any suggestions or comments about where to look at or how to debug such issue is highly appreciated. Shawn

8 years, 3 months

android-build toolchain-trunk, toolchain64-trunk jobs are broken due to unavailability of TCWG files

by Paul Sokolovsky

Hello, Following jobs: https://android-build.linaro.org/jenkins/job/linaro-android_toolchain-trunk/ https://android-build.linaro.org/jenkins/job/linaro-android_toolchain64-tru… appear to be broken for a month or more. Of their 6h15m runtime (when they're killed by build timeout) it spends about 3h in what appears to be an infinite loop trying to download some TCWG deliverables: https://android-build.linaro.org/jenkins/job/linaro-android_toolchain64-tru… As it happens for prolonged time and uses an anti-pattern (infinite loop) which wastes good deal of resources, I'm disabling these jobs now. Please review whether they're needed and fix them, and please be sure to use finite number of retries. P.S. This came up with me reviewing job status after Jenkins security upgrade over the weekend. Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

8 years, 12 months

[ANN] Gerrit upgraded to 2.11.5

by Paul Sokolovsky

Hello, All Linaro Gerrit servers have been upgraded to Gerrit 2.11.5 in planned manner. As was announced previously, we intended to upgrade directly to the latest 2.12, but literally couple of dates before upgrade we found out that there's known issue which affects replication services and thus our Git HA infrastructure. The bug has bean fixed by now in the Gerrit master, but the date of 2.12.1 release wasn't yet announced. As the aim of the current upgrade was to get on newer Gerrit version than now-old 2.10, we decided to upgrade to 2.11.5 in the meantime, and revisit upgrade to 2.12 after bug fix releases. Upgrade services appear to work stable based based on weekend monitoring, ditto for CI loops integrating with Gerrit. If you spot any issues, please provide details in a direct reply (not "Reply All") to this mail. One of the most user-facing changes in 2.11 is dropping support for "old" change screen UI design. About 20 people of (hundreds) in Linaro used the old design, and they were notified beforehand of the upgrade. You can read about changes and new features in 2.11 at https://gerrit-documentation.storage.googleapis.com/ReleaseNotes/ReleaseNot… As a sneak peek: * Yet in 2.10, there was introduced feature of editing a commit message in the Web UI. That's convenient if you e.g. spotted a typo in colleague's commit message - you don't need describe him/her an issue and make them rebase a change via command line, but can fix it on spot in the browser (subject to ACLs). * 2.11 brings this idea forward and allows to create entire patchsets via web browser, or post follow-up changes changes in the same way. It yet to be seen how useful this functionality is (in github, which has similar functionality, it's actually useful - if you e.g. read a README and spot a typo, you can submit a pull request with the fix on spot). Happy code reviewing from Systems Team! -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

9 years

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android February 2016