[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH 00/17] xenpaging changes for xen-unstable
- To: xen-devel@xxxxxxxxxxxxxxxxxxx
- From: Olaf Hering <olaf@xxxxxxxxx>
- Date: Mon, 6 Dec 2010 22:16:48 +0100
- Delivery-date: Mon, 06 Dec 2010 13:41:32 -0800
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1291670209; l=576; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=uOAD1oURz2vlZjy1T3Mf/DYG5+g=; b=pAQc9dAZZQg2PbCGiPOyQo78P1oTCNv6NZLVRc2pBFAjDsDcSxgPu8qSW3MOI4TYVOC TfR+OyKcthZf1Qv0urAvICWBnY6Fs7ty02nQz+WDQ/IBKfwTX31dQ5l2PgI00vSyX33ud f9IGC7DqImv1t4MLm3BBk54Agc3zvTxiT+Q=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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.
Xen-devel mailing list