From owner-freebsd-current Thu Aug 22 22:36: 8 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 B631337B400 for ; Thu, 22 Aug 2002 22:36:06 -0700 (PDT) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6304B43E6E for ; Thu, 22 Aug 2002 22:36:06 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0311.cvx21-bradley.dialup.earthlink.net ([209.179.193.56] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17i76l-0003Ay-00; Thu, 22 Aug 2002 22:35:45 -0700 Message-ID: <3D65C8B2.EF3EB14@mindspring.com> Date: Thu, 22 Aug 2002 22:31:30 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Schultz Cc: Will Andrews , Peter Wemm , 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}] References: <20020822233846.GJ90596@procyon.firepipe.net> <20020823002846.BBF082A7D6@canning.wemm.org> <20020823004257.GM90596@procyon.firepipe.net> <3D6587ED.F602F06@mindspring.com> <20020823044659.GA2687@HAL9000.homeunix.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 David Schultz wrote: > Thus spake Terry Lambert : > > DISABLE_PSE is a 1:6 probability; DISABLE_PG_G is a 1:100 (both > > estimates, but on that order), so mixing and matching them will > > not usually give any additional information. Martin got "lucky" > > with his machine... it seems to require both. > > > > The problem is a hardware bug in most Pentium on up processors, > > which gets worse in newer CPUs (P4, AMD) as they try to optimize > > certain things. It's like writing ANSI C without "volatile". > > It sounds like you're describing a cache coherence problem. Could > you elaborate or point me to a reference on this? Thanks. There is no reference on this. It is an undocumented hardware bug. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message