Date: Mon, 08 Feb 1999 15:55:14 -0800 From: Mike Smith <mike@smith.net.au> To: tcobb@staff.circle.net Cc: current@FreeBSD.ORG Subject: Re: Tracking a Fatal Double Fault Message-ID: <199902082355.PAA01476@dingo.cdrom.com> In-Reply-To: Your message of "Mon, 08 Feb 1999 17:24:29 EST." <A0CFA284C004D211B7EE0060082F32A412E13D@freya.circle.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902082355.PAA01476>