From owner-freebsd-sparc64@FreeBSD.ORG  Wed Dec 30 01:10:03 2009
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
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 7179E1065676
	for <freebsd-sparc64@hub.freebsd.org>;
	Wed, 30 Dec 2009 01:10: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 5F6F78FC13
	for <freebsd-sparc64@hub.freebsd.org>;
	Wed, 30 Dec 2009 01:10: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 nBU1A39h016238
	for <freebsd-sparc64@freefall.freebsd.org>;
	Wed, 30 Dec 2009 01:10:03 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBU1A3pv016237;
	Wed, 30 Dec 2009 01:10:03 GMT (envelope-from gnats)
Date: Wed, 30 Dec 2009 01:10:03 GMT
Message-Id: <200912300110.nBU1A3pv016237@freefall.freebsd.org>
To: freebsd-sparc64@FreeBSD.org
From: Marius Strobl <marius@alchemy.franken.de>
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: Marius Strobl <marius@alchemy.franken.de>
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>, 
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Dec 2009 01:10:03 -0000

The following reply was made to PR sparc64/142102; it has been noted by GNATS.

From: Marius Strobl <marius@alchemy.franken.de>
To: Manuel Tobias Schiller <mala@hinterbergen.de>
Cc: Mark Linimon <linimon@lonesome.com>, FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: sparc64/142102: FreeBSD 8.0 kernel panics on sparc64 when accessing NFS
Date: Wed, 30 Dec 2009 02:08:01 +0100

 On Wed, Dec 30, 2009 at 01:25:55AM +0100, Manuel Tobias Schiller wrote:
 > On Tue, 29 Dec 2009 19:53:58 +0100
 > Marius Strobl <marius@alchemy.franken.de> wrote:
 > > Oh, sorry, I had a bug in there, the svc code used a stale
 > > pointer to the mbuf with this. Could you please re-fetch
 > > and try again? I can't guarantee that this fixes the hang
 > > you experienced but at least in theory just re-aligning
 > > the data can't make the issue with the unaligned access
 > > any worse. Using the LOM or by breaking into the kernel
 > > by sending a break you should be able to power-cycle/
 > > reboot the machine without removing the power cord should
 > > it hang again though.
 > > What NFS client and with which mount options are you
 > > using to trigger is problem?
 > > 
 > > Marius
 > 
 > I managed to compile and test a kernel with your updated patch, and things
 > seem to work. I'll try to stress-test it over the night by copying a few
 > tens of gigabytes over and report back with the results. Also, if I'm
 > reading your patch correctly, we should be able to do without the bcopy
 > hack from PR 140797, so I'll recompile a kernel without it and try if that
 > works as well.
 
 I don't think so; nfs_realign() only guarantees 4-byte alignment
 as required by XDR and assumed by nfsm_srvmtofh_xx() further down
 the road but nfsfh_t needs 8-byte alignment.
 
 > 
 > Thanks a lot for all your help and your patience!
 > 
 
 Well, thanks a lot for testing so far!
 
 Marius