From owner-freebsd-questions@FreeBSD.ORG Fri Jul 11 18:27:17 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0F9F37B401 for ; Fri, 11 Jul 2003 18:27:17 -0700 (PDT) Received: from mail.listas.com.mx (krusty.intranet.com.mx [200.33.246.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 044B243FBF for ; Fri, 11 Jul 2003 18:27:17 -0700 (PDT) (envelope-from jbiquez@icsmx.com) Received: from intra1ofi.icsmx.com ([200.33.246.4]) by mail.listas.com.mx (8.12.8/8.12.8) with ESMTP id h6C1M4Pk016923 for ; Fri, 11 Jul 2003 20:24:35 -0500 (CDT) (envelope-from jbiquez@icsmx.com) Message-Id: <5.1.0.14.2.20030711201531.02194450@mail.icsmx.com> X-Sender: jbiquez@mail.icsmx.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 11 Jul 2003 20:23:14 -0500 To: "freebsd-questions@freebsd.org" From: Jorge Biquez In-Reply-To: <20030711205321.279c582a.rod.person@hotpop.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: WhatchDog Error on a Lan Card. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jul 2003 01:27:18 -0000 Hello all. Today I started receiving this error on the lan card. r10: WATCHDOG TIMEOUT And seems like the TCP/IP services stop passing thought the card. The machine continues running without seeing the world but no other errors beside the above on the console. One thing I notices is that if I try to ping any machine I receive and "overflow error". If I restart the machine everything works normally again. The machine is running 4.8 Stable, running on a PIII - 1.0 Ghz with 512 RAM and more than enough free space. The machine is running only Apache with some load. I changed the card with another of the same brand and type, its backup since I always buy 2 same cards for each equipment, just in case. After a few hours and under some load the machine send the same error. Any ideas on what could be causing the problem? Thanks in advance. JB