From owner-freebsd-current@FreeBSD.ORG  Sat Nov 23 10:25:01 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-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 ESMTPS id 19768FA9;
 Sat, 23 Nov 2013 10:25:01 +0000 (UTC)
Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id F1E7E20C6;
 Sat, 23 Nov 2013 10:25:00 +0000 (UTC)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id rANAOiVS023613;
 Sat, 23 Nov 2013 02:24:48 -0800 (PST)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201311231024.rANAOiVS023613@gw.catspoiler.org>
Date: Sat, 23 Nov 2013 02:24:44 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: Anyone else seeing uma_zalloc_arg panics?
To: markm@FreeBSD.org
In-Reply-To: <6527E3D8-55D8-45B9-80F1-3AC83250F02A@FreeBSD.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: freebsd-current@FreeBSD.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Nov 2013 10:25:01 -0000

On 23 Nov, Mark Robert Vaughan Murray wrote:
> Hi *
> 
> Anyone else seeing panics like this?
> 
> This is CURRENT, amd64, 2 CPUs, source synced on Thursday 21st Nov evening GMT sometime.
> 
> +panic: uma_zalloc_arg: Returning an empty bucket.
> +cpuid = 1
> +KDB: stack backtrace:
> +db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe003c7dd820
> +kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe003c7dd8d0
> +vpanic() at vpanic+0x126/frame 0xfffffe003c7dd910
> +kassert_panic() at kassert_panic+0x136/frame 0xfffffe003c7dd980
> +uma_zalloc_arg() at uma_zalloc_arg+0x49a/frame 0xfffffe003c7dd9f0
> +bucket_alloc() at bucket_alloc+0x8b/frame 0xfffffe003c7dda10
> +uma_zfree_arg() at uma_zfree_arg+0x2a1/frame 0xfffffe003c7dda70
> +bucket_cache_drain() at bucket_cache_drain+0x1b/frame 0xfffffe003c7ddaa0
> +zone_drain_wait() at zone_drain_wait+0xd1/frame 0xfffffe003c7ddb00
> +uma_reclaim() at uma_reclaim+0x42d/frame 0xfffffe003c7ddb30
> +vm_pageout() at vm_pageout+0x3bc/frame 0xfffffe003c7ddbb0
> +fork_exit() at fork_exit+0x84/frame 0xfffffe003c7ddbf0
> +fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe003c7ddbf0
> +--- trap 0, rip = 0, rsp = 0xfffffe003c7ddcb0, rbp = 0 ---
> +KDB: enter: panic
> 
> M

Yes, I got one of these a couple days ago:
<http://docs.freebsd.org/cgi/mid.cgi?201311212234.rALMY0bN009437>

Just curious ... are you running i386 or amd64?  My test machine is
i386, but I suspect that most people running head are running amd64.