From owner-freebsd-stable@FreeBSD.ORG Sat Mar 4 23:37:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7271816A422 for ; Sat, 4 Mar 2006 23:37:20 +0000 (GMT) (envelope-from freebsd.macgregor@blueyonder.co.uk) Received: from the-macgregors.org (82-46-96-19.cable.ubr06.stav.blueyonder.co.uk [82.46.96.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9B6743D49 for ; Sat, 4 Mar 2006 23:37:19 +0000 (GMT) (envelope-from freebsd.macgregor@blueyonder.co.uk) X-Urban-Legend: Mail headers contain urban legends Received: from fire (rob@fire.macgregor [192.168.32.100]) (user=freebsd mech=LOGIN bits=0) by the-macgregors.org (8.13.5/8.13.5) with ESMTP id k24NbGdb017253 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 4 Mar 2006 23:37:16 GMT From: "Rob MacGregor" To: Date: Sat, 4 Mar 2006 23:37:16 -0000 Message-ID: <000001c63fe4$923c3330$0100a8c0@macgregor> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 thread-index: AcY/4jywqOA+ZbwORNWpmAuQ1g+zLgAAS9kw In-Reply-To: <440A1F61.8070501@wcubed.net> X-Virus-Scanned: by amavisd-new Subject: RE: 5.4-STABLE hangs every few days X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2006 23:37:20 -0000 When we last met our heroes on 04 March 2006 23:15, Brad Waite <> was heard to say: > How do I determine if it's a hardware issue, namely RAM or CPU? Can > breaking into the debugger tell me that, or do I have to start swapping > pieces out? memtest86 can help diagnose RAM problems. I'm not aware of any free programs for testing the CPU etc though (I've only used PC-Check before - it's good, but it isn't cheap). Worth trying to see if there's anything that the freezes have in common - busy system, particular program, time of day, etc. -- Rob | Oh my God! They killed init! You bastards!