From owner-freebsd-alpha Thu Nov 7 21:34:31 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FBBD37B401; Thu, 7 Nov 2002 21:34:30 -0800 (PST) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 534AD43E3B; Thu, 7 Nov 2002 21:34:29 -0800 (PST) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id gA85YFZ50745; Thu, 7 Nov 2002 21:34:19 -0800 (PST) (envelope-from mjacob@feral.com) Date: Thu, 7 Nov 2002 21:34:14 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Jeff Roberson Cc: Andrew Gallatin , alpha@FreeBSD.ORG, alc@FreeBSD.ORG, John Baldwin Subject: Re: alpha: top of tree kernel blooie In-Reply-To: <20021106204331.F17759-100000@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Didn't crash doing a -j4 buildworld. But now it's locked up so I can't log in. Oh well. And we were planning on releasing when?.... On Wed, 6 Nov 2002, Jeff Roberson wrote: > On Wed, 6 Nov 2002, Andrew Gallatin wrote: > > > > > alpha/include/atomic.h rev 1.17 (try 1.16) > > alpha/alpha/atomic.s rev 1.6 (try 1.5) > > > > John thinks the expensive extra memory barriers in the atomic ops may > > have masked existing pmap problems. I've been running the patch for > > 2 months on a UP config and not seen any problems. I did once see a > > strange Heisenbug when using an SMP kernel on a UP machine, but, > > again, not sure if that's related to the atomic changes. Once I put > > in a ktr to trace the trap, the bug disappeared. > > > > Since you're using the K0SEG, I"m not sure how pmap comes into play. > > > > Drew > > > > > Well, I have actually seen this panic one other time on a SMP system. > Although this was a two way and not four. I have single proc alphas that > get almost as much usage and have never had this panic. Unfortunately, I > too have only seen this once. This was way before the K0SEG changes as > well. I bring up pmap because it was already somewhat suspect and we're > panicing through some vm weirdness. > > There is definitely some bug here that is alpha specific. Hopefully when > I get my 4way system up again I can reproduce it and get some more insight > into the problem. > > Cheers, > Jeff > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message