From owner-freebsd-current@FreeBSD.ORG Wed Mar 7 12:05:44 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 6E94B16A400 for ; Wed, 7 Mar 2007 12:05:44 +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 2839713C441 for ; Wed, 7 Mar 2007 12:05:44 +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 1HOutk-000Kjc-6i; Wed, 07 Mar 2007 14:05:36 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: pyunyh@gmail.com In-reply-to: Your message of Wed, 7 Mar 2007 13:30:12 +0900 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Mar 2007 14:05:35 +0200 From: Danny Braniss Message-ID: Cc: "Bjoern A. Zeeb" , "Andrey V. Elsukov" , 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, 07 Mar 2007 12:05:44 -0000 > On Wed, Feb 21, 2007 at 12:17:52PM +0200, Danny Braniss wrote: > > > 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 > > > > > > Sorry for late reply. > Do you use MCP65 based hardware? It seems that MCP65 does not have > checksum offload capability on the hardware so TSO should not be > used on MCP65. it's supposed to be a MCP51, but: nfe0: > (Due to lack of datasheet I've unconditionally enabled TSO for > hardwares that have checksum offload capability.) > dmesg will show you what hardware were attached. > > If your hardware is not MCP65 based one please try latest tcp_output.c > (rev, 1.125). Recently andre@ fixed TSO related bug. I tried the latest, and it 'seems' to work ok if I boot of the disk, but still having problems when booting via PXE: ... nfe0: port 0xdc00-0xdc07 mem 0xfe02c000-0xfe02cfff irq 22 at device 20.0 on pci0 nfe0: Ethernet address: 57:6c:a9:f3:18:00 miibus1: on nfe0 e1000phy0: PHY 11 on miibus1 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: [ITHREAD] ... nfs_diskless: no interface ... danny PS: maybe it's time to change the Subject:?