Date: Thu, 22 Aug 2002 17:42:57 -0700
From: Will Andrews <will@csociety.org>
To: Peter Wemm <peter@wemm.org>
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>
In-Reply-To: <20020823002846.BBF082A7D6@canning.wemm.org>
References: <20020822233846.GJ90596@procyon.firepipe.net> <20020823002846.BBF082A7D6@canning.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020823004257.GM90596>