From owner-freebsd-stable@FreeBSD.ORG Thu Jan 19 10:08:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD15A16A41F for ; Thu, 19 Jan 2006 10:08:14 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id F350243D49 for ; Thu, 19 Jan 2006 10:08:13 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k0JA8FTH071482; Thu, 19 Jan 2006 08:08:16 -0200 (BRST) (envelope-from joao@matik.com.br) From: JoaoBR To: freebsd-stable@freebsd.org Date: Thu, 19 Jan 2006 08:08:03 -0200 User-Agent: KMail/1.8.3 References: <7.0.0.16.2.20060118090616.04209af8@micom.mng.net> <20060118023646.GA40276@rndsoft.co.kr> <7.0.0.16.2.20060119141302.04354d70@micom.mng.net> In-Reply-To: <7.0.0.16.2.20060119141302.04354d70@micom.mng.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200601190808.05418.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Cc: pyunyh@gmail.com, Ganbold Subject: Re: fxp0: device timeout and sk0: watchdog timeout problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2006 10:08:14 -0000 On Thursday 19 January 2006 04:14, 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 > Jan 19 12:59:20 gw kernel: fxp0: device timeout > Jan 19 12:59:52 gw kernel: fxp0: device timeout > Jan 19 13:00:23 gw kernel: fxp0: device timeout > Jan 19 13:00:29 gw kernel: sk0: watchdog timeout > Jan 19 13:00:52 gw kernel: fxp0: device timeout > Jan 19 13:01:05 gw kernel: sk0: watchdog timeout > > Ganbold > hi=20 maybe a stupid hint but did you checked the TP cable and pin order? I often= =20 saw such problems when a gigabit connected to an older /10 HUB or when usin= g=20 incorrect pin orders on the cables or even to long cables Appearently the sk down events are gone on my server with Pyun's patched=20 drivers, did you checked if you compiled with them in the right place? My=20 servers are now almost 24h up with the new sk driver and none of them is=20 having the problem any more until now. Until this I had crontab run "ifconf= ig=20 sk0 up" all 10 minutes what helped me so long. On my SMP system when sk stopped it caused also watchdog timeout on all oth= er=20 NICs, on UP kernel not. Do you use interface polling? Check with vmstat -i because you may have=20 overlapping IRQs and you cards may not support it. Look into the MB manual= =20 and see which pci slots are shared and don't use them or try another bios=20 setting. What MB you are using? you may try ifconfig fxp link0 to load its microcode which could help but i= n=20 my opinion and experience the fxp cards are bad when using more than one an= d=20 I through them all out but interesting is that they work well on until=20 releng_5, btw the sk also works well on releng_5 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br