From owner-freebsd-questions Tue Feb 6 0: 4:22 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id B0ACB37B491 for ; Tue, 6 Feb 2001 00:04:04 -0800 (PST) Received: (qmail 47082 invoked by uid 100); 6 Feb 2001 08:04:04 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14975.45044.295769.589613@guru.mired.org> Date: Tue, 6 Feb 2001 02:04:04 -0600 (CST) To: Jim Durham Cc: questions@freebsd.org Subject: Re: 4.2 Problem possibly I/O related In-Reply-To: <51429498@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Durham types: > Due to the nature of this problem, I can't do any tracing. > > I have noticed several times since upgrading to 4.2-RELEASE > that the system will just "freeze". > > When this happens, you can still ping the IP of the machine > on the local network, but you cannot get a telnet or ftp connection. [...] > This could, of course, be a hardware problem that is creeping up, This seems most likely. Since the kernel is answering pings, it's still running. Getting a stack trace of what's going on when this happens would be very useful. Read the handbook section about On-line kernel debugging using DDB for information on how to do that. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message