From owner-freebsd-current Thu Aug 22 17:43:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF1AD37B400 for ; Thu, 22 Aug 2002 17:43:50 -0700 (PDT) Received: from procyon.firepipe.net (procyon.firepipe.net [198.78.66.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89E4043E65 for ; Thu, 22 Aug 2002 17:43:50 -0700 (PDT) (envelope-from will@csociety.org) Received: by procyon.firepipe.net (Postfix, from userid 1000) id 9C37421429; Thu, 22 Aug 2002 17:42:57 -0700 (PDT) Date: Thu, 22 Aug 2002 17:42:57 -0700 From: Will Andrews To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: Memory corruption in -CURRENT [was Re: Plea to committers to only commit to HEAD if you run -current {from developers@FreeBSD.org}] Message-ID: <20020823004257.GM90596@procyon.firepipe.net> Mail-Followup-To: Peter Wemm , current@FreeBSD.ORG References: <20020822233846.GJ90596@procyon.firepipe.net> <20020823002846.BBF082A7D6@canning.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020823002846.BBF082A7D6@canning.wemm.org> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Aug 22, 2002 at 05:28:46PM -0700, Peter Wemm wrote: For the benefit of the mailing list: > Is this on a uniprocessor system? Yes, with a UP kernel. > Note that the old SMP code never had PG_G active for SMP before the last > round of pmap changes. DISABLE_PG_G almost goes back to the old way for > SMP systems. DISABLE_PSE should be irrelevant since we've been using it all > along. > > I've become aware of some nasty races in the pmap code for SMP boxes about > a week ago while working on PAE stuff. DISABLE_PG_G *might* minimize the > effect of them but they are still there. Well, I'm rebuilding without DISABLE_PSE to see whether it had any effect on the outcome. Regardless, hopefully the information I can provide will help squash this annoying bug. Regards, -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message