From owner-freebsd-stable@FreeBSD.ORG Tue Dec 7 03:31:26 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DC1C16A4CE; Tue, 7 Dec 2004 03:31:26 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68D4343D39; Tue, 7 Dec 2004 03:31:26 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D13AB5124E; Mon, 6 Dec 2004 19:37:36 -0800 (PST) Date: Mon, 6 Dec 2004 19:37:36 -0800 From: Kris Kennaway To: Jeff Behl Message-ID: <20041207033736.GA32688@xor.obsecurity.org> References: <41B4CCFA.6070202@fastclick.com> <41B4EFB2.3020704@freebsd.org> <41B52324.9050001@fastclick.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline In-Reply-To: <41B52324.9050001@fastclick.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org cc: Paul Saab cc: Arjan Van Leeuwen Subject: Re: reproducible kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 03:31:26 -0000 --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 06, 2004 at 07:27:32PM -0800, Jeff Behl wrote: > You're helpful reply doesn't seem to include any information on where to= =20 > upload a crash dump, if that's what is being asked. I haven't dealt=20 > with them before. Perhaps you'd be so kind as to direct? >=20 > A reply that helps work around a problem is always welcome, especially=20 > when it keeps a remotely located host from continuously rebooting. Earlier in this thread I already pointed you to the developers' handbook that explains the necessary details. Did you find something unclear there? Kris --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtSWAWry0BWjoQKURAgsBAJ9osNDkmzLqV2w37iBS+osaL6LmZgCdFxLj x2mmaCT9rB94Ci5o+54vrF4= =J1CF -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+--