Hi, Shuah. Thank you for replying. I tried as non-root, but step_after_suspend_test was skipped. What should I do to pass step after suspend test ? Is it need to resume the kernel from Qemu console after suspending?
thanks.
--------------------- TAP version 13 1..1 # selftests: android: run.sh # ./run.sh: line 3: ./ion_test.sh: not found not ok 1 selftests: android: run.sh # exit=127 TAP version 13 1..2 # selftests: breakpoints: step_after_suspend_test # TAP version 13 # 1..186 # not ok 1 # SKIP Please run the test as root - Exiting. not ok 1 selftests: breakpoints: step_after_suspend_test # SKIP ---------------------
2020年6月11日(木) 21:02 Shuah Khan skhan@linuxfoundation.org:
On 6/11/20 5:21 AM, Akira Shibakawa wrote:
Hi, I tried to run kselftest but it stops with logs below.
# ./run_kselftest.sh [ 126.214906] kselftest: Running tests in android TAP version 13 # selftests: android: run.sh 1..1 # ./run.sh: line 3: ./ion_test.sh: not found not ok 1 selftests: android: run.sh # exit=127 [ 126.351342] kselftest: Running tests in breakpoints TAP version 13 # selftests: breakpoints: step_after_suspend_test 1..2 [ 126.464495] PM: suspend entry (s2idle) [ 126.496441] Filesystems sync: 0.031 seconds [ 126.499299] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 126.501161] OOM killer disabled. [ 126.501293] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 126.503018] printk: Suspending console(s) (use no_console_suspend to debug)
Looks like you are running as root. breakpoints has a suspend test and suspending the system. Try as non-root.
thanks, -- Shuah