Date: Tue, 15 May 2007 07:51:23 +0200 From: Randy Bush <randy@psg.com> To: LI Xin <delphij@delphij.net> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: em driver Message-ID: <46494A5B.9080808@psg.com> In-Reply-To: <464940C6.2010808@delphij.net> References: <17993.9973.237807.213217@roam.psg.com> <46492B3B.3020305@delphij.net> <46492CFC.6060506@psg.com> <464940C6.2010808@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46494A5B.9080808>