From owner-freebsd-current Tue Jul 21 23:18:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16097 for freebsd-current-outgoing; Tue, 21 Jul 1998 23:18:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16069 for ; Tue, 21 Jul 1998 23:18:27 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id XAA26587; Tue, 21 Jul 1998 23:17:11 -0700 (PDT) Message-Id: <199807220617.XAA26587@implode.root.com> To: Kevin Day cc: current@FreeBSD.ORG Subject: Re: panic: page fault while in kernel mode - from gcc In-reply-to: Your message of "Wed, 22 Jul 1998 00:59:55 CDT." <199807220559.AAA03924@home.dragondata.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 21 Jul 1998 23:17:11 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This seems to indicate that the new process's page directory either hasn't >> been allocated yet or went away for some reason. Apparantly one of several >> new bugs that John has left us with. >> > >Is there any reason why someone doesn't back out his last few batches of >large vm changes? Apparently he was half done with some of it, and what we >had before seemed more stable than what we have now. That may ultimately be what we have to do, but the fixes also fixed some serious 'leak' style problems with the Mach derived VM system, so I'd rather that we find the bugs and fix them rather than going back to the previous code. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message