From owner-freebsd-questions@FreeBSD.ORG Tue Feb 7 15:23:01 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4755616A420 for ; Tue, 7 Feb 2006 15:23:01 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADDB143D49 for ; Tue, 7 Feb 2006 15:23:00 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 20292 invoked from network); 7 Feb 2006 15:22:56 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 7 Feb 2006 15:22:56 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 405B328439; Tue, 7 Feb 2006 10:22:56 -0500 (EST) Sender: lowell@be-well.ilk.org To: ashas@takas.lt References: <43E76692.503@takas.lt> From: Lowell Gilbert Date: 07 Feb 2006 10:22:56 -0500 In-Reply-To: <43E76692.503@takas.lt> Message-ID: <44slqv8a7j.fsf@be-well.ilk.org> Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: system freezes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 15:23:01 -0000 ashas@takas.lt writes: > I'm using freebsd 6.0. > > After some time my system (router+nfs+ftp) freezes. After 10days I > noticed that I cant ping my system. > The monitor was kept shutdown so I got no message to screen and > pushing any buttons didnt help out to wake up monitor. > After reboot I haven't fount anything strange in my system or logs. > > How to try to find system freeze problem, because it happens at least > twice a month. Unfortunately, these kinds of problems are hard to diagnose, because they are usually (not always, but most of the time) caused by hardware problems. So you can check the usual culprits for hardware failure, but obviously if it's working okay at the moment, it can be extremely difficult to figure out where the blame lies. If you can figure out whether there are any patterns to when the system freezes, and even what it was doing at the time, you will have the most important clues for starting with. Good luck.