From owner-freebsd-bugs@FreeBSD.ORG Wed Sep 7 22:50:15 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CE8D16A41F for ; Wed, 7 Sep 2005 22:50:15 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAE0743D45 for ; Wed, 7 Sep 2005 22:50:14 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j87MoEOV062045 for ; Wed, 7 Sep 2005 22:50:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j87MoEN1062044; Wed, 7 Sep 2005 22:50:14 GMT (envelope-from gnats) Date: Wed, 7 Sep 2005 22:50:14 GMT Message-Id: <200509072250.j87MoEN1062044@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Harald Schmalzbauer Cc: Subject: Re: kern/85804: panic after chown -R from chrooted shell X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harald Schmalzbauer List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Sep 2005 22:50:15 -0000 The following reply was made to PR kern/85804; it has been noted by GNATS. From: Harald Schmalzbauer To: bug-followup@freebsd.org, harry@schmalzbauer.de Cc: Subject: Re: kern/85804: panic after chown -R from chrooted shell Date: Thu, 8 Sep 2005 00:40:32 +0200 Ok, obviously this panic has nothing todo with the chown or chroot, I got a very similar one while the machine was doing pretty nothing (MUA, Browser and a hand full xterms, all more or less idling). Here's the message and the trace: KDB: enter: panic [thread pid 48 tid 100040 ] Stopped at kdb_enter+0x30: leave db> trace Tracing pid 48 tid 100040 td 0xc1dfd780 kdb_enter(c0791b35,c0801560,c07a683f,d5894bac,100) at kdb_enter+0x30 panic(c07a683f,c07a48c0,7c,0,c408669c) at panic+0xd5 mtrash_ctor(c4086680,80,0,0,d5894c14) at mtrash_ctor+0x65 mtrash_fini(c4086680,80,2,2df,c085a640) at mtrash_fini+0x28 zone_drain(c144d880,0,c07a620b,5d6,0) at zone_drain+0x1a6 zone_foreach(c06e3850,d5894ce0,c06faed9,c1d97d0c,0) at zone_foreach+0x55 uma_reclaim(c1d97d0c,0,c07a85e7,2d1,c08065a0) at uma_reclaim+0x17 vm_pageout_scan(0,0,c07a85e7,604,1388) at vm_pageout_scan+0x159 vm_pageout(0,d5894d38,c078ef39,30d,3aa1f429) at vm_pageout+0x31b fork_exit(c06fc050,0,d5894d38) at fork_exit+0xc1 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd5894d6c, ebp = 0 --- System is like originally mentioned 6.0-beta4, seems to be a show stopper for 6.0-release... Thanks, -Harry