From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Xen pv_ops dom0 2.6.32.13 issues
Date: Wed, 09 Jun 2010 15:37:38 -0700
Message-ID: <4C1017B2.90800@goop.org>
References: <1382341628.4833695.1276117331660.JavaMail.root@vms170009.mailsrvcs.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1382341628.4833695.1276117331660.JavaMail.root@vms170009.mailsrvcs.net>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: greno@verizon.net
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 06/09/2010 02:02 PM, greno@verizon.net wrote:
>
> Ok, I've been running this 2.6.32.13 pv_ops dom0 kernel for several
> weeks and it has twice killed my domU's.  I get numerous CPU soft
> lockup bug errors and at times it will freeze which means a power
> cycle boot.

The lockups are in dom0 or domU?  Do the backtraces indicate a common
subsystem, or are they all over the place?

> This has resulted in things like:
> EXT-fs error (device dm-0): ext4_lookup: deleted inode reference
> EXT-fs error (device dm-0): ext4_lookup: deleted inode reference
> in the domU boots which has killed two of them.

What's your storage path from guest device to media?  Are they using
barriers?

    J