From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 08:23:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6748716A41F for ; Sun, 30 Oct 2005 08:23:14 +0000 (GMT) (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 25C0A43D46 for ; Sun, 30 Oct 2005 08:23:14 +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 034081A3C25; Sun, 30 Oct 2005 01:23:14 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8474B51BF0; Sun, 30 Oct 2005 03:23:12 -0500 (EST) Date: Sun, 30 Oct 2005 03:23:11 -0500 From: Kris Kennaway To: "Chad Leigh -- Shire.Net LLC" Message-ID: <20051030082309.GA83399@xor.obsecurity.org> References: <200510191623.j9JGNSfr007356@magus.nostrum.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Problem remains with FreeBSD 6.0-RC1 as seen in RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 08:23:14 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 30, 2005 at 01:39:14AM -0600, Chad Leigh -- Shire.Net LLC wrote: > I will try and contribute but this is a major production machine and =20 > cannot be screwed around with until such time as an upgrade or =20 > planned reboot happens or the problem happens and we have to reboot =20 > anyway. You need to configure DDB, and when the hang occurs, break to DDB on the console and trigger a dump (see the chapter on kernel debugging in the developers' handbook). A developer may then be able to begin to help you. Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZILsWry0BWjoQKURArOWAJ9GNS3WoZVHSH0/qiri0EKwMzdI+gCgzjaG oQuD6RMDomykXBleIKatgow= =vJDN -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--