From owner-freebsd-questions@freebsd.org Thu Dec 24 06:52:27 2015 Return-Path: Delivered-To: freebsd-questions@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 6794AA504F5 for ; Thu, 24 Dec 2015 06:52:27 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB7441452; Thu, 24 Dec 2015 06:52:26 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id tBO6qFSW097139; Thu, 24 Dec 2015 17:52:16 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Thu, 24 Dec 2015 17:52:15 +1100 (EST) From: Ian Smith To: Vijay Rjah cc: freebsd-questions@freebsd.org, Ed Maste Subject: Re: Need help with New Build -- Skylake In-Reply-To: Message-ID: <20151224173146.H8562@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2015 06:52:27 -0000 In freebsd-questions Digest, Vol 603, Issue 5, Message: 5 On Wed, 23 Dec 2015 23:20:54 +0530 Vijay Rjah wrote: > On 12/23/15 2:29 AM, Ed Maste wrote: > > On 22 December 2015 at 12:39, Vijay Rjah wrote: > >> The only issue i have is that the boot process takes a lot of time.. > >> (similar to > >> https://forums.freebsd.org/threads/new-motherboard-and-processor-kernel-load-very-slow.53511/ > >> ). the system ultimately boots, but boot times are around 4 - 5 Mins.. > >> > >> How do I debug it? any suggestions? > > A useful first step is to get a verbose boot ("boot -v" from the > > loader prompt) and note where there are any large or unexpected > > delays. The "memory test" that was responsible for many reports of > > slow FreeBSD boots has been disabled in 11.x for quite some time, so > > it won't be that. > Thanks for your reply.. > > It takes about 3-4 Mins just to get to the boot option screen.. ( I mean > the menu where it lets you select multi/single user mode etc...) > > I have attached the output of "boot -v".. > > -Thanks > Vijay > -------------- next part -------------- > Dec 23 23:03:13 vrajah-bsd syslogd: kernel boot file is /boot/kernel/kernel Note the timestamp. You often can't rely on bootup timestamps as most of it has to be buffered until being reported somewhat later, as there's nowhere for syslog to write to, but in any case, everything else is logged at the same second until: > Dec 23 23:03:13 vrajah-bsd kernel: re0: link state changed to UP > Dec 23 23:03:13 vrajah-bsd ntpd[605]: ntpd 4.2.8p4-a (1): Starting > Dec 23 23:03:14 vrajah-bsd ntpd[606]: leapsecond file ('/etc/ntp/leap-seconds'): good hash signature > Dec 23 23:03:14 vrajah-bsd ntpd[606]: leapsecond file ('/etc/ntp/leap-seconds'): loaded, expire=2015-12-28T00:00:00Z last=2015-07-01T00:00:00Z ofs=36 > Dec 23 23:03:14 vrajah-bsd ntpd[606]: leapsecond file ('/etc/ntp/leap-seconds'): will expire in less than 5 days > Dec 23 23:03:14 vrajah-bsd sm-mta[643]: My unqualified host name (vrajah-bsd) unknown; sleeping for retry > Dec 23 23:04:12 vrajah-bsd sm-mta[643]: unable to qualify my own domain name (vrajah-bsd) -- using short name Where it waited for all but a minute .. > Dec 23 23:04:12 vrajah-bsd sm-msp-queue[646]: My unqualified host name (vrajah-bsd) unknown; sleeping for retry Then almost another minute, util you logged in and su'd .. > Dec 23 23:05:10 vrajah-bsd su: vrajah to root on /dev/pts/0 > Dec 23 23:05:12 vrajah-bsd sm-msp-queue[646]: unable to qualify my own domain name (vrajah-bsd) -- using short name So there's ~2 minutes delay there. sendmail (mta and msp both) at least are unhappy about your hostname, and sleep on it. I don't know whether that's significant or related to the longer delay you report. I just skimmed through your dmesg, but didn't spot anything glaringly obvious. FWIW, cheers, Ian