Date: Thu, 19 Jun 2008 20:05:33 -0700 From: "Garrett Cooper" <yanefbsd@gmail.com> To: freebsd-current@freebsd.org Subject: Re: em(4) - memory access and bus master bits were not set Message-ID: <7d6fde3d0806192005p15355cd4w8196c0deac235955@mail.gmail.com> In-Reply-To: <20080620015123.GI388@stlux503.dsto.defence.gov.au> References: <20080620015123.GI388@stlux503.dsto.defence.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 19, 2008 at 6:51 PM, Wilkinson, Alex <alex.wilkinson@dsto.defence.gov.au> wrote: > Hi all, > > I am using em(4) on a VMware ESX - FreeBSD 7.0-STABLE VM. > > My em0 interface will consistently go down when it is hit with a reasonable amount > of I/O. Upon bootstrap dmesg(8) reports: > > "em0 memory access and or bus master bits were not set" > > I suspect this is the likely cause (bug) of my problem. This has been discussed > and supposedly fixed: > [http://unix.derkeiler.com/Mailing-Lists/FreeBSD/net/2007-07/msg00262.html] > > I am enabling em(4) via the following *.vmx tweak as recomened by Ivan > (http://ivoras.sharanet.org/freebsd/vmware.html): > > ethernet0.virtualDev="e1000" > > I am having to revert back to the crusty lnc driver - le(4). > > Can anyone suggest how to make em(4) play ball in a -STABLE ESX VM ? > > -aW Strange -- em(4) works perfectly fine in VMware Fusion. What version of ESX are you using? -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0806192005p15355cd4w8196c0deac235955>