-
Notifications
You must be signed in to change notification settings - Fork 418
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
Test failed on riscv64 #242
Comments
If a simple |
OK, the process indeed hangs in one of write syscalls:
The kernel is expected to perform a short write, e.g. on x86_64 it does the following:
|
Yeah, I got this also. thanks for helps. I will try to catch the bug. |
Here is my some updates. Could you tell me which debug options enabled for kernel are helpful to debug the issue? There are no dmesg messages occurred when hang reproduced. Next I have to git bisect bettween kernel 5.18 and 5.17. BTW, there is one test failed since 5.10 on Qemu: FAIL: filtering_syscall-syntax.test |
I guess I found the commit that introduced the issue. 631f871f071746789e9242e514ab0f49067fa97a fs/iomap: Fix buffered write page prefaulting After I revert the commit, I can pass all test cases that I reported fail tests here expect ============================================================================
Testsuite summary for strace 6.2
============================================================================
# TOTAL: 1256
# PASS: 1065
# SKIP: 190
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See tests/test-suite.log
Please report to strace-devel@lists.strace.io
... I am not sure this commit how to effect behavior on riscv and have to cost more time to debug here. |
I have forwarded this to riscv kernel mail list: I need more time to fix it. |
The kernel issue has been fixed: |
Hi,
Strace was built ok on Debian riscv64 but since 6.1 it has ftbfs issue due to test failed:
https://buildd.debian.org/status/logs.php?pkg=strace&arch=riscv64
I grep it on 6.2 also like:
The trouble is that I can not reproduce the test step by step. For example, clock.gen.test, I got almost 10K log like:
Could you tell me how to debug this or which directory to look at? TIA.
yeah, I have a real riscv64 hardware, Unmatched boards by hand.
The text was updated successfully, but these errors were encountered: