From owner-freebsd-stable@FreeBSD.ORG Mon Aug 30 01:10:36 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B33C916A4CF for ; Mon, 30 Aug 2004 01:10:36 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A45A843D41 for ; Mon, 30 Aug 2004 01:10:36 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 9967E72DD5; Sun, 29 Aug 2004 18:10:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 9728972DD4; Sun, 29 Aug 2004 18:10:36 -0700 (PDT) Date: Sun, 29 Aug 2004 18:10:36 -0700 (PDT) From: Doug White To: Mike Tancsa In-Reply-To: <6.1.2.0.0.20040829140325.111c1708@64.7.153.2> Message-ID: <20040829180443.L69068@carver.gumbysoft.com> References: <6.1.2.0.0.20040829140325.111c1708@64.7.153.2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: panics after updating to RELENG_4 aug 25 from May 17th X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 01:10:36 -0000 On Sun, 29 Aug 2004, Mike Tancsa wrote: > > The box was quite stable prior to this with well burnt in hardware. Both > panics seem to be in the same location. The box functions as an outbound > smtp smarthost running stock sendmail. dmesg and kernel config at the end The double faults aren't helping to debug this. But at first glance it kinda looks like some sort of memory corruption. Here's the meat of the first trace: > #16 0xc014013e in statclock (frame=0xc023a130) at > /usr/src/sys/kern/kern_clock.c:439 > #17 0xc01ff66d in rtcintr (frame={cf_vec = 0, cf_ppl = 0, cf_fs = 16, cf_es > = -65520, cf_ds = 16, cf_edi = -1, cf_esi = 0, > cf_ebp = -1071406728, -1071406748, cf_ebx = 0, cf_edx = 2517, cf_ecx > = -425803104, cf_eax = 0, 0, 0, cf_eip = -1071702170, > cf_cs = 8, cf_eflags = 514, cf_esp = 0, cf_ss = -1071670027}) at > /usr/src/sys/i386/isa/clock.c:385 > #18 0xc01f1f66 in cpu_idle () at /usr/src/sys/i386/i386/machdep.c:1000 statclock() doesn't do a whole lot. Line 439 (in RELENG_4 at least) is: 439 if (--pscnt > 0) 440 return; pscnt is a static local variable. Not likely thats going to fly off into space. Please check this on your install. If its the same thing I'd start suspecting hardware failure. Dumping lists of the generic trap code isn't telling us anything new :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org