From owner-freebsd-current@FreeBSD.ORG Thu May 8 21:26:01 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 3880837B401 for ; Thu, 8 May 2003 21:26:01 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9990B43FB1 for ; Thu, 8 May 2003 21:26:00 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0039.cvx21-bradley.dialup.earthlink.net ([209.179.192.39] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19DzS8-0005NT-00; Thu, 08 May 2003 21:25:49 -0700 Message-ID: <3EBB2D5E.CC94FE24@mindspring.com> Date: Thu, 08 May 2003 21:23:58 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Heiko Schaefer References: <20030508142234.GA1359@laptop.6bone.nl> <3908.1052404777@critter.freebsd.dk> <20030508172630.C79286@daneel.foundation.hs> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a49b7d29e124e58521f7404fe1a7a34f77a2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: John Hay 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: Fri, 09 May 2003 04:26:01 -0000 Heiko Schaefer wrote: > > 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. The problem appears on any processor that supports 4M pages; that includes both Intel and AMD processors. Whether or not you personally see it is based on the memory usage patterns that are required to trigger it. > 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...) The were in the last developer preview. There were specific hacks for the P4, which would not have helped the AMD K6 (it may be that other processors also have the problem, too; I have only regressed it personally on P3's, P4's, and the AMD K6). They were removed after the autotuning changes by Matt Dillon and the memory allocator changes by Jeff Robertson went in. Both changes added preterbations to the memory usage patterns which, in my opinion, would add steep stair functions into where you would see the problem occur, and tend to mask it on a large variety of systems (but not all of them, so it's a land mine waiting for the unexpecting person with the right hardware and software combinations). -- Terry