From owner-freebsd-net@FreeBSD.ORG Sat Oct 30 02:20:07 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 21ACA1065670 for ; Sat, 30 Oct 2010 02:20:07 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id D2AAE8FC15 for ; Sat, 30 Oct 2010 02:20:06 +0000 (UTC) Received: by yxl31 with SMTP id 31so2513238yxl.13 for ; Fri, 29 Oct 2010 19:20:06 -0700 (PDT) Received: by 10.150.198.19 with SMTP id v19mr86492ybf.336.1288403748397; Fri, 29 Oct 2010 18:55:48 -0700 (PDT) MIME-Version: 1.0 Sender: juli@clockworksquid.com Received: by 10.236.103.139 with HTTP; Fri, 29 Oct 2010 18:55:28 -0700 (PDT) In-Reply-To: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7BF@SJ-EXCH-1.adaranet.com> References: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7BF@SJ-EXCH-1.adaranet.com> From: Juli Mallett Date: Fri, 29 Oct 2010 18:55:28 -0700 X-Google-Sender-Auth: I8ksIAFo1FOw-XqR57fvLQ9Q_nw Message-ID: To: Ricky Charlet Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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:20:07 -0000 On Fri, Oct 29, 2010 at 17:07, Ricky Charlet wrote= : > Howdy, > =A0 =A0 =A0 =A0I 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 =A0vmware vm. =A0And I see this in dmesg: > > ------------cut------------- > em0: port 0x2000-203f mem 0= xd8940000-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------------ > > =A0 =A0 =A0 =A0But, 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?