From owner-freebsd-net@FreeBSD.ORG  Sat Mar 19 15:31:13 2011
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 14264106568B;
	Sat, 19 Mar 2011 15:31:13 +0000 (UTC) (envelope-from bz@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id E3B0B8FC17;
	Sat, 19 Mar 2011 15:31:12 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p2JFVC9a034517;
	Sat, 19 Mar 2011 15:31:12 GMT (envelope-from bz@freefall.freebsd.org)
Received: (from bz@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p2JFVCMh034508;
	Sat, 19 Mar 2011 15:31:12 GMT (envelope-from bz)
Date: Sat, 19 Mar 2011 15:31:12 GMT
Message-Id: <201103191531.p2JFVCMh034508@freefall.freebsd.org>
To: bz@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org
From: bz@FreeBSD.org
Cc: 
Subject: Re: kern/148018: [flowtable] flowtable crashes on ia64
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2011 15:31:13 -0000

Synopsis: [flowtable] flowtable crashes on ia64

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: bz
Responsible-Changed-When: Sat Mar 19 15:30:27 UTC 2011
Responsible-Changed-Why: 
Over to maintainer(s).
This may sounds ia64 specific but it's really network stack
aligment problem on archs with more strict alignment.

http://www.freebsd.org/cgi/query-pr.cgi?pr=148018