From owner-freebsd-current@freebsd.org Thu Jan 19 06:50:11 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 6DD66CB7F69 for ; Thu, 19 Jan 2017 06:50:11 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (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 2F75511E5; Thu, 19 Jan 2017 06:50:10 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id U6XpcaH1pBSTMU6XqcBhJF; Wed, 18 Jan 2017 23:50:03 -0700 X-Authority-Analysis: v=2.2 cv=MKYQoIRl 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=XAmG3Ujv1MT0TMYk14QA:9 a=CjuIK1q_8ugA:10 a=mFeOnlTyF09QQMGr2mMI:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id E39DB816; Wed, 18 Jan 2017 22:50:00 -0800 (PST) Received: from slippy (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id v0J6nxrs014131; Wed, 18 Jan 2017 22:49:59 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201701190649.v0J6nxrs014131@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: John Baldwin cc: Cy Schubert , Hans Petter Selasky , FreeBSD Current , Konstantin Belousov Subject: Re: Strange issue after early AP startup In-Reply-To: Message from John Baldwin of "Tue, 17 Jan 2017 17:20:48 -0800." <1922021.4HJeqFJ74r@ralph.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Jan 2017 22:49:59 -0800 X-CMAE-Envelope: MS4wfKoa5jp3BRPuEqIgBRl3tOPTqtWrgFC5Xmcm69LFrt8t1pK2HQWMi301mh1m5Tq1YmaQulBYc8/nIGqkPS0IxJz++5FIg4sEm75irMPaYwdLaV9sbbtZ AaO6CSq9WmF4xDSPIHyGO0CEBq8pScsFygzmTko0cBkvtbcNjmWyT+p846M4E3FtXjBjEZYgWKXAW6ptMtR/VokRessE/fgh9gXS3aEnqQsZ9GIPtnlRomlO hMPDqb5wfQ2p8J2zLh0npc5K2GckOnAyrxJ12PORGZU= 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, 19 Jan 2017 06:50:11 -0000 In message <1922021.4HJeqFJ74r@ralph.baldwin.cx>, John Baldwin writes: > On Tuesday, January 17, 2017 05:08:58 PM Cy Schubert wrote: > > In message <1492450.XZfNz8zFfg@ralph.baldwin.cx>, John Baldwin writes: > > > On Tuesday, January 17, 2017 12:53:19 PM Cy Schubert wrote: > > > > In message , Hans Pet > ter > > > > 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 w > ith > > > > early AP startup. It affects one of my four machines, my laptop. My thr > ee > > > > 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 > > > > > > So it panics and reboots after this? > > > > Yes, it goes into a panic/reboot loop for a few iterations until it > > successfully boots. Disabling early AP startup allows it to boot up without > > > the assumed race. > > Can you add DDB to the kernel config (and remove DDB_UNATTENDED) to get it > to break into DDB when it panics to get the panic message (and a stack trace > as well)? I found and fixed the problem. It was in some code I had added a long time ago but not committed yet to the bge driver to implement WOL. It was a lock assertion. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.