From owner-freebsd-hardware@FreeBSD.ORG Mon Jul 16 23:45:19 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 73238106566C for ; Mon, 16 Jul 2012 23:45:19 +0000 (UTC) (envelope-from ayoung@mosaicarchive.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 3695D8FC08 for ; Mon, 16 Jul 2012 23:45:19 +0000 (UTC) Received: by obbun3 with SMTP id un3so12767559obb.13 for ; Mon, 16 Jul 2012 16:45:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=qovnb/06Xo3Qckuo16lkv3YcgOOwPxLNBNikqUlIwhY=; b=KRVX+UoZPCnpiMj6IukeMSjwYqcsR4m9CoqhWy/0Fop5W+OcoFY1YiJUokTt/d/7SV HK4rI9qO0nYW2SkmdfY7U+FiqQRP7oM/UgochYhPU1Gr5s5Jxa+QTTp0R3ooiy4XYCZx rYm37e35/vsHIzp/MP1FTipndh2oorvQa9Fskc5qYGo6qwUPb8ugGrcv+rCM6B3+Xsov Xka3H//zpP5j5E/eCyQPjSpU2A7mSF5JCOzjho6zhJgA1QhcuwFs3DS+ieNgkos+VHw/ eH4IKKe4kZ0TzGRpZyTP4NZLgcJn6XWa5uCE5A5IPpvi3vVv5NBdzlFTVj1Pbm0YUvZ0 KcTA== MIME-Version: 1.0 Received: by 10.182.167.101 with SMTP id zn5mr318768obb.60.1342482318461; Mon, 16 Jul 2012 16:45:18 -0700 (PDT) Received: by 10.76.79.165 with HTTP; Mon, 16 Jul 2012 16:45:18 -0700 (PDT) X-Originating-IP: [96.237.242.243] Date: Mon, 16 Jul 2012 19:45:18 -0400 Message-ID: From: Andy Young To: freebsd-hardware@freebsd.org X-Gm-Message-State: ALoCoQng2E/cfo5UbfnmdRir4edwxJPi5p2Xgl7RTLfngRv/B01dHveA3n9ZLwNvLrzRBzLRSTc+ Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Server memory problems X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 23:45:19 -0000 I am having trouble with one of our servers and I'm not sure what to try next. It has a Supermicro H8DGi-F motherboard with two 16-core AMD processors and two memory banks, one for each processor. When I originally built it, I only had one processor and 40 GB of ram. Everything worked awesome. I recently upgraded it, adding another processor and another 40 GB of ram. It was incredibly unstable and constantly rebooted within minute or two of uptime, sometimes it wouldn't even boot all the way before crashing and rebooting again. Seemed like a memory issue so I scaled it back to two processors and 32 GB (4x8GB) of ram. Worked well so I added the remaining 8 GB sticks I had, bringing it up to 64 GB. Still worked great. The sticks I had left were a mix and match variety of 8GB and 4GB sticks. Thinking maybe there was some problem with mixing them, I ordered more 8GB memory just like the ones in the box. While waiting for the new memory, the machine performed great with no issues. New memory arrived and I added two more 8GB sticks. Immediately the constant crashing returned. It seems really unlikely that I got bad memory in two separate orders. Does anyone have any other ideas? Again, its perfectly stable with two processors and 64 GB of memory but goes nuts when I more. I really appreciate the help!! Motherboard: Supermicro H8DGi-F CPU: 2 x AMD 6274 (2.2 Ghz 16-core) Memory: Kingston 8GB DDR3 1333 -- Andrew Young Mosaic Storage Systems, Inc http://www.mosaicarchive.com/ Follow us on: Twitter , Facebook , Google Plus , Pinterest