From owner-freebsd-stable@FreeBSD.ORG Fri Nov 24 03:01:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B663416A415 for ; Fri, 24 Nov 2006 03:01:16 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD65A43D58 for ; Fri, 24 Nov 2006 03:00:37 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 2ACD01A3C1C; Thu, 23 Nov 2006 19:01:16 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 13E5B512FA; Thu, 23 Nov 2006 22:01:01 -0500 (EST) Date: Thu, 23 Nov 2006 22:01:00 -0500 From: Kris Kennaway To: Ganbold Message-ID: <20061124030100.GA92039@xor.obsecurity.org> References: <456652AF.7070808@micom.mng.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <456652AF.7070808@micom.mng.net> User-Agent: Mutt/1.4.2.2i Cc: FreeBSD Stable Mailing List Subject: Re: application hangs in STABLE from time to time 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: Fri, 24 Nov 2006 03:01:16 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Nov 24, 2006 at 10:02:23AM +0800, Ganbold wrote: > So do I have interrupt storms here and it is something related to bge? No, your interrupts look fine. > What else should I check when application hangs again? The most important thing to know is what is the application doing when it hangs. Unfortunately none of the information you provided shows this. Next time use the -o wchan argument to ps to find out what state the process is blocked in. You can also use kgdb to find out where it is waiting in the kernel: kgdb /dev/mem /boot/kernel/kernel.symbols info threads thread bt Kris --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFZmBsWry0BWjoQKURAloOAKDqpWIsF3ac5oFrKGmw2B8tEcYViwCgttf1 jDnWwYobWv7R1X9qmdfXHv0= =1xsq -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--