From owner-freebsd-current Fri Jul 24 09:36:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10132 for freebsd-current-outgoing; Fri, 24 Jul 1998 09:36:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10085 for ; Fri, 24 Jul 1998 09:36:30 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA05611; Fri, 24 Jul 1998 11:35:41 -0500 (EST) (envelope-from toor) Message-Id: <199807241635.LAA05611@dyson.iquest.net> Subject: Re: panic: page fault while in kernel mode - from gcc In-Reply-To: <199807240219.TAA23545@implode.root.com> from David Greenman at "Jul 23, 98 07:19:17 pm" To: dg@root.com Date: Fri, 24 Jul 1998 11:35:41 -0500 (EST) Cc: tlambert@primenet.com, toasty@home.dragondata.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman said: > >> Right now, with my -current server, I get a 'panic: page fault while in > >> kernel mode' about once a week.... Dual Processor, P/200 with 256M of ram. > >> Most of the problems seem to occur when the system is starting to swap.. > >> (obviously) > > > >You are running with John Dyson's patches, which were published in > >his home directory, but not integrated into FreeBSD itself? > > > >Or you are running with FreeBSD-current? > > > >If you are running FreeBSD-current, you should try adding John's > >patches. > > All of the reports that I've seen to date (about five) have indicated that > the patches that used to be in John's directory caused major instabilities > which is the reason why they haven't been committed. > As I said earlier, those "fixes" are a little rough, and the SMP "improvements", need to be distilled from the patches for review. Most of the SMP changes were to start improving the granularity of SMP, not to actually fix bugs. (However, some bugfixing might be in the code -- I don't even remember what is in the patch kits. One note: the -current patchkit is really bad, and the "b" version is more workable. Right now, the code that I have been running for the last few months is rock-solid stable, with NO crashes from anything except the ancient softupdates that I am running, and a heat problem from a broken air conditioner.) I don't have a patchkit for the code that I am running though, but probably has some fixes relative to the "current" version that is sitting on Eivind's site.) The bug in traceback is either a reference count problem left over from previous usage of the code, or a problem with pmap_copy. (I suspect pmap_copy.) Take a look at the patches that I had provided earlier, and see if there are any pmap_copy bugs fixed. If there aren't, the bug is likely fairly easy to fix. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message