From owner-freebsd-stable Mon Nov 15 7:25:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id B425C1511C for ; Mon, 15 Nov 1999 07:24:42 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA00495 for ; Mon, 15 Nov 1999 10:24:38 -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 KAA12988 for ; Mon, 15 Nov 1999 10:24:37 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id KAA03066 for freebsd-stable@freebsd.org; Mon, 15 Nov 1999 10:24:36 -0500 (EST) Date: Mon, 15 Nov 1999 10:24:36 -0500 (EST) From: Thomas David Rivers Message-Id: <199911151524.KAA03066@lakes.dignus.com> To: freebsd-stable@freebsd.org Subject: 3.3-RELEASE panics & Linux emu. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If the happy reader recalls - I announced last week that I had solved my panic problems on 3.3-RELEASE (I had suspected a partially built kernel issue...) Well - I just got the panics again; so I suspect that is not the problem. Although, I am able to drop into DDB now and take a look around. I believe the panic is related to Linux emulation, as a Linux program is always what's running for the panic. And - the panic is interesting in that EIP seems to be the culprit. The kernel is branching to 0x80000000... (which doesn't look like a really nice place to jump to.) I'm building a debuggable kernel and will report more info when I have it. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message