Closed n2vi closed 3 months ago
I've been able to reproduce a kernel panic without anything involving Go, so will be pursuing that and temporarily not running swarm. I'll update here when we've made progress with the kernel.
Change https://go.dev/cl/593736 mentions this issue: main.star: set openbsd-ppc64 timeout scale to 3
Although the kernel issue is not fully solved, I'm satisfied that it is sufficiently understood and being worked on in Mac Studio locking bug. I now regard the LUCI migration as complete for openbsd-ppc64 builder and am no longer running the buildlet there. As long as we keep the machine load at a reasonable level, we're rarely triggering the kernel lock issue.
@dmitshur Thanks again for all your help with this. You may remove knownissue for me if you like. I would submit a CL myself except that the machine with my GitHub login is too locked down to import all the luciconfig toolchain. I'll think about how to get around that eventually.
Change https://go.dev/cl/596817 mentions this issue: main.star: unset known issue for openbsd/ppc64 builder type
I regret to say that my comment seems to have jinxed things. After the change, openbsd-ppc64 builder is crashing more frequently again.
Anyway, let's leave things be for a couple weeks while y'all are at GopherCon and OpenBSD works on locks.
Sure.
As my system kernel friends say, multicore MMU is an art. I believe there are remaining bugs encountered when under high load, but I reboot the server when needed.
Following the instructions at Dashboard builders:
hostname openbsd-ppc64-n2vi
CSR is attached after renaming since Github doesn't seem to allow attaching with the name openbsd-ppc64-n2vi.csr you asked for.