kern/62094: 3com 940 gigabit ethernet dhcp failure

Kenneth Culver culverk at sweetdreamsracing.biz
Thu Jan 29 20:00:29 PST 2004


>Number:         62094
>Category:       kern
>Synopsis:       3com 940 gigabit ethernet dhcp failure
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 29 20:00:25 PST 2004
>Closed-Date:
>Last-Modified:
>Originator:     Kenneth Culver
>Release:        FreeBSD 5.2-CURRENT i386
>Organization:
none	
>Environment:
System: FreeBSD ken.sweetdreamsracing.biz 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Thu Jan 29 11:12:54 EST 2004 culverk at ken.sweetdreamsracing.biz:/usr/src/sys/i386/compile/KEN i386

>Description:
	On an Asus K8V Deluxe motherboard (athlon 64) in both the i386 and
	amd64 versions of FreeBSD, when the machine first boots up, and
	dhclient starts, it hangs, and eventually times out. During this time
	the lights on the switch showing whether the ethernet card is connected
	keep flashing on and off (not the activity lights but the ones that
	show whether it's actually got a connection).

	A few minutes after boot (and breaking out of the dhclient that happens
	on boot using ctrl-c) I can type "dhclient sk0" on the commandline,
	and there is no problem. This leads me to believe that the auto-
	negotiaton code for my PHY is messed up. Here is the relevent output
	from dmesg:

skc0: <3Com 3C940 Gigabit Ethernet> port 0xdc00-0xdcff mem 0xfdc00000-0xfdc03fff irq 10 at device 10.0 on pci0
skc0: 3Com Gigabit LOM (3C940)
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:0c:6e:ba:a7:49
miibus0: <MII bus> on sk0
e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto

>How-To-Repeat:
	All that's needed is to have this on-board ethernet controller, and try
	to use dhclient to get network configuration.	
>Fix:
	Currently the only workaround is to set a static ip, and hope
	nobody else is using it.
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list