From owner-freebsd-amd64@FreeBSD.ORG  Mon Oct 18 05:26:09 2010
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 197991065670;
	Mon, 18 Oct 2010 05:26:09 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id E3E2E8FC08;
	Mon, 18 Oct 2010 05:26:08 +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 o9I5Q8Af044654;
	Mon, 18 Oct 2010 05:26:08 GMT
	(envelope-from avg@freefall.freebsd.org)
Received: (from avg@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o9I5Q8b1044650;
	Mon, 18 Oct 2010 05:26:08 GMT (envelope-from avg)
Date: Mon, 18 Oct 2010 05:26:08 GMT
Message-Id: <201010180526.o9I5Q8b1044650@freefall.freebsd.org>
To: avg@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: avg@FreeBSD.org
X-Mailman-Approved-At: Mon, 18 Oct 2010 12:29:14 +0000
Cc: 
Subject: Re: kern/151409: Problem with Marvell driver, e1000phy.c
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 05:26:09 -0000

Synopsis: Problem with Marvell driver, e1000phy.c

Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs
Responsible-Changed-By: avg
Responsible-Changed-When: Mon Oct 18 05:24:14 UTC 2010
Responsible-Changed-Why: 
I don't see any indication that this is amd64-specific bug; this
is a problem with network driver.

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