From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christopher S. Aker" Subject: Re: netback Oops then xenwatch stuck in D state Date: Mon, 11 Feb 2013 11:17:47 -0500 Message-ID: <511919AB.3070001@theshore.net> References: <510C3AA3.2090508@theshore.net> <50E3A390-C52B-476A-8B20-BADBA42F3775@theshore.net> <51181924.4050500@theshore.net> <1360583103.16636.29.camel@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1360583103.16636.29.camel@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 2/11/13 6:45 AM, Wei Liu wrote: > OK, so the guest is faulting at different offset now. It is very likely > that there is OOM / race condition in other places. And judging from > your two emails, I presume this bug can be reproduce steadily. It is frequent enough to be a problem, yes. We're constantly deploying new servers and upgrading the stack on existing ones, so testing changes won't be a problem. > A quick check on the xen_spinlock struct, its offset should not be > 0x8b8. Reading the backtrace suggests that it is the netbk struct is > gone. Great, we've narrowed it down some. > Do you manipulate the number of vcpus Dom0 has after it's up? No, we do not. Thanks, -Chris