From owner-freebsd-stable@FreeBSD.ORG Tue Jul 15 19:42:02 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9376F1065674; Tue, 15 Jul 2008 19:42:02 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2DED18FC1D; Tue, 15 Jul 2008 19:42:00 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <487CFD8B.2060905@FreeBSD.org> Date: Tue, 15 Jul 2008 21:42:03 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: john@basicnets.co.uk References: <854CADB9D95147CAB10BC35887A8E5DC@emea.hubersuhner.net> <20080715102135.GA18082@eos.sc1.parodius.com> <487C8486.1040904@FreeBSD.org> <20080715201915.8m5j3k1lw00k4gck@mail.basicnets.co.uk> In-Reply-To: <20080715201915.8m5j3k1lw00k4gck@mail.basicnets.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 'Jeremy Chadwick' , freebsd-stable@freebsd.org Subject: Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2008 19:42:02 -0000 john@basicnets.co.uk wrote: > (kgdb) backtrace > #0 doadump () at pcpu.h:194 > #1 0xffffff0004742440 in ?? () > #2 0xffffffff80477699 in boot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:409 > #3 0xffffffff80477a9d in panic (fmt=0x104
) > at /usr/src/sys/kern/kern_shutdown.c:563 > #4 0xffffffff8072ed44 in trap_fatal (frame=0xffffff00048ee000, > eva=18446742974275512528) at /usr/src/sys/amd64/amd64/trap.c:724 > #5 0xffffffff8072f115 in trap_pfault (frame=0xffffffffb1d7f4e0, > usermode=0) > at /usr/src/sys/amd64/amd64/trap.c:641 > #6 0xffffffff8072fa58 in trap (frame=0xffffffffb1d7f4e0) > at /usr/src/sys/amd64/amd64/trap.c:410 > #7 0xffffffff807156be in calltrap () > at /usr/src/sys/amd64/amd64/exception.S:169 > #8 0x0000006400000000 in ?? () > #9 0xffffffff8067d3ee in uma_zalloc_arg (zone=0xffffff00bfed07e0, > udata=0x0, > flags=-256) at /usr/src/sys/vm/uma_core.c:1835 OK, that is if (zone->uz_ctor != NULL) { if (zone->uz_ctor(item, zone->uz_keg->uk_size, uz_ctor is indeed not null, but it's got 3 bits set. Not impossible that it's bad RAM still. I didn't spot anything that could cause it otherwise but I don't know this code in detail. Do all of the panics have the same backtrace? Kris > #10 0xffffffff80661ecf in ffs_vget (mp=0xffffff00047f4978, ino=47884512, > flags=2, vpp=0xffffffffb1d7f728) at uma.h:277 > #11 0xffffffff8066d010 in ufs_lookup (ap=0xffffffffb1d7f780) > at /usr/src/sys/ufs/ufs/ufs_lookup.c:573 > #12 0xffffffff804dfa89 in vfs_cache_lookup (ap=Variable "ap" is not > available. > ) at vnode_if.h:83 > #13 0xffffffff8077235f in VOP_LOOKUP_APV (vop=0xffffffff809e7de0, > a=0xffffffffb1d7f840) at vnode_if.c:99 > ---Type to continue, or q to quit--- > #14 0xffffffff804e6394 in lookup (ndp=0xffffffffb1d7f950) at vnode_if.h:57 > #15 0xffffffff804e7228 in namei (ndp=0xffffffffb1d7f950) > at /usr/src/sys/kern/vfs_lookup.c:219 > #16 0xffffffff804f4717 in kern_stat (td=0xffffff00048ee000, > path=0x8006f7040
, > pathseg=Variable "path > seg" is not available. > ) > at /usr/src/sys/kern/vfs_syscalls.c:2109 > #17 0xffffffff804f4987 in stat (td=Variable "td" is not available. > ) at /usr/src/sys/kern/vfs_syscalls.c:2093 > #18 0xffffffff8072f397 in syscall (frame=0xffffffffb1d7fc70) > at /usr/src/sys/amd64/amd64/trap.c:852 > #19 0xffffffff807158cb in Xfast_syscall () > at /usr/src/sys/amd64/amd64/exception.S:290 > #20 0x000000000043127c in ?? () > Previous frame inner to this frame (corrupt stack?) > > I really don't understand this -any advice you can give would really > be appreciated. > > John > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > >