Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

systemtest unstable because of rcu issue #119

Open
enkerewpo opened this issue Mar 4, 2025 · 3 comments
Open

systemtest unstable because of rcu issue #119

enkerewpo opened this issue Mar 4, 2025 · 3 comments
Assignees
Labels
aarch64 bug Something isn't working ci Github CI

Comments

@enkerewpo
Copy link
Member

enkerewpo commented Mar 4, 2025

The PR that added system tests for hvisor passed all CI checks, including the system tests themselves. However, after merging into the dev branch, the CI failed. The report indicates that the system test is unstable and may pass on a retry. This instability could be related to a previous RCU issue (noted by Honghao Cheng).

@enkerewpo enkerewpo added bug Something isn't working aarch64 ci Github CI labels Mar 4, 2025
@enkerewpo enkerewpo added this to the hvisor-v0.1.1 milestone Mar 4, 2025
@enkerewpo
Copy link
Member Author

...
[INFO  0] (hvisor::memory::mm:97) region.start: 0x8000004000
[INFO  0] (hvisor::zone:210) zone cpu_set: 0b1100
[INFO  2] (hvisor::event:100) cpu 2 wakeup
[INFO  2] (hvisor::arch::aarch64::cpu:155) cpu 2 started
00:00:02 WARN  virtio_console.c:107: char device redirected to /dev/pts/0
Script started, file is /dev/null
# bash
root@(none):/home/arm64# dmesg | tail -n 3 | awk -F ']' '{print $2}' > ./test/tes
stresult/test_zone1_start.txt
root@(none):/home/arm64# [    5.515636] random: fast init done
./test/textract_dmesg.sh ./test/testresult/test_zone1_st
tart.txt
root@(none):/home/arm64# ./screen_linux2.sh
00:00:02 WARN  virtio_console.c:107: char device redirected to /dev/pts/0
/dev/pts/0
�
bash
# bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
root@(none):/# cd /home/arm64
root@(none):/home/arm64# ls | grep zone1.txt
zone1.txt
root@(none):/home/arm64# 
[detached from 196.screen_linux2]
root@(none):/home/arm64# echo "zone1.txt" > ./test/testresult/test_zone1_ls.txt
root@(none):/home/arm64# ./hvisor zone list > ./test/testresult/test_zone_list2.t
txt
root@(none):/home/arm64# ./hvisor zone shutdown -id 1
[INFO  0] (hvisor::hypercall:240) handle hvc zone shutdown, id=1
[INFO  3] (hvisor::arch::aarch64::cpu:168) cpu 3 idle
[INFO  3] (hvisor::arch::aarch64::cpu:189) cpu 3 started from parking

(stuck forever)

@CHonghaohao
Copy link
Contributor

CHonghaohao commented Mar 4, 2025

Stuck Log Information:
Image

Normal Log Information:

Image

@enkerewpo enkerewpo changed the title ci failed on systemtest systemtest unstable because of rcu issue Mar 4, 2025
@enkerewpo
Copy link
Member Author

enkerewpo commented Mar 4, 2025

I suggest we temporarily disable the problematic subtests and keep this issue open until we fixed related problem in hvisor.

@enkerewpo enkerewpo removed this from the hvisor-v0.1.1 milestone Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aarch64 bug Something isn't working ci Github CI
Projects
None yet
Development

No branches or pull requests

5 participants