From owner-freebsd-questions@FreeBSD.ORG Sun Apr 26 21:05:52 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C5D3FD5 for ; Sun, 26 Apr 2015 21:05:52 +0000 (UTC) Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 14E5A121B for ; Sun, 26 Apr 2015 21:05:52 +0000 (UTC) Received: by wgen6 with SMTP id n6so97436348wge.3 for ; Sun, 26 Apr 2015 14:05:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=1z954vAp+XYQ/pcKHtn3TPQeusSAY/ispgA+UL0x8K8=; b=mBIoE7gVZVTGY4WwRZEFzhEM7NsFjMQCD48upmw+jS1R/pZGMBsFpvW/wfJqUEC3GN rPTusMjZMj64umpFMEGYkLBS5E8sWA+82X5RqD5kqzv/f5vTDQ/VtiFHUgYnQx5RpDaa w8Qk05xaH8BQwUkq2Wa5I1kX8APXlSjkF14MVtYquK5MSKjBzzpJHep871bcWypGDLij csqk+DCXnesB/hVKQZgPcGrjlGNKhlrmN4v5ZUwYskmRPDQ0kVsAGPt1hAQOqHjt0s1q eEvKkeEI8bbZlSRVR7UbOZZZH5Vr7YyIOZPNPZLX54kTP+3bvPU/djX4rjmAtabHAVhf SY/w== MIME-Version: 1.0 X-Received: by 10.180.74.208 with SMTP id w16mr15023789wiv.31.1430082350597; Sun, 26 Apr 2015 14:05:50 -0700 (PDT) Received: by 10.180.44.172 with HTTP; Sun, 26 Apr 2015 14:05:50 -0700 (PDT) In-Reply-To: <5480.69.209.235.143.1430078703.squirrel@cosmo.uchicago.edu> References: <5480.69.209.235.143.1430078703.squirrel@cosmo.uchicago.edu> Date: Sun, 26 Apr 2015 23:05:50 +0200 Message-ID: Subject: Re: Debugging bad memory problems From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= To: galtsev@kicp.uchicago.edu Cc: User Questions Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Apr 2015 21:05:52 -0000 On Sun, Apr 26, 2015 at 10:05 PM, Valeri Galtsev wrote: > > On Sun, April 26, 2015 12:11 pm, Fernando Apestegu=C3=ADa wrote: >> Hi, >> >> I suspect my old and beloved AMD64 laptop is suffering from bad memory >> problems: I get random crashes of well tested programs like sh, which, >> etc even when I executed some of them from /rescue. > > If RAM is a suspect the first thing I would do is re-seat memory modules. > Open the box. (Observe static precautions!) Remove memory modules. Instal= l > them again. > > Do memtest86 (by booting into memtest86, you can have that in your boot > options, or you can boot off external media as others suggested). > > If you still have problems: try to run with one memory module instead of > two. At some point when they went to higher RAM speeds memory bus > amplifier became more fragile (some chips, some manufacturers, as not it > is part of CPU, this may be true only about some of the CPU models). You > sometimes can slightly fry it if you merely leave laptop running on > battery, letting battery run down and laptop powering off due to that. > With some of chips this may lead to slightly frying it - memory controlle= r > portion of it, address bus amplifier in particular. Bus amplifier becomes > slightly lower frequency, which results in poorer handling capacitive loa= d > (which is larger if you have more RAM), and it is marginally OK, > occasionally having address errors. Going to one module may resolve this. > You will know if this is likely the case if memtest86 is successful with > each of single RAM modules, but fails (in random places, often not > reproducible) with both. > > Good luck! I booted from a memtest CD-ROM. It passed a couple of tests fine and then it rebooted while doing a "bit fade" test at around 93%. Removing the modules is tricky since this laptop has screws all around in dark corners (even removing the battery needs a screw driver). I will try to limit physical memory with hw.physmem and see if it makes any difference. Thanks! > > Valeri > >> >> I wanted to check the memory banks. I installed >> /usr/ports/sysutils/memtest86+ and try to run it at boot. According to >> the documentation, from the boot loader prompt: >> >> unload >> load /boot/opt/memtest86+ >> boot >> >> But at the time of loading the file, the laptop reboots. >> >> I also tried /usr/ports/sysutils/memtest. But when I run it (as root), I >> get: >> >> $memtester 1G >> >> memtester version 4.3.0 (64-bit) >> Copyright (C) 2001-2012 Charles Cazabon. >> Licensed under the GNU General Public License version 2 (only). >> >> pagesize is 4096 >> pagesizemask is 0xfffffffffffff000 >> want 1024MB (1073741824 bytes) >> got 1024MB (1073741824 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073737728 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073733632 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073729536 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073725440 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073721344 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073717248 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073713152 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073709056 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073704960 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073700864 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073696768 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073692672 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073688576 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073684480 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073680384 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073676288 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073672192 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073668096 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073664000 bytes), trying mlock ...too many pages, >> reducing... >> got 1023MB (1073659904 bytes), trying mlock ...too many pages, >> reducing... >> >> ... >> ... >> >> got 0MB (73728 bytes), trying mlock ...too many pages, reducing... >> got 0MB (69632 bytes), trying mlock ...too many pages, reducing... >> got 0MB (65536 bytes), trying mlock ...locked. >> >> Any help with these two problems or any alternative programs? >> >> Thanks in advance. >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > > > ++++++++++++++++++++++++++++++++++++++++ > Valeri Galtsev > Sr System Administrator > Department of Astronomy and Astrophysics > Kavli Institute for Cosmological Physics > University of Chicago > Phone: 773-702-4247 > ++++++++++++++++++++++++++++++++++++++++