From owner-freebsd-current Sat Jul 19 10:01:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA03222 for current-outgoing; Sat, 19 Jul 1997 10:01:25 -0700 (PDT) Received: from veda.is (spiral.veda.is [193.4.230.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA03215 for ; Sat, 19 Jul 1997 10:01:21 -0700 (PDT) Received: from ubiq.veda.is (ubiq.veda.is [193.4.230.60]) by veda.is (8.8.6/8.8.5) with ESMTP id RAA10991 for ; Sat, 19 Jul 1997 17:01:18 GMT From: Adam David Received: (from adam@localhost) by ubiq.veda.is (8.8.6/8.8.5) id RAA00380 for freebsd-current@freebsd.org; Sat, 19 Jul 1997 17:01:15 GMT Message-Id: <199707191701.RAA00380@ubiq.veda.is> Subject: fatal double fault To: freebsd-current@freebsd.org Date: Sat, 19 Jul 1997 17:01:14 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. 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. -- Adam David