Re: How assign some logic to handle system-gone-totally-unresponsive events (if not else then to enable admin with differentiated failure tracking between userland and hardware failures)

[Karel Gardas]

1) use machine with proper ECC support
2) man sendbug -- and following it report your OpenBSD kernel misbehavior

On Mon, Oct 17, 2016 at 3:48 PM, Tinker <ti...@openmailbox.org> wrote:
> Sometimes a machine goes unresponsive. In this case, a non-ECC RAM machine.
>
> The reason could be that something in the hardware or kernel failed, e.g. a
> bit flip error [1].
>
> In this case (for a non-kernel developer), tough luck, and the proper thing
> would be to reboot, and keep statistics over failures on that machine and
> replace the hardware should the crashes go above some frequency threshold.