From owner-freebsd-stable@FreeBSD.ORG Wed Aug 20 02:12:55 2003 Return-Path: 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 BDD9916A4C0 for ; Wed, 20 Aug 2003 02:12:55 -0700 (PDT) Received: from mest.ru (ns.mest.ru [81.176.64.4]) by mx1.FreeBSD.org (Postfix) with SMTP id E6FA943F3F for ; Wed, 20 Aug 2003 02:12:53 -0700 (PDT) (envelope-from tarkhil@over.ru) Received: (qmail 33434 invoked by uid 1003); 20 Aug 2003 09:12:51 -0000 From: tarkhil@over.ru Date: Wed, 20 Aug 2003 13:12:51 +0400 To: stable@freebsd.org Message-ID: <20030820091251.GA27377@mest.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: Strange fork-trlated problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2003 09:12:56 -0000 Hello! This problem has been persisted on two different MBs (diffrent CPUs, different memory), half dozen of different NICs, 4.7-RELEASE and 4.8-RELEASE. Common router/NAT (ipnat, kld loaded) behaves very strangely after about 10-20 minutes of work. New processes doesn't create anymore, process trying to fork looks in top having -20 PRI and "temp" STATE. I was unable to find out what that state means. New TCP connections from internal networks fails to create as well. Top also shows absurdly high Interrupt CPU state (from 5 to even 50 sometimes!). I will try to work without ipnat. But surely it doesn't suppose to "work" that way. It should not be hardware-related, save possibly hard disk (the only common thing). Computer pings from outside well. Help please. Alex.