From owner-freebsd-current@FreeBSD.ORG Thu May 8 08:28:40 2003 Return-Path: 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 E71FB37B401 for ; Thu, 8 May 2003 08:28:40 -0700 (PDT) Received: from sauron.fto.de (p15106025.pureserver.info [217.160.140.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FB2E43FA3 for ; Thu, 8 May 2003 08:28:40 -0700 (PDT) (envelope-from hschaefer@fto.de) Received: from localhost (localhost.fto.de [127.0.0.1]) by sauron.fto.de (Postfix) with ESMTP id A1D5225C0F7; Thu, 8 May 2003 17:28:38 +0200 (CEST) Received: from sauron.fto.de ([127.0.0.1]) by localhost (sauron [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22976-02; Thu, 8 May 2003 17:28:37 +0200 (CEST) Received: from giskard.foundation.hs (p5091A984.dip.t-dialin.net [80.145.169.132]) by sauron.fto.de (Postfix) with ESMTP id E30E725C0C2; Thu, 8 May 2003 17:28:36 +0200 (CEST) Received: from daneel.foundation.hs (daneel.foundation.hs [192.168.20.2]) by giskard.foundation.hs (8.9.3/8.9.3) with ESMTP id RAA64492; Thu, 8 May 2003 17:28:35 +0200 (CEST) (envelope-from hschaefer@fto.de) Date: Thu, 8 May 2003 17:28:35 +0200 (CEST) From: Heiko Schaefer X-X-Sender: heiko@daneel.foundation.hs To: John Hay In-Reply-To: <20030508151810.GA72636@zibbi.icomtek.csir.co.za> Message-ID: <20030508172630.C79286@daneel.foundation.hs> References: <20030508142234.GA1359@laptop.6bone.nl> <3908.1052404777@critter.freebsd.dk> <20030508151810.GA72636@zibbi.icomtek.csir.co.za> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at fto.de cc: freebsd-current@freebsd.org Subject: Re: data corruption with current (maybe sis chipset related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2003 15:28:41 -0000 Hello, > > >They prevent the usage of 4M pages. It's a CPU bug that will cause data > > >corruption if enabled. > > > > > >Terry Lambert (at least) knows the details. > > > > I _really_ doubt that. > > > > Please treat all information from Terry as highly suspect, he has not > > been in touch with our source code for years. > > Be that as it may, it was still he that suggested those options and > claims that he knows more. On my machine at work, a 1.8GHz P4, those > options give me a useable stable machine and without it I get signal > 10 and 11's left,right and center. That machine is building a snap > every night and has an uptime of 37 days because that is when I last > updated it. the thread i found in -current archives suggested that these flags work around an amd-specific issue. now you say that a p4-based machine also needs them to run stable. i am wondering more and more: why are these options not in GENERIC ?!? ...if someone knows what he's doing he can always throw them out again. (just like back in the day, dma was not enabled by default...) Heiko -- Free Software. Why put up with inferior code and antisocial corporations? http://www.gnu.org/philosophy/why-free.html