From owner-freebsd-current@freebsd.org Sun Nov 27 17:19:11 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 13005C590B5 for ; Sun, 27 Nov 2016 17:19:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F35C483C for ; Sun, 27 Nov 2016 17:19:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EFEB3C590B4; Sun, 27 Nov 2016 17:19:10 +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 EDEB5C590B3 for ; Sun, 27 Nov 2016 17:19:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C2A7E83A for ; Sun, 27 Nov 2016 17:19:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id E92D610A729; Sun, 27 Nov 2016 12:19:01 -0500 (EST) From: John Baldwin To: "O. Hartmann" Cc: current@freebsd.org Subject: Re: Please test EARLY_AP_STARTUP Date: Sun, 27 Nov 2016 09:18:46 -0800 Message-ID: <2030105.iquFVMheHd@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: <20161127124631.1e4f1fb0@thor.walstatt.dynvpn.de> References: <7005233.xZtqgRZ2t6@ralph.baldwin.cx> <20161127124631.1e4f1fb0@thor.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Sun, 27 Nov 2016 12:19:02 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean 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 17:19:11 -0000 On Sunday, November 27, 2016 12:46:31 PM O. Hartmann wrote: > 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 > > 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. > > > > (To enable, add 'options EARLY_AP_STARTUP' to your kernel config.) > > > > Note that non-x86 platforms should eventually adopt this, but I don't > > think any of them are ready yet. > > > > I tried. I use three boxes, all running most recent CURRENT. Only one box does work and > boot with the option mentioned above in the kernel. The other two don't, they 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 notebook 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. > > The working box has an ASROCK Z77-Pro4 M (mini ATX size mobo), 16 GB RAM (2x 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. > > 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 about to be tested > also with the most recent CURRENT and the option in question set - but it takes time. > > Just for the record, my apologizes if someone feels disturbed from naive observations. Some things to help debug: - See if you can break into the debugger via Ctrl-Alt-Esc. If so, please grab the output of 'ps' and 'tr 0' from DDB. - Boot with SMP disabled (kern.smp.disabled=1). This isn't a permament solution but can help narrow down the issue. - Compile a kernel with KTR, KTR_COMPILE=KTR_PROC, KTR_VERBOSE, and KTR_MASK=KTR_PROC (all are options) and boot. Hopefully it stops printing lines when it hangs rather than spinning forever. If so, grab a screen shot (or console serial log) when it hangs. -- John Baldwin