From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 2 22:27:41 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1753C16A41F for ; Sun, 2 Oct 2005 22:27:41 +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 C829943D45 for ; Sun, 2 Oct 2005 22:27:40 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [70.30.70.180]) by elvis.mu.org (Postfix) with ESMTP id A9FEE1A3C1F; Sun, 2 Oct 2005 15:27:40 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 91CEB51288; Sun, 2 Oct 2005 18:27:39 -0400 (EDT) Date: Sun, 2 Oct 2005 18:27:39 -0400 From: Kris Kennaway To: "David S. Madole" Message-ID: <20051002222739.GA87041@xor.obsecurity.org> References: <049901c5c78b$d94163d0$c3e7a8c0@david> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <049901c5c78b$d94163d0$c3e7a8c0@david> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: How to troubleshoot solid freeze-up? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2005 22:27:41 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 02, 2005 at 03:59:50PM -0400, David S. Madole wrote: > I'm looking for some tips on how to troubleshoot a possible driver=20 > problem. Here is the scenario: >=20 > 1. Using a Pentium II 333Mhz mobile processor, 82443BX motherboard, and= =20 > Intel i82559 NIC (fxp driver). >=20 > 2. A combination of heavy disk I/O, high CPU utilization, and high=20 > network traffic causes a solid machine freeze-up sometime between 10=20 > minutes and 3 hours of running. >=20 > 3. Replacing the NIC with a DP83815-based card (sis driver) seems to=20 > solve the problem. I have run the problem load for up to 8 hours without= =20 > issue on this NIC. >=20 > 4. The problem is reproducable on multiple identical machines with=20 > multiple identical NICs. Also reproducable on an i82558 NIC integrated on= =20 > the motherboard. >=20 > How can I go about collecting useful information to troubleshoot this=20 > when the machine locks solid? How can a get a core under this scenario? >=20 > Switching to another NIC permanently is not a great solution because this= =20 > is a semi-embedded application and I need to use the NIC on the=20 > motherboard. You can't break to DDB in the usual way, right (Ctrl+alt+esc)? Try turning on KDB_STOP_NMI instead. Also try turning on WITNESS in case you're seeing a lock order reversal. Actually you forgot to mention what version of FreeBSD you're running, those suggestions only apply to 5.x and above. Kris --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDQF7bWry0BWjoQKURAhJCAJ46tcntdtd30WvUAN5wfDmSi4KFNQCdEhgU 3zgbUOwcBhdgqmiWZ/faxyE= =gk7Y -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC--