From nobody@FreeBSD.org  Sun May 30 22:06:40 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0779510656C9
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 30 May 2010 22:06:40 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id EAA518FC0C
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 30 May 2010 22:06:39 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o4UM6dcm083897
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 30 May 2010 22:06:39 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o4UM6dYI083896;
	Sun, 30 May 2010 22:06:39 GMT
	(envelope-from nobody)
Message-Id: <201005302206.o4UM6dYI083896@www.freebsd.org>
Date: Sun, 30 May 2010 22:06:39 GMT
From: Andreas Schwarz <freebsd.asc@schwarzes.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: network problem with system start
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         147239
>Category:       misc
>Synopsis:       network problem with system start
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun May 30 22:10:00 UTC 2010
>Closed-Date:    
>Last-Modified:  Tue Aug 10 23:20:01 UTC 2010
>Originator:     Andreas Schwarz
>Release:        8.1-PRERELEASE
>Organization:
>Environment:
FreeBSD tapir.schwarzes.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Sun May 30 21:50:08 CEST 2010     root@tapir.schwarzes.net:/usr/obj/usr/src/sys/tapir.schwarzes.net  amd64
>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.org
May 30 22:36:32 tapir ntpdate[633]: can't find host 1.freebsd.pool.ntp.org
May 30 22:36:32 tapir ntpdate[633]: can't find host 2.freebsd.pool.ntp.org
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.pool.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.pool.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.pool.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



>How-To-Repeat:
Reboot the system.
>Fix:


>Release-Note:
>Audit-Trail:

From: Garrett Cooper <yanefbsd@gmail.com>
To: Andreas Schwarz <freebsd.asc@schwarzes.net>
Cc: freebsd-gnats-submit@freebsd.org, Jeremy Chadwick <koitsu@freebsd.org>
Subject: Re: misc/147239: network problem with system start
Date: Sun, 30 May 2010 16:18:20 -0700

 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

From: Andreas Schwarz <freebsd.asc@schwarzes.net>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: misc/147239: network problem with system start
Date: Tue, 01 Jun 2010 11:13:13 +0100

 The ntpdate rc script requires NETWORKING. The question is,
 why is NETWORKING provided when NETWORKING is not possible?
 
 Al possible workaround is to add a "sleep 5" (depends on NIC) to 
 "/etc/rc.d/NETWORKING" (which provides NETWORKING).
 
 
 best regards
 Andreas
 

From: Andreas Schwarz <Andreas.Schwarz@schwarzes.net>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc:  
Subject: Re: misc/147239: network problem with system start
Date: Tue, 01 Jun 2010 11:01:32 +0100

 The ntpdate rc script requires NETWORKING. The question is,
 why is NETWORKING provided when NETWORKING is not possible?
 
 Al possible workaround is to add a "sleep 5" (depends on NIC) to 
 "/etc/rc.d/NETWORKING" (which provides NETWORKING).
 
 
 best regards
 Andreas
 
 

From: Garrett Cooper <yanefbsd@gmail.com>
To: Andreas Schwarz <Andreas.Schwarz@schwarzes.net>
Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org
Subject: Re: misc/147239: network problem with system start
Date: Tue, 1 Jun 2010 08:47:27 -0700

 On Tue, Jun 1, 2010 at 3:01 AM, Andreas Schwarz
 <Andreas.Schwarz@schwarzes.net> wrote:
 >
 > The ntpdate rc script requires NETWORKING. The question is,
 > why is NETWORKING provided when NETWORKING is not possible?
 >
 > Al possible workaround is to add a "sleep 5" (depends on NIC) to
 > "/etc/rc.d/NETWORKING" (which provides NETWORKING).
 
 That's a hack at best as not all links are usable after 5 seconds.
 -Garrett

From: Andreas Schwarz <Andreas.Schwarz@schwarzes.net>
To: bug-followup@FreeBSD.org
Cc:  
Subject: Re: misc/147239: network problem with system start
Date: Wed, 11 Aug 2010 00:38:53 +0100

 MIME-Version: 1.0
 Content-Type: text/plain
 
 
 Unfortunately, with 8.1-STABLE the problem is still there. 8(
 
 best regards,
 Andreas
 
 
>Unformatted:
