From owner-freebsd-sparc64@FreeBSD.ORG Mon Dec 28 21:50:03 2009 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFCED1065670 for ; Mon, 28 Dec 2009 21:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DF6C08FC1C for ; Mon, 28 Dec 2009 21:50:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBSLo3Ch074350 for ; Mon, 28 Dec 2009 21:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBSLo3EM074347; Mon, 28 Dec 2009 21:50:03 GMT (envelope-from gnats) Date: Mon, 28 Dec 2009 21:50:03 GMT Message-Id: <200912282150.nBSLo3EM074347@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Manuel Tobias Schiller Cc: Subject: Re: sparc64/142102: FreeBSD 8.0 kernel panics on sparc64 when accessing NFS X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Manuel Tobias Schiller List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Dec 2009 21:50:04 -0000 The following reply was made to PR sparc64/142102; it has been noted by GNATS. From: Manuel Tobias Schiller To: Mark Linimon Cc: FreeBSD-gnats-submit@FreeBSD.org, Marius Strobl , Manuel Tobias Schiller Subject: Re: sparc64/142102: FreeBSD 8.0 kernel panics on sparc64 when accessing NFS Date: Mon, 28 Dec 2009 22:40:47 +0100 On Mon, 28 Dec 2009 15:18:09 -0600 Mark Linimon wrote: > It turns out the kernels on the T1s is much older than I thought. > I know I have been using something pretty close to 8.0R on one of > my machines at home but I am traveling right now and accessing it > would be kind of a pain. > > All our other sparcs don't use NFS to the same extent the above do > (they are pxebooted and e.g. /usr will go across NFS.) > > mcl > Hi Mark, thanks for the clarification. With the situation being what you describe, I think I'll try upgrading my sources to the latest RELENG_8_0 ones to be on the safe side, check if the problem persists, and if so, I'll try to find a solution (unless I hear from someone to try something different). Another question springs to mind: If /usr goes across NFS, most traffic arriving at the NFS server should be reading, right? Because that appears to work without a glitch with the fix (at least on my machine). Right now, the panic is pushed back to the point when I try to write (i.e. copy a new file to the NFS server). Thanks for the quick reply, Manuel -- Homepage: http://www.hinterbergen.de/mala OpenPGP: 0xA330353E (DSA) or 0xD87D188C (RSA)