em driver

Jack Vogel jfvogel at gmail.com
Tue May 15 07:57:49 UTC 2007


On 5/14/07, Randy Bush <randy at psg.com> wrote:
> > Is there anything shows up in system log?
>
> nope.  and i managed to get in oob while it was borked once, and ifconfig
> looked good,
>
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         options=18b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWCSUM,TSO4>
>         ether 00:30:48:80:b3:72
>         inet 147.28.0.35 netmask 0xffffff00 broadcast 147.28.0.255
>         inet 147.28.0.41 netmask 0xffffffff broadcast 147.28.0.41
>         media: Ethernet autoselect (1000baseTX <full-duplex>)
>         status: active
>
> dmesg normal
>
> em0: <Intel(R) PRO/1000 Network Connection Version - 6.5.0> port \
> 0xa000-0xa01f m
> em 0xfd000000-0xfd01ffff irq 18 at device 1.0 on pci1
> em0: Ethernet address: 00:30:48:80:b3:72
> em0: [FILTER]
>
> etc.
>
> but i was just hoping that this was a known issue and someone would tell me
> it was indeed fixed by the cvsup and build i just did.  if i get more time
> to debug, as opposed to just reverting, i will whine more eloquently.

I understand where you're coming from, sometimes there's a quick and
easy answer :) But unfortunately this sounds like nothing I've heard about,
which means we need more data of some sort, you left out pciconf -l, I
need to know exactly what kind of adapter it is.

Whenever I see weird things like this the first suspect in my mind is that
annoying management subsystem, this new driver tries to keep the beast
under control, but perhaps there's some problem.

Oh, and BTW, do make sure you have the latest code, although my
last change is such that if it were that it would be much more obvious.

Jack


More information about the freebsd-current mailing list