From owner-freebsd-current@FreeBSD.ORG Wed Feb 21 10:18:00 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB37116EA85 for ; Wed, 21 Feb 2007 10:18:00 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 76F3413C441 for ; Wed, 21 Feb 2007 10:18:00 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1HJoXo-000Imh-BK; Wed, 21 Feb 2007 12:17:52 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: "Andrey V. Elsukov" In-reply-to: <45DA9F40.1070604@yandex.ru> References: <20070110120731.GA1515@shark.localdomain> <20070210171130.D47107@maildrop.int.zabbadoz.net> <45D98B62.1060402@yandex.ru> <20070220014535.GC912@cdnetworks.co.kr> <45DA9F40.1070604@yandex.ru> Comments: In-reply-to "Andrey V. Elsukov" message dated "Tue, 20 Feb 2007 10:12:00 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Feb 2007 12:17:52 +0200 From: Danny Braniss Message-ID: Cc: pyunyh@gmail.com, "Bjoern A. Zeeb" , FreeBSD current mailing list , Sergey Zaharchenko Subject: Re: nve related LOR triggered by lots of small packets, and a hard hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Feb 2007 10:18:00 -0000 > Pyun YongHyeon wrote: > > Because your dmesg for nfe(4) shows 'obsoleted if_watchdog interface' > > message I think you've used stock nfe(4) on CURRENT. > > Try overhauld nfe(4) at the following URL. > > > > http://people.freebsd.org/~yongari/nfe/if_nfe.c > > http://people.freebsd.org/~yongari/nfe/if_nfereg.h > > http://people.freebsd.org/~yongari/nfe/if_nfevar.h > > > > The new nfe(4) has several protections for watchdog timeout errors > > reported on the driver. One user repored TSO related issues for > > the new driver so if you encounter strange errors in the new driver > > please turn off TSO capability(e.g. #ifconfig nfe0 -tso) > hi, I'm having 2 - probably related - problems: 1- on a diskless host, it boots via PXE, attaches the NIC but somehow the mount root nsf is bypassed. 2- booting of the disk, and with ifconfig_nfe0="DHCP", dhclient fails. if I run: dhclient nfe0 all is fine. adding 'net.inet.tcp.tso="0"' to sysctl.conf fixed 2, but adding the same to loader.conf did not help with the PXE boot. danny