From owner-freebsd-sparc64@FreeBSD.ORG Sat Oct 11 18:42:27 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 157BE16A4C0 for ; Sat, 11 Oct 2003 18:42:27 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-107-253.dsl.lsan03.pacbell.net [64.169.107.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C97F43F85 for ; Sat, 11 Oct 2003 18:42:26 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id D04AB66D6A; Sat, 11 Oct 2003 18:42:24 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 984809AD; Sat, 11 Oct 2003 18:42:24 -0700 (PDT) Date: Sat, 11 Oct 2003 18:42:24 -0700 From: Kris Kennaway To: Tillman Hodgson Message-ID: <20031012014224.GA95189@rot13.obsecurity.org> References: <20031011114819.GA54814@freebie.xs4all.nl> <20031012003402.GA32486@rot13.obsecurity.org> <20031011193836.A564@seekingfire.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline In-Reply-To: <20031011193836.A564@seekingfire.com> User-Agent: Mutt/1.4.1i cc: freebsd-sparc@freebsd.org cc: Kris Kennaway Subject: Re: X on sparc64? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Oct 2003 01:42:27 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 11, 2003 at 07:38:36PM -0600, Tillman Hodgson wrote: > On Sat, Oct 11, 2003 at 05:34:02PM -0700, Kris Kennaway wrote: > > Be aware that 4.x's NFS code doesn't like talking to sparc64 clients - > > it causes the i386 server to double fault. 5.x as a server is > > perfectly happy though. >=20 > I have an Ultra 5 running a recent -current that uses an i386 -stable as > it's NFS server ... I've never seen any problems with it. Is this an > issue that is only affected via certain NFS options or is otherwise > possible to (unknowingly) avoid? It only occurs under load..if you've never put heavy (I mean heavy!) loads on the server you've probably avoided it. I was able to repeat this on two separate networks. Kris --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/iLGAWry0BWjoQKURAhRaAKDUuQUDxwpk2hHhOxQ18xV6w6cJBwCgnmza tajelgmzPAu0f1CxdFFQD4g= =fv1I -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG--