Bug 134079 - [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8.0)
Summary: [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8.0)
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: jfv
URL:
Keywords: IntelNetworking
Depends on:
Blocks:
 
Reported: 2009-04-29 06:50 UTC by Asp Gao
Modified: 2015-07-01 15:20 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Asp Gao 2009-04-29 06:50:01 UTC
when load the intel Pro/1000 ethernet card by using :
   kldload if_em.ko or kldload if_igb.ko
system raise issue : 
   em0:<Intel(R) PRO/1000 Network Connection 6.9.9> port 0x3000-0x301f mem 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2
   em0: Using MSI interrupt
   em0: Invalid MAC address
   device_attach:em0 attach returned 5

Note: I am using IBM T60 Laptop, and I have no this issue when use FreeBSD 7.0 stable. it only raised when upgraded to FreeBSD-Current.

Fix: 

Dont know how to fix it .
How-To-Repeat: Use IBM T60 Laptop, install FreeBSD 7.0 stable with default setup . upgrade system by resource code to Freebsd 8.0-CURRENT. rebuild world, kernel. and install kernel and world .after reboot system , I get this issue .
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-04-29 06:58:30 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).
Comment 2 Stacey Son freebsd_committer 2009-05-14 19:18:35 UTC
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.
Comment 3 korba 2009-11-30 18:52:45 UTC
I had the same problem. I changed the e1000_read_mac_addr_generic()
function in /usr/src/sys/dev/e1000/e1000_nvm.c to the 7.2 version. It
works for me.

Good luck,
Piotr "Korba" Tomczyk
Comment 4 jaz 2010-01-12 00:32:22 UTC
I have the same problem since upgrading from 7.2 to 8.0. I have a PCI
Intel 1000 card.

Perhaps someone could make a patch that does what Korba has done?
Comment 5 Andre Oppermann freebsd_committer 2010-08-23 18:53:32 UTC
Responsible Changed
From-To: freebsd-net->jfv

Over to maintainer.
Comment 6 Sean Bruno freebsd_committer 2015-07-01 15:20:00 UTC
This doesn't happen on my old and crusty T60 that I have installed current on.  If this is still testable and/or happening on head for you, please reopen this ticket.