From owner-freebsd-current@FreeBSD.ORG Fri May 9 22:59:32 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 652AC37B401 for ; Fri, 9 May 2003 22:59:32 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6FFD43FCB for ; Fri, 9 May 2003 22:59:31 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0008.cvx22-bradley.dialup.earthlink.net ([209.179.198.8] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19ENOM-0004Qo-00; Fri, 09 May 2003 22:59:31 -0700 Message-ID: <3EBC94F9.AD988862@mindspring.com> Date: Fri, 09 May 2003 22:58:17 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: walt References: <3EBC6C6A.1040602@myrealbox.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40c9c9e221565070fe9d7fda875586443a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c 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: Sat, 10 May 2003 05:59:32 -0000 walt wrote: > Terry Lambert wrote: > <...> > > 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... > > Do I recall from some months ago that this bug would not > affect machines with less than a gig of RAM? The amount of memory at which you see it depends on the processor features. Now that autotuning is in, there's a stair-step for how much the system uses for each resource pool, based on how much RAM is in the system. It's quite unpredictable where it will show up in -current, because of this (and the new memory allocator). Basically, the problem will show wherever the memory size vs. memory utilization tickles it (that's why upping maxfiles was enough to scare it off, before the tuning/allocator changes went in). -- Terry