Date: Sat, 11 Oct 2003 18:42:24 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Tillman Hodgson <tillman@seekingfire.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: X on sparc64? Message-ID: <20031012014224.GA95189@rot13.obsecurity.org> In-Reply-To: <20031011193836.A564@seekingfire.com> References: <20031011114819.GA54814@freebie.xs4all.nl> <20031012003402.GA32486@rot13.obsecurity.org> <20031011193836.A564@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031012014224.GA95189>