From owner-freebsd-current Wed Sep 3 22:32:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA06764 for current-outgoing; Wed, 3 Sep 1997 22:32:02 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA06742 for ; Wed, 3 Sep 1997 22:31:59 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id AAA03246; Thu, 4 Sep 1997 00:31:20 -0500 (EST) From: "John S. Dyson" Message-Id: <199709040531.AAA03246@dyson.iquest.net> Subject: Re: 3.0/SMP panic In-Reply-To: <199709040405.WAA07230@pluto.plutotech.com> from Kenneth Merry at "Sep 3, 97 10:05:31 pm" To: ken@plutotech.com (Kenneth Merry) Date: Thu, 4 Sep 1997 00:31:20 -0500 (EST) Cc: mrcpu@schizo.cdsnet.net, current@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG 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-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kenneth Merry said: > > By any chance do you have more than 64MB in your machine and > options MAXMEM=... in your kernel config file? > > I did, and I had panics very much like that (in pmap_enter) > immediately on boot. When I took the MAXMEM line out (I've got 128MB), > things worked just fine... I'm still not sure why, though. > > > Ken > -- > Kenneth Merry > ken@plutotech.com > I have been having the same panic at pmap_enter (note that it ISN'T a pmap_enter bug.) At least I can reproduce it, and it appears to be excited by simple (kernel) code mods or movement. There is a problem lurking, and I have spent the last 4-5 days trying to track it down. I am now more methodically trying to ferret the problem out, and am trying to fix it ASAP. It has held up my deliverables and it NEEDS to be fixed!!! :-(. -- John dyson@freebsd.org jdyson@nc.com