From owner-freebsd-bugs@FreeBSD.ORG Sun May 30 23:20:06 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91AE11065675 for ; Sun, 30 May 2010 23:20:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (unknown [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 678A18FC15 for ; Sun, 30 May 2010 23:20:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o4UNK6tC053131 for ; Sun, 30 May 2010 23:20:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o4UNK6MD053130; Sun, 30 May 2010 23:20:06 GMT (envelope-from gnats) Date: Sun, 30 May 2010 23:20:06 GMT Message-Id: <201005302320.o4UNK6MD053130@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Garrett Cooper Cc: Subject: Re: misc/147239: network problem with system start X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Garrett Cooper List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 May 2010 23:20:06 -0000 The following reply was made to PR misc/147239; it has been noted by GNATS. From: Garrett Cooper To: Andreas Schwarz Cc: freebsd-gnats-submit@freebsd.org, Jeremy Chadwick Subject: Re: misc/147239: network problem with system start Date: Sun, 30 May 2010 16:18:20 -0700 On Sun, May 30, 2010 at 3:06 PM, Andreas Schwarz wrote: > >>Number: =A0 =A0 =A0 =A0 147239 >>Category: =A0 =A0 =A0 misc >>Synopsis: =A0 =A0 =A0 network problem with system start >>Confidential: =A0 no >>Severity: =A0 =A0 =A0 critical >>Priority: =A0 =A0 =A0 medium >>Responsible: =A0 =A0freebsd-bugs >>State: =A0 =A0 =A0 =A0 =A0open >>Quarter: >>Keywords: >>Date-Required: >>Class: =A0 =A0 =A0 =A0 =A0sw-bug >>Submitter-Id: =A0 current-users >>Arrival-Date: =A0 Sun May 30 22:10:00 UTC 2010 >>Closed-Date: >>Last-Modified: >>Originator: =A0 =A0 Andreas Schwarz >>Release: =A0 =A0 =A0 =A08.1-PRERELEASE >>Organization: >>Environment: > FreeBSD tapir.schwarzes.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Sun= May 30 21:50:08 CEST 2010 =A0 =A0 root@tapir.schwarzes.net:/usr/obj/usr/sr= c/sys/tapir.schwarzes.net =A0amd64 >>Description: > After upgrade from 8.0-STABLE #0: (Fri Mar 26 21:58:46 CET 2010), > to 8.1-PRERELEASE something seems to be wrong with the network > startup. The network is not up when essential network daemons > are starting (like ntpd). This causes that they will not work > properly. I have to run manually "/etc/rc.d/ntpd restart". > > Have a look at the following part of the boot log, age0 link > state changed to up after the ntpdate/ntpd init is processed. > Compared to 8.0-STABLE the ntpdate/ntpd init is processed 3 > seconds (absolute from kernel log start) earlier, this makes > the difference. > > May 30 22:36:32 tapir ntpdate[633]: can't find host 0.freebsd.pool.ntp.or= g > May 30 22:36:32 tapir ntpdate[633]: can't find host 1.freebsd.pool.ntp.or= g > May 30 22:36:32 tapir ntpdate[633]: can't find host 2.freebsd.pool.ntp.or= g > May 30 22:36:32 tapir ntpdate[633]: no servers can be used, exiting > May 30 22:36:32 tapir ntpd[822]: ntpd 4.2.4p5-a (1) > May 30 22:36:32 tapir kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 > May 30 22:36:34 tapir ntpd_initres[830]: host name not found: 0.freebsd.p= ool.ntp.org > May 30 22:36:34 tapir ntpd_initres[830]: couldn't resolve `0.freebsd.pool= .ntp.org', giving up on it > May 30 22:36:34 tapir ntpd_initres[830]: host name not found: 1.freebsd.p= ool.ntp.org > May 30 22:36:34 tapir ntpd_initres[830]: couldn't resolve `1.freebsd.pool= .ntp.org', giving up on it > May 30 22:36:34 tapir ntpd_initres[830]: host name not found: 2.freebsd.p= ool.ntp.org > May 30 22:36:34 tapir ntpd_initres[830]: couldn't resolve `2.freebsd.pool= .ntp.org', giving up on it > May 30 22:36:34 tapir kernel: age0: link state changed to UP This issue has existed for some time now, but has only become more noticeable in 8.0+ with the rc script rework. koitsu@ had a proposal out a while back to hack around this problem, but I'm not sure what the status is on his work. Thanks, -Garrett