From owner-freebsd-i386@FreeBSD.ORG  Sun Mar 19 18:18:10 2006
Return-Path: <owner-freebsd-i386@FreeBSD.ORG>
X-Original-To: freebsd-i386@hub.freebsd.org
Delivered-To: freebsd-i386@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6E34416A420;
	Sun, 19 Mar 2006 18:18:10 +0000 (UTC)
	(envelope-from remko@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2D00743D46;
	Sun, 19 Mar 2006 18:18:10 +0000 (GMT)
	(envelope-from remko@FreeBSD.org)
Received: from freefall.freebsd.org (remko@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k2JIIA5I009270;
	Sun, 19 Mar 2006 18:18:10 GMT
	(envelope-from remko@freefall.freebsd.org)
Received: (from remko@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k2JII9r8009266;
	Sun, 19 Mar 2006 18:18:09 GMT (envelope-from remko)
Date: Sun, 19 Mar 2006 18:18:09 GMT
From: Remko Lodder <remko@FreeBSD.org>
Message-Id: <200603191818.k2JII9r8009266@freefall.freebsd.org>
To: tony@saign.com, remko@FreeBSD.org, freebsd-i386@FreeBSD.org
Cc: 
Subject: Re: i386/62280: [em] em0 broken after resume in 5.2-CURRENT
X-BeenThere: freebsd-i386@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: I386-specific issues for FreeBSD <freebsd-i386.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-i386>
List-Post: <mailto:freebsd-i386@freebsd.org>
List-Help: <mailto:freebsd-i386-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Mar 2006 18:18:10 -0000

Synopsis: [em] em0 broken after resume in 5.2-CURRENT

State-Changed-From-To: open->feedback
State-Changed-By: remko
State-Changed-When: Sun Mar 19 18:17:25 UTC 2006
State-Changed-Why: 
Can you tell me whether this is still a current problem on
recent versions of FreeBSD?  There were a lot of em fixes
lately which might have fixed the issue you are reporting.

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