From owner-freebsd-smp Thu Sep 4 10:32:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13016 for smp-outgoing; Thu, 4 Sep 1997 10:32:11 -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 KAA13009; Thu, 4 Sep 1997 10:32:05 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id MAA01880; Thu, 4 Sep 1997 12:31:53 -0500 (EST) From: "John S. Dyson" Message-Id: <199709041731.MAA01880@dyson.iquest.net> Subject: Re: 3.0/SMP panic In-Reply-To: <199709041720.LAA09408@Ilsa.StevesCafe.com> from Steve Passe at "Sep 4, 97 11:20:37 am" To: smp@csn.net (Steve Passe) Date: Thu, 4 Sep 1997 12:31:52 -0500 (EST) Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG, smp@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-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve Passe said: > 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? > I haven't been able to reproduce it in UP, but I really don't think that it is an SMP problem. However, that is only my "feeling." -- John dyson@freebsd.org jdyson@nc.com