Quoting Guru Shetty <[email protected]>:
Thanks for looking into this. I reproduced it a few more times. When the machine boots up and the strongswan daemon is started, it triggers the loading of the following kernel modules. insmod /lib/modules/3.2.14-server-nn19+/kernel/net/ipv4/ah4.ko insmod /lib/modules/3.2.14-server-nn19+/kernel/net/ipv4/esp4.ko insmod /lib/modules/3.2.14-server-nn19+/kernel/net/xfrm/xfrm_ipcomp.ko insmod /lib/modules/3.2.14-server-nn19+/kernel/net/ipv4/ipcomp.ko insmod /lib/modules/3.2.14-server-nn19+/kernel/net/ipv4/tunnel4.ko insmod /lib/modules/3.2.14-server-nn19+/kernel/net/ipv4/xfrm4_tunnel.ko insmod /lib/modules/3.2.14-server-nn19+/kernel/net/xfrm/xfrm_user.ko After the last kernel module is loaded, the backtrace is printed on the screen. It could be that the kernel modules are all loaded fine and it is a system call that triggers this bug as shown in the trace. Does adding any printk messages and doing a few reboots help in providing any more information?
I think modules are loading fine. Problem might be related to nested crypto allocations with aesni-intel. You could try kernel with "CONFIG_DEBUG_LIST=y" config setting, for more output.
-Jussi -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
