Date: Fri, 29 Oct 2010 18:55:28 -0700 From: Juli Mallett <jmallett@FreeBSD.org> To: Ricky Charlet <RCharlet@adaranet.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: em driver problem on vmware Message-ID: <AANLkTimcsQtj%2BVX4O=4JHqwndfgYHu35SS-PtGndbL5w@mail.gmail.com> In-Reply-To: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7BF@SJ-EXCH-1.adaranet.com> References: <32AB5C9615CC494997D9ABB1DB12783C024CA4A7BF@SJ-EXCH-1.adaranet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 29, 2010 at 17:07, Ricky Charlet <RCharlet@adaranet.com> 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: <Intel(R) PRO/1000 Network Connection 6.9.14> 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimcsQtj%2BVX4O=4JHqwndfgYHu35SS-PtGndbL5w>