From owner-freebsd-current@FreeBSD.ORG Sun Jan 23 14:30:19 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 470EF16A4D0 for ; Sun, 23 Jan 2005 14:30:19 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB64A43D1D for ; Sun, 23 Jan 2005 14:30:18 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0NETx88047814; Sun, 23 Jan 2005 09:29:59 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0NETvJ9047811; Sun, 23 Jan 2005 14:29:59 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 23 Jan 2005 14:29:57 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ganbold In-Reply-To: <6.2.0.14.2.20050110151705.03f2f470@202.179.0.80> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: fxp0: device timed out problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 14:30:19 -0000 On Mon, 10 Jan 2005, Ganbold wrote: > I'm having trouble on FreeBSD 5.3 with squid-2.5.7. Squid installed from > ports collection. > > cache4# uname -an > FreeBSD cache4.micom.mng.net 5.3-STABLE FreeBSD 5.3-STABLE #2: Wed Dec 15 > 18:26:14 ULAT > 2004 tsgan@cache4.micom.mng.net:/usr/obj/usr/src/sys/CACHEK i386 > > After few hours machine hangs and stops responding saying following > error: > > fxp0: device timed out. > > I turned off debug.mpsafenet to 0 and it seems like problem goes away. > Is this problem related to network stack? Or is it related to fxp driver? It's most likely a problem with the device driver or interrupt configuration on your system. There are a couple of other variables you might try frobbing: - Use of ACPI to configure the hardware - Use of "device apic" if the system is non-SMP Usually a device timed out error is related to interrupts from the device not being delivered, being delivered improperly, etc. Does your dmesg contain any references to interrupt storms? Once the above message has printed, do you see any further interrupts on the fxp interrupt source when checking intermittently with "systat -vmstat 1" or "vmstat -i"? Robert N M Watson