Disabling vsyscall emulation in the kernel causes all rosetta apps to crash immediately when started. The most likely cause of this is a static linkage against a glibc version prior to 2.14 (2011).

syscall emulation has a small impact on security. I decided to keep it disabled and suspend rosetta number crunching for now. I'll check back in ocassionally, to see if newer versions run successfully.

I'm mentioning this for other users that have the same problem.

Update: Still crashing.

As the tasks your machine fails on are sent to other systems, they seem to run normally. What are you seeing for messages in the message log as tasks fail?

Here is a similar report from years past.

---

Rosetta Moderator: Mod.Sense

Same problem here.
running Debian Testing 64-bit.
After update to Kernel 4.8 all workunits fail immediately.
Starting PC with Kernel boot parameter vsyscall=emulate everything is running fine.

This is from Debian changelog:
[amd64] Enable LEGACY_VSYSCALL_NONE instead of LEGACY_VSYSCALL_EMULATE. This breaks (e)glibc 2.13 and earlier, and can be reverted using the kernel parameter: vsyscall=emulate