* selftests: test stops at step_after_suspend_test
@ 2020-06-11 11:21 Akira Shibakawa
2020-06-11 12:02 ` Shuah Khan
0 siblings, 1 reply; 3+ messages in thread
From: Akira Shibakawa @ 2020-06-11 11:21 UTC (permalink / raw)
To: linux-kselftest
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)
----------------------------
I used kernel 5.6.15 stable on qemu(x86_64) and used kselftest from same source.
I built kernel adding configurations below to be able to mount
kselftest directory on host.
----------------------------
CONFIG_NET_9P=y
CONFIG_BLK_MQ_VIRTIO=y
CONFIG_NET_9P_VIRTIO=y
CONFIG_VIRTIO=y
CONFIG_NET_9P_DEBUG=y
CONFIG_VIRTIO_PCI=y
CONFIG_FUSE_FS=y
CONFIG_VIRTIO_PCI_LEGACY=y
CONFIG_9P_FS=y
CONFIG_VIRTIO_FS=y
CONFIG_9P_FS_POSIX_ACL=y
CONFIG_CRYPTO_ENGINE=m
CONFIG_9P_FS_SECURITY=y
CONFIG_CRYPTO_DEV_VIRTIO=m
CONFIG_GDB_SCRIPTS=y
CONFIG_DEBUG_INFO=y
----------------------------
Then, I boot kernel with rootfs geterated by buildroot like this.
----------------------------
qemu-system-x86_64 -kernel arch/x86/boot/bzImage -boot c -m 2049M -hda
../buildroot/output/images/rootfs.ext4 -append \
"root=/dev/sda rw console=ttyS0,115200 acpi=off nokaslr" -serial
mon:stdio -display none \
-virtfs local,path=/home/arabishi/work/kselftest/kselftest,mount_tag=host0,security_model=passthrough,id=host0
----------------------------
What should I do ?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: selftests: test stops at step_after_suspend_test
2020-06-11 11:21 selftests: test stops at step_after_suspend_test Akira Shibakawa
@ 2020-06-11 12:02 ` Shuah Khan
2020-06-17 7:52 ` Akira Shibakawa
0 siblings, 1 reply; 3+ messages in thread
From: Shuah Khan @ 2020-06-11 12:02 UTC (permalink / raw)
To: Akira Shibakawa, linux-kselftest; +Cc: Shuah Khan
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: selftests: test stops at step_after_suspend_test
2020-06-11 12:02 ` Shuah Khan
@ 2020-06-17 7:52 ` Akira Shibakawa
0 siblings, 0 replies; 3+ messages in thread
From: Akira Shibakawa @ 2020-06-17 7:52 UTC (permalink / raw)
To: Shuah Khan; +Cc: linux-kselftest
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-06-17 7:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-11 11:21 selftests: test stops at step_after_suspend_test Akira Shibakawa
2020-06-11 12:02 ` Shuah Khan
2020-06-17 7:52 ` Akira Shibakawa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).