From owner-freebsd-stable@FreeBSD.ORG Wed Feb 18 10:06:54 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF371106566C for ; Wed, 18 Feb 2009 10:06:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C8BAD8FC21 for ; Wed, 18 Feb 2009 10:06:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 77C1B46B0C; Wed, 18 Feb 2009 05:06:54 -0500 (EST) Date: Wed, 18 Feb 2009 10:06:54 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Mike Tancsa In-Reply-To: <200902180110.n1I1AaPL031693@pyroxene.sentex.ca> Message-ID: References: <200902180110.n1I1AaPL031693@pyroxene.sentex.ca> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Pete French Subject: Re: Big problems with 7.1 locking up :-( X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Feb 2009 10:06:55 -0000 On Tue, 17 Feb 2009, Mike Tancsa wrote: > At 05:38 PM 1/29/2009, Robert Watson wrote: > >> On Fri, 9 Jan 2009, Pete French wrote: >> >>> I have a number of HP 1U servers, all of which were running 7.0 perfectly >>> happily. I have been testing 7.1 in it's various incarnations for the last >>> couple of months on our test server and it has performed perfectly. >>> >>> So the last two days I have been round upgrading all our servers, knowing >>> that I had run the system stably on identical hardware for some time. >> >> For those following this other than Pete, who I've been in private >> correspondence with: it seems that he is running into two different >> deadlocks in the routing code. One of them (at least) is triggered by a >> lock order problem relating to the processing of ICMP redirects -- uncommon >> in most configurations, but quite a few on his network, which triggers >> quickly under load. Kip Macy has corrected at least one (both?) problems >> in head, and plans to MFC the fixes in the near future. We'll follow up >> further once the fixes are merged, and if any further problems transpire. > > Do you have any other details about these issues ? Were the fixes ever MFC'd Hi Mike, et al, I gave Kip a ping about MFCing the fixes and he said he would do that, but has apparently been preoccupied. I'm working on an MFC patch currently, but as I'm not all that familiar with the routing code, and the bug fixes were mixed with feature enhancements in his original commits, it will probably take me a bit longer to produce a candidate patch. Robert N M Watson Computer Laboratory University of Cambridge