On 3 January 2018 at 16:55, Greg KH gregkh@google.com wrote:
On Tue, Jan 02, 2018 at 10:47:01PM +0000, Linaro QA wrote:
Summary
git repo: https://android.googlesource.com/kernel/hikey-linaro git branch: android-hikey-linaro-4.9 git commit: 96ae075d5bd1c0003edf9ec385dd8ba6dfb6fc6b git describe: v4.9.73-638772-g96ae075d5bd1 Test details: https://qa-reports.linaro.org/lkft/android-hikey-linaro-4.9-aosp/build/v4.9....
Regressions (compared to build v4.9.71-638768-g19675ab872e1)
hi6220-hikey - arm64: vts-test/arm64-v8a.VtsKernelBinderTest: * VtsKernelBinderTest.BinderDriverInterfaceTest.Transaction_IPC64_64bit
* test src: not informedvts-test/arm64-v8a.VtsKernelLtp: * KernelLtpTest.syscalls.nanosleep01_64bit
LTP test case nanosleep01 and poll02 failed on OE userspace also.
We have an open bug and the investigation is in progress. LKFT: 4.4, 4.9: Hikey: LTP: clock_nanosleep02 epoll_wait02 futex_wait05 nanosleep01 poll02 failed https://bugs.linaro.org/show_bug.cgi?id=3388#c21
Summery: The erroneous RCU_LOCKDEP_WARN() and the CONFIG_PROVE_RCU=y hided the fact that with the schedutil cpufreq governor, some of the timer related LTP fail on hikey620 with OPP_208MHz enabled. This issue can't be seen on juno r0.
Why this happens on hikey620 has still to be figured out ... Maybe the OPP_208Mhz delivers to little capacity for these testcases and the RCU_LOCKDEP_WARN() with CONFIG_PROVE_RCU=y in the wakeup path lets the system use this OPP_208Mhz less often.
- Naresh
* test src: not informedSame question here. _______________________________________________ Lts-dev mailing list Lts-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lts-dev