From owner-freebsd-current@FreeBSD.ORG Wed Nov 19 07:20:14 2003 Return-Path: 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 1E09A16A4CE; Wed, 19 Nov 2003 07:20:14 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE34143FBD; Wed, 19 Nov 2003 07:20:10 -0800 (PST) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 22B7C1FF91D; Wed, 19 Nov 2003 16:20:09 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 73D8B1FF90D; Wed, 19 Nov 2003 16:20:07 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 0F54F154DF; Wed, 19 Nov 2003 15:13:55 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 05159154D7; Wed, 19 Nov 2003 15:13:55 +0000 (UTC) Date: Wed, 19 Nov 2003 15:13:55 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Robert Watson In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020300 cc: current@freebsd.org cc: Hajimu UMEMOTO Subject: Re: another trap 12 while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 19 Nov 2003 15:20:14 -0000 On Wed, 19 Nov 2003, Robert Watson wrote: Hi, > You should still be able to turn the bad instruction pointer into at least > a function name using nm on your compiled kernel. Run nm on the kernel > binary, and search through it until you find the symbols just before > (lower) and just after (higher) than the value listed for the instruction > pointer below. That would at least tell us what function the fault is > occuring in. I suspect to get anywhere useful, we'll need the full > debugging results, but it's probably a useful start, and it will allow us > to be sure the panics you might get after you have debugging support > compiled in are the same failure mode. thanks for your answer. > > instruction pointer = 0x8:0xc055a00a c0559e10 T key_sa_routechange c0559f10 t key_sa_chgstate c0559fb0 T key_sa_stir_iv c0559fe0 t key_sp_dead c0559ff0 t key_sp_unlink c055a020 t key_alloc_mbuf c055a100 t kdebug_typestr c055a150 t kdebug_sadb_msg_typestr c055a170 t kdebug_sadb_ext_typestr Cc'ed ume. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/