From owner-freebsd-stable@FreeBSD.ORG Wed Oct 18 22:42:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 CF03916A417; Wed, 18 Oct 2006 22:42:48 +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 EF7AF43D7F; Wed, 18 Oct 2006 22:42:34 +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 296D11A3C19; Wed, 18 Oct 2006 15:42:34 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8C4ED51872; Wed, 18 Oct 2006 18:42:33 -0400 (EDT) Date: Wed, 18 Oct 2006 18:42:33 -0400 From: Kris Kennaway To: Jack Vogel Message-ID: <20061018224233.GA1632@xor.obsecurity.org> References: <2a41acea0610181046k822afd1qcec4187dc8514187@mail.gmail.com> <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: Kip Macy , freebsd-stable@freebsd.org, freebsd-net Subject: Re: em network issues 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: Wed, 18 Oct 2006 22:42:48 -0000 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 18, 2006 at 03:31:53PM -0700, Jack Vogel wrote: > On 10/18/06, Kip Macy wrote: > >I have a Sun T2000 that I generally run with the em driver from as of > >July in order to avoid watchdog timeouts. One trivial scenario that > >reproduces the problem with 100% consistency is running the ghc > >configure script (a 20kloc shell script) over NFS. As the T2000 > >doesn't exactly represent "typical" PC hardware it may not be the most > >desirable test platform. Nonetheless, let me know if you're > >interested. > >Thanks for looking into this issue. > > > > -Kip >=20 > I'm a bit confused from the way you worded this, do you have watchdogs > with em, or you use em to avoid them? >=20 > If you have problems when running NFS then thats a clue, is it TCP or > UDP based NFS? I am interested, give me details about the setup please. >=20 > I have one of the engineers in our test organization trying to repro=20 > symptoms > on a system installed with BETA2, it has shared interrupts between em and > usb. Any additional stuff he could run would be helpful. I have been working with someone's system that has em shared with fxp, and a simple fetch over the em (e.g. of a 10 GB file of zeroes) is enough to produce watchdog timeouts after a few seconds. As previously mentioned, changing the INTR_FAST to INTR_MPSAFE in the driver avoids this problem. However, others are seeing sporadic watchdog timeouts at higher system load on non-shared em systems too. This is in addition to the hardware instances you already know about where the em driver has not worked going back to 5.x. Kris --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFNq3ZWry0BWjoQKURAiPQAKCpkojPf1a5JdBEsMrEpK65UQ/02ACeO4DN +5ON1GttnrVHCaXPWE2fGkY= =puGc -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd--