From owner-freebsd-stable@FreeBSD.ORG Sat Mar 6 00:48:56 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B65E8106564A for ; Sat, 6 Mar 2010 00:48:56 +0000 (UTC) (envelope-from ncrogers@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5A1028FC0C for ; Sat, 6 Mar 2010 00:48:56 +0000 (UTC) Received: by pvg3 with SMTP id 3so1441530pvg.13 for ; Fri, 05 Mar 2010 16:48:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=5IgSnFnASLGmaXLKzmnSTxqOCsUBE6LOwHeHywwx86Y=; b=swbeK1mrA1oZ7ko3KmYRIX9dYfVBwPzodO2FJZRDIPivty5/hPvkYIOLMsCPfN3R9s +XwAdu39FOd456/eY4rX8LWXicqLP36QMgejtfb8IO9e6FVVaksuYXxThzpWyOLtvoF1 OxDazxeUDKk4oxAv146M+CZiUurmK67aLYLQs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ItDnzvjO691v0F0Ozuzq5GXeO1XxwzgIAV39QBcjSwZOf0si+16agWDfy610tKs6mf FGpoHoeHqLEPGDTAFD1q3AnZxC3aHQjUkE9efocafCSJmtNqxp4vna33ak1+bHH+Tgq6 VU4R8YQfHh8D4WRoJd5JTwJTQmrHXjYtPGJIY= MIME-Version: 1.0 Received: by 10.142.61.20 with SMTP id j20mr1139798wfa.105.1267836532541; Fri, 05 Mar 2010 16:48:52 -0800 (PST) Date: Fri, 5 Mar 2010 16:48:52 -0800 Message-ID: <147432021003051648x1a1417dfp3c778922ea2c571f@mail.gmail.com> From: Nick Rogers To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: em(4) interface hangs under 8.0-RELEASE 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: Sat, 06 Mar 2010 00:48:56 -0000 I'm still having a problem where an em(4) interface mysteriously "hangs" and mostly stops sending/receiving packets until I issue an ifconfig emX down followed by an ifconfig emX up, which fixes the problem for some amount of time. Traffic on the interface is about a consistent 3mb/s. One interesting thing to note is that if I tcpdump the interface during the "hang", I sometimes see a portion of the expected packets, usually only outbound. I've tried compiling a custom 8.0-RELEASE kernel with the em(4) driver (sys/dev/e1000) from 7.2-RELEASE as well as the same from cvs HEAD. Neither seem to fix the problem. I've also tried, as suggested in a previous thread, disabling TSO, TXCSUM, RXCSUM via the following: sysctl net.inet.tcp.tso=0 ifconfig em1 -tso -txcsum ifconfig em1 down ifconfig em1 up Relevant ifconfig and pciconf dump below. There are no attached VLAN interfaces. em1: flags=8843 metric 0 mtu 1500 options=98 ether 00:04:23:ca:a7:b7 inet 172.31.1.3 netmask 0xfffffff8 broadcast 172.31.1.7 media: Ethernet autoselect (1000baseT ) status: active em1@pci0:2:2:1: class=0x020000 card=0x11798086 chip=0x10798086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Dual Port Gigabit Ethernet Controller (82546EB)' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D3 current D0 cap 07[e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 05[f0] = MSI supports 1 message, 64 bit Any suggestions are greatly appreciated. Thanks.