From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 17 17:12:30 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DBEAFE80 for ; Sat, 17 Jan 2015 17:12:29 +0000 (UTC) Received: from mail-yk0-f175.google.com (mail-yk0-f175.google.com [209.85.160.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7078FD3 for ; Sat, 17 Jan 2015 17:12:29 +0000 (UTC) Received: by mail-yk0-f175.google.com with SMTP id q9so636372ykb.6 for ; Sat, 17 Jan 2015 09:12:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GqEn/9kyk31XCSwURLDDyHV80nOM5mvIxzeFl4yYDnI=; b=AxKj49O4hSG9FWdYm3UAeyXomtg2OxBqV1rAq5E6GsEVRIyXuF/iuUfFgDpIcaSFmZ Y1A5svFrfVzzgmrYVaM7pvQajKbL8BWnlxzcgZwYKGw5BnUMNqOCQHIBcgDGmQqbwpT6 lmAELHhRO82gJpuBjAUnuaS2SQj9C2KaE9Uc6RRD33NW9abpLDIZHMiPH2lahFLa2mNq N8SKhT/ohzYP7vK5kUL6x9r+1HxNke/1+yu5sBH8yuN7sbfDCR+HSQ/j142SkXCnESRj GVQC3cY0oHB1PgjNCIfuK0+/dTNIg+d97FS2dEHeCcQkEHxChqHD3xzqGNphlqgCwzl7 hDAQ== X-Gm-Message-State: ALoCoQlK7K4B4md91b0Jz+JTI+Nr4AgvGEMReKrLuG83gYnmSW3tcq6DtufX48sbNKHKiXmjUVwr MIME-Version: 1.0 X-Received: by 10.236.21.234 with SMTP id r70mr13175708yhr.70.1421514742978; Sat, 17 Jan 2015 09:12:22 -0800 (PST) Received: by 10.170.46.213 with HTTP; Sat, 17 Jan 2015 09:12:22 -0800 (PST) In-Reply-To: <54BA9487.2040509@astart.com> References: <54B7656D.9000704@freebsd.org> <54B927F9.1010401@astart.com> <54BA9487.2040509@astart.com> Date: Sat, 17 Jan 2015 18:12:22 +0100 Message-ID: Subject: Re: [PATCH] Display progress during getmemsize() so the kernel doesn't look like it hanged From: Oliver Pinter To: papowell@astart.com Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , Ed Maste X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 17:12:30 -0000 On Sat, Jan 17, 2015 at 5:57 PM, Patrick Powell wrote: > On 01/16/15 13:56, Ed Maste wrote: >> >> On 16 January 2015 at 10:02, Patrick Powell wrote: >>> >>> On 01/14/15 22:59, Allan Jude wrote: >>>> >>>> Glad to see this, thanks for doing the work Ravi. Also, I agree with >>>> jhb@, >>>> we should disable the test by default in stable/10 (i think it is off by >>>> default only for VMs currently). >>> >>> >>> Please please do not disable memory tests by default. If you do, when >>> trying to boot from a CD/Memory Stick >>> image on a system with bad memory (which would be found by the tests) >>> then >>> it gets quite difficult to find this >>> problem. >> >> The boot time "memory test" is not particularly valuable, especially >> on contemporary amd64 hardware. While it won't have any false >> positives, there are a huge number of failure modes it will not catch. >> It also does not inform the user of "failure" -- it just removes that >> memory from the kernel's map. It's really a test of memory presence, >> not quality. > > > Right. But at least it gets you crawling... or staggering... so you can do > further diagnostics. > > Bad memory is a *((*&^( NASTY problem. > > Since we seem to have diverged a bit on topic, any recommendations for > stand-alone memory tests? I tried memtest86+ from ports and from pkg, but when I load it from loader via load /boot/opt/memtest86+ I got constant reboot. And fully reproducible with real and virtual machine too. > > -- > Patrick Powell Astart Technologies > papowell@astart.com 1530 Jamacha Rd, Suite X > Network and System San Diego, CA 92019 > Consulting 858-874-6543 FAX 858-751-2435 > Web: www.astart.com > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"