From owner-freebsd-current@freebsd.org Thu Dec 1 05:53:31 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 99B64C61E33 for ; Thu, 1 Dec 2016 05:53:31 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 796041873 for ; Thu, 1 Dec 2016 05:53:31 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 78C71C61E2F; Thu, 1 Dec 2016 05:53:31 +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 786F4C61E2D for ; Thu, 1 Dec 2016 05:53:31 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 32DF71870; Thu, 1 Dec 2016 05:53:31 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-ua0-x232.google.com with SMTP id 51so237499297uai.1; Wed, 30 Nov 2016 21:53:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xwQZm19FX/K5iW14t6/PTscYROZZphALqvTRiw/KfDY=; b=M4hp/vOFI0o1oeJ1/xEVzRPDD/8n/5e5TGyozyrMNObDuqxymuhoRRp7NnE0XE/qBj 0J2AqbYmcwxSxUyiOkzQ/AQqzvITxVBr+b4AEoZ+l7jpa7ZWL6NVrMAngO4XsqFo1GjY +hKSnbCawNQ/eS3uCJIsv/5RviPjPDvyiWU2x/MjxvNI1spfI0HbUYzPorHnDIPzYUqF jd/NXVIFpGKBQdIy5ChZJIaW2aVvsZyLTPRACfOKugiO4/nE2y1QbKJPvEMWGwViDl07 KlsA2Xu2VLdub38G1JLUB0Cq8oqhrHfLZCdDj3YxJTmeKVoD3gUyLrdv1CsEkFkGOH5G ECUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xwQZm19FX/K5iW14t6/PTscYROZZphALqvTRiw/KfDY=; b=m+axzd4JZyBLOgs0bz2uM582yk+jpfnSpQNkpiaLKe407YQgU2mtNC0Dff+9+K6NqJ WX55zzrbwut83ALdJssZNmRvYT8J3CxgSB2X2aFkzMIUkOi4OQJAZ1zLoGKInFjgTqn6 jkAuF7YhSTuStsRC+BmW2eF8dhAfv2zLfogMBDX0/ULbntQG0JfcG27WhLRcw9yqf+6M JISkTN7IdHvGirpMSkbMnozRG/ORQ6CnOLkv9R34AFglORMdQta1/rZgMByfFs2UYWNn 1zPfGXgLX6LC6jt0X0G4cIWfVVtMI/ZC0D5yoVr4QmLpEXMMOjeZaISXQOCDcl09sdPT sjcw== X-Gm-Message-State: AKaTC00oT9ljCc4NkpcNEX5F/Xz/OUBB8UgmNWzHsWhEaEtlV6w/g9D1yOg186J+RZHO7wInoPa7oSFQEaoG0w== X-Received: by 10.176.65.167 with SMTP id 36mr17302744uap.175.1480571610016; Wed, 30 Nov 2016 21:53:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.5.198 with HTTP; Wed, 30 Nov 2016 21:53:29 -0800 (PST) In-Reply-To: References: <7005233.xZtqgRZ2t6@ralph.baldwin.cx> <5196546.NF2ntCjvkx@ralph.baldwin.cx> From: Sepherosa Ziehau Date: Thu, 1 Dec 2016 13:53:29 +0800 Message-ID: Subject: Re: Please test EARLY_AP_STARTUP To: John Baldwin Cc: "freebsd-current@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Thu, 01 Dec 2016 05:53:31 -0000 On Wed, Nov 30, 2016 at 9:59 AM, Sepherosa Ziehau wrote: > On Tue, Nov 29, 2016 at 2:27 AM, John Baldwin wrote: >> 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). > > > The base of my kernel tree is ~20 days old :) > > >> >>> 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) > > Just tried, but I failed to break into DDB during the 30 seconds > delay. DDB was entered after the 30 seconds delay, though I press the > break key when the delay started. I tried add VERBOSE_SYSINIT option in order to get a rough location of this delay, but the system boots just fine w/ VERBOSE_SYSINIT option, sigh. Thanks, sephe -- Tomorrow Will Never Die