From owner-freebsd-questions@FreeBSD.ORG Sat Mar 22 06:26:07 2014 Return-Path: Delivered-To: questions@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 E68EAF32 for ; Sat, 22 Mar 2014 06:26:07 +0000 (UTC) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id BC0938F0 for ; Sat, 22 Mar 2014 06:26:07 +0000 (UTC) Received: from [10.0.1.3] (static-71-177-216-148.lsanca.fios.verizon.net [71.177.216.148]) (authenticated bits=0) by zoom.lafn.org (8.14.7/8.14.2) with ESMTP id s2M6PxMU016033 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Mar 2014 23:26:00 -0700 (PDT) (envelope-from bc979@lafn.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Frequent Page Faults From: Doug Hardie In-Reply-To: Date: Fri, 21 Mar 2014 23:25:59 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <808F4ABB-27FA-48D6-B526-A19C4A361667@lafn.org> References: To: Olivier Nicole X-Mailer: Apple Mail (2.1510) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean Cc: "questions@freebsd.org FreeBSD" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Mar 2014 06:26:08 -0000 On 15 March 2014, at 20:35, Olivier Nicole = wrote: > Hi, >=20 > Wild guess, but if you could have someone checking the hardware for > you: dirty memory connector, dust clogged CPU fan... As you said, the > system has been running for over 4 years, this could very much be > hardware. >=20 > Olivier Well, it took a long time to get to the bottom of this. The CPU fan was = fine, no dust. The machine is cleaned every 6 months so I didn't expect = that to be the cause. Adding a new NIC changed the character of the = crashes and the traces were completely different after that. We = replaced the memory and power supply. Neither had any effect on the = crashes or messages. Updated the OS to 9.2 on brand new disks. = Likewise no change in the crashes. Finally gave up and replaced the = entire computer. Problem solved. It must be the motherboard or CPU. = We are taking the unit back to the manufacturer (its local) and they are = going to see what is causing the problem. Unfortunately our backup = machine doesn't have as much horsepower so it tends to run a bit slower. = Its noticeable by our users. The OS upgrade cause a few issues. A = couple of packages have new configuration parameters that are not = documented anywhere I could find. It took awhile of reading through a = lot of code to figure out what to do to get them working again. There = is real value in keeping UPDATING and README files current, complete, = and accurate. Yes I know its a real pain to do that, but it really pays = off for those who use them.