Subject: kern/30490: wm(4) fails to link up if configured as 100baseT-FDX at the boot time
To: None <email@example.com, firstname.lastname@example.org,>
From: None <email@example.com>
Date: 06/10/2005 11:22:00
>Synopsis: wm(4) fails to link up if configured as 100baseT-FDX at the boot time
>Arrival-Date: Fri Jun 10 11:22:00 +0000 2005
>Originator: UMEZAWA Takeshi
Internet Initiative Japan
NetBSD idgw07.iij.ad.jp 1.6.2_STABLE NetBSD 1.6.2_STABLE (GENERIC) #0: Mon May 2 11:40:58 JST 2005 firstname.lastname@example.org:/usr/src/sys/arch/i386/compile/GENERIC i386
When wm(4) is connected to switching hub port which is 100/full fixed
(not autonegotiated), and wm is also configured as 100/full
(by /etc/ifconfig.wm0), it fails to link up at the boot time.
This problem relies on switching hub, as far as I know.
For example, it occurs if we use Catalyst 3512, and does not occur
if we use CentreCOM GS916GT.
On the other hand, all of i8254x chips which I tested makes this problem.
If the cable is unplugged and re-plugged, wm links up successfully.
But after rebooting, the link is down again.
This problem does not occur under FreeBSD em(4) driver.
Probably wm driver lacks some workarounds which exist in em driver.
described in Full Description.