From owner-freebsd-current@freebsd.org Mon Nov 28 18:27:56 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 8B4B3C59600 for ; Mon, 28 Nov 2016 18:27:56 +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 770FC139F for ; Mon, 28 Nov 2016 18:27:56 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 73BC1C595FF; Mon, 28 Nov 2016 18:27:56 +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 71C8AC595FE for ; Mon, 28 Nov 2016 18:27:56 +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 45A0F139D for ; Mon, 28 Nov 2016 18:27:55 +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 407C910A80C; Mon, 28 Nov 2016 13:27:54 -0500 (EST) From: John Baldwin To: Sepherosa Ziehau Cc: "freebsd-current@freebsd.org" Subject: Re: Please test EARLY_AP_STARTUP Date: Mon, 28 Nov 2016 10:27:40 -0800 Message-ID: <5196546.NF2ntCjvkx@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: References: <7005233.xZtqgRZ2t6@ralph.baldwin.cx> 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); Mon, 28 Nov 2016 13:27:54 -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: Mon, 28 Nov 2016 18:27:56 -0000 On Monday, November 28, 2016 02:35:07 PM Sepherosa Ziehau wrote: > Hi John, > > fdc seems to cause panic on Hyper-V: > https://people.freebsd.org/~sephe/fdc_panic.png You shouldn't get this panic in latest HEAD (post-r309148). > I then commented out device fdc, and I fixed one panic on Hyper-V here: > https://reviews.freebsd.org/D8656 Replied to the review. > After fdc is disabled and hyperv/storvsc is fixed, it seems to boot > fine, except a long delay (28~30seconds) here: > .... > Timecounters tick every 1.000 msec > ----- > 28 ~ 30 seconds delay > ----- > vlan: initialized, using hash tables with chaining > .... > > I have the bootverbose dmesg here: > https://people.freebsd.org/~sephe/dmesg_earlyap.txt > > I booted 10 times, only one boot does not suffer this 30 seconds > delay. It sounds like some races to me. Any hints? It is likely a race as we start running things sooner now, yes. Can you break into DDB during the hang and see what thread0 is waiting on? If it is in the interrupt hooks you can use 'show conifhk' in DDB to see the list of pending interrupt hooks. That provides a list of candidate drivers to inspect (e.g. stack traces of relevant kthreads) for what is actually waiting (and what it is waiting on) -- John Baldwin