From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 7 22:30:36 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1C8016A420 for ; Tue, 7 Feb 2006 22:30:36 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C8B543D46 for ; Tue, 7 Feb 2006 22:30:36 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k17MUamR007786; Tue, 7 Feb 2006 14:30:36 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k17MUaWt007785; Tue, 7 Feb 2006 14:30:36 -0800 (PST) (envelope-from sgk) Date: Tue, 7 Feb 2006 14:30:36 -0800 From: Steve Kargl To: Chaim Rieger Message-ID: <20060207223036.GA7766@troutmask.apl.washington.edu> References: <0A0EBF53-035D-4396-8721-D7401146C10E@gmail.com> <20060207212659.GB5747@troutmask.apl.washington.edu> <62459965-A688-4386-93CD-A831598B085A@gmail.com> <20060207214922.GB6853@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: core dump need some help X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 22:30:37 -0000 On Tue, Feb 07, 2006 at 02:17:47PM -0800, Chaim Rieger wrote: > > > >Yes. Except your kernel.debug appears to be missing its symbols. > > #0 doadump () at pcpu.h:172 > #1 0x0000000000000004 in ?? () > #2 0xffffffff803b50c3 in boot (howto=260) at /usr/src/sys/kern/ > kern_shutdown.c:399 > #3 0xffffffff803b56c6 in panic (fmt=0xffffff0090d8dbe0 "@\003?\211") > at /usr/src/sys/kern/kern_shutdown.c:555 > #4 0xffffffff8058bfbf in trap_fatal (frame=0xffffff0090d8dbe0, > eva=18446742976510559040) at /usr/src/sys/amd64/amd64/trap.c:655 > #5 0xffffffff8058c462 in trap (frame= > {tf_rdi = 4, tf_rsi = 4096, tf_rdx = -1096354855944, tf_rcx = > 4607, tf_r8 = -1629884416, tf_r9 = -1629888512, tf_rax = 0, tf_rbx = > -1629888512, tf_rbp = -1629892608, tf_r10 = 1, tf_r11 = 0, tf_r12 = > 0, tf_r13 = 255, tf_r14 = -1710923336, tf_r15 = 2, tf_trapno = 1, > tf_addr = 0, tf_flags = 0, tf_err = 0, tf_rip = -2143234582, tf_cs = > 8, tf_rflags = 66067, tf_rsp = -1253652768, tf_ss = 16}) at /usr/src/ > sys/amd64/amd64/trap.c:467 > #6 0xffffffff8057bb6b in calltrap () at /usr/src/sys/amd64/amd64/ > exception.S:168 > #7 0xffffffff8040d5ea in vfs_bio_clrbuf (bp=0xffffffff9a0561b8) at / > usr/src/sys/kern/vfs_bio.c:3470 I'm guessing that frame 7 is where things wnet south on you. I've taken you as far as my kernel debugging knowledge can. Hopefully, someone can help. You may want to submit a PR with send-pr. -- Steve