From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: Re: [PATCH 00/17] xenpaging changes for xen-unstable
Date: Mon, 6 Dec 2010 22:16:48 +0100
Message-ID: <20101206211648.GA15153@aepfle.de>
References: <20101206205907.848643876@aepfle.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <20101206205907.848643876@aepfle.de>
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: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On Mon, Dec 06, Olaf Hering wrote:

> This series uses the recently added wait_event feature. The __hvm_copy
> patch crashes Xen with what looks like stack corruption. After a few
> populate/resume iterations. I have added some printk to the
> populate/resume functions and also wait.c. This leads to crashes.  It
> rarely prints a clean backtrace like the one shown below (most of the
> time a few cpus crash at once).

I have to add, sometimes the ASSERT in do_softirq() triggers.
But I havent had a chances to see what of the 3 checks actually trigger.


Olaf