Jeremy Fitzhardinge schrieb:
OK, that confirms that its sysret32 that's failing. vdso32=0 on the
kernel command line should be the workaround until we've got a proper
fix.
vdso32=0 works. Thank you for your help!
But i wonder: what's the drawback of this workaround? Performance
loss? Or something more dramatic?