Date: Thu, 22 Aug 2002 21:46:59 -0700
From: David Schultz <dschultz@uclink.Berkeley.EDU>
To: Terry Lambert <tlambert2@mindspring.com>
Cc: Will Andrews <will@csociety.org>, Peter Wemm <peter@wemm.org>, 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: <20020823044659.GA2687@HAL9000.homeunix.com>
In-Reply-To: <3D6587ED.F602F06@mindspring.com>
References: <20020822233846.GJ90596@procyon.firepipe.net> <20020823002846.BBF082A7D6@canning.wemm.org> <20020823004257.GM90596@procyon.firepipe.net> <3D6587ED.F602F06@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Terry Lambert <tlambert2@mindspring.com>: > 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. 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?20020823044659.GA2687>