From owner-freebsd-current@FreeBSD.ORG Mon Jan 10 07:27:54 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 5C62E16A4CE; Mon, 10 Jan 2005 07:27:54 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7143243D49; Mon, 10 Jan 2005 07:27:52 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1Cnu1t-0005rC-OP; Mon, 10 Jan 2005 15:31:58 +0800 Message-Id: <6.2.0.14.2.20050110151705.03f2f470@202.179.0.80> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 10 Jan 2005 15:27:33 +0800 To: freebsd-current@freebsd.org From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: rwatson@freebsd.org Subject: 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: Mon, 10 Jan 2005 07:27:54 -0000 Hi, 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. kernel compiled with following options: options MSGMNB=8192 # max # of bytes in a queue options MSGMNI=40 # number of message queue identifiers options MSGSEG=512 # number of message segments per queue options MSGSSZ=64 # size of a message segment options MSGTQL=2048 # max messages in system options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=100 options IPDIVERT #divert sockets options IPFIREWALL_FORWARD #packet destination changes device gre # GRE tunneling Is this problem related to network stack? Or is it related to fxp driver? thanks, Ganbold