From owner-freebsd-current@FreeBSD.ORG Thu Oct 24 22:26:47 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BE159313 for ; Thu, 24 Oct 2013 22:26:47 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7D93A2FA0 for ; Thu, 24 Oct 2013 22:26:47 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id h1so177096oag.38 for ; Thu, 24 Oct 2013 15:26:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TeZ8LHRBwPwqH2sK7nwz6SxUt6ivF7XHFfpQcn+ZGn4=; b=ybYdKzLbstDbNvkhf8JJKpXIZUM8gskcYOE/84I+MBvyc/J8QqP6tc1oHrJXiINjum 8pa3p6/yr8BWGpMrJHEiunpAjRomzqGiHJjSk0Kny1/VVFZkNW/A6pHIb0FC/ncVg0BE Mt1KmWiQlzHe0hHgONvZUthVmkOdXdAkukiRSN+BSb9hlInW6asXDAXh7yIQaz8ihZZX o95NHsm03QRQhWkosQbP5Cjdw2WvZtNS9lOm+U330IXJ1wCHwCdU64zZy6KIfRTSK6Pj J/BTRkxtiNDmTS4Wm88N9E7PiBvBCWR1obrL0nYeHLYsd1OwYFfvdW1ypv5/gCZ7DPfW 7ULw== MIME-Version: 1.0 X-Received: by 10.182.129.201 with SMTP id ny9mr509030obb.0.1382653606472; Thu, 24 Oct 2013 15:26:46 -0700 (PDT) Received: by 10.76.19.115 with HTTP; Thu, 24 Oct 2013 15:26:46 -0700 (PDT) In-Reply-To: References: <5268F37E.9050004@citrix.com> <526986E0.2050807@citrix.com> <20131024211507.GD10625@kib.kiev.ua> <52699C97.7070105@citrix.com> Date: Thu, 24 Oct 2013 18:26:46 -0400 Message-ID: Subject: Re: CUREENT issue with ballon.c From: Outback Dingo To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= 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 , current@freebsd.org 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: Thu, 24 Oct 2013 22:26:47 -0000 On Thu, Oct 24, 2013 at 6:24 PM, Outback Dingo wrot= e: > > > > On Thu, Oct 24, 2013 at 6:17 PM, 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? < >> roger.pau@citrix.com >> >>> > 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 @ >> >>> /usr/src/sys/dev/xen/balloon/balloon.c:339 >> >>> > exclusive sleep mutex balloon_mutex (balloon_mutex) r =3D 0 >> >>> > (0xffffffff816e9c38) locked @ >> >>> /usr/src/sys/dev/xen/balloon/balloon.c:373 >> >>> > KDB: stack backtrace: >> >>> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >> >>> > 0xfffffe00002c67c0 >> >>> > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00002c6870 >> >>> > witness_warn() at witness_warn+0x4a8/frame 0xfffffe00002c6930 >> >>> > uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfffffe00002c69= a0 >> >>> > 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 >> 0xfffffe00002c6ab0 >> >>> > --- 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 @ >> >>> /usr/src/sys/dev/xen/balloon/balloon.c:339 >> >>> > exclusive sleep mutex balloon_mutex (balloon_mutex) r =3D 0 >> >>> > (0xffffffff816e9c38) locked @ >> >>> /usr/src/sys/dev/xen/balloon/balloon.c:373 >> >>> > KDB: stack backtrace: >> >>> > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >> >>> > 0xfffffe00002c67c0 >> >>> > kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe00002c6870 >> >>> > witness_warn() at witness_warn+0x4a8/frame 0xfffffe00002c6930 >> >>> > uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfffffe00002c69= a0 >> >>> > 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 >> 0xfffffe00002c6ab0 >> >>> > --- trap 0, rip =3D 0, rsp =3D 0xfffffe00002c6b70, rbp =3D 0 -= -- >> >>> > uma_zalloc_arg: zone "16" with the following non-sleepable >> locks held: >> >>> >> >>> Did you do anything specific to trigger the crash? Can you >> explain the >> >>> steps needed to reproduce it? >> >>> >> >>> >> >>> just recompiled a kernel, and booted it scrolls continuously across >> the >> >>> screen >> >>> doesnt seem to ever stop. >> >> >> >> I've tried r257051 and it seems to work fine, could you please post >> your >> >> Xen version, the config file used to launch the VM and the toolstack >> used? >> > >> > Do you have witness enabled in your kernel config ? >> >> Yes, but I'm not touching balloon memory target. >> >> > There is an obvious case of calling malloc(M_WAITOK) while holding bot= h >> > balloon_lock and balloon_mutex: >> > ballon_process->decrease_reservation->balloon_append. >> >> 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. >> >> Anyway, this should be clearly fixed and pulled into 10 no matter what >> triggered it. I will send a patch as soon as possible. >> >> > Yes, WITNESS was enabled, im using Kubuntu / XEN kernel / and > virt-manager.... it was fine running Current, until i ran updates this we= ek > then encountered this. Ive since disabled WITNESS with a recompile, but t= he > VM still apears more sluggish then before. > > root@M14xR2:/home/dingo# xm info > host : M14xR2 > release : 3.11.0-12-generic > version : #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 2 > cpu_mhz : 2494 > xen:/// capabilities: > > > > > x86_64 > > > > > > > > > > > > > xenmigr > > > > > > xen > > 64 > qemu-dm > xenpv > > > > > > > xen > > 32 > qemu-dm > xenpv > > > > > > > > > > hvm > > 32 > qemu-dm > hvmloader > xenfv > > > > > > > > > > > > > > > hvm > > 64 > qemu-dm > hvmloader > xenfv > > > > > > > > > > > > > > > > hw_caps : > bfebfbff:28100800:00000000:00007f00:77bae3bf:00000000:00000001:00000281 > virt_caps : hvm > total_memory : 8074 > free_memory : 12 > free_cpus : 0 > xen_major : 4 > xen_minor : 3 > xen_extra : .0 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xffff800000000000 > xen_changeset : > xen_commandline : placeholder > cc_compiler : gcc (Ubuntu/Linaro 4.8.1-10ubuntu5) 4.8.1 > cc_compile_by : stefan.bader > cc_compile_domain : canonical.com > cc_compile_date : Wed Oct 2 11:17:12 UTC 2013 > xend_config_format : 4 > root@M14xR2:/home/dingo# uname -a > Linux M14xR2 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 > x86_64 x86_64 x86_64 GNU/Linux > and it appears to be XEN 4.3 kernel from installed via Kubuntu apt-get