From owner-freebsd-current Sat Jul 19 20:34:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA26144 for current-outgoing; Sat, 19 Jul 1997 20:34:38 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA26139 for ; Sat, 19 Jul 1997 20:34:35 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA16060; Sun, 20 Jul 1997 13:04:26 +0930 (CST) From: Michael Smith Message-Id: <199707200334.NAA16060@genesis.atrad.adelaide.edu.au> Subject: Re: fatal double fault In-Reply-To: <199707191701.RAA00380@ubiq.veda.is> from Adam David at "Jul 19, 97 05:01:14 pm" To: adam@veda.is (Adam David) Date: Sun, 20 Jul 1997 13:04:26 +0930 (CST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Adam David stands accused of saying: > I had an NFS client and X server machine double fault panic on me today. > There's a heavily loaded machine with all kinds of servers running that is > holding out robustly. This is with current from before the NFSweb stuff > was added. It might have nothing to do with NFS or X. I don't think it would. > The only debug info that I have follows: > > /kernel: Fatal double fault: > /kernel: eip = 0xf01bf6a5 > /kernel: esp = 0xf3859e9c > /kernel: ebp = 0xf3859ec0 > /kernel: panic: double fault > > # nm /kernel | sort | dwimgrep > f01bf390 F swtch.o > [...] > f01bf57c T _cpu_switch > f01bf5ce t sw1 > f01bf5cf t sw1a > f01bf5fd t rt3 > f01bf605 t nortqr > f01bf637 t idqr > f01bf665 t id3 > f01bf66b t swtch_com > f01bf6b4 T cpu_switch_load_fs > f01bf6ba T cpu_switch_load_gs > f01bf6c4 T _savectx > > If this is not useful information, perhaps it would make sense to log more > verbosely without requiring a full crash dump to be made. It's almost impossible to log anything more useful on a double fault; that's why it's called a 'fatal' double fault. If you get the above on a regular basis, then I'd be starting to get worried about the usual memory/cache problems. > Adam David -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[