From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: kvm deadlock Date: Wed, 14 Dec 2011 10:25:11 -0200 Message-ID: <20111214122511.GD18317@amt.cnet> References: <54FC5923-2123-4BDD-A506-EA57DCE0C1F6@cpanel.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm@vger.kernel.org To: Nate Custer Return-path: Received: from mx1.redhat.com ([209.132.183.28]:24357 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754894Ab1LNMZo (ORCPT ); Wed, 14 Dec 2011 07:25:44 -0500 Content-Disposition: inline In-Reply-To: <54FC5923-2123-4BDD-A506-EA57DCE0C1F6@cpanel.net> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, Dec 05, 2011 at 04:48:16PM -0600, Nate Custer wrote: > Hello, > > I am struggling with repeatable full hardware locks when running 8-12 KVM vms. At some point before the hard lock I get a inconsistent lock state warning. An example of this can be found here: > > http://pastebin.com/8wKhgE2C > > After that the server continues to run for a while and then starts its death spiral. When it reaches that point it fails to log anything further to the disk, but by attaching a console I have been able to get a stack trace documenting the final implosion: > > http://pastebin.com/PbcN76bd > > All of the cores end up hung and the server stops responding to all input, including SysRq commands. > > I have seen this behavior on two machines (dual E5606 running Fedora 16) both passed cpuburnin testing and memtest86 scans without error. > > I have reproduced the crash and stack traces from a Fedora debugging kernel - 3.1.2-1 and with a vanilla 3.1.4 kernel. Busted hardware, apparently. Can you reproduce these issues with the same workload on different hardware?