em(4) on FreeBSD is sometimes annoying

Martin nakal at web.de
Sat Aug 2 04:47:31 UTC 2008


On Fri, 1 Aug 2008 09:24:53 -0700
"Jack Vogel" <jfvogel at gmail.com> wrote:

> If the poster gives me EXACT hardware list I will see about repro'ing the
> problem inhouse. We do not do much of anything with laptops but I
> will see. Oh and a pciconf would help too.

Hi Jack,

pciconf -lv gives me:

em0 at pci0:2:0:0:	class=0x020000 card=0x200117aa chip=0x109a8086
rev=0x00 hdr=0x00 vendor     = 'Intel Corporation'
    device     = '82573L Intel PRO/1000 PL Network Adaptor'
    class      = network
    subclass   = ethernet


One thing, I have to add. I described the behavior wrong. The adapter
actually IS available in the interface list, but it gets "no carrier".
Sorry for that.

This is what I get from ifconfig when the NIC is plugged in:

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500 options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
	ether xx:xx:xx:xx:xx:xx
	media: Ethernet autoselect
	status: no carrier

All LEDs are off.

Device was found on boot:

em0: <Intel(R) PRO/1000 Network Connection 6.9.5> port 0x3000-0x301f
mem 0xee000 000-0xee01ffff irq 16 at device 0.0 on pci2
em0: Using MSI interrupt
em0: [FILTER]
em0: Ethernet address: xx:xx:xx:xx:xx:xx

-- 
Martin


More information about the freebsd-stable mailing list