From owner-freebsd-current@FreeBSD.ORG Sun Jun 19 23:03:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FA3016A41C for ; Sun, 19 Jun 2005 23:03:22 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AD7343D48 for ; Sun, 19 Jun 2005 23:03:22 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 28F9E72DD9; Sun, 19 Jun 2005 16:03:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2370C72DCB; Sun, 19 Jun 2005 16:03:22 -0700 (PDT) Date: Sun, 19 Jun 2005 16:03:22 -0700 (PDT) From: Doug White To: Wesley Morgan In-Reply-To: <20050618232951.P77492@volatile.chemikals.org> Message-ID: <20050619160022.R83634@carver.gumbysoft.com> References: <20050618232951.P77492@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: odd panics on -current recently X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jun 2005 23:03:22 -0000 On Sat, 18 Jun 2005, Wesley Morgan wrote: > Been getting what appear to be the same panic for at least a week on > -current. Enabled dumps and this is the best trace I can get. I don't have > the panic message, and this trace doesn't make a lot of sense to me: > > #0 doadump () at pcpu.h:165 > 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); > (kgdb) bt > #0 doadump () at pcpu.h:165 > #1 0xc0706e40 in buf.1 () > #2 0xc051bfee in boot (howto=260) at ../../../kern/kern_shutdown.c:397 > #3 0xc051c416 in panic (fmt=0xc06b19aa "%s") > at ../../../kern/kern_shutdown.c:553 > #4 0xc0688e6c in trap_fatal (frame=0xd3c1dc40, eva=0) > at ../../../i386/i386/trap.c:831 > #5 0xc06883a9 in trap (frame= > {tf_fs = -1068302328, tf_es = -1066401752, tf_ds = -1047068632, > tf_edi = -1047265920, tf_esi = -1035014144, tf_ebp = 0, tf_isp = > -742269844, tf_ebx = -1066355360, tf_edx = -1035014144, tf_ecx = 0, tf_eax > = -2, tf_trapno = 12, tf_err = 0, tf_eip = -1068198526, tf_cs = 32, > tf_eflags = 589954, tf_esp = -1035014144, tf_ss = 4}) at > ../../../i386/i386/trap.c:269 > #6 0xc067674a in calltrap () at ../../../i386/i386/exception.s:139 > (kgdb) You didn't post the panic message, which is necessary to determine why the trap occured in the first place, and there appears to be a lot of missing backtrace since you can't get to trap_fatal from a userspace trap. You might also derive a kernel config from GENERIC instead of LINT so you don't include some of the more esoteric options and trigger uncommonly used code paths. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org