From owner-freebsd-net@FreeBSD.ORG Fri Aug 10 20:17:38 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 26B471065673 for ; Fri, 10 Aug 2012 20:17:38 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id AD7078FC0C for ; Fri, 10 Aug 2012 20:17:37 +0000 (UTC) Received: from Octca64MkIV.tdx.co.uk (octa64.tdx.co.uk [62.13.130.232]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3) with ESMTP id q7AKHX3g020675 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Fri, 10 Aug 2012 21:17:33 +0100 (BST) Date: Fri, 10 Aug 2012 21:18:37 +0100 From: Karl Pielorz To: "EXT-Glatting, Dennis P" , freebsd-net@freebsd.org Message-ID: In-Reply-To: <0457799DC5A3A5479336B9A1F2E7FC6450E4FF2F5F@XCH-NW-21V.nw.nos.boeing.com> References: <26ABB168B4C8E32E7D127EF9@Octca64MkIV.tdx.co.uk> <0457799DC5A3A5479336B9A1F2E7FC6450E4FF2F5F@XCH-NW-21V.nw.nos.boeing.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: RE: FreeBSD 9.0-R em0 issues? 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, 10 Aug 2012 20:17:38 -0000 --On 10 August 2012 12:18 -0700 "EXT-Glatting, Dennis P" wrote: > I've seen this too on a H8DG6-F but changed to the igb interfaces. I am > also seeing a problem under ESXi 5.0 on an unpatched system but haven't > had the opportunity to patch (ESXi) it. There I will see these messages > under a FreeBSD instance: > > nms# uname -a > FreeBSD nms 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #9: Mon Aug 6 22:02:46 > PDT 2012 root@nms:/sys/amd64/compile/SMUNI amd64 > > > nms# grep em0 /var/log/messages > Jul 9 15:50:39 nms kernel: em0: Connection 1.0.4> port 0x2000-0x203f mem > 0xd1020000-0xd103ffff,0xd1000000-0xd100ffff irq 18 at device 0.0 on pci2 > Jul 9 15:50:39 nms kernel: em0: Memory Access and/or Bus Master bits > were not set! Jul 9 15:50:39 nms kernel: em0: Ethernet address: > 00:0c:29:a2:36:c2 Jul 10 09:28:49 nms kernel: em0: Watchdog timeout -- > resetting Your NIC's ID differently to mine: Mine - em0: Yours - em0: Looks like that's different driver code? (presuming the 7.2.3 and 1.0.4 are the driver versions) - the 'virtual' NIC created by ESXi must be using a different driver. Also - I don't get anything logged on the console or anywhere - it just "stops" (i.e. no watchdog errors or similar - nothing). Aside from the apparent 'billions' of packets errors (or corrupt counters) - the only other thing I've found that was weird was the '-1's in the dump from doing 'dev.em.0.debug=1' I think you've got a problem :( - But probably not the same problem that I have on this SuperMicro machine :-( -Karl