Date: Mon, 13 Apr 2009 00:08:10 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: Jack F Vogel <jfv@FreeBSD.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r190872 - head/sys/dev/e1000 Message-ID: <alpine.BSF.2.00.0904130003560.89405@odysseus.silby.com> In-Reply-To: <200904100005.n3A05lIu025175@svn.freebsd.org> References: <200904100005.n3A05lIu025175@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack, either this or some other recent change to the em driver caused it to stop working correctly on the e1000 virtual device inside VMware ESX. Unfortunately, I have not updated my 8.x VMs recently, so I don't know when this broke. I got the message about an invalid MAC address. I modified em_is_valid_ether_addr to always return True, but it looks like the effect of that was to cause the driver to load, but give the NIC a MAC of 00:00:00:00:00:00. However, if I manually set a MAC after that, the virtual NIC IS functional. So I think the sole problem may just be that the code which reads the MAC is incompatible with the ESX emulation. Do you want me to try a kernel from immediately before this change to confirm that this was the cause of the problem? Mike "Silby" Silbersack On Fri, 10 Apr 2009, Jack F Vogel wrote: > Author: jfv > Date: Fri Apr 10 00:05:46 2009 > New Revision: 190872 > URL: http://svn.freebsd.org/changeset/base/190872 > > Log: > This delta syncs the em and igb drivers with Intel, > adds header split and SCTP support into the igb driver. > Various small improvements and fixes. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0904130003560.89405>