From owner-freebsd-net@FreeBSD.ORG  Tue Sep  6 00:44:04 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 9F8271065672;
	Tue,  6 Sep 2011 00:44:04 +0000 (UTC)
	(envelope-from yongari@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 8EF988FC12;
	Tue,  6 Sep 2011 00:44:04 +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 p860i44k028054;
	Tue, 6 Sep 2011 00:44:04 GMT
	(envelope-from yongari@freefall.freebsd.org)
Received: (from yongari@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p860i4rH028050;
	Tue, 6 Sep 2011 00:44:04 GMT (envelope-from yongari)
Date: Tue, 6 Sep 2011 00:44:04 GMT
Message-Id: <201109060044.p860i4rH028050@freefall.freebsd.org>
To: yoitsmeremember@gmail.com, yongari@FreeBSD.org, freebsd-net@FreeBSD.org,
	yongari@FreeBSD.org
From: yongari@FreeBSD.org
Cc: 
Subject: Re: kern/160442: [vlan] Packets transmitted on vlan(4) interfaces
	with a parent vge(4) vanish.
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: Tue, 06 Sep 2011 00:44:04 -0000

Synopsis: [vlan] Packets transmitted on vlan(4) interfaces with a parent vge(4) vanish.

State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Tue Sep 6 00:43:02 UTC 2011
State-Changed-Why: 
It seems parent interface vge(4) thinks it does not have established
link. vge(4) actively keeps track of current link state and it does
not try to send packets when it lost link. Unlike other drivers,
vge(4) relies on its PHY hardware generates an interrupt on link
status change. If the PHY failed to generate interrupt for link
establishment, parent device may not see the update link status.
To experiment this, try unplug the UTP cable and replug it and see
whether that makes any difference for you.

I'd also like to know your PHY hardware and controller revision so
post dmesg and "pciconf -lcbv" output. I failed to reproduce the
issue on my VIA VT6130 PCIe controller though.


Responsible-Changed-From-To: freebsd-net->yongari
Responsible-Changed-By: yongari
Responsible-Changed-When: Tue Sep 6 00:43:02 UTC 2011
Responsible-Changed-Why: 
Grab.

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