Date: Thu, 22 Aug 2002 22:31:30 -0700
From: Terry Lambert <tlambert2@mindspring.com>
To: David Schultz <dschultz@uclink.Berkeley.EDU>
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: <3D65C8B2.EF3EB14@mindspring.com>
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>
next in thread | previous in thread | raw e-mail | index | archive | help
David Schultz wrote: > 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. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D65C8B2.EF3EB14>