The following reply was made to PR kern/29629; it has been noted by GNATS.

From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org,
	netbsd-bugs@NetBSD.org
Subject: Re: kern/29629: PCI driver stge does not function with 2.0.1
Date: Wed, 9 Mar 2005 17:34:20 +0100

 On Tue, Mar 08, 2005 at 01:34:00PM +0000, florence.henry@obspm.fr wrote:
 > The ethernet PCI card "D-Link DGE 550T" does not work.
 > 
 > It is well recognized at boot time :
 > 
 > stge0 at pci2 dev 2 function 0: D-Link DL-4000 Gigabit Ethernet, rev. 12
 > stge0: interrupting at irq 10
 > stge0: Ethernet address 00:0f:3d:cd:e9:26
 > makphy0 at stge0 phy 1: Marvell 88E1000 Gigabit PHY, rev. 4
 > makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
 > 
 > ifconfig reports that it should be ok :
 > 
 > stge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 >         capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
 >         enabled=0
 >         address: 00:0f:3d:cd:e9:26
 >         media: Ethernet 100baseTX full-duplex (1000baseT full-duplex)
 
 Hum, it looks like you selected 100baseTX full-duplex, but the adapter
 thinks it's in 1000baseT full-duplex mode. I don't know if it's the
 real cause of your problem, or just that the driver doesn't update the
 values passed to ifconfig properly.
 What happens if you use 'media autoselect' ?
 
 >         inet 10.0.3.1 netmask 0xffffff00 broadcast 10.0.3.255
 
 > ---
 > Listening to the stge0 interface and sending a ping to a machine located on the same private network (10.0.3.3), and linked directly with a cross-cable to the D-link card :
 > 
 > # /root # tcpdump -i stge0 
 > tcpdump: listening on stge0
 > 14:19:02.358978 arp who-has 10.0.3.1 tell 10.0.3.3
 > 14:19:02.358986 10.0.3.1 > 10.0.3.3: icmp: echo request seq 5
 > 14:19:02.358988 arp reply 10.0.3.1 is-at 0:f:3d:cd:e9:26
 > 14:19:07.393062 arp who-has 10.0.3.1 tell 10.0.3.3
 > 14:19:07.393072 arp reply 10.0.3.1 is-at 0:f:3d:cd:e9:26
 > 
 > # /root # ping 10.0.3.3
 > PING 10.0.3.3 (10.0.3.3): 56 data bytes
 > ping: sendto: Host is down
 > ping: sendto: Host is down
 > ping: sendto: Host is down
 > ping: sendto: Host is down
 > ping: sendto: Host is down
 > 
 > ---
 > Listening to the stge0 interface and sending a ping from 10.0.3.3 :
 > 
 > # /root # tcpdump -i stge0 
 > tcpdump: listening on stge0
 > 14:18:31.325929 arp who-has 10.0.3.3 tell 10.0.3.1
 > 14:18:32.330039 arp who-has 10.0.3.3 tell 10.0.3.1
 > 14:18:33.340026 arp who-has 10.0.3.3 tell 10.0.3.1
 > 14:18:34.340024 arp who-has 10.0.3.3 tell 10.0.3.1
 > 14:18:35.340025 arp who-has 10.0.3.3 tell 10.0.3.1
 > 
 > The ping on the 10.0.3.3 machine results in a timeout, with 100.0% packet loss.
 > 
 > So it seems that the card hears well but cannot talk...
 
 What does 'netstat -i' show on the stge0 interface ?
 
 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --