From owner-freebsd-current@FreeBSD.ORG  Fri Nov 28 01:55:58 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 C11C316A4CE; Fri, 28 Nov 2003 01:55:58 -0800 (PST)
Received: from kai.xtaz.net (82-32-25-111.cable.ubr04.azte.blueyonder.co.uk
	[82.32.25.111])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6070C43FBD; Fri, 28 Nov 2003 01:55:57 -0800 (PST)
	(envelope-from matt@xtaz.net)
Received: from xtaz.net (tao.xtaz.net [10.0.0.2])
	by kai.xtaz.net (Postfix) with ESMTP
	id 0494C8FDA3; Fri, 28 Nov 2003 09:55:55 +0000 (GMT)
Message-ID: <3FC71BAB.2040003@xtaz.net>
Date: Fri, 28 Nov 2003 09:55:55 +0000
From: Matt Smith <matt@xtaz.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031101
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andre Oppermann <andre@freebsd.org>
References: <3FC67F2E.EBF83B89@freebsd.org>
In-Reply-To: <3FC67F2E.EBF83B89@freebsd.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: sam@errno.com
cc: freebsd-current@freebsd.org
Subject: Re: Fix for 5.2-BETA lockup problems
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Nov 2003 09:55:58 -0000

Andre Oppermann wrote:
> Hello all,
> 
> I've found what probably is going wrong in tcp_hostcache.  The problem is me
> cutting corners (what goes around comes around...) in tcp_hc_insert when the
> bucket limit is reached.  I made the #if 0 too big and the bucket was not
> removed from the tailqueue when we hit the bucket limit.  A couple of lines
> later it is inserted again as head element which leads to an infinite loop
> either when the next lookup on the same bucket row is done, or when the
> the tcp_hc_purge function is run to timeout the entries.
> 
> Please try the attached patch which should fix it.
> 

This appears to have succesfully cured my lockup. I now have the 
original kernel config booted again with full inet6 etc and it's not 
locked up.

Regards, Matt.