From owner-freebsd-current Mon Feb 8 15:59:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26236 for freebsd-current-outgoing; Mon, 8 Feb 1999 15:59:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26231 for ; Mon, 8 Feb 1999 15:59:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01476; Mon, 8 Feb 1999 15:55:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902082355.PAA01476@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: tcobb@staff.circle.net cc: current@FreeBSD.ORG Subject: Re: Tracking a Fatal Double Fault In-reply-to: Your message of "Mon, 08 Feb 1999 17:24:29 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Feb 1999 15:55:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can someone please give me a short guide > on how to track down a fatal double fault? > System is 3.0-19990205-STABLE, and I've written > down the fault info. Ack. It's actually pretty difficult. You can start by trying to locate the PC for the fault in the kernel image, but the typical cause of a double fault is running out of kernel stack. Are you running any custom kernel code? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message