Closed
Description
2021-01-19T12:49:13-d047c91/linux-arm64-packet
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x2e430]
runtime stack:
runtime.throw(0x59c4d8, 0x2a)
/workdir/go/src/runtime/panic.go:1112 +0x54
runtime.sigpanic()
/workdir/go/src/runtime/signal_unix.go:714 +0x29c
runtime.readgstatus(...)
/workdir/go/src/runtime/proc.go:830
runtime.markroot(0x4000038e98, 0x4a)
/workdir/go/src/runtime/mgcmark.go:199 +0x2b0
runtime.gcDrain(0x4000038e98, 0x3)
/workdir/go/src/runtime/mgcmark.go:1014 +0x100
runtime.gcBgMarkWorker.func2()
/workdir/go/src/runtime/mgc.go:1980 +0x74
runtime.systemstack(0xffff47ffe930)
/workdir/go/src/runtime/asm_arm64.s:248 +0xa0
runtime.mstart()
/workdir/go/src/runtime/proc.go:1244
2019-08-27T16:04:01-ba9fcec/linux-ppc64le-power9osu
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x2d220]
runtime stack:
runtime.throw(0x93df99, 0x2a)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/panic.go:774 +0x5c
runtime.sigpanic()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/signal_unix.go:378 +0x474
runtime.readgstatus(...)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/proc.go:707
runtime.markroot(0xc000025770, 0xc)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgcmark.go:195 +0x300
runtime.gcDrain(0xc000025770, 0x7)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgcmark.go:915 +0x118
runtime.gcBgMarkWorker.func2()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/mgc.go:1936 +0x178
runtime.systemstack(0x42150)
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/asm_ppc64x.s:269 +0x94
runtime.mstart()
/tmp/workdir-host-linux-ppc64le-power9-osu/go/src/runtime/proc.go:1182
Given the gap in time and the difference in architecture I'm not sure whether these are due to the same root cause, but they sure seem to have the same stack trace.