From owner-freebsd-current@FreeBSD.ORG  Sun May 14 23:04:05 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: 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 8B79C16A42C;
	Sun, 14 May 2006 23:04:05 +0000 (UTC)
	(envelope-from sobomax@FreeBSD.org)
Received: from sippysoft.com (gk.360sip.com [72.236.70.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E521343D55;
	Sun, 14 May 2006 23:04:04 +0000 (GMT)
	(envelope-from sobomax@FreeBSD.org)
Received: from [192.168.1.73] (S0106000f3d63befd.vs.shawcable.net
	[70.71.19.119]) (authenticated bits=0)
	by sippysoft.com (8.13.6/8.13.6) with ESMTP id k4EN41Nx007390
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 14 May 2006 16:04:03 -0700 (PDT)
	(envelope-from sobomax@FreeBSD.org)
Message-ID: <4467B75F.2030406@FreeBSD.org>
Date: Sun, 14 May 2006 16:03:59 -0700
From: Maxim Sobolev <sobomax@FreeBSD.org>
Organization: Sippy Software, Inc.
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: "current@freebsd.org" <current@FreeBSD.org>, Nate Lawson <njl@FreeBSD.org>,
	John Baldwin <jhb@FreeBSD.org>
Content-Type: text/plain; charset=KOI8-U; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: SMP on MacBook Pro, some new info
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Sun, 14 May 2006 23:04:05 -0000

Hi,

I have discovered that it's possible with a very good repeatability (90% 
or more) to start the second core by pressing power button promptly 
during the 5 second period when BSP have sent startup IPIs already and 
is waiting for the AP going online. I am not sure how to interpret this 
info - perhaps there is some problem with caching BSPs LAPIC writes, and 
interrupt generated by the power button causes the cache to be flushed.

Any ideas?

-Maxim