From owner-freebsd-current@freebsd.org Mon Nov 28 06:35:09 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 F1DF1C58031 for ; Mon, 28 Nov 2016 06:35:09 +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 D3AD51A50 for ; Mon, 28 Nov 2016 06:35:09 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D01FAC5802F; Mon, 28 Nov 2016 06:35:09 +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 CFC35C5802E for ; Mon, 28 Nov 2016 06:35:09 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::235]) (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 8C46E1A4F; Mon, 28 Nov 2016 06:35:09 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-ua0-x235.google.com with SMTP id 51so133152869uai.1; Sun, 27 Nov 2016 22:35:09 -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=Doe3qEWF0QUlL0OjD8BYFIV6hKWtPZOWHMwOzMLv47Q=; b=dcX1/LHTzMSHOLiO9gEj/bBzNpNDoPMd4YmltnLTAKImF8d2GVDtWkr/K83NY2x0uA S5RBisGMwoXe0CHYm0G3CbCQzhLzp5Zz+Qr3CZueSKIvp7m5C54KXHTdRA3kbjv8N2mP OgnBg2BHf+N8Mg7t8wOA3CAIaFLXDpjQ4hch8aoov2tw2TaqYc0eXxU8G/UUbHBzL/mx S6AdrIVDUps9NtPKiss6MwQYeKIAyjI0SkqtoS8H3FvrGvJtwx4xCW8X1J8yQuk8K5UT 93ZGAY4UHKWDmUSp8oFvIYtjgfM1l9mw/lmXuJ0ZAyQD4LPyNIINpvQC+F0HagSD0zL8 4umQ== 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=Doe3qEWF0QUlL0OjD8BYFIV6hKWtPZOWHMwOzMLv47Q=; b=VkSxKkatsaT3m4eN6+fv3+/qrA0SA6us+YuVZj8yNm7Qj0zNTAw0n03KeK1KBaXSLV Rj/JdQkota64EiTdtqGHW1KESwdzvnvqCKJ1VK3afgP+px+KwsgHUvrHYTatmHr0lakU aSPooSue5AuO6Ky/cYHHFNcT5M+XfszTrWEPSDThWBzPYD+TYqbcxElSko7RtQjCKgDE 81jnyBjg3HGtQl64eZfx/25pIep1ki3EkdXQERCOT6hPtNm8stGC4N/TpNsMeUIVMvSq RNd9LMOGg5B2lpqXh62QOTFSZ72uSg6hXRx/kUWLGcraTCRmpG+SQZmfxo09Ji6aREKk tu7g== X-Gm-Message-State: AKaTC00mItj8mcqWFFOO8yO+bFFZ1h7qg0z3zlsJ5cQPLyZN89B2r4ANwvGi2IYFOmgiI/RHbmM1ZKi1o85PXA== X-Received: by 10.159.55.168 with SMTP id q37mr15234186uaq.63.1480314908401; Sun, 27 Nov 2016 22:35:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.36.247 with HTTP; Sun, 27 Nov 2016 22:35:07 -0800 (PST) In-Reply-To: <7005233.xZtqgRZ2t6@ralph.baldwin.cx> References: <7005233.xZtqgRZ2t6@ralph.baldwin.cx> From: Sepherosa Ziehau Date: Mon, 28 Nov 2016 14:35:07 +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: Mon, 28 Nov 2016 06:35:10 -0000 Hi John, fdc seems to cause panic on Hyper-V: https://people.freebsd.org/~sephe/fdc_panic.png I then commented out device fdc, and I fixed one panic on Hyper-V here: https://reviews.freebsd.org/D8656 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? Thanks, sephe On Sat, Nov 26, 2016 at 2:20 AM, John Baldwin wrote: > 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. > > -- > John Baldwin > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Tomorrow Will Never Die