From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 18 00:19:12 2004 Return-Path: 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 2F3B016A4CE for ; Sun, 18 Jan 2004 00:19:12 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-67-119-53-122.dsl.lsan03.pacbell.net [67.119.53.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1477F43D1F for ; Sun, 18 Jan 2004 00:19:11 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BF5EA66C78; Sun, 18 Jan 2004 00:19:10 -0800 (PST) Date: Sun, 18 Jan 2004 00:19:10 -0800 From: Kris Kennaway To: Danny Braniss Message-ID: <20040118081910.GA84236@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQksG6bCIzRHxTLp" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Sun, 18 Jan 2004 05:27:28 -0800 cc: hackers@freebsd.org Subject: Re: network constipation? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2004 08:19:12 -0000 --LQksG6bCIzRHxTLp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 18, 2004 at 09:46:33AM +0200, Danny Braniss wrote: > hi, > i have 2 amd64s (one dual opteron, one athlon64), which behave=20 > identicaly. Im trying to compile /usr/ports/x11-fonts, ports & obj are > nfs mounted (on the the same server).=20 > so things go nicely, but after a while gzip hangs, and later > i get 'nfs server dev:/r+d: not responding', this happens on both > hosts, (i just tried it on both to see if the error was in the driver, > since they have different cards). > it's almost obvious that i've hit on a deadlock, where can i look > for some hint? First step when you encounter strange kernel problems is to turn on the debugging options: INVARIANTS, INVARIANTS_SUPPORT, WITNESS etc. Kris --LQksG6bCIzRHxTLp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFACkF+Wry0BWjoQKURAg/OAKCQhgn/M8cxRQ0cUCyy0/BQGCydjgCgtJmS LRZPSuvcYiTWWuJHFuoUu3o= =YGtc -----END PGP SIGNATURE----- --LQksG6bCIzRHxTLp--