<div dir="ltr">Unfortunately there's nothing relevant in dmesg. It could just be that I waited too long and it got overwritten, or it could be that it was never there. I grabbed this out of the ec2 instance log, which doesn't contain anything else that looks relevant.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 19, 2015 at 2:37 PM, Cyrill Gorcunov <span dir="ltr"><<a href="mailto:gorcunov@gmail.com" target="_blank">gorcunov@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Aug 19, 2015 at 02:21:56PM -0700, Ross Boucher wrote:<br>
> This may or may not be related to CRIU, I'm not yet sure. I've experienced<br>
> a complete machine lockup a couple of times now, and one of the things I'm<br>
> seeing in logs is repeats of this:<br>
> [129476.256052] BUG: soft lockup - CPU#1 stuck for 23s! [criu:15631]<br>
> [129504.256052] BUG: soft lockup - CPU#1 stuck for 23s! [criu:15631]<br>
> [129532.256018] BUG: soft lockup - CPU#1 stuck for 23s! [criu:15631]<br>
> [129560.256053] BUG: soft lockup - CPU#1 stuck for 22s! [criu:15631]<br>
> [129588.256052] BUG: soft lockup - CPU#1 stuck for 22s! [criu:15631]<br>
> [129616.256052] BUG: soft lockup - CPU#1 stuck for 22s! [criu:15631]<br>
> Does anyone have any idea what this might be about?<br>
<br>
</span>dmesg should show you some longer backtrace, post it please<br>
</blockquote></div><br></div>