Date: Thu, 24 Oct 2019 14:05:26 -0400 From: Michael Butler <imb@protected-networks.net> To: Gleb Smirnoff <glebius@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org>, freebsd@intel.com Subject: Re: SVN r353868 breaks net/intel-em-kmod Message-ID: <5ef99ae6-9e95-7511-f64e-8f824733cd68@protected-networks.net> In-Reply-To: <20191024175642.GN4086@FreeBSD.org> References: <d622987a-2527-d652-3a06-a2a138b6abaf@protected-networks.net> <20191024175642.GN4086@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/24/19 1:56 PM, Gleb Smirnoff wrote: > On Thu, Oct 24, 2019 at 11:12:10AM -0400, Michael Butler wrote: > M> The removal of these KPIs yields: > M> > M> link_elf_obj: symbol if_multiaddr_array undefined > M> linker_load_file: /boot/modules/if_em_updated.ko - unsupported file type > > What's the reason to keep these outside of the tree drivers? AFAIU, they > are maintained by the same team that maintains in-tree drivers. Cced them. For some reason, the default in-kernel driver doesn't play nicely with VirtualBox especially when attempting to bridge the host and client. I have not explored why it works with NAT but not bridge, imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5ef99ae6-9e95-7511-f64e-8f824733cd68>