From owner-freebsd-sparc64@FreeBSD.ORG  Tue Dec 29 19:00:15 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 301BA106568F
	for <freebsd-sparc64@hub.freebsd.org>;
	Tue, 29 Dec 2009 19:00:15 +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 1D4088FC15
	for <freebsd-sparc64@hub.freebsd.org>;
	Tue, 29 Dec 2009 19:00:15 +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 nBTJ0ExZ079553
	for <freebsd-sparc64@freefall.freebsd.org>;
	Tue, 29 Dec 2009 19:00:14 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBTJ0Eai079552;
	Tue, 29 Dec 2009 19:00:14 GMT (envelope-from gnats)
Date: Tue, 29 Dec 2009 19:00:14 GMT
Message-Id: <200912291900.nBTJ0Eai079552@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: Tue, 29 Dec 2009 19:00:15 -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: Tue, 29 Dec 2009 19:53:58 +0100

 On Tue, Dec 29, 2009 at 04:34:11PM +0100, Manuel Tobias Schiller wrote:
 > On Tue, 29 Dec 2009 01:58:29 +0100
 > Marius Strobl <marius@alchemy.franken.de> wrote:
 > > I'm using a more or less current HEAD but the NFS code hasn't
 > > changed that much since 8.0, at least it doesn't contain any
 > > other alignment fixes I'm aware of.
 > > I think I got what the problem is but I still haven't managed
 > > to reproduce it so far. Could you please test whether the
 > > following patch makes a difference?
 > > http://people.freebsd.org/~marius/fha_extract_info_realign.diff
 > > 
 > > Marius
 > 
 > I applied the patch, compiled the kernel and rebooted. NFS read access
 > seems to work as before. When I try to write to the server, the server
 > locks up solid, i.e. I do not even get a kernel panic reported on the
 > serial console, so I can't give you a backtrace or anything. I had to
 > disconnect the cable from the wall outlet to the power supply to restart
 > it. It came up without problems, though.
 > 
 
 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