From owner-freebsd-net@FreeBSD.ORG Fri Nov 25 21:12:06 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C18916A41F for ; Fri, 25 Nov 2005 21:12:06 +0000 (GMT) (envelope-from volcane.uk@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAADE43D53 for ; Fri, 25 Nov 2005 21:12:05 +0000 (GMT) (envelope-from volcane.uk@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so466187nzo for ; Fri, 25 Nov 2005 13:12:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=gC03PVUVbEi5QMBrd2sxy1i6+hI0zD4pzJUkrBDSdhQy6lxrNWz4dMzYQ0p7SFSXRhZB7EHkCX7hCQJC64NoiTuXDeMipT2b0+yw6GMgbZG6k/pVdgXUk8TSLOnsFgofwKdONesQqJTkR15fElZjm/e58IMsNHEgkLTK+Jbzmew= Received: by 10.36.251.76 with SMTP id y76mr1428810nzh; Fri, 25 Nov 2005 13:12:04 -0800 (PST) Received: by 10.36.8.20 with HTTP; Fri, 25 Nov 2005 13:12:04 -0800 (PST) Message-ID: <964bdb4d0511251312j10b21214hc8218aa6eadb3894@mail.gmail.com> Date: Fri, 25 Nov 2005 21:12:04 +0000 From: Volcane To: freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: em driver woes X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 21:12:06 -0000 I scanned through the archive and noticed a posting there about an interrupt storm on the em driver, I am not sure if my symptoms are related so I decided on a new thread. I first installed the 6.0-RELEASE using FTP install and everything was happy, I then CVSUP'd to RELENG_6 which had an em driver update a few hours ago. Did the world and kernel and booted, on the boot with the new kernel I noticed my network was dead. I could get the initial DHCP from my server but once it got an IP it wasn't working. Further investigation with tcpdump showed me a massive amount of arp requests for my gateway IP, with replies coming back to the card.=20 Output of 'arp -an' showed that the gateway ARP was indeed in the arp table so there shouldnt have been any reason for all the arp requests. At this point I investigated the driver version and found that the GENERIC from the installation media was: em0: port 0x4000-0x403fmem 0xd8000000-0xd801ffff irq 16 at device 10.0 on pci10 em0: Ethernet address: 00:14:85:08:60:c6 em0: Speed:N/A Duplex:N/A The em from the new -STABLE kernel was: em0: port 0x4000-0x403fmem 0xd8000000-0xd801ffff irq 16 at device 10.0 on pci10 em0: [GIANT-LOCKED] em0: Ethernet address: 00:14:85:08:60:c6 Below is a diff from the config file I used to build -STABLE and the GENERIC config: < cpu I486_CPU < cpu I586_CPU 25c23 < ident GENERIC --- > ident WEB1 36d33 < options INET6 # IPv6 communications protocols 64a62,72 > options SMP # Symmetric MultiProcessor Kernel > options IPSEC > options IPSEC_ESP > options IPSEC_DEBUG > options IPSEC_FILTERGIF > options IPFIREWALL > options IPFIREWALL_VERBOSE > options IPFIREWALL_DEFAULT_TO_ACCEPT > options IPFIREWALL_FORWARD_EXTENDED Hope this helps anyone, for now I'm heading back to -RELEASE