From owner-freebsd-current@FreeBSD.ORG  Tue Jun 18 22:08:31 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 704FF39E
 for <freebsd-current@FreeBSD.org>; Tue, 18 Jun 2013 22:08:31 +0000 (UTC)
 (envelope-from jlh@FreeBSD.org)
Received: from caravan.chchile.org (caravan.chchile.org [178.32.125.136])
 by mx1.freebsd.org (Postfix) with ESMTP id 3FE5D179B
 for <freebsd-current@FreeBSD.org>; Tue, 18 Jun 2013 22:08:30 +0000 (UTC)
Received: by caravan.chchile.org (Postfix, from userid 1000)
 id A31B9BD783; Tue, 18 Jun 2013 22:08:24 +0000 (UTC)
Date: Wed, 19 Jun 2013 00:08:24 +0200
From: Jeremie Le Hen <jlh@FreeBSD.org>
To: freebsd-current@FreeBSD.org
Subject: Panic with RACCT on a jailed process
Message-ID: <20130618220824.GA11548@caravan.chchile.org>
Mail-Followup-To: freebsd-current@FreeBSD.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
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: Tue, 18 Jun 2013 22:08:31 -0000

Hi,

I've been bit by a panic three times over the last month.

I'm currently running:
    FreeBSD obiwan.piupiu.local 10.0-CURRENT FreeBSD 10.0-CURRENT #7 r251519: Sun Jun  9 22:37:09 CEST 2013 root@obiwan.piupiu.local:/usr/obj/usr/src/sys/OBIWAN  amd64

The panic message is:
    panic: destroying non-empty racct: 1007616 allocated for resource 4

I quicky tried to track this down, but in half an hour I didn't get very
far.  Resource 4 is RACCT_RSS.  The faulty process seems to be 66555
which looks like a 32-bits cron(8) running in a jail.

This is the call trace:

    kdb_enter() at kdb_enter+0x3e/frame 0xffffff80e63b3610
    vpanic() at vpanic+0x146/frame 0xffffff80e63b3650
    kassert_panic() at kassert_panic+0x136/frame 0xffffff80e63b36c0
    racct_destroy() at racct_destroy+0x8e/frame 0xffffff80e63b36f0
    uifree() at uifree+0x5e/frame 0xffffff80e63b3710
    crfree() at crfree+0x48/frame 0xffffff80e63b3730
    thread_wait() at thread_wait+0xac/frame 0xffffff80e63b3750
    proc_reap() at proc_reap+0x43f/frame 0xffffff80e63b37a0
    proc_to_reap() at proc_to_reap+0x340/frame 0xffffff80e63b37f0
    kern_wait6() at kern_wait6+0x1fa/frame 0xffffff80e63b3890
    kern_wait() at kern_wait+0x5a/frame 0xffffff80e63b39e0
    freebsd32_wait4() at freebsd32_wait4+0x2e/frame 0xffffff80e63b3ae0
    ia32_syscall() at ia32_syscall+0x26c/frame 0xffffff80e63b3bf0

The panic happened each three times because of cron(8), but both with
32-bits and 64-bits versions.


crashinfo + ddb textdump available here:
    http://people.freebsd.org/~jlh/crash/core.txt.9.txt

Note that the dmesg included in the core contains another panic I got
with ZFS.  I usually wait to see it twice before reporting, but if you
want I still have the core and the crashinfo around.

-- 
Jeremie Le Hen

Scientists say the world is made up of Protons, Neutrons and Electrons.
They forgot to mention Morons.