From owner-freebsd-current@FreeBSD.ORG Tue May 16 03:26:11 2006 Return-Path: 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 3F60B16A4DD; Tue, 16 May 2006 03:26:11 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id B024543D4C; Tue, 16 May 2006 03:26:08 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k4G3Q6bJ019502; Mon, 15 May 2006 23:26:07 -0400 X-ORBL: [71.139.38.236] Received: from [10.0.0.53] (ppp-71-139-38-236.dsl.snfc21.pacbell.net [71.139.38.236]) by pimout7-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id k4G3Q2Pq153170; Mon, 15 May 2006 23:26:07 -0400 Message-ID: <446945FA.7020103@root.org> Date: Mon, 15 May 2006 20:24:42 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Maxim Sobolev References: <4467B75F.2030406@FreeBSD.org> In-Reply-To: <4467B75F.2030406@FreeBSD.org> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: "current@freebsd.org" , John Baldwin Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 May 2006 03:26:12 -0000 Maxim Sobolev wrote: > 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? My completely unresearched opinion is that the IPI is not reaching the AP or the response is getting lost. I don't know why. -- Nate