From owner-freebsd-current@FreeBSD.ORG Mon Jun 23 16:30:20 2014 Return-Path: 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 E83BAB4B; Mon, 23 Jun 2014 16:30:20 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 A272229AC; Mon, 23 Jun 2014 16:30:20 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) with esmtp (envelope-from ) id <1Wz78H-002Erc-4Z>; Mon, 23 Jun 2014 18:30:13 +0200 Received: from g225054098.adsl.alicedsl.de ([92.225.54.98] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from ) id <1Wz78H-002Y7i-16>; Mon, 23 Jun 2014 18:30:13 +0200 Date: Mon, 23 Jun 2014 18:30:07 +0200 From: "O. Hartmann" To: Ian Lepore Subject: Re: [CURRENT]: weird memory/linker problem? Message-ID: <20140623183007.699d7733.ohartman@zedat.fu-berlin.de> In-Reply-To: <1403537266.20883.296.camel@revolution.hippie.lan> References: <20140622165639.17a1ba1e.ohartman@zedat.fu-berlin.de> <20140623163115.03bdd675.ohartman@zedat.fu-berlin.de> <1403537266.20883.296.camel@revolution.hippie.lan> Organization: FU Berlin X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_//OwiSGw7PVC0sD5g8HlinfF"; protocol="application/pgp-signature" X-Originating-IP: 92.225.54.98 X-ZEDAT-Hint: A Cc: Adrian Chadd , FreeBSD CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 23 Jun 2014 16:30:21 -0000 --Sig_//OwiSGw7PVC0sD5g8HlinfF Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Mon, 23 Jun 2014 09:27:46 -0600 Ian Lepore schrieb: > On Mon, 2014-06-23 at 16:31 +0200, O. Hartmann wrote: > >=20 > > 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)? > >=20 > > Thanks for your patience, >=20 > 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: >=20 > for i in $(jot $(sysctl -n hw.ncpu) 0) ; do > sleep $((i * 2)) && mprime -t -a$i >/tmp/mprime$i.log & > done >=20 > 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. >=20 > -- Ian A great idea, but regretably I receive this error while trying to install t= hat neat port: mprime-0.0.24.14 is only for i386, while you are running amd64. *** Error code 1 Is there a 64bit counterpart? Oliver --Sig_//OwiSGw7PVC0sD5g8HlinfF Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJTqFYUAAoJEOgBcD7A/5N8Ts4H/j2aN5MjPcvvD+KG+jidva1F I69W6A2hCVmZKkNRZS/tEbMcw4MFXB9ng9pF98Kb4VWaYl5cpx2CCZa4eEzywXNu xhxoZsieT3/ZkDU36dnn+5ZYFa+rZp80jdU14+TJZCKIVfIB6bHvImmZH9rGVd2r el/UbbPX5rol9qe5I+wCAlEF0FPGPexmRc8tqYWigavVyqsy+STqgxVSZz9Rs4bH Vc3IsXAkLDcuh4p1BWsi7AdTx9PKgukhSgCKhUrPMpBeIPmuKEPTEFc4kKJrZPm3 6bL9zZlN1udl3Fb366NcGMM3jfIXS0za11RCQe7BhoF8sl8POBgZ0rMcWOSrdq8= =AmrR -----END PGP SIGNATURE----- --Sig_//OwiSGw7PVC0sD5g8HlinfF--