From owner-freebsd-net@FreeBSD.ORG Sat Oct 30 02:42:11 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87F8A1065670 for ; Sat, 30 Oct 2010 02:42:11 +0000 (UTC) (envelope-from RCharlet@adaranet.com) Received: from barracuda.adaranet.com (smtp.adaranet.com [72.5.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 6866D8FC12 for ; Sat, 30 Oct 2010 02:42:11 +0000 (UTC) X-ASG-Debug-ID: 1288404202-0d0f05240001-QdxwpM Received: from SJ-EXCH-1.adaranet.com ([10.10.1.29]) by barracuda.adaranet.com with ESMTP id ARmuZAoiqI7nIAVG; Fri, 29 Oct 2010 19:03:22 -0700 (PDT) X-Barracuda-Envelope-From: RCharlet@adaranet.com Received: from SJ-EXCH-1.adaranet.com ([fe80::7042:d8c2:5973:c523]) by SJ-EXCH-1.adaranet.com ([fe80::7042:d8c2:5973:c523%14]) with mapi; Fri, 29 Oct 2010 19:03:22 -0700 From: "Ricky Charlet" X-Barracuda-BBL-IP: fe80::7042:d8c2:5973:c523 X-Barracuda-RBL-IP: fe80::7042:d8c2:5973:c523 To: Juli Mallett Date: Fri, 29 Oct 2010 19:03:21 -0700 X-ASG-Orig-Subj: RE: em driver problem on vmware Thread-Topic: em driver problem on vmware Thread-Index: Act31ZQndnSu3rnWTEC6BSIcrR2fuwAANDrA Message-ID: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7E0@SJ-EXCH-1.adaranet.com> References: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7BF@SJ-EXCH-1.adaranet.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Barracuda-Connect: UNKNOWN[10.10.1.29] X-Barracuda-Start-Time: 1288404202 X-Barracuda-URL: http://172.16.10.203:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at adaranet.com Cc: "freebsd-net@freebsd.org" Subject: RE: em driver problem on vmware 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: Sat, 30 Oct 2010 02:42:11 -0000 > -----Original Message----- > From: juli@clockworksquid.com [mailto:juli@clockworksquid.com] On > Behalf Of Juli Mallett > Sent: Friday, October 29, 2010 6:55 PM > To: Ricky Charlet > Cc: freebsd-net@freebsd.org > Subject: Re: em driver problem on vmware > > On Fri, Oct 29, 2010 at 17:07, Ricky Charlet > wrote: > > Howdy, > > I have freebsd80-release with an upgraded em0 driver from > freebsd8.1 (and an appropriate touch of if_var.h). I'm running an amd64 > on a vmware vm. And I see this in dmesg: > > > > ------------cut------------- > > em0: port 0x2000-203f > mem 0xd8940000-0xd895ffff, 0xd8900000-0xd890ffff irq 18 at device 0.0 > on pci2 > > em0: Memory Access and/or Bus Master bits were not set > > em0: [FILTER] > > em0: Ethernet address: 00:0c:29:57:d7:7f > > ------------paste------------ > > > > But, on the other hand, has anyone seen the new em driver > working/failing on a vmware vm? > > "Memory Access and/or Bus Master bits were not set" is not a fatal > error, it is correctable, indeed that is printed out when it is > corrected; that is not something to worry about in and of itself as > such, are you actually having a problem or just concerned because you > saw that in dmesg? It is truly not working. I agree those lines in dmesg are good and indicat= e em0 is ready. but `ifconfig` does not see em0. --- Ricky Charlet Adara Networks USA 408-433-4942