I am using a custom initramfs on my ~amd64 fully encrypted system. Everything worked as expected until i did an upgrade to sysvinit-2.88-r7.
The initramfs starts properly and all devices get decrypted. The root filesystem is mounted and accessable.
But when the initramfs tries to call "exec switch_root -c /dev/console /newroot /sbin/init" i get a kernel panic:
"attempted to kill init"

After some debugging i noticed that the system starts normally without an initramfs (copied the encrypted root to another partition).
I already tried rebuilding the initramfs many times. Upgrading to a newer version of busybox and so on.

f_resume_tuxonice() {
local tuxonice_userui_program="/sys/power/tuxonice/user_interface/program"
local tuxonice_do_resume="/sys/power/tuxonice/do_resume"
local tuxonice_resume="/sys/power/tuxonice/resume"

i've tried building a new custom initramfs for a couple of hours now (as a longtime full-crypto user). a common problem seems to be gcc:4.8 (hardened and also non-hardened). using the older gcc:4.7 (hardened) it works just fine.
although my busybox resigned early on with: