From owner-freebsd-current@freebsd.org Wed Nov 30 01:59:29 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 978D8C5C658 for ; Wed, 30 Nov 2016 01:59:29 +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 7877A1A51 for ; Wed, 30 Nov 2016 01:59:29 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 74BFEC5C657; Wed, 30 Nov 2016 01:59:29 +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 7464EC5C656 for ; Wed, 30 Nov 2016 01:59:29 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (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 2FEC81A50; Wed, 30 Nov 2016 01:59:29 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-ua0-x233.google.com with SMTP id 12so198778526uas.2; Tue, 29 Nov 2016 17:59:29 -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=kmo99RtiWecDjd1khG7kI4Mr46lrDmfqfb1AfHQtTz0=; b=umY3WJYIHxihMOOxwGrtLSa/teCAXJ2PrBtga9T3wKaM+LlM07RrKfj/+VWeqNAq1l +zGsnVc3J16vKKd26+6qRI5Y8HouRndnMQMUkBZQ1eFHJ5KwO1KswGbsBHQ/hKx0bL47 EylXXtADGbDRWz4xOBh0+R4TRffyGPcrlqxxaEtptG/JK6TnEUZruHylxCuYs88LVMSL aUgJkyh2y9LaiUqjQxpAVEnQNA4WnkvAV4udOpVKuyTSTjtFe9HFiu6Et9wY87FGtxZL Yqn2sppf5Gl7sPc+2dutUaOsGiDEi9MKUck75Hr8ZOkmX9+4sffyld3k8r2fHGexff+q pO6Q== 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=kmo99RtiWecDjd1khG7kI4Mr46lrDmfqfb1AfHQtTz0=; b=iND+Er1vpWHlccTTYwH49mxYTAkCV222g2TXNpLhq1YQhHVgudhDUbRQN/m8qiYTZ2 P1hi9PZ8rt18L0OkAQ5pPUuQMhGhsrQYwoIWHc75nsTnyr8PXtI3D7MEZz6651sXc7Ks lcOn6dTufV+22rDxB3fsEUBL6SFABAS/X9Y06MmVIDh0dumGDRTxUdhDgvY1PRmbYGcS c7T7j+RKYq1JTyxU+95HLhChJ2HWisnnQwsHUNS5YA3BfTkaT0LhZyqe2v23nivStMip VVp1CwTmoeADqjh8HgOXQ5NrSfPh8Y1unLOA9Xh4zcagjfzuUfVUS1tu1KOVSddHLZV6 Zj3A== X-Gm-Message-State: AKaTC00V2o9xUSp/Ew+GAayEpF/7Vqbtve2tRPiPAWBY+yWG8DoZVvIFDmvEB9UW39ilhHB0mba27omRRPBSqg== X-Received: by 10.159.49.11 with SMTP id m11mr24118889uab.178.1480471167931; Tue, 29 Nov 2016 17:59:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.5.198 with HTTP; Tue, 29 Nov 2016 17:59:27 -0800 (PST) In-Reply-To: <5196546.NF2ntCjvkx@ralph.baldwin.cx> References: <7005233.xZtqgRZ2t6@ralph.baldwin.cx> <5196546.NF2ntCjvkx@ralph.baldwin.cx> From: Sepherosa Ziehau Date: Wed, 30 Nov 2016 09:59:27 +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: Wed, 30 Nov 2016 01:59:29 -0000 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. Thanks, sephe -- Tomorrow Will Never Die