From owner-freebsd-current@FreeBSD.ORG Fri Oct 25 07:34:11 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DE2EF47F; Fri, 25 Oct 2013 07:34:11 +0000 (UTC) (envelope-from SNasonov@BCC.RU) Received: from extmx.bcc.ru (extmx.bcc.ru [217.170.85.214]) by mx1.freebsd.org (Postfix) with ESMTP id BB27B23A0; Fri, 25 Oct 2013 07:34:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by extmx.bcc.ru (Postfix) with ESMTP id C73F416EE6; Fri, 25 Oct 2013 11:09:29 +0400 (GMT-4) Received: from extmx.bcc.ru ([127.0.0.1]) by localhost (extmx.bcc.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29463-06; Fri, 25 Oct 2013 11:09:27 +0400 (GMT-4) Received: from mail.bcc (unknown [172.16.250.23]) by extmx.bcc.ru (Postfix) with ESMTP id 6554D16105; Fri, 25 Oct 2013 11:09:25 +0400 (GMT-4) Received: from snasonovnbwxp.bcc ([192.168.201.205]) by mail.bcc over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 25 Oct 2013 11:15:18 +0400 From: Sergey Nasonov To: freebsd-current@freebsd.org Subject: Re: CUREENT issue with ballon.c Date: Fri, 25 Oct 2013 11:15:16 +0400 Message-ID: <2353358.uiOMYug52O@snasonovnbwxp.bcc> Organization: BCC User-Agent: KMail/4.10.5 (FreeBSD/9.2-PRERELEASE; KDE/4.10.5; amd64; ; ) In-Reply-To: <52699C97.7070105@citrix.com> References: <20131024211507.GD10625@kib.kiev.ua> <52699C97.7070105@citrix.com> MIME-Version: 1.0 X-OriginalArrivalTime: 25 Oct 2013 07:15:19.0045 (UTC) FILETIME=[F605BB50:01CED151] X-Virus-Scanned: amavisd-new at bcc.ru Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Konstantin Belousov , Outback Dingo , current@freebsd.org, Roger Pau =?ISO-8859-1?Q?Monn=E9?= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Oct 2013 07:34:11 -0000 On Thursday 24 October 2013 23:17:59 Roger Pau Monn=E9 wrote: > On 24/10/13 22:15, Konstantin Belousov wrote: > > On Thu, Oct 24, 2013 at 09:45:20PM +0100, Roger Pau Monn? wrote: > >> On 24/10/13 13:01, Outback Dingo wrote: > >>> On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monn?=20 >>>=20 > >>> > wrote: > >>> On 24/10/13 03:02, Outback Dingo wrote: > >>> > --- trap 0, rip =3D 0, rsp =3D 0xfffffe00002c6b70, rbp =3D = 0 --- > >>> > uma_zalloc_arg: zone "16" with the following non-sleepable = locks > >>> > held: > >>> > exclusive sleep mutex balloon_lock (balloon_lock) r =3D 0 > >>> > (0xffffffff816e9c58) locked @ > >>> =20 > >>> /usr/src/sys/dev/xen/balloon/balloon.c:339 > >>> =20 > >>> > exclusive sleep mutex balloon_mutex (balloon_mutex) r =3D 0= > >>> > (0xffffffff816e9c38) locked @ > >>> =20 > >>> /usr/src/sys/dev/xen/balloon/balloon.c:373 > >>> =20 > >>> > KDB: stack backtrace: > >>> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame= > >>> > 0xfffffe00002c67c0 > >>> > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00002c6= 870 > >>> > witness_warn() at witness_warn+0x4a8/frame 0xfffffe00002c69= 30 > >>> > uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfffffe00002= c69a0 > >>> > malloc() at malloc+0x101/frame 0xfffffe00002c69f0 > >>> > balloon_process() at balloon_process+0x44a/frame > >>> > 0xfffffe00002c6a70 > >>> > fork_exit() at fork_exit+0x84/frame 0xfffffe00002c6ab0 > >>> > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000= 2c6ab0 > >>> > --- trap 0, rip =3D 0, rsp =3D 0xfffffe00002c6b70, rbp =3D = 0 --- > >>> > uma_zalloc_arg: zone "16" with the following non-sleepable = locks > >>> > held: > >>> > exclusive sleep mutex balloon_lock (balloon_lock) r =3D 0 > >>> > (0xffffffff816e9c58) locked @ > >>> =20 > >>> /usr/src/sys/dev/xen/balloon/balloon.c:339 > >>> =20 > >>> > exclusive sleep mutex balloon_mutex (balloon_mutex) r =3D 0= > >>> > (0xffffffff816e9c38) locked @ > >>> =20 > >>> /usr/src/sys/dev/xen/balloon/balloon.c:373 > >>> =20 > >>> > KDB: stack backtrace: > >>> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame= > >>> > 0xfffffe00002c67c0 > >>> > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00002c6= 870 > >>> > witness_warn() at witness_warn+0x4a8/frame 0xfffffe00002c69= 30 > >>> > uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfffffe00002= c69a0 > >>> > malloc() at malloc+0x101/frame 0xfffffe00002c69f0 > >>> > balloon_process() at balloon_process+0x44a/frame > >>> > 0xfffffe00002c6a70 > >>> > fork_exit() at fork_exit+0x84/frame 0xfffffe00002c6ab0 > >>> > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000= 2c6ab0 > >>> > --- trap 0, rip =3D 0, rsp =3D 0xfffffe00002c6b70, rbp =3D = 0 --- > >>> =20 > >>> > uma_zalloc_arg: zone "16" with the following non-sleepable = locks=20 held: > >>> Did you do anything specific to trigger the crash? Can you ex= plain > >>> the > >>> steps needed to reproduce it? > >>>=20 > >>> just recompiled a kernel, and booted it scrolls continuously acro= ss the > >>> screen > >>> doesnt seem to ever stop. > >>=20 > >> I've tried r257051 and it seems to work fine, could you please pos= t your > >> Xen version, the config file used to launch the VM and the toolsta= ck > >> used? > >=20 > > Do you have witness enabled in your kernel config ? >=20 > Yes, but I'm not touching balloon memory target. >=20 > > There is an obvious case of calling malloc(M_WAITOK) while holding = both > > balloon_lock and balloon_mutex: > > ballon_process->decrease_reservation->balloon_append. >=20 > Yes, I'm aware of that, it's just that it shouldn't happen unless you= > actually trigger a balloon memory decrease, which should not happen > automatically AFAIK, that's why I was asking if this was happening > without the user specifically requesting it. For me this problem appears when I try to migrate VM to another physica= l=20 XenServer 6.2. And only when this VM configured with dynamical memory.= Have=20 no problem with static memory configuration. You can find details here http://support.citrix.com/proddocs/topic/xencenter-61/xs-xc-dmc-about.h= tml >=20 > Anyway, this should be clearly fixed and pulled into 10 no matter wha= t > triggered it. I will send a patch as soon as possible. Thanks for that. >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd= .org" --=20 Best Regards, Nasonov Sergey