fxp0: device timeout and sk0: watchdog timeout problems

[Pyun YongHyeon]

On Thu, Jan 19, 2006 at 03:52:58PM +0800, Ganbold wrote:
 > Hi,
 > 
 > At 03:16 PM 1/19/2006, you wrote:
 > >On Thu, Jan 19, 2006 at 02:14:13PM +0800, Ganbold wrote:
 > > > I have same problem even after updating the sk code to the latest:
 > > >
 > > > Jan 19 12:58:53 gw kernel: fxp0: device timeout
 > > > Jan 19 12:59:10 gw kernel: sk0: watchdog timeout
 > > > Jan 19 12:59:10 gw kernel: sk0: link state changed to DOWN
 > > >
 > >
 > >Does interface down and up help your situation?
 > 
 > This server is located 370km from where I'm now. People there just 
 > reboot the server.
 > 
:-(

 > >It would be great to know what mwchan is used if your application
 > >was blocked.
 > 
 > mwchan?
 > 

You can check it with ps(1) or top(1).

 > >Would you try another onboard NIC with fxp to narrow down the issue?
 > 
 > Hard to say since it is on remote site. I could ask person there.
 > 
 > >Since it's hard to reproduce the problem on my system I need more
 > >information. Would you show me more information for your network
 > >configuration and how to reproduce it?
 > 
 > This machine is doing NAT, ipfw and it has squid from ports. It seems 
 > like 3GB-9GB web traffic is going through per day.

Hmm, it seems it's very complex setup. I guess diabling ipfw/NAT
is not a option to you. Do you use "uid" rule to check packets
in your ipfw rule? The "uid" is known to have issues on system
with debug.mpsafenet=1.

 > gw# ifconfig -a
 > sk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 >         options=2b<RXCSUM,TXCSUM,VLAN_MTU,JUMBO_MTU>
 >         inet 175.176.1.11 netmask 0xffff0000 broadcast 175.176.255.255
 >         ether 00:11:95:e1:7d:16
 >         media: Ethernet autoselect (1000baseTX <full-duplex,flag0,flag1>)
 >         status: active
 > pcn0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
 >         ether 00:06:29:50:e2:3c
 >         media: Ethernet autoselect (none)
 >         status: no carrier
 > fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 >         options=b<RXCSUM,TXCSUM,VLAN_MTU>
 >         inet x.x.x.x netmask 0xfffffff0 broadcast x.x.x.x
 >         ether 00:03:47:e0:64:3c
 >         media: Ethernet autoselect (100baseTX <full-duplex>)
 >         status: active
 > 
 > Other onboard NIC is pcn:
 > pcn0 at pci0:9:0:  class=0x020000 card=0x20001014 chip=0x20001022 
 > rev=0x36 hdr=0x00
 >     vendor   = 'Advanced Micro Devices (AMD)'
 >     device   = 'Am79C970/1/2/3/5/6 PCnet LANCE PCI Ethernet Controller'
 >     class    = network
 >     subclass = ethernet
 > I heard this card also might have some problems, but I'm not sure. 
 > Correct me if I'm wrong.
 > 

Sorry, I don't know how well pcn(4) works.
Anyway I'll try to reproduce it here and let you know if I have
more information.

-- 
Regards,
Pyun YongHyeon