From owner-freebsd-current Thu Sep 4 10:24:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA12483 for current-outgoing; Thu, 4 Sep 1997 10:24:49 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA12315; Thu, 4 Sep 1997 10:21:13 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id LAA09408; Thu, 4 Sep 1997 11:20:37 -0600 (MDT) Message-Id: <199709041720.LAA09408@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: dyson@FreeBSD.ORG cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: 3.0/SMP panic In-reply-to: Your message of "Thu, 04 Sep 1997 00:31:20 CDT." <199709040531.AAA03246@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Sep 1997 11:20:37 -0600 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John, > 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!!! :-(. one user reports this happens to him with SMP but not UP. In your setup where you can reproduce it, is it SMP only or UP also? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD