From owner-freebsd-current@freebsd.org Sun Nov 27 11:46:46 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82515C589D7 for ; Sun, 27 Nov 2016 11:46:46 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 65B7CF46 for ; Sun, 27 Nov 2016 11:46:46 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: by mailman.ysv.freebsd.org (Postfix) id 623D5C589D6; Sun, 27 Nov 2016 11:46:46 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60187C589D5 for ; Sun, 27 Nov 2016 11:46:46 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C0C3BF45; Sun, 27 Nov 2016 11:46:44 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.walstatt.dynvpn.de ([92.225.34.14]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LtJ5T-1cqJy33z0F-012sex; Sun, 27 Nov 2016 12:46:37 +0100 Date: Sun, 27 Nov 2016 12:46:31 +0100 From: "O. Hartmann" To: John Baldwin Cc: current@freebsd.org Subject: Re: Please test EARLY_AP_STARTUP Message-ID: <20161127124631.1e4f1fb0@thor.walstatt.dynvpn.de> In-Reply-To: <7005233.xZtqgRZ2t6@ralph.baldwin.cx> References: <7005233.xZtqgRZ2t6@ralph.baldwin.cx> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/eIRlBuYrefrJmtsNWEQCL9q"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:xDO5CYeTJc3LWGOnuOVCmNJsal6qHHCW1D6moGpop6oZtqBapw/ Y0wyH1qWOFDe3e3qGFIkqFlN84NDqGKuORrp1D3GCwKhOXglGxsYje37d9SGNwU4a0iUx3+ mxoeWHTZrC4kMI5P5XQhKWJlD/2dFM/fcgjhHTHrD+d7z8DSgcFy1JXWZByweTiUZOXmFxT 7lN+SNLGBN36GU0TadaiQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:mh8mehERQDA=:Dwdlj/BTiBaDXTrqIeTSLX tpDGDUGo9UixNH22awvGwrvqBsZu89yxgjJnMveYophyYH7eoN4HI+oDvwjPMYupmP4LmFeQk gDEMJfb+KdsE2kV7kBzYgBvF3LqVpzaSp5R8hyW24j8rYiManIb3T6h3YvERaaf/129fuecii ZT9r0QLChEkg6I5967/gNN6LtCWkOxRayic2fLPXlSTOjfUpmmXQt63vKTtksoSuTzrfbVcPf 62JkJeO1XIhIkWndnoONDTsHlfhfTk6oNESppDLdgHoOiFX6op+QmXlSfZQcGYM1FcNUdmmNf Ahap+M0E8N4ZnYoDid/RR/zxC57BuiTwFM8fnlHHRmF3GT65Ogt1vN+mdy3DRE1mZL9jXYhz9 IyLEAdTCQzIID6TvjtytN2cZGzKNyVln7kR9HsgB7Aj8X5jP7Od1679JTtn4bk5TRzNCQTj95 /gDN+dPaDdpcHipZ4zyWi1BM0r12DuzufDBTY8l/cYdY6TFZruACmUjUHfW6I9WiBx+wYLrIR okzZKZKwo20Tl3ykUNNUHM/AItnxS+wg5+PNvdH05z2CwVfnXNCz0Z8Kq0beOJroWpTf3yLUH KF8nyljxj72NLtUhfQ/d8ASR1CCx9z8wMzsNUPHIxfCCS5Vv9Rj0DFKdvOr5ydrc/RSH+JmHo jw5WkFfvgTclm8OETIvnM2CMmPP5TH7Qkpd/I+xrfXp28MvupXZ9dqGOjJXkJlArYNsyl9xOP DO+b/ncxcFMnUqmzEIBAbs5UdcQSW0waDHumZInM1AXJPUW5bMSGGLnQtLY= X-Mailman-Approved-At: Sun, 27 Nov 2016 12:35:50 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 27 Nov 2016 11:46:46 -0000 --Sig_/eIRlBuYrefrJmtsNWEQCL9q Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Fri, 25 Nov 2016 10:20:36 -0800 John Baldwin schrieb: > I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks > have been testing it for the last week or so which has exposed some=20 > additional things to fix. I think I've resolved most of those in one > way or another, but it will make things smoother if other folks can > start testing this over the next few days before it is enabled by default. >=20 > (To enable, add 'options EARLY_AP_STARTUP' to your kernel config.) >=20 > Note that non-x86 platforms should eventually adopt this, but I don't > think any of them are ready yet. >=20 I tried. I use three boxes, all running most recent CURRENT. Only one box d= oes work and boot with the option mentioned above in the kernel. The other two don't, th= ey stop at printing something about HPET timer initialisation and stop - forever. I did not digg deeper into it, but there is something strange: Both failing boxes have CPUs with two cores, four threads. One is a noteboo= k with an Haswell 4200M, the other is a i3-3220. The i3-3220 box has a motherboard ASROCK Z77-Pro4 (UEFI on this crap is not= working), 8 GB RAM (2x 4GB), lates firmware from 2013.=20 The working box has an ASROCK Z77-Pro4 M (mini ATX size mobo), 16 GB RAM (2= x 8GB), but a 4 core/8 thread XEON IvyBridge E3-1245 V2. The firmare is the latest, from = 2013. The box is running well with the option EARLY_AP_STARTUP set.=20 At a first glance it looks like the failure is dependend on the CPU count ;= -) I have also a small PCengine APU 2C4, AMD Jaguar CPU with 4 core/4 threads which is abo= ut to be tested also with the most recent CURRENT and the option in question set - but it t= akes time. Just for the record, my apologizes if someone feels disturbed from naive ob= servations. Kind regards, oh --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/eIRlBuYrefrJmtsNWEQCL9q Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWDrHlwAKCRDS528fyFhY lHj1Af4r9LX/SFMfm2WcXtn/KbOX5icSgwJHrR2u4796ydR47OcjNtRRlgkLZQMn yDgtAKPyUlgysqfCd+aHM18ZywmsAf94P2FLh7T4pRPaC90mGEQ649dzD7noSuC+ ocEdFx9xrO8Kt7HKO/Tu+wheUtS5jMvs23tYVXtHMBaZU7O6cSEq =hvnj -----END PGP SIGNATURE----- --Sig_/eIRlBuYrefrJmtsNWEQCL9q--