constant Kernel bug at AWS ami-95a845e2

Hi. I have tried to use ami-95a845e2 from amazon's AWS marketplace. After launching and configuring everything, and after everything is working, the instance has a reachability check failed. I have done this process several times. Terminated the old instance, and launched a new one. Same behavior appears I have contacted AWS support, and this is the exact reply :

Hello Roee, The instance right now looks to be responding to icmp and a telnet to port 22 is working. It was showing good checks and responding to telnet 22 and then went to failure, just while I was typing this. I also see the cpu running 100% and this in the console log. "BUG: soft lockup - CPU3 stuck for 67s! [csyncd:6067]" This indicates a kernel bug. As an overall action You'll want to go back to the vendor to let them know about this. To get you working I have two courses of action you can pursue. The first is a stop start action. You may have to do this multiple times. Each start stop will move you to new host hardware. I suspect a change in the underlying host hardware from a previous stop start has triggered the kernel bug. The alternative course of action that may be more effective would be to try an instance size increase or decrease as the underlying host hardware can be different. As a final solution though, you will need to seek vendor input as to the kernel version in use. The root cause is a kernel bug. Hope this helps. Please let me know if you need any further assistance. Best regards, Mike P. Amazon Web Services

After several reboots, I can see this : BIG-IP 11.5.0 Build 0.0.158 Kernel 2.6.32-279.19.1.el6.f5.x86_64 on an x86_64 ip-10-0-0-184.eu-west-1.compute.internal login: BUG: soft lockup - CPU1 stuck for 67s! [chmand:6483] Jan 6 16:47:36 ip-10-0-0-184 emerg kernel: BUG: soft lockup - CPU1 stuck for 67s! [chmand:6483]

Can you please help me solve the problem ?

Thank you,

Roee.