From owner-freebsd-stable Mon Nov 15 7:48:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 4BFDD15065 for ; Mon, 15 Nov 1999 07:48:01 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA09766 for ; Mon, 15 Nov 1999 10:47:58 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id KAA13029; Mon, 15 Nov 1999 10:47:56 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id KAA00386; Mon, 15 Nov 1999 10:47:55 -0500 (EST) Date: Mon, 15 Nov 1999 10:47:55 -0500 (EST) From: Thomas David Rivers Message-Id: <199911151547.KAA00386@lakes.dignus.com> To: freebsd-stable@FreeBSD.ORG, rivers@dignus.com Subject: Re: 3.3-RELEASE panics & Linux emu. In-Reply-To: <199911151524.KAA03066@lakes.dignus.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG More info... With the debug kernel, I get the same panic, but IP is 0x0 instead of 0x8000000. So, we are taking a bad branch (a function ptr is likely not initialized properly?) Unfortunately, DDB's trace command only gives me the panic message... no trace back. So - I'm at a loss to say exactly where this is occuring. Would a knowledgeable kernel debugger care to share some wisdom when debugging things like this - that is - if IP is 0, how do you tell from whence the bad branch came? - Thanks - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message