Segfault on init process?

[stevefan1999-personal]

I saw this on my node, it is causing a boot loop:

 user: warning: [2024-02-10T17:57:37.973433632Z]: [talos] service[etcd](Waiting): Error running Containerd(etcd), going to restart forever: task "etcd" failed: exit code 139
 user: warning: [2024-02-10T17:57:37.988724632Z]: [talos] removed static pod {"component": "controller-runtime", "controller": "k8s.StaticPodServerController", "id": "kube-scheduler"}
 user: warning: [2024-02-10T17:57:37.994857632Z]: [talos] removed static pod {"component": "controller-runtime", "controller": "k8s.StaticPodServerController", "id": "kube-apiserver"}
 user: warning: [2024-02-10T17:57:38.000713632Z]: [talos] removed static pod {"component": "controller-runtime", "controller": "k8s.StaticPodServerController", "id": "kube-controller-manager"}
 user: warning: [2024-02-10T17:57:43.104050632Z]: [talos] service[etcd](Running): Started task etcd (PID 4185) for container etcd
 kern: warning: [2024-02-10T17:57:44.748155632Z]: show_signal_msg: 28 callbacks suppressed
 kern:    info: [2024-02-10T17:57:44.748169632Z]: init[1673]: segfault at 7f510d35f755 ip 0000000000419cc0 sp 000000c0011a7de8 error 6 in init[400000+2245000] likely on CPU 3 (core 3, socket 0)

The whole cluster is basically livelocked on this particular error. Given it is all Golang binaries, and because there is a GC, I'm not sure why are there any segfaults because it is not possible to have UAF or buffer overflow with Golang in the first place right? Or maybe this is going to be a panic, and I don't know how do I get to debug this...

[smira]

Please provide a full console log so that we could look into this better

[stevefan1999-personal]

Well maybe I should close it. I just destroyed the VM on the host provider. Probably just some race condition that checks whether the process is up or not