EDIT: ISSUE SEEMS TO HAVE BEEN POWER-SUPPLY RELATED, SEE MOST RECENT POST.
After some teething problems, I was able to get my new ODROID-XU4 booting fine under ALARM, along with setting up my network shares and other various services I run thereon. So far, so good.
However, I decided to try installing some extra stuff relevant to my mathematical/computational work, specifically the AUR package "openblas-lapack", which is a fairly long build even on desktop hardware.
From a mostly-stock installation of ALARM, the XU4 undergoes an instant reboot about 10-15 seconds into the build process. I spoke with some people on #archlinux-arm on Freenode last night, but nothing useful seemed to be showing up in journalctl or when watching the temps (though I assume there are many sensors I should monitor simultaneously).
I do suspect that it has something to do with load though, since the machine can otherwise idle fine for at least several hours, and other package builds (yet) haven't caused the issue. I think that as part of this package's build process it sets the j makeflag to the number of cores, but I'd have to source that somehow if that's relevant.
I decided to check which CPU governor was set and, to my surprise, it was "performance", which seems a bit overkill for devices like these. I haven't had chance to test "ondemand" or "conservative", but I used cpupower to set "powersave" after which I was able to perform a complete build of this package, albeit not much faster than my should-be-obsolete RPI2.
Short of purchasing the serial debug cable, what can I do to further diagnose this issue, or scrutinise my (various) assumptions?
As an aside, the kernel version I had was:
$this->bbcode_second_pass_code('', '
core/linux-odroid-xu3 4.9.47-2 [installed]
')
but I notice just now that there's an update to 4.9.47-3 so I'll apply that and test again later.