bge && amd systems- a curious side note...

[Kevin Oberman]

> Date: Fri, 20 Apr 2007 15:41:58 -0700
> From: "Matthew Jacob" <lydianconcepts at gmail.com>
> Sender: owner-freebsd-current at freebsd.org
> 
> I have an AMD box graciously given to me by David O'Brien. It has a
> bge chip on it. This box has suffered over the spasms of the bge
> driver of late in current.
> 
> What *does* seem to happen is that it hangs during DHCP discovery- but
> if I ping it, it seems to unfreeze (see below). Just an FYI for those
> who are interested....
> 
> 
> bge0: no link .....bge0: link state changed to UP
>  got link
> DHCPDISCOVER on bge0 to 255.255.255.255 port 67 interval 3
> DHCPDISCOVER on bge0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on bge0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on bge0 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on bge0 to 255.255.255.255 port 67 interval 13
> <<<< Sent Ping at this point >>>>
> DHCPOFFER from 172.16.1.79
> DHCPOFFER from 172.16.1.79
> DHCPOFFER already seen.
> DHCPOFFER from 172.16.1.79
> DHCPOFFER already seen.
> DHCPREQUEST on bge0 to 255.255.255.255 port 67
> DHCPACK from 172.16.1.79

Interesting. I often see similar behavior on my i386 system with a
bge. Clearly not an amd64 only issue.

I am a bit curious as to how you ping it before it gets an address and
from where you ping it.

I get similar results from killing the dhcpclient and starting it again.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 224 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070420/c71f38fc/attachment.pgp