From owner-freebsd-current Sun Jan 21 18:59:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA00447 for current-outgoing; Sun, 21 Jan 1996 18:59:36 -0800 (PST) Received: from mpp.minn.net (root@mpp.Minn.Net [204.157.201.242]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA00441 for ; Sun, 21 Jan 1996 18:59:32 -0800 (PST) Received: (from mpp@localhost) by mpp.minn.net (8.7.3/8.6.9) id UAA00228 for freebsd-current@freebsd.org; Sun, 21 Jan 1996 20:59:23 -0600 (CST) Message-Id: <199601220259.UAA00228@mpp.minn.net> Subject: Fatal double fault To: freebsd-current@freebsd.org Date: Sun, 21 Jan 1996 20:59:23 -0600 (CST) From: "Mike Pritchard" X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk I just had my machine die with the error message "Fatal double fault:", looking at sys/i386/i386/trap.c is where this message is coming out. The other 3 printfs that are supposed to follow that message never came out. The interesting this is that my machine died just at the same point where I've been having lockups when starting my PPP connection. For the past several days or so I've been getting lockup where everything is sleeping on "lockrd" (something in the vm code) just as my PPP connection is established. I suspect that the above crash is related. Now the other interesting this is that at the same time as the "lockrd" hangups started, pppd started doing something strange. It will run the /etc/ip-up script, immediately run the /etc/ip-down script and then immediately run the /etc/ip-up script again and leave the connection up. I'm going to go play around and see exactly what I have in those two scripts that might be causing problems, but I thought I would mention it here in case anyone had any ideas. All of these problems have happened with various -current kernels over the past several days (maybe even as long as a week). The "double fault" problem just happened with a kernel I sup-ed at 7 am this morning. -- Mike Pritchard mpp@minn.net "Go that way. Really fast. If something gets in your way, turn"