From owner-freebsd-questions  Sun Mar 30 13:10:48 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA12856
          for questions-outgoing; Sun, 30 Mar 1997 13:10:48 -0800 (PST)
Received: from gdi.uoregon.edu (cisco-ts14-line16.uoregon.edu [128.223.150.182])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12825
          for <questions@freebsd.org>; Sun, 30 Mar 1997 13:10:29 -0800 (PST)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id NAA00471; Sun, 30 Mar 1997 13:09:44 -0800 (PST)
Date: Sun, 30 Mar 1997 13:09:43 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: David Lowe <dlowe@sirius.com>
cc: questions@freebsd.org
Subject: Re: Fatal double fault...
In-Reply-To: <Pine.NXT.3.95q.970327122010.2079A-100000@ds9>
Message-ID: <Pine.BSI.3.94.970330130903.242c-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 27 Mar 1997, David Lowe wrote:

> I've got a new Pentium Pro 150, 64MB RAM, running FreeBSD 2.2.1.  The
> machine was running 2.2.0 for about a day, and seemed to be solid.  I
> cvsupped 2.2.1 yesterday, built a new kernel, and ran make world before I
> left yesterday.  This morning, the machine was hosed (it had apparently
> rebooted at least once overnight, and was totally hung when I got here).
> 
> I built a new kernel with DDB enabled, and played around with it for a
> while, but was unable to cause a crash.  It was when I came back to it
> after leaving for a few minutes (about 10 or 15, i think) that it was
> down.
> 
> I've been able to duplicate this several times now - leave the machine
> alone for 10-15 minutes, and...
> 
>   Fatal double fault:
>   eip = 0xf01bc45c
>   esp = 0xefbfe000
>   ebp = 0xefbfe058
>   panic: double fault
>   Debugger("panic")
>  
>   [now it's completely hung, needs to be rebooted...]
> 
> Does this point to some unhandled power management feature, since it only
> seems to happen when the machine is idling?  Bad RAM?  Screwy BIOS things?
> This is the first time I've used a PPro - any quirks I should know about?

Not sure.  Report to hackers@freebsd.org, they've been working with
another double fault and may be able to help you.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major