From owner-freebsd-bugs@FreeBSD.ORG Mon Sep 25 15:13:11 2006 Return-Path: X-Original-To: freebsd-bugs@FreeBSD.org Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CBDC16A4A0; Mon, 25 Sep 2006 15:13:11 +0000 (UTC) (envelope-from andrew@rinet.ru) Received: from mowgli.rinet.ru (merlin.rinet.ru [195.54.192.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15B1843D60; Mon, 25 Sep 2006 15:13:06 +0000 (GMT) (envelope-from andrew@rinet.ru) Received: from [192.168.0.101] (16-113.admiral.tvoe.tv [87.237.113.16]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mowgli.rinet.ru (Mail Transport Agent) with ESMTP id EFC8235; Mon, 25 Sep 2006 19:13:04 +0400 (MSD) In-Reply-To: <200609251212.k8PCCBM1099938@freefall.freebsd.org> References: <200609251212.k8PCCBM1099938@freefall.freebsd.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andrew Kolchoogin Date: Mon, 25 Sep 2006 19:13:01 +0400 To: Bruce M Simpson X-Mailer: Apple Mail (2.752.2) Cc: freebsd-bugs@FreeBSD.org Subject: kern/96413: NULL inpcb pointer in tcp_timewait() X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 15:13:11 -0000 On 25.09.2006, at 12:12, Bruce M Simpson wrote: > This may have been fixed by rev 1.281.2.9 on RELENG_6. > Can you update sources and verify if the problem has been fixed? No, it's impossible - the machine in question is fairly heavy loaded Internet server resides on remote Data Centre. I'll upgrade it after 6.2-R, and for now I'll try to sumulate similar network activity using my laptop with fairly recent RELENG_6. > It would be helpful if you could give more detailed information > about what > you're doing with the system when this happens. There is an /usr/ports/net-mgmt/ng_ipacct port had built and installed, and me set up a Web server moderate-to-heavy loaded. All worked fine, and I was happy. :) But some time after I have raised number of processes Apache initially starts up to 256, and kernel goes to panic under some network load -- as I'm not monitoring that machine 24x7, I can't precisely say what kind of load crashes the machine. -- Yours Andrew Kolchioogin ... Only two things are infinite - the Universe and human stupidity, and I'm not sure about the former. A. Einstein.