From owner-freebsd-net@FreeBSD.ORG Thu May 14 18:40:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EF1F1065676 for ; Thu, 14 May 2009 18:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8D3608FC14 for ; Thu, 14 May 2009 18:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n4EIe3FU060813 for ; Thu, 14 May 2009 18:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n4EIe3E3060812; Thu, 14 May 2009 18:40:03 GMT (envelope-from gnats) Date: Thu, 14 May 2009 18:40:03 GMT Message-Id: <200905141840.n4EIe3E3060812@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Stacey Son Cc: Subject: Re: kern/134079: [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8.0) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stacey Son List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 18:40:04 -0000 The following reply was made to PR kern/134079; it has been noted by GNATS. From: Stacey Son To: bug-followup@freebsd.org, g.zhengming@gmail.com Cc: Subject: Re: kern/134079: [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8.0) Date: Thu, 14 May 2009 13:18:35 -0500 I have the same, exact problem with FreeBSD-Current running on VMWare Fusion (64-bit, 2 virtual procs, 4096MB Memory allocation, Mac Pro host). Running 7.2 on this same configuration there is no problem with the e1000 (if_em) driver. Upgrading to -current I get the following error (in dmesg): em0: Invalid MAC address device_attach:em0 attach returned 5 My work around is to edit the "vmx" config file on the host for the virtual image and change: ethernet0.virtualDev="e1000" to: ethernet0.virtualDev="vlance" so the virtual machine emulates an AMD Lance instead. -stacey.