From owner-freebsd-hackers Sun Feb 10 6:50:53 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.taconic.net (mail.taconic.net [205.231.144.5]) by hub.freebsd.org (Postfix) with ESMTP id D3BA037B402 for ; Sun, 10 Feb 2002 06:50:50 -0800 (PST) Received: from coyotepoint.com ([205.231.27.66]) by mail.taconic.net (8.10.2+Sun/8.11.4) with ESMTP id g1AEohp19119; Sun, 10 Feb 2002 09:50:43 -0500 (EST) Message-ID: <3C668925.EFF8FA34@coyotepoint.com> Date: Sun, 10 Feb 2002 09:52:21 -0500 From: Bill Kish X-Mailer: Mozilla 4.79 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Terry Lambert Cc: hackers Subject: Re: Debugging double page fault References: <3C6478BE.BE6F5A70@coyotepoint.com> <3C6497EA.73CDEC64@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Terry, Nothing's changed hardware or configuration wise. Since this system handles alot of network traffic, I was thinking it might be some kind of martian packet causing the crash. I'd seen that happen before with RR pings from Linux systems, but at least had a reasonable dump to work with. I'll try swapping out the hardware and see what happens. But I'm still curious about a methodology for analyzing such dumps. -=BK Terry Lambert wrote: > Bill Kish wrote: > > I've recently started seeing "double fault" panics on a formerly FreeBSD > > 2.2.8 based system (It's running 2.2.8 as a somewhat embedded OS, so please > > don't flame me about being back rev!) > [ ... ] > > My rough understanding is that double faults are usually the result of > > running out of stack, and that the underlying cause of the panic can probably > > be uncovered if I can find the previous stack . > > > > Can anyone point me towards some hints for debugging this sort of crash. Any > > advice greatly appreciated. > > It's very old. > > This makes me think that it used to work, and now it > doesn't. > > What did you change just before it stopped working? > > If nothing, then it's likely a hardware problem. > > -- Terry -- --------------------------------------------------------------- Bill Kish Ph: 650.969.6000 Chief Engineer, 12 S. First Street, Suite 616 Coyote Point Systems Inc. San Jose, CA 95113 Email: kish@coyotepoint.com http://www.coyotepoint.com/ --------------------------------------------------------------- For support call: 1-888-891-8150 Email: --------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message