From owner-freebsd-current@FreeBSD.ORG Mon Jul 23 22:27:27 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CD2F16A417 for ; Mon, 23 Jul 2007 22:27:27 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id EECE513C46E for ; Mon, 23 Jul 2007 22:27:26 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by ug-out-1314.google.com with SMTP id o4so48118uge for ; Mon, 23 Jul 2007 15:27:25 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=NjICRbp8IQg3AlWAqCGaV3MsGUMkU64ooiOIs0Q+QU1K4iP500rnqZXr+NCAYNGiQyB32Yzz9szlyb/Aww2agxy8WeWjKqSr8kq/a7Mnlr5EuVNuRKChmiQRDCETseljgC4LZPT7Ned1KNealnVCC0bsamUKVEWUheZ1xe6xEic= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=fSjPK8W3LROxCtNVegkzow/PuIAOuttuZbJ4uYLiZ1TA0zmxr/GSdUIRcXDM0Zg+geDThNf3f+wI22g9VoBPJN6FTDfXnYtaTBrGoHSHJdPEkgSfPGzYouz/1Cz7cs+IvrBPGrXpBO+kwTjoWz+tPyEjri0apnw6rCxgfm5FZRk= Received: by 10.66.225.1 with SMTP id x1mr158133ugg.1185229645466; Mon, 23 Jul 2007 15:27:25 -0700 (PDT) Received: from ?151.75.245.150? ( [151.75.245.150]) by mx.google.com with ESMTPS id c14sm7558754nfi.2007.07.23.15.27.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Jul 2007 15:27:25 -0700 (PDT) Message-ID: <46A52B19.9060909@FreeBSD.org> Date: Tue, 24 Jul 2007 00:26:33 +0200 From: Attilio Rao User-Agent: Thunderbird 1.5 (X11/20060526) MIME-Version: 1.0 To: Jeff Roberson References: <20070721174631.S561@10.0.0.1> <20070723152212.O561@10.0.0.1> In-Reply-To: <20070723152212.O561@10.0.0.1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: Attilio Rao Cc: current@freebsd.org, Matt Subject: Re: ULE status, invalid load, buildkernel times. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2007 22:27:27 -0000 Jeff Roberson wrote: > On Mon, 23 Jul 2007, Matt wrote: > >> On 7/21/07, Jeff Roberson wrote: >>> I have a patch available at: >>> >>> http://people.freebsd.org/~jeff/ulehtt.diff >>> >>> This resolves issues in the code that handles HTT enabled processors and >>> also adds some ULE information to bootverbose on SMP systems. Peter >>> Wemm >>> has a seperate patch that fixes a bug where some amd64 cpus were still >>> being misidentified as HTT. Those of you with invalid loads either have >>> Hyper-threading CPUs or misidentified amd cores. You should expect >>> slightly poorer performance as long as your cores are misidentified but >>> the bad loads should be fixed. >>> >>> I also believe that the buildkernel/world times are now significantly >>> improved. If this is not the case for you please send a mail. Any >>> other >>> performance data is appreciated. >>> >>> Thanks, >>> Jeff >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >>> >> >> -current system with sources update July 22 at approx. 3PM central >> time with the ulehtt.diff patch applied experienced a panic this >> afternoon while restarting a local Apache Tomcat server. Backtrace >> information is shown below. Unclear to me whether or not the patch >> and the panic are related. > > I suspect that this is unrelated to my patch but I can't say for > certain. There have been some kse locking problems that Attilio has a > patch for. I believe it went in today. Hopefully he will comment. This is exactly the same bug pav@ experienced on amd64 machines some weeks ago. Basically, there is a race with ku_owner accesses which make it unconsistent in SMP / PREEMPTION systems. I committed a fix for that, but since I broke buildkernel too with that commit I would suggest to wait until the fix for a correct kernel building won't be committed (it should be rather soon though) and than to CVSup again sources. Thanks, Attilio