From owner-freebsd-current@FreeBSD.ORG  Mon Jun 23 15:49:43 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D423373B;
 Mon, 23 Jun 2014 15:49:43 +0000 (UTC)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A725A2599;
 Mon, 23 Jun 2014 15:49:43 +0000 (UTC)
Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52]
 helo=damnhippie.dyndns.org)
 by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
 (Exim 4.72) (envelope-from <ian@FreeBSD.org>)
 id 1Wz69t-000NrD-5V; Mon, 23 Jun 2014 15:27:49 +0000
Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240])
 by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s5NFRk4P001349;
 Mon, 23 Jun 2014 09:27:46 -0600 (MDT) (envelope-from ian@FreeBSD.org)
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 24.8.230.52
X-Report-Abuse-To: abuse@dyndns.com (see
 http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse
 reporting information)
X-MHO-User: U2FsdGVkX1+vewjNobcGTTpADhOsPh8I
Subject: Re: [CURRENT]: weird memory/linker problem?
From: Ian Lepore <ian@FreeBSD.org>
To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
In-Reply-To: <20140623163115.03bdd675.ohartman@zedat.fu-berlin.de>
References: <20140622165639.17a1ba1e.ohartman@zedat.fu-berlin.de>
 <CAJ-Vmok0Oh6XGe62acXE-82pTmEaouibd1GqDT0pCo8P6x6Hog@mail.gmail.com>
 <20140623163115.03bdd675.ohartman@zedat.fu-berlin.de>
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 23 Jun 2014 09:27:46 -0600
Message-ID: <1403537266.20883.296.camel@revolution.hippie.lan>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Cc: Adrian Chadd <adrian@FreeBSD.org>,
 FreeBSD CURRENT <freebsd-current@FreeBSD.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 15:49:43 -0000

On Mon, 2014-06-23 at 16:31 +0200, O. Hartmann wrote:
> 
> I'm out of ideas. Is there a way to stress test the CPU and memory
> system to check
> whether RAM, the CPU itself and, as an additional possibility, the
> disk i/o controller
> (Intel ICH10)?
> 
> Thanks for your patience,

A really good tool for stress-testing a system is ports/math/mprime.  It
will find memory and cpu errors that memtest86 and other tools
completely overlook.  Run one copy per cpu, something like this:

for i in $(jot $(sysctl -n hw.ncpu) 0) ; do
    sleep $((i * 2)) && mprime -t -a$i >/tmp/mprime$i.log &
done

Many overclockers use this to ensure the system is stable with the OC
settings.  If your system can run a copy of mprime per cpu continuously
for 24 hours the hardware is fine.

-- Ian