Skip to content

x/build: bot linux-riscv64-mengzhuo--megrez-1 reported as broken #73745

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

Closed
gopherbot opened this issue May 16, 2025 · 2 comments
Closed

x/build: bot linux-riscv64-mengzhuo--megrez-1 reported as broken #73745

gopherbot opened this issue May 16, 2025 · 2 comments
Assignees
Labels
Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done. Unfortunate
Milestone

Comments

@gopherbot
Copy link
Contributor

The bot linux-riscv64-mengzhuo--megrez-1 has been reported as broken. It is currently in "dead" state. Please work to resolve the issue.

@golang/riscv64

watchflakes

@gopherbot gopherbot added Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels May 16, 2025
@gopherbot gopherbot added this to the Unreleased milestone May 16, 2025
@mengzhuo
Copy link
Contributor

It might be the kernel panic? Anyway I've start the service.
Here is the journalctl -b -1 -e

kernel: testp[2384600]: unhandled signal 11 code 0x1 at 0x0000000000000000
kernel: CPU: 0 PID: 2384600 Comm: testp Not tainted 6.6.73-win2030 #2025.01.23.02.46+aeb0f375c
kernel: Hardware name: Milk-V Megrez (DT)
kernel: epc : 0000555572157a14 ra : 00005555721579a0 sp : 00007fffff3e2ba0
kernel:  gp : 00005555722b3bc2 tp : 00007fffa771a420 t0 : 0000000000000001
kernel:  t1 : 00007fffff3e2a78 t2 : 00005555721c3b9c s0 : 00007fffff3e2be0
kernel:  s1 : 0000000000000002 a0 : 0000000000000000 a1 : 0000000000000002
kernel:  a2 : 0000000000000003 a3 : 0000000000000000 a4 : 0000000000000001
kernel:  a5 : 0000000000000000 a6 : 0000000000000000 a7 : 00000000195fe2ad
kernel:  s2 : 0000000000000000 s3 : 000055557220fc18 s4 : 0000555572157942
kernel:  s5 : 00007fffff3e2d80 s6 : 000055557220fc18 s7 : 00007fffa7759cc0
kernel:  s8 : 00007fffa775a008 s9 : 0000000000000000 s10: 0000000000000000
kernel:  s11: 00007fff5412c1c0 t3 : 0000000040d43c84 t4 : fffffffffa4ce809
kernel:  t5 : ffffffffb85fd417 t6 : 00007fffa771a420
kernel: status: 0000000200004020 badaddr: 0000000000000000 cause: 000000000000000f
kernel: testnoshared[2388792]: unhandled signal 11 code 0x1 at 0x0000000000000000 in testnoshared[10000+b9000]
kernel: CPU: 2 PID: 2388792 Comm: testnoshared Not tainted 6.6.73-win2030 #2025.01.23.02.46+aeb0f375c
kernel: Hardware name: Milk-V Megrez (DT)
kernel: epc : 00000000000116d2 ra : 000000000001165e sp : 00007fffdd0fbb90
kernel:  gp : 000000000016dbc8 tp : 00007fff82047420 t0 : 0000000000000001
kernel:  t1 : 00007fffdd0fba68 t2 : 000000000007d82c s0 : 00007fffdd0fbbd0
kernel:  s1 : 0000000000000002 a0 : 0000000000000000 a1 : 0000000000000002
kernel:  a2 : 0000000000000003 a3 : 0000000000000000 a4 : 0000000000000001
kernel:  a5 : 0000000000000000 a6 : 0000000000000000 a7 : ffffffff702a95a1
kernel:  s2 : 0000000000000000 s3 : 00000000000c9c38 s4 : 00000000000114f2
kernel:  s5 : 00007fffdd0fbd70 s6 : 00000000000c9c38 s7 : 00007fff82086cc0

@mengzhuo mengzhuo self-assigned this May 16, 2025
@mengzhuo mengzhuo added Unfortunate and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels May 16, 2025
@dmitshur
Copy link
Member

Thanks for addressing this so quickly. I've closed this since the builder is back online and working. If it's useful to have an open issue, we can make a new one.

@dmitshur dmitshur added the NeedsFix The path to resolution is known, but the work has not been done. label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Builders x/build issues (builders, bots, dashboards) NeedsFix The path to resolution is known, but the work has not been done. Unfortunate
Projects
None yet
Development

No branches or pull requests

3 participants