Re: kern/40345: nfe: watchdog timeout

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

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

From: Christoph Egger <Christoph_Egger%gmx.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
 netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/40345: nfe: watchdog timeout
Date: Thu, 08 Jan 2009 23:27:43 +0100

 > nfe is not working/usable, periodic "nfe0: watchdog timeout" on network 
 > activity.
 > tcpdump on this host shows all outgoing packets (for example ping from this 
 > host)
 > and no incoming packets (eg. icmp to this host). No outgouing packets on the 
 > wire at all.
 > 
 > MB: Biostar nf4st-a9 ( 
 > http://www.biostar-usa.com/mbdetails.asp?model=NF4ST-A9 ) 
 > Chipset: nForce4
 > 
 > dmesg:
 > nfe0 at pci0 dev 10 function 0: vendor 0x10de product 0x0057 (rev. 0xa3)
 > nfe0: interrupting at ioapic0 pin 21
 > nfe0: Ethernet address 00:14:2a:7f:ba:ea
 > ciphy0 at nfe0 phy 17: Cicada CS8201 10/100/1000TX PHY, rev. 3
 > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 > 1000baseT-FDX, auto
 > 
 > lspci:
 > 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
 
 Give this a try:
 
 disable ciphy in userconf and check if ukphy attaches on nfe0.
 If it does, test if you still have watchdog timeouts or not.
 
 If you still have watchdog timeouts, then the problem is nfe0.
 If there are no more watchdog timeouts, then the problem is ciphy0.
 
 Christoph