From owner-freebsd-current Mon Feb 8 16:13:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00280 for freebsd-current-outgoing; Mon, 8 Feb 1999 16:13:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00269 for ; Mon, 8 Feb 1999 16:13:03 -0800 (PST) (envelope-from tcobb@staff.circle.net) From: tcobb@staff.circle.net Received: by freya.circle.net with Internet Mail Service (5.5.2232.9) id <1PTHK00A>; Mon, 8 Feb 1999 19:12:13 -0500 Message-ID: To: mike@smith.net.au Cc: current@FreeBSD.ORG Subject: RE: Tracking a Fatal Double Fault Date: Mon, 8 Feb 1999 19:12:11 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The machine is running a custom kernel, but nothing very unusual. My instinct is that it may be related to something with the 3c905B 3COM cards that I reported earlier, I'm trying with Intel EtherExpresses right now and getting no fault problems. The double-fault does not occur consistently, unfortunately, and typically only occurs during my rc.local stuff (loading a bunch (100+) of chrooted daemons) on boot-up. Would the eip/esp/ebp values be worth sending? -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > Sent: Monday, February 08, 1999 6:55 PM > To: tcobb@staff.circle.net > Cc: current@FreeBSD.ORG > Subject: Re: Tracking a Fatal Double Fault > > > > 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