From owner-freebsd-stable@FreeBSD.ORG Wed Jan 14 14:16:44 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 15E8F106567F; Wed, 14 Jan 2009 14:16:44 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from constantine.ticketswitch.com (constantine.ticketswitch.com [IPv6:2002:57e0:1d4e:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id C560D8FC1A; Wed, 14 Jan 2009 14:16:43 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from dilbert.rattatosk ([10.64.50.6] helo=dilbert.ticketswitch.com) by constantine.ticketswitch.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN6Xt-000AtJ-Qj; Wed, 14 Jan 2009 14:16:37 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LN6Xt-0001Je-On; Wed, 14 Jan 2009 14:16:37 +0000 To: rwatson@FreeBSD.org In-Reply-To: Message-Id: From: Pete French Date: Wed, 14 Jan 2009 14:16:37 +0000 Cc: freebsd-stable@freebsd.org, drosih@rpi.edu, rblayzor.bulk@inoc.net 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, 14 Jan 2009 14:16:44 -0000 > effect on control flow, unlike, say, WITNESS, which significantly distorts > timing. Is there any chance you picked up any of the recent fixes that went > into RELENG_7 without noticing, and that perhaps one of those did it? With I'm pretty certian of that - I hav just been changing kernel config files, I havent actually csup'd at all. > regard to what to do: if you didn't pick up a fix without noticing, yeah, I > think it's worth testing the hypothesis that BREAK_TO_DEBUGGER fixed (or at > least, masked) the problem. OK. I think I need at leats 4 kernels to try here: GENERIC (which should show the problenm), my original DEBUG (which also shows the problem) plus both of those with BREAK_TO_DEBUGGER included to see if that fixes it. Can I just add BREAK_TO_DEBUGGER on its own to a config file ? I was wondering if I need to include one of the other debugger options so that it has something to break to ? > FWIW, I suspect the various reports we are seeing reflect more than one > problem, and that they must be relatively edge-case individually but reports > of a few problems have lead to more "coming out of the woodwork". Obviously, > the problems are not edge-case to the people experiencing them... I was thinking that too - I've been guilty of this in the past too, lumping my problem in with others under the asusmption that it's all the same. This is onbiously pretty rare - out of 24 of the HP servers the problems only crops up on 4 of them. But there is nothing dfferent about those 4. I will let you know what my various kerenl compiles give me - am buolding again from scratch, which is slow with WITNESS enabled. -pete.