> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> HI,
> 
>    I'll ask again.  I'm running NetBSD/beta on a Intel® Entry Server Board
> SE7210TP1-E that uses an i82547GI giga-bit ether.   dmesg reports
> 
> - ---->~
> pm02[2]$ dmesg | grep wm
> wm0 at pci1 dev 1 function 0: Intel i82547GI 1000BASE-T Ethernet, rev. 0
> wm0: interrupting at irq 5
> wm0: Communication Streaming Architecture
> wm0: 65536 word (16 address bits) SPI EEPROM
> wm0: Ethernet address 00:...... (deleted)
> igphy0 at wm0 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
> 
>    I'm running the same version of NetBSD on another machine (Dell 750)
> that 
> reports the same ethernet chip, but a different EEPROM.   It reports
> 
>  ---->~
> pm30[1]$ dmesg | grep wm
> wm0 at pci1 dev 1 function 0: Intel i82547GI 1000BASE-T Ethernet, rev. 0
> wm0: interrupting at irq 3
> wm0: Communication Streaming Architecture
> wm0: 64 word (6 address bits) MicroWire EEPROM
> wm0: Ethernet address 00:...... (deleted)
> igphy0 at wm0 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
> 
> Here is the problem I'm having.
> 
>    The Dell is working just fine.  No problems no nothing.
> 
>    The Intel board machines are having problems when using the wm0
> interface.  
> Specifically, after running a while, they turn off power to the entire 
> machine and report a hardward error on the front pannel.   I've also
> noticed 
> extreme delays in using ssh to get into the machines.   In some cases it
> is 
> only 1 second and others as much as a minute.   This can't be a reverse
> DNS 
> issue because the primary DNS machines is on the same "wire".
> 
>    Has anyone else seen a machine turn off its power when using the wm 
> interface?   (This board has 2 ethernet interfaces and runs great with no 
> problems when using the fxp driver using the other interface.)   Does
> anyone 
> know what the different EEPROM have to do with the functioning of this 
> interface and whether it requires changes to NetBSD.  
> 
>    Intel (and the local distributor) is saying that this is a NetBSD
> problem 
> and not a hardware problem.
> 
>     Thanks for any help!
> 
> - --Phil
> 
> - -- 
> Phil Nelson                       NetBSD: http://www.netbsd.org
> e-mail: phil@cs.wwu.edu           Coda: http://www.coda.cs.cmu.edu
> http://www.cs.wwu.edu/nelson 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (NetBSD)
> 
> iD8DBQFBonUlzbodwsP3RI0RAhu2AJ9yZ7U7NPb5gX2T0FLSl0JGBm8nTACgkb4d
> EQbTlW5rBBsS0ZrmorEy3pk=
> =xB7u
> -----END PGP SIGNATURE-----
> 
Hej Phil,

I'm running a Tyan 7210 Board with Intel Chipset with wm0 & wm1 without any
Problems.

wm0 at pci1 dev 1 function 0: Intel i82547GI 1000BASE-T Ethernet, rev. 0
wm0: interrupting at irq 5
wm0: 32-bit 33MHz PCI bus
wm0: 65536 word (16 address bits) SPI EEPROM
wm0: Ethernet address 00:e0:81:61:85:22
igphy0 at wm0 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
igphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX
, auto
wm1 at pci3 dev 2 function 0: Intel i82541GI 1000BASE-T Ethernet, rev. 0
wm1: interrupting at irq 9
wm1: 32-bit 33MHz PCI bus
wm1: 64 word (6 address bits) MicroWire EEPROM
wm1: Ethernet address 00:e0:81:61:85:22
igphy1 at wm1 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
igphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX
, auto


Regards, Zafer.