From owner-freebsd-stable@FreeBSD.ORG Mon Oct 20 12:50:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F76B1065683 for ; Mon, 20 Oct 2008 12:50:33 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 4B2618FC27 for ; Mon, 20 Oct 2008 12:50:32 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 7667E744173; Mon, 20 Oct 2008 15:50:29 +0300 (EEST) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Le2vn7oQeDER; Mon, 20 Oct 2008 15:50:29 +0300 (EEST) Received: from [10.2.1.87] (gateway.cybervisiontech.com.ua [91.198.50.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 62AB0744172; Mon, 20 Oct 2008 15:50:28 +0300 (EEST) Message-ID: <48FC7E8D.2000506@icyb.net.ua> Date: Mon, 20 Oct 2008 15:50:21 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.17 (X11/20080929) MIME-Version: 1.0 To: pyunyh@gmail.com References: <47A3041D.5050402@icyb.net.ua> <20080201123603.GA14050@cdnetworks.co.kr> <47A321BB.1060708@icyb.net.ua> <47A32501.7080703@icyb.net.ua> <20080204035242.GA28554@cdnetworks.co.kr> <47C2BC50.5040702@icyb.net.ua> <47C2DBEF.301@icyb.net.ua> <20080226073633.GC47750@cdnetworks.co.kr> <486D440F.1090601@icyb.net.ua> In-Reply-To: <486D440F.1090601@icyb.net.ua> Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, yongari@freebsd.org Subject: Re: 6.3 nfe: dead after system reset X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2008 12:50:33 -0000 Pyun, something new about this issue. Today I got another instance of it, but with a new twist. In addition to all the usual symptoms I got a lot of messages like the following in console: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) and even couple like this: nfe0: discard frame w/o leading ethernet header (len 4294967295 pkt len 4294967295) nfe0: discard frame w/o leading ethernet header (len 3 pkt len 3) Maybe these messages could give a hint about what was going wrong in nfe. on 04/07/2008 00:26 Andriy Gapon said the following: > > As they say - long time, no see :-) > I am back with some more details, but still with no insights. > > Let me refresh an essence of the issue. > The issue: after 'abrupt' reset/reboot of a system my nfe interface is > dead. > That is, if I do a graceful reboot (e.g. via shutdown -r) everything is > ok, ditto if I do power-down (whether graceful or not) and the power-up. > The problem happens only if I press reset button and then boot up. > > Details. > The issue can not be reproduced with nve driver. > Moreover, when I reproduce the problem with nfe, then kldunload nfe > driver, kldload nve driver - nve interface is alive. Then kldunload nve, > kldload nfe - nfe interface is dead again. > > Specification of dead. > There are no errors. ifconfig shows the same output (active, media, up, > etc) as in normal case. But I can not ping any host on local network > (connected to the same switch), ping outputs "Host is down". tcpdump > also doesn't show any incoming traffic. > > More details. > I was able to verify that packets do actually go through the interface. > When I try to ping some machine I see (on the other host) arp requests > for its ethernet address. All address in arp packets are correct > (ethernet and ip). So the interface works for outgoing packets, but > somehow loses incoming arp replies. Not sure if thap happens in the NIC > or in the driver itself (see the above nve/nfe live replacement > experiment). > > So, there are some facts, but still no clues. > -- Andriy Gapon