From owner-freebsd-arch@FreeBSD.ORG Tue Mar 22 22:56:43 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DA21106564A; Tue, 22 Mar 2011 22:56:43 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) by mx1.freebsd.org (Postfix) with ESMTP id 8F1D08FC0A; Tue, 22 Mar 2011 22:56:42 +0000 (UTC) Received: from labgw2.phaedrus.sandvine.com (192.168.222.22) by WTL-EXCH-1.sandvine.com (192.168.196.31) with Microsoft SMTP Server id 14.0.694.0; Tue, 22 Mar 2011 18:45:54 -0400 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 10332) id 5495B33C02; Tue, 22 Mar 2011 18:45:54 -0400 (EDT) Date: Tue, 22 Mar 2011 18:45:54 -0400 From: Ed Maste To: John Baldwin Message-ID: <20110322224554.GA67925@sandvine.com> References: <201103221551.14289.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <201103221551.14289.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: "Bjoern A. Zeeb" , freebsd-arch@freebsd.org Subject: Re: kernel memory checks on boot vs. boot time X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2011 22:56:43 -0000 On Tue, Mar 22, 2011 at 03:51:13PM -0400, John Baldwin wrote: > Do other platforms bother with these sorts of memory tests? If not I'd vote > to just drop it. I think this mattered more when you didn't have things like > SMAP (so you had to guess at where memory ended sometimes). Also, modern > server class x86 machines generally support ECC RAM which will trigger a > machine check if there is a problem. I doubt that the early checks are > catching anything even for the non-ECC case. In the common case at work we want this off to reduce boot time. The desire for a tunable though that can add extended memory tests is to be able to use the FreeBSD startup code as a replacement for memtest86+, for a couple of reasons: - FreeBSD's serial console output is more easily parsed by automated tools - Memtest86+ appears to be limited to 64GB of RAM at the moment - Memtest86+ lacks support for the Tylersburg architecture last I looked -Ed