From owner-freebsd-questions Tue Feb 6 18:19:42 2001 Delivered-To: freebsd-questions@freebsd.org Received: from w2xo.pgh.pa.us (ipl-229-034.npt-sdsl.stargate.net [208.223.229.34]) by hub.freebsd.org (Postfix) with ESMTP id 586CE37B401 for ; Tue, 6 Feb 2001 18:19:24 -0800 (PST) Received: from shazam (shazam [192.168.5.3]) by w2xo.pgh.pa.us (8.9.3/8.9.3) with ESMTP id CAA11206; Wed, 7 Feb 2001 02:19:22 GMT (envelope-from durham@w2xo.pgh.pa.us) Date: Tue, 6 Feb 2001 21:19:55 -0500 (EST) From: Jim Durham X-Sender: durham@shazam.int To: Mike Meyer Cc: questions@freebsd.org Subject: Re: 4.2 Problem possibly I/O related In-Reply-To: <14975.45044.295769.589613@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 6 Feb 2001, Mike Meyer wrote: > 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. > I'll do that. If I can get a stack trace somehow, I'll post it. However, this is not something that happens a lot. It just happens once in a while, so I could go quite a while without any problem. Thanks, Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message