From owner-freebsd-net Mon Feb 21 3:39:27 2000 Delivered-To: freebsd-net@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 8156337BC2B; Mon, 21 Feb 2000 03:39:21 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id UAA04827; Mon, 21 Feb 2000 20:39:19 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id UAA15500; Mon, 21 Feb 2000 20:39:18 +0900 (JST) Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id UAA00279; Mon, 21 Feb 2000 20:39:17 +0900 (JST) To: asmodai@bart.nl Cc: sameh@fr.clara.net Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) In-Reply-To: <20000221121246.F18727@noc.fr.clara.net> References: <20000221110752.A83583@lucifer.bart.nl> <20000221121246.F18727@noc.fr.clara.net> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000221204008M.shin@nd.net.fujitsu.co.jp> Date: Mon, 21 Feb 2000 20:40:08 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 29 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Just caught panic #3 on my Diablo newstransit box running 4.0 from the > > 7th of February. > We have 60GB IN/OUT each day, and it runs fine: > > $ uptime > 12:09PM up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64 > > 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan 5 14:36:46 CET 2000 > > Try downgrading ? Wmmm, there were much changes to tcp code for IPv6 support after Jan 5. I reviewed tcp_setpersist related code and such problem not seems to happen in correct state. Might there be incorrect memory over writing? Do you have any other date, such as *tt_persist value at panic? And is there any other person who experienced same kind of problem and have any hints to diagnose this? I'll again review my changes. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message