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:m...@smith.net.au] > Sent: Monday, February 08, 1999 6:55 PM > To: tc...@staff.circle.net > Cc: curr...@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. \\ m...@smith.net.au > \\ The race is long, and in the \\ msm...@freebsd.org > \\ end it's only with yourself. \\ msm...@cdrom.com > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
