From owner-freebsd-current@freebsd.org Tue Jan 17 20:53:41 2017 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 64093CB46D2 for ; Tue, 17 Jan 2017 20:53:41 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 16F511830; Tue, 17 Jan 2017 20:53:40 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id Tal6cS5eaVQuxTal7ckOLH; Tue, 17 Jan 2017 13:53:39 -0700 X-Authority-Analysis: v=2.2 cv=BNTDlBYG c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=kj9zAlcOel0A:10 a=IgFoBzBjUZAA:10 a=ndaoGXS1AAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=XPXHXC5chYUayAn0q0QA:9 a=CjuIK1q_8ugA:10 a=mFeOnlTyF09QQMGr2mMI:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id 1DBD44A1; Tue, 17 Jan 2017 12:53:36 -0800 (PST) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id v0HKrJAS046364; Tue, 17 Jan 2017 12:53:19 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201701172053.v0HKrJAS046364@slippy.cwsent.com> X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Hans Petter Selasky cc: FreeBSD Current , John Baldwin , Konstantin Belousov Subject: Re: Strange issue after early AP startup In-Reply-To: Message from Hans Petter Selasky of "Mon, 16 Jan 2017 16:51:42 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Jan 2017 12:53:19 -0800 X-CMAE-Envelope: MS4wfBB9LjaDZuKi2KEcLAPEV4nZb7G7dH4iLC5Ekm0NeBUkORw+zpUQUw/71sr7zBkmFjK51R/6AgNptrffObq9Q/TqZh0NOFAaTGSHcQ7Y0/u0gew8KgGM cAwBak74jdpqVY6mIkVjZCw7zl6srOLnmrzzEdNqjrttg/UlA44VtjwMGmjvSyUeTPWxvES70btYuyRyeR/r5kqhDaYP8eFwNBbUCSLmTkrDo3VCbuSnUO1W wOOs5+c0gxCR2U3fxjLypO5WelkvuXKTeKcRU3Mqhg8= 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: Tue, 17 Jan 2017 20:53:41 -0000 In message , Hans Petter Sela sky writes: > Hi, > > When booting I observe an additional 30-second delay after this print: > > > Timecounters tick every 1.000 msec > > ~30 second delay and boot continues like normal. > > Checking "vmstat -i" reveals that some timers have been running loose. > > > cpu0:timer 44300 442 > > cpu1:timer 40561 404 > > cpu3:timer 48462822 483058 > > cpu2:timer 48477898 483209 > > Trying to add delays and/or prints around the Timecounters printout > makes the issue go away. Any ideas for debugging? > > Looks like a startup race to me. just picking a random email to reply to, I'm seeing a different issue with early AP startup. It affects one of my four machines, my laptop. My three server systems downstairs have no problem however my laptop will reboot repeatedly at: Jan 17 11:55:16 slippy kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed Then finally boot after a number of reboots (0-N), it finally boots. Disabling early AP start allows it to boot past that point first time. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.